Anti-ATS Evaluatorv1.3

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5-mini] Candidate brings strong foundational Python/SQL and RAG/LLM experience relevant to a Databricks-focused role, but lacks explicit Databricks/Unity Catalog/MLflow hands-on experience required by the JD. Score reflects transferable skills (ML/LLM, vector search) but penalties for missing the platform-specific items. Improve chances by completing a Databricks/MLflow project and surfacing it (or listing migrations and Delta Lake/dbt work). **Strengths:** Experience with LLMs, RAG, and embedding/vector search, Python data engineering and pipeline skills, Production system design and constraint-based engineering **Missing Required:** Databricks expertise (preferred/required)

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5-mini] Candidate has relevant AI/data platform architecture and Python/SQL skills but lacks explicit Apache Iceberg, Kubernetes/EKS, MCP and PySpark expertise required for the Principal role; local Sao Paulo location is a plus. Score gives weight to leadership, AI data work, and migration experience but major deductions for missing specific enterprise technologies. To improve, surface any Kubernetes/EKS, Iceberg, or Snowflake-to-Iceberg migration experience and emphasize local presence and mentorship experience. **Strengths:** Systems architecture and AI/RAG pipeline experience, Data pipeline design and migration thinking, Local Sao Paulo presence and leadership experience **Missing Required:** Deep Apache Iceberg and MCP experience, Kubernetes/EKS operational experience

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] The ATS sees strong alignment on Python, ETL-like pipelines, data quality, and AI/analytics-oriented systems, but detects gaps around explicit Azure Storage experience and a formal Data Engineer title. Inferred skills from the job intelligence platform, ERP data remediation, and trading systems show the person can design, monitor, and maintain data workflows, yet the lack of Azure and SQL Server/Oracle keywords drags the score down and triggers caps on missing required skills. To improve for this JD, the person should explicitly frame past work as 'Data Engineering' (including years), add concrete Python/OOP, ETL, and SQL bullets, and, if possible, include any Azure hands-on work (even small projects) plus mention of Microsoft SQL Server/Oracle exposure. **Strengths:** Proven Python, SQL, and automation skills building production data and AI pipelines (job intelligence platform, ERP remediation, trading systems)., Strong track record of data integrity, validation logic, and monitoring for operational reliability at scale., Systems-thinking profile that bridges business requirements and technical implementation for analytics and automation. **Missing Required:** 4+ years professional experience explicitly titled as a Data Engineer, Hands-on experience with Azure Storage / Azure cloud data solutions

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The candidate is an excellent semantic match: strong Python, extensive experience building and operating IA/LLM pipelines, data preparation and scoring, and integrating models via APIs into real products, plus solid data modeling and pipeline design. The main gap is limited explicit experience with classical ML frameworks like TensorFlow/PyTorch/scikit-learn, as the profile is more LLM/RAG/GenAI-centric than traditional supervised modeling, but this is partially offset by depth in modern IA. To improve, the candidate should surface any past classical ML work (even small projects), explicitly mention at least one ML library, and highlight interest in personalization/education if present. **Strengths:** Deep hands-on experience with LLMs, APIs and GenAI, including RAG and embedding-based search, End-to-end pipeline design from data collection and cleaning through scoring and deployment, Strong ability to integrate IA into real products with attention to performance and cost

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The candidate strongly matches OpenAI/LLM usage, prompt engineering, Python and solution architecture/integration, and has a clear focus on security, constraints and governance thinking, which are central to this role. The biggest gaps are Microsoft Copilot Studio, Power Apps/Power Automate and Databricks/Medallion-specific experience, which are not mentioned and will cap the ATS score despite the strong IA alignment. To improve, the candidate should self-initiate a small Copilot/Power Platform project, mention any Microsoft ecosystem exposure, and explicitly describe data architecture work in terms that mirror Medallion and Databricks concepts. **Strengths:** Deep hands-on LLM and prompt engineering expertise across multiple providers, Proven track record designing and deploying IA solutions under tight infrastructure constraints, Strong architectural mindset with emphasis on security, reliability and cost optimization **Missing Required:** Microsoft Copilot Studio, Power Apps, Power Automate, Python on Databricks and Medallion-style data architecture

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Candidate shows strong general infra/systems ability (Linux, Docker, CI/CD mindset, cost optimization, production shipping) and can code in Go/JS, but the JD’s core requirement is 6+ years of hands-on GCP + IaC + GKE, which is not demonstrated. Professional Services + enterprise GCP architecture experience is also not evidenced at customer scale. To improve ATS: explicitly add any real GCP project work (services used, migrations, IAM/VPC), Terraform examples, and quantified production reliability/incident ownership. **Strengths:** Go systems engineering, Linux/Docker/automation, Cost-optimization mindset (FinOps-adjacent) **Missing Required:** 6+ years GCP infrastructure, IaC (Terraform or equivalent), GKE container orchestration experience

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The ATS will see a strong match on systems design, ERP experience (including deep work with TOTVS) and business-domain knowledge in finance and operations, which align closely with the responsibilities of designing and improving complex systems and supporting administrative areas. The main gap is lack of explicit IT service management/ITIL-style language and day-to-day IT operations wording, even though the Candidate has run production infrastructure for an e-commerce and a market-intelligence platform. To improve for this JD, the Candidate should foreground ERP governance projects, monitoring/administration of services, cost control of TI, and explicitly label that experience as "Administração de Serviços de TI / ITIL-like" in the resume. **Strengths:** Deep ERP (TOTVS) and administrative domain experience in finance and supply chain, Proven track record designing and automating complex business systems end-to-end, Strong bridge between business stakeholders and technical implementation

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] The JD is highly focused on FPGA/VHDL and embedded C for microcontrollers, none of which appear explicitly in the Candidate’s recent work history. While the Mechatronics degree suggests some exposure to embedded concepts, the practical experience shown is mostly in backend systems, automation and AI infrastructure, which ATS will treat as a different domain. To be competitive here, the Candidate would need concrete projects with VHDL/Verilog, FPGA boards and embedded C firmware, clearly spelled out with toolchains (Quartus/Vivado) and validation flows. **Strengths:** Mechatronics engineering background aligned with embedded and control concepts, Solid programming foundations in Go, Python and JavaScript, Experience designing reliable automated systems and data pipelines **Critical Gaps:** Hands-on FPGA/VHDL design for embedded systems, Professional embedded firmware development experience **Missing Required:** Experience with FPGA projects in VHDL or Verilog, Programming microcontrollers in C

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.2] Candidate demonstrates strong systems thinking (custom orchestrator, reliability concepts, state persistence) and production delivery in Go/SQL, which maps to distributed-systems fundamentals. However the JD hard-emphasizes 5+ years professional data engineering + 2+ years leading teams of 5+ and enterprise-level distributed systems at scale, which are not clearly demonstrated. To improve ATS: reframe recent work as “backend/distributed systems,” add scale metrics (throughput, latency, uptime), and any direct team leadership scope (reports, hiring, reviews). **Strengths:** Production-grade Go systems design, Automation/orchestration with state machines & watchdog concepts, Cross-domain architecture and stakeholder translation **Missing Required:** 5+ years professional data engineering experience, 2+ years leading teams of 5+ engineers, Multiple full project lifecycles (explicitly evidenced)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] This role demands deep Siemens PLC, Sinamics drives and WinCC SCADA expertise in crane systems, which are not present on the resume. The Candidate has control/automation foundations and experience automating operations, but ATS will not treat that as equivalent to Siemens PLC/SCADA in heavy crane environments. Improving for this JD would require concrete projects with Siemens PLCs, WinCC, Sinamics and crane/hoisting systems, all explicitly named. **Strengths:** Control and automation fundamentals from a Mechatronics degree, Experience automating complex operational workflows and inventories, Ability to deliver technical training and explain systems to non-technical stakeholders **Critical Gaps:** Industrial cranes/hoisting equipment domain experience, Siemens PLC and WinCC ecosystem expertise **Missing Required:** PLC software development experience, Knowledge of automation and drives Siemens stack

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] The JD explicitly requires advanced PCS 7 experience plus CREA and CNH B, which are not present on the resume, and PCS 7 is a core technology rather than a nice-to-have. This triggers ATS hard filters tied to legal/professional credentials in Brazil and a very specific Siemens automation stack. No realistic resume adjustment can compensate for missing PCS 7 and CREA for this type of industrial engineering role. **Strengths:** Strong systems thinking and automation background in other domains, Experience coordinating technical stakeholders and projects, Fluent English for interacting with global engineering teams **Critical Gaps:** PCS 7 ecosystem expertise, Industrial automation leadership for large automotive plants **Missing Required:** CREA professional engineering registration, CNH B driver's license, Advanced PCS 7 experience

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] The Candidate matches well on Linux, scripting (Python/Bash) and automation, but lacks direct 4G/5G core network, OpenStack and telecom KPI experience that are central to this JD. ATS will give credit for systems and scripting, yet penalize the absence of mobile core platforms and network analysis tools. To improve, the resume should highlight any networking, virtualized infrastructure, monitoring and troubleshooting work, and ideally add concrete telecom or networking side projects (traces, packet analysis, basic OpenStack/K8s exposure). **Strengths:** Strong Linux and scripting skills (Python/Bash) suitable for automation and operations, Proven automation of production systems and monitoring of live platforms, Solid understanding of systems and infrastructure operations from e-commerce and AI tooling **Missing Required:** Direct experience with 4G/5G core data network operations, OpenStack or equivalent NFV/virtualization stack exposure

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] The JD is AAA multiplayer game systems with Unreal and multiple shipped titles; Candidate’s experience is systems/automation and web/infrastructure, not game development. This is a domain-critical mismatch, so ATS will rank it near the bottom even with transferable networking/data skills. To improve (only if genuinely true): add Unreal projects, shipped titles, and real-time multiplayer gameplay system experience. **Strengths:** Systems architecture mindset, Automation/tooling orientation, Data schema/design experience (non-game) **Critical Gaps:** AAA game development + Unreal + shipped titles required; experience is in automation/infrastructure instead **Missing Required:** Direct Unreal Engine experience, Multiple shipped titles, AAA multiplayer gameplay systems experience

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] The Candidate aligns with the need for complex systems design, fault-tolerant architectures and systems administration, but lacks explicit aeronautical and real-time embedded flight systems experience. ATS will recognize engineering degrees, systems architecture and automation as relevant, but will not see aerospace-specific tools or standards. To improve, the resume would need explicit references to real-time control, safety-critical systems, and any use of systems-engineering tools or methodologies common in aerospace. **Strengths:** Strong background designing complex automated systems and orchestrators, Mechatronics degree with control systems and robotics focus, Experience architecting reliable, redundant backend services on constrained infrastructure **Missing Required:** Experience with tools and software specific to systems engineering in aerospace

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] This role mandates solid Simatic Step 7 Classic/Siemens PLC experience, Profibus/Profinet networks, WinCC Flexible and requires CREA and CNH B, none of which appear in the Candidate’s profile. These are non-negotiable requirements for industrial automation engineering roles in Brazil and are also likely tied to legal and safety responsibilities. Without Siemens PLC/SCADA background and the required registrations, the ATS will hard-reject. **Strengths:** Mechatronics degree aligned with industrial systems concepts, Experience leading technical initiatives and coordinating stakeholders, Strong systems-thinking and automation mindset in other domains **Critical Gaps:** Industrial PLC/SCADA project leadership experience, Siemens automation stack expertise **Missing Required:** CREA professional engineering registration, CNH B driver's license, Solid experience with Simatic Step 7 Classic and related Siemens tools

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] This role requires aerospace systems engineering standards (ARP-4754/ARP-4761) and regulatory/certification experience, plus CREA registration eligibility. None of those required aerospace certification signals are present in the resume, so screening fails before skill transferability matters. To improve only if applicable: add explicit ARP/FAA/EASA work, certification artifacts, and CREA registration status. **Strengths:** Engineering degree (general), Systems thinking (non-aerospace), Requirements/constraints mindset (general) **Critical Gaps:** Regulatory/certification aerospace systems domain is required and not evidenced **Missing Required:** CREA registration/eligibility, ARP-4754/ARP-4761 experience, Aerospace regulatory/certification experience

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.2] Candidate is unusually aligned on integrations: OAuth2/OIDC, production scraping/orchestration, APIs/data models, and shipping a full product under tight constraints. The main gaps are “SaaS multi-tenant foundations” and “analytics dashboards/tool observability” being implied but not clearly demonstrated as product features. To improve ATS: explicitly describe multi-tenant/permissions patterns implemented, webhook/rate-limit handling, and integration connector semantics (sync, idempotency, retries). **Strengths:** OAuth2/OIDC + integration comfort, Proven end-to-end product shipping (backend+ops+frontend), AI-assisted engineering fluency with strong validation discipline

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Candidate is strong in systems building and AI tool usage, but the JD is narrowly about deep Codex-first workflows and letting AI generate most implementation code, which conflicts with the stated “review every line” approach. It also calls for 5+ years professional software development experience, which ATS may interpret as missing due to non-standard titles. To improve ATS: if true, add explicit Codex-led multi-file delivery examples, and present roles/projects under a clear “Software Engineer” framing with dates and shipped outcomes. **Strengths:** Context/specification engineering mindset, Full-stack + infra comfort, AI pipeline design and systematic variance reduction **Critical Gaps:** JD expects AI-generated majority code workflow; candidate explicitly positions as not accepting AI code without heavy review **Missing Required:** 5+ years professional software development experience (explicitly evidenced), Deep Codex workflow experience (explicit)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] While the Candidate is very strong in Python, relational databases, Docker, CI/CD and security (OAuth2/OIDC), this JD lists a long set of "imprescindíveis" around Celery, API Gateways, Kubernetes/Openshift, NoSQL, observability/OpenTelemetry, Kafka/RabbitMQ, SRE/FinOps and chaos engineering that do not appear. ATS will match on core Python/backend blocks but heavily penalize these missing production SRE/microservices tools. To improve, the Candidate would need documented experience (or high-signal projects) using at least some of Celery, API gateways, Kubernetes, Kafka and modern observability stacks. **Strengths:** Strong Python background with production-grade automation and tooling, Experience with relational databases and infrastructure optimization on constrained hardware, Solid grounding in Docker, CI/CD and security (OAuth2/OIDC) **Missing Required:** Experience building Python microservices with Celery, Hands-on Kubernetes/Openshift container orchestration, Production observability and OpenTelemetry experience

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.2] Candidate matches the role’s core shape: designing scalable systems/APIs, strong SQL/Postgres familiarity, and translating customer pain into technical delivery. The main ATS weakness is the non-traditional job titles and limited explicit “software engineer on product team” tenure signals. To improve ATS: move “Job Intelligence Platform” into a clearly labeled Software Engineering Experience section with API endpoints, auth, deployment, and reliability metrics. **Strengths:** API/system design + production shipping, SQL/Postgres + data architecture mindset, Business-technical translation (product engineering fit)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] This is a .NET/C# role with explicit seniority and long tenure requirements; Candidate’s resume centers on Go/JS/Python rather than C#/.NET Core. The required C# depth and “8+ years as a Software Engineer” filter will dominate ATS ranking. To improve ATS: only apply if there is real C#/.NET history to add (projects, years, .NET Core, EF, performance work). **Strengths:** SQL/database familiarity (general), Systems thinking and refactoring mindset, Remote async communication (likely) **Critical Gaps:** Primary stack is C#/.NET Core with 5+ years required; not evidenced **Missing Required:** 5+ years C#/.NET Core, 8+ years as Software Engineer, Data-intensive high-volume product experience (explicit)

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The Candidate matches strongly on JavaScript/Node.js, REST API integrations, LLM-based conversational systems and project/requirements work with stakeholders. The main gaps are explicit TypeScript, named chatbot platforms and agile tooling like Jira, which are relatively minor compared to the demonstrated experience building LLM-powered systems, scrapers, orchestrators and client-facing automation. To improve, the resume should explicitly mention TypeScript (if used), detail any chatbot-like flows built with LLMs and highlight experience managing project scope, timelines and client communication. **Strengths:** Strong JavaScript/Node.js experience including production web and automation systems, Deep experience integrating REST APIs and orchestrating services with LLMs, Proven ability to interface with stakeholders and manage scope and delivery

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.2] Candidate aligns with the “builder” aspect (shipping end-to-end, AI tools, APIs, databases) but the JD is Azure-ecosystem heavy (Functions/Cosmos/Container Apps/Power Platform/D365) and consulting delivery, which is not evidenced. The resume shows cloud-agnostic skills but not Azure service implementation depth. To improve ATS: add any real Azure project details (services used, architecture diagrams in bullet form, deployment/monitoring), plus React/Next examples if applicable. **Strengths:** End-to-end shipping under constraints, AI tool fluency + integration mindset, API/DB/system design foundation **Missing Required:** Experience building and deploying on Azure (or clearly equivalent) with evidence

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Candidate has Node.js/JS, SQL/PostgreSQL, production system delivery, and automation experience, which overlaps with backend fundamentals. The JD explicitly requires 8+ years as a Software Engineer plus deep Postgres optimization at scale, queues, JWT auth, and high-transaction SaaS patterns that are not clearly evidenced. To improve ATS: add concrete backend service ownership (APIs, JWT, queues, migrations), performance metrics, and explicitly state TypeScript experience if real. **Strengths:** SQL/Postgres usage, Production shipping and bug-fixing mindset, Automation + systems design **Missing Required:** 8+ years as a Software Engineer, Deep PostgreSQL optimization experience (explicit evidence), Scalability patterns (idempotency/queues) with evidence

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] This is an Azure + Java/Spring + event-driven/messaging architect role; Candidate is strong in Go/automation and has cloud-native instincts but does not show Azure services, Java/Spring microservices, or Terraform/Bicep. Messaging platforms (Service Bus/Event Hubs) and enterprise architecture patterns are central here and are missing. To improve ATS: only apply if there is real Azure/Java/event-driven experience to add with concrete systems built and scale metrics. **Strengths:** Systems architecture mindset, Production delivery + code review rigor, OAuth/SSO security familiarity **Critical Gaps:** Core stack mismatch: Azure + Java/Spring + enterprise messaging required; resume centers on Go/JS with no Azure/Java evidence **Missing Required:** Hands-on Azure services (listed), Java/Spring microservices experience, Event-driven messaging architecture experience, IaC (Terraform/Bicep)