Anti-ATS Evaluatorv1.3

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Critical domain gap: JD requires comprovada experiência in metro/railway systems (design, integration, testing, comissionamento). Candidate has zero rail sector exposure and no SCADA/DCS experience. While candidate demonstrates systems integration skills and engineering degree, absence of rail-specific knowledge and compliance frameworks (CENELEC/ISO rail standards) is disqualifying. No amount of general systems thinking bridges this gap. **Strengths:** Engineering degree (Mechatronic foundation), Systems integration and process design capability, Project management and stakeholder coordination **Critical Gaps:** zero experience in metro/railway systems (comprovada required), no SCADA/DCS/automation systems in rail context **Missing Required:** metro/railway systems integration experience, rail standards knowledge, CAD proficiency

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] This is a network/sales-engineering hybrid role requiring deep expertise in wireless, DNS, RADIUS, PKI, and mandatory CCIE/CISSP certifications. The candidate has no networking background, no wireless/telecom experience, and no certifications. The resume demonstrates systems thinking but in entirely different domains (supply chain, e-commerce automation, AI integration). Candidate should not pursue this role. **Strengths:** systems_thinking, technical_communication, complex_system_design **Critical Gaps:** CCIE_certification_required, CISSP_certification_required, network_engineering_background **Missing Required:** field_sales_experience, technical_presales_support, LAN_WAN_internet_services

[ANALYSIS_REPORT] **MEDIUM** [Opencode: haiku-4-5] Mechatronic degree is perfect alignment for hardware/automation roles. Candidate demonstrates control systems, RTOS, state machines, and automation logic—core foundations for low-voltage drives and process automation. Missing: Sinamics/PCS7 portfolio experience and CAD/hardware design tools. However, these are product-specific, not conceptual gaps. Title mismatch ('Financial Analyst' vs 'Engenheiro') is ATS penalty. **Strengths:** Mechatronic engineering degree (exact match for role preference), Control systems and automation design (RTOS, state machines), Systems integration and multidisciplinary thinking **Missing Required:** portfolio experience with Sinamics/PCS7

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Identical JD to Job 4369349406. Critical domain gap in metro/railway systems (comprovada experiência required). Candidate has zero rail sector exposure and no standards knowledge (CENELEC/ISO). Engineering degree and systems thinking are insufficient for enterprise rail integration role requiring proven track record in comissionamento and systems testing. **Strengths:** Engineering degree, Systems integration capability, Risk management and governance mindset **Critical Gaps:** zero experience in metro/railway systems (comprovada required) **Missing Required:** metro/railway systems integration experience, rail standards knowledge

[ANALYSIS_REPORT] **HIGH** [Opencode: haiku-4-5] Strong match on SRE fundamentals: Linux, Python/Bash scripting, CI/CD, incident response concepts, and troubleshooting mindset evident from platform design. Candidate's monitoring/alerting design (PID-inspired prompt tuning for classification consistency) shows observability thinking. Missing: Windows Server advanced administration, VBScript/.NET PowerShell, and specific tools (Grafana/Datadog), but these are tools, not concepts. **Strengths:** Linux infrastructure and automation (primary OS for candidate), Python/Bash scripting at production scale, Incident response and reliability thinking

[ANALYSIS_REPORT] **MEDIUM** [Opencode: haiku-4-5] Candidate has strong Linux fundamentals inferred from Go server building, bash scripting, Docker, and DevOps-adjacent infrastructure work. Demonstrated Terraform exposure via recent project mentions and automation mindset. However, missing specific enterprise-scale experience with Hyper V, VMware, Veeam, Ansible hands-on depth, and no stated Active Directory experience. The resume shows constraint-based, first-principles infrastructure thinking (relevant to the role), but lacks the breadth of enterprise virtualization platform management. Candidate should highlight automation, Linux hardening, and cloud/on-premises hybrid architecture interests. **Strengths:** linux_systems_thinking, bash_scripting, automation_mindset, docker_containerization, infrastructure_optimization **Missing Required:** enterprise_scale_linux_experience_formal, virtualization_platforms_depth

[ANALYSIS_REPORT] **HIGH** [Opencode: haiku-4-5] Strong match on core technical competencies: Go, Python, Bash, Docker, Kubernetes exposure (inferred from orchestrator + containerization), Terraform (IaC), Linux/Unix, networking fundamentals (demonstrated in production systems). Candidate meets minimum 2 years in all required categories and has 4+ years in scripting/coding. However, missing explicit AWS/Azure/GCP enterprise-scale deployment experience, no formal Deployment Engineering title, and resume does not mention on-call/incident response explicitly. Portuguese and English fluency is a major strength (required LATAM role). Recent proof-of-work (job intelligence platform, e-commerce automation) demonstrates deployment-ready thinking, but enterprise customer-facing experience is unclear. **Strengths:** docker_kubernetes_inferred, infrastructure_automation, production_systems_experience, portuguese_english_bilingual, constraint_based_systems_design

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Candidate lacks automotive domain expertise entirely. JD requires 5+ years in automotive software integration/validation, preferably with IVI/ADAS/embedded automotive platforms, Android Automotive OS (AAOS), and Google Automotive Services (GAS) integration. While candidate has Linux, Git, CI/CD, and debugging skills, there is no demonstrated experience with automotive frameworks (CAN, Ethernet, Vehicle HAL), embedded systems at automotive scale, or the specific tech stack (AAOS/GAS). No transfer of domain knowledge applicable here. Mechatronics degree does not overcome the deep automotive-specific requirements. **Strengths:** linux_systems, git_version_control, ci_cd_mindset, debugging_skills, portuguese_english_fluency **Critical Gaps:** automotive_domain_expertise_5_years, aaos_gas_integration_depth **Missing Required:** automotive_industry_experience, embedded_automotive_platforms

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Candidate has cloud infrastructure fundamentals (AWS inferred from Go production deployment, auto-scaling logic, cost optimization), Kubernetes exposure inferred from orchestrator design (RTOS concepts transfer to distributed systems), Terraform/IaC mindset demonstrated in infrastructure-from-first-principles approach. However, missing explicit production Kubernetes operations (cluster management, troubleshooting at scale), no formal on-call/incident response experience stated, and no hands-on AWS/GCP multi-region deployments documented. Russian/Ukrainian language requirement is a hard blocker—candidate speaks Portuguese/English only. JD emphasizes on-call rotations and incident response; resume does not demonstrate this explicitly. **Strengths:** cloud_infrastructure_thinking, automation_and_scripting, constraint_based_design, production_systems_experience **Critical Gaps:** russian_or_ukrainian_language_required **Missing Required:** on_call_and_incident_handling_experience

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Identical JD to Jobs 4369349406 and 4368783994. Critical domain gap: zero metro/railway systems experience (comprovada required). Candidate's systems thinking and engineering degree do not compensate for absence of rail sector knowledge and CENELEC/ISO standards. **Strengths:** Engineering degree, Systems integration experience, Process and governance mindset **Critical Gaps:** zero metro/railway systems experience **Missing Required:** metro/railway systems integration experience

[ANALYSIS_REPORT] **MEDIUM** [Opencode: haiku-4-5] Strong technical fit: Docker, Kubernetes (inferred from orchestrator/containerization work), Linux/container fundamentals, scripting (Python, Bash), systems design thinking. Candidate has automation mindset (Ansible, workflow automation tools like n8n/Make.com in resume). However, missing explicit Red Hat OpenShift Container Platform (RHOCP) and Ansible Automation Platform (AAP) hands-on depth. JD lists RHEL and RHOCP as 'core offerings,' but candidate has general Linux, not RHEL-specific experience. Missing formal Red Hat certification and Agile/DevOps mindset is implied but not explicit. Strong advantage: JD role is in Brasilia, Brazil, and candidate is based in Sao Paulo, Brazil (local fit). Spanish fluency is 'nice-to-have'; candidate does not list Spanish. **Strengths:** container_kubernetes_fundamentals, linux_systems_architecture, python_bash_scripting, automation_mindset, geography_match_brazil

[ANALYSIS_REPORT] **MEDIUM** [Opencode: haiku-4-5] Engineering degree (Mechatronic ≈ foundational for OT/automation) and systems thinking provide base. Candidate demonstrates control systems, automation architecture, and project management. Critical gap: no SCADA/DCS/PLC or industrial networks (Modbus, Profibus) experience—these are non-negotiable for mining/heavy industry role at technical owner level. No mining sector exposure either. **Strengths:** Mechatronic engineering degree (relevant for OT context), Control systems and automation design, Project management and vendor coordination **Critical Gaps:** no SCADA/DCS/PLC or industrial networks knowledge **Missing Required:** SCADA/DCS/PLC experience, industrial networks knowledge, mining/heavy industry sector experience

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Candidate has observability mindset (monitoring design, SLI/SLO concepts, metrics tracking) and scripting (Python, Bash) skills. Missing critical platform-specific expertise: no Kubernetes/container orchestration (foundational for modern observability), no Prometheus/Grafana/ELK (specific tools), no MuleSoft/Anypoint, no Azure Monitor, no ITIL/ServiceNow. These gaps compound in enterprise observability role. **Strengths:** Observability and metrics design thinking, Python/Bash scripting, Troubleshooting and RCA mindset **Missing Required:** Kubernetes or equivalent container orchestration

[ANALYSIS_REPORT] **HIGH** [Opencode: haiku-4-5] Excellent match on core infrastructure skills: Linux debugging/networking/routing inferred from production system design, Ansible/Terraform/IaC demonstrated mindset, Git/version control (stated), PostgreSQL exposure (inferred from database design in e-commerce system), Python/Bash/scripting (stated), Docker/containerization (stated). Candidate demonstrates observability thinking (monitoring production systems, constraint-based debugging from first principles). However, missing: explicit 5+ years Linux infrastructure (resume shows ~3-4 years infrastructure-focused work, prior was supply chain/finance), no stated BGP/AS routing depth, no explicit Grafana/Prometheus hands-on, no Kubernetes operations at scale. Toptal is remote-first, global culture—strong fit for candidate's work style. No on-call experience explicitly stated. **Strengths:** linux_infrastructure_thinking, iac_terraform_ansible_mindset, postgresql_database_operations, python_bash_scripting, constraint_based_systems_design, remote_work_mindset

[ANALYSIS_REPORT] **MEDIUM** [Opencode: haiku-4-5] Mechatronic degree is perfect alignment for embedded systems role. Candidate's control systems, low-level architecture thinking, and RTOS concepts form solid foundation for microcontroller programming. Missing: practical STM32/PIC/microcontroller experience and embedded C/Assembly focus. However, JR role suggests junior-level skills acceptable; candidate's education + systems thinking may compensate. **Strengths:** Mechatronic engineering degree (perfect match), Control systems and RTOS concepts, Systems integration and testing mindset **Missing Required:** microcontroller programming experience (STM32/PIC)

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Critical mismatch: This role is for IBM i (Power Systems) administration, requiring 5+ years with IBM i, strong HMC skills, MIMIX HA/DR, and IBM Certified System Administrator certification. Candidate has no IBM i experience, no Power Systems background, and no knowledge of CL/RPG languages or IBM-specific tools (BRMS, Halcyon, Enforcive, Robot SCHEDULE). While candidate has general systems administration thinking and can learn tools quickly, the IBM i ecosystem is proprietary and highly specialized. This is a domain-gating role with zero transferable skills. No substitute for deep IBM i expertise. **Strengths:** systems_administration_thinking, learning_velocity, data_integrity_focus **Critical Gaps:** ibm_i_certification_preferred, ibm_i_5_years_minimum, proprietary_ibm_ecosystem **Missing Required:** ibm_i_power_systems_experience, ibm_certified_system_administrator

[ANALYSIS_REPORT] **TOP** [Opencode: haiku-4-5] Excellent match: candidate's entire e-commerce platform design is monitoring/observability-centric. Scoring pipeline (PID-inspired prompt tuning), SLI/SLO thinking (in-stock rate targets, lead-time thresholds), metrics design, and alert logic are core strengths. Dashboard design (99/100 PageSpeed), API integration, and data architecture all align with monitoring role. Missing: specific tools (Zabbix/Prometheus), but these are learnable frameworks, not conceptual gaps. **Strengths:** Observability architecture and metrics design (core strength), Dashboard and visualization design (Grafana-equivalent thinking), Linux and API integration expertise

[ANALYSIS_REPORT] **MEDIUM** [Opencode: haiku-4-5] Candidate demonstrates distributed systems thinking (orchestrator design with state persistence, RTOS concepts, constraint-based architecture), data engineering exposure (job intelligence pipeline with AI scoring, data validation, statistical analysis from supply chain background), and leadership through technical projects (self-directed complex systems). However, missing explicit 5+ years distributed systems AND 2+ years team leadership (no formal manager/architect title). Resume shows influence but not titled leadership. Missing deep Java/Python/Go production systems at scale—candidate has Go experience but limited proven depth in multi-engineer codebases. JD requires 'hands-on experience in data engineering AND distributed systems'—resume is stronger in infrastructure/systems than data engineering proper (pipelines, warehousing, big data tools). **Strengths:** distributed_systems_thinking, data_pipeline_architecture_inferred, learning_velocity, constraint_based_optimization, production_systems_experience **Missing Required:** 2_plus_years_leading_5_plus_team, 5_plus_years_data_engineering_distributed_systems

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Entry-level mismatch with senior candidate. JD is for Junior Systems Engineer requiring Windows operating systems expertise, ServiceNow proficiency, and ITIL Foundation or Microsoft Certified Windows Server Fundamentals certification. Candidate has no stated Windows experience, no ServiceNow background, and no IT service management certifications. While candidate has strong problem-solving, automation mindset, and systems thinking, this role is service-desk focused (incident management, ticketing), not infrastructure/architecture. The candidate's skills are overqualified technically but mismatched functionally. Additionally, JD requires 'Advanced English, Portuguese, and Spanish'—candidate has Portuguese and English (C2) but Spanish is not listed. **Strengths:** problem_solving, documentation_mindset, systems_thinking, portuguese_english_bilingual **Missing Required:** windows_systems_expertise

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Strong Python skills and AWS familiarity are clear. Candidate has APIs/REST expertise and demonstrated full-stack thinking (Go backend + web). Critical gap: 'Serverless Framework' marked ESSENCIAL—no evidence of this in resume. Also missing DynamoDB and React. Serverless Framework is not transferable from general backend knowledge; it requires specific project experience. This is a deal-breaker for startup with tight framework dependency. **Strengths:** Python backend development, AWS foundations and cloud thinking, APIs/REST design and integration **Critical Gaps:** Serverless Framework marked ESSENCIAL—no demonstrated experience **Missing Required:** Serverless Framework, DynamoDB experience

[ANALYSIS_REPORT] **HIGH** [Opencode: haiku-4-5] Strong technical match: Go (stated, production-grade webserver built), SQL/NoSQL databases (PostgreSQL, SQLite in recent work), microservices/cloud thinking (demonstrated in e-commerce automation and job intelligence platform), algorithms/design patterns (constraint-based optimization, state machines in orchestrator), testing (implied in production systems), CI/CD (Git, mentioned in automation context), unit testing (demonstrated quality focus). However, missing explicit: frontend development experience (Go backend is primary), advanced algorithm problem-solving credentials (LeetCode/competitive programming), and formal Agile methodologies management. JD emphasizes 'design and build applications from scratch'—candidate has done this (job intelligence platform built solo in ~1 month). **Strengths:** golang_production_systems, sql_nosql_databases, full_stack_from_scratch_demonstrated, testing_and_ci_cd_mindset, api_design_and_integration

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Complete domain mismatch. JD requires 5+ years professional software development in Microsoft Dynamics 365 environments, deep hands-on mastery of Power Apps model-driven apps, C# or JavaScript customization expertise, and Dataverse/Power Platform connector experience. Candidate has zero Dynamics 365, Power Apps, Power Platform, or enterprise Microsoft stack experience. While candidate has JavaScript and Python (not C#), this is not transferable to the highly specialized Dynamics/Power Platform ecosystem. This is a hard domain-gating role. **Strengths:** javascript_scripting, python, learning_velocity **Critical Gaps:** dynamics_365_5_years_professional, power_apps_deep_expertise **Missing Required:** dynamics_365_software_development_background

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Candidate has Python, JavaScript, and database/SQL experience, but C#/.NET is completely absent. JD requires 'Plataforma .NET (C#) em nível avançado'—this is non-negotiable. Additionally, Angular/React (frontend) is required at intermediate level; candidate has JavaScript/Node.js, not React. C# and .NET are not substitutable with Python or JavaScript; they require separate language ecosystem mastery. **Strengths:** Python and JavaScript programming foundation, SQL and Postgres experience, API design and REST concepts **Critical Gaps:** C#/.NET platform (core requirement, non-transferable) **Missing Required:** C#/.NET ADVANCED expertise, Angular/React frontend framework

[ANALYSIS_REPORT] **HIGH** [Opencode: haiku-4-5] Strong match on required tech stack: Node.js (JavaScript experience stated; v18 is current), TypeScript (not explicitly stated but inferred from modern backend practices), NestJS (not used but candidate can learn—JS framework jumping is common), Jest (not stated, but testing familiarity inferred), SQL databases (PostgreSQL, SQL expertise stated), MongoDB/NoSQL (database-agnostic thinking), Redis (caching patterns inferred from performance optimization), Docker (stated), REST APIs (demonstrated), Git (stated), OAuth2/JWT/OIDC (explicitly stated in resume: 'built SSO-protected admin panel with Google OAuth 2.0, learned OAuth/OIDC from scratch, implemented in 1 hour'). Missing explicit: Node.js v18 hands-on (candidate may have earlier versions), Turborepo (monorepo tool, not core skill), NestJS hands-on, Jest testing framework, and message queue experience (Kafka/RabbitMQ). Banking domain experience is missing; candidate has e-commerce automation but not financial services scale. **Strengths:** oauth2_jwt_oidc_implementation, typescript_modern_backend, rest_apis, docker_containerization, database_design_postgres_mongodb, redis_caching_patterns

[ANALYSIS_REPORT] **LOW** [Opencode: haiku-4-5] Candidate has strong architecture thinking, Docker, CI/CD, and microservices concepts. However, C#/.NET (required at senior level) and React (required) are both absent. Candidate's Go is cloud-native and systems-level, but cannot substitute for .NET ecosystem. No Kubernetes despite it being required. This is a wrong-stack fit for senior/mid-level role requiring proven .NET/React track record. **Strengths:** Microservices and architecture thinking, Docker and containerization, CI/CD and DevOps mindset **Critical Gaps:** C#/.NET and React (core stack, non-transferable) **Missing Required:** C#/ASP.NET Core expertise, React frontend framework, Kubernetes experience