Anti-ATS Evaluatorv1.3

[ANALYSIS_REPORT] **TOP** [gemini-3.1-pro-preview] This job is an exceptional match. It requires integrating LLMs, building RAG systems with vector DBs, and automating workflows while interacting with legacy systems. The candidate's proven experience building Go orchestrators, applying RAG, and working with strict legacy constraints (TOTVS ERP) fits perfectly. He should highlight his Go orchestrator specifically as an agentic workflow engine. **Strengths:** LLM & Agentic Workflows, RAG / Vector DBs, Legacy system constraint engineering

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-1] Good match on AI architecture and prompt engineering. Demonstrated production AI deployment and model customization. Missing Azure-specific experience but shows cloud-agnostic capability. Python and data engineering skills align well. **Strengths:** AI architecture, Prompt engineering, Production deployment **Missing Required:** Azure AI services

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-1] Strong data pipeline and ML fundamentals from supply chain analytics background. Python proficiency and end-to-end project experience demonstrated. Missing formal ML frameworks but shows practical implementation ability. **Strengths:** ETL/ELT expertise, Python proficiency, Data analysis

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-1] Good Python and data analysis match, demonstrated ML concepts through trading algorithms. Missing specific fraud detection experience and ML frameworks. Statistical forecasting background from supply chain applies to fraud patterns. **Strengths:** Python expertise, Statistical analysis, Pattern recognition **Missing Required:** ML frameworks, Fraud detection experience

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-1] Strong Python and AI integration skills demonstrated through job intelligence platform. LLM API experience and production deployment proven. Missing specific ML frameworks but shows practical implementation ability. **Strengths:** LLM integration, Python proficiency, Production AI systems

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-1] Leadership experience from Head of Engineering role, strong AI/ML implementation with job intelligence platform. Missing formal team management in tech context and specific NLP frameworks. English C2 requirement met. **Strengths:** AI architecture, Python expertise, English fluency **Missing Required:** Tech team management experience

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-1] Critical gaps in entire Microsoft stack despite strong general AI capabilities. No Copilot Studio, Azure OpenAI, or Databricks experience. Built similar systems on completely different technology stack. **Strengths:** RAG architecture, Python development, AI integration **Critical Gaps:** Microsoft ecosystem, Azure AI services, Enterprise delivery **Missing Required:** Copilot Studio, Azure OpenAI, Databricks

[ANALYSIS_REPORT] **HIGH** [Opencode: opus-4-1] Excellent match for AI architecture role. Demonstrated complex system design, RAG implementation, and production deployment. Built entire AI-powered platform showing exact architectural skills needed. Portuguese language advantage for Brazilian role. **Strengths:** RAG architecture, Production AI systems, System design

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-1] Critical gaps in multimodal AI experience. Candidate's work focuses on text/LLM, not vision-language models or document understanding. Missing 4-5 years requirement in multimodal systems which cannot be inferred from current experience. **Strengths:** Python proficiency, Data validation, System architecture **Critical Gaps:** Multimodal AI experience, Vision processing, 4-5 years multimodal requirement **Missing Required:** Multimodal data experience, Vision-language expertise

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-5] Critical gap in ML model training/deployment experience - JD requires 5+ years building production ML systems with TensorFlow/PyTorch, designing text classification and anomaly detection models. Candidate has LLM API integration and prompt engineering but no model training, no Spark/Databricks experience, no ML lifecycle ownership. To improve: cannot bridge this gap without formal ML engineering experience; this is a research-adjacent ML role, not an AI integration role. **Strengths:** Python proficiency, Data pipeline experience, Production systems mindset **Critical Gaps:** 5+ years production ML systems, ML model development and training, large-scale data processing frameworks **Missing Required:** 5+ years ML production experience, TensorFlow/PyTorch hands-on, Spark/Databricks experience

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-5] Strong alignment on LLM APIs, RAG, and production systems thinking, but critical gap on 7+ years software engineering requirement with 2+ years in production AI/ML. Candidate has demonstrable LLM pipeline work and agent-adjacent architecture but lacks formal SE tenure. To improve: emphasize the Go orchestrator as production-grade software engineering, highlight the full-stack nature of the job platform, but the years requirement is an ATS hard filter. **Strengths:** LLM API proficiency (Claude, Gemini, OpenAI), RAG implementation experience, Production deployment on constrained infrastructure, Cost optimization and caching strategies **Critical Gaps:** 7+ years software engineering experience, 2+ years production AI/ML applications **Missing Required:** 7+ years hands-on software engineering, 2+ years production AI/ML

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-5] Good alignment on LLM integration, RAG, embeddings, and production deployment. Candidate has PostgreSQL with pgvector potential, API development, and containerization basics. Gaps in Kubernetes expertise, IaC with Terraform, and cloud-native observability at enterprise scale. To improve: add explicit Terraform/IaC experience if any, emphasize Docker usage, highlight the production deployment with monitoring. **Strengths:** LLM API integration (Claude, Gemini, OpenAI), RAG pipeline design, Python with good practices, PostgreSQL and data architecture, Production deployment experience **Missing Required:** Kubernetes production experience, IaC (Terraform), Cloud platform depth (AWS/Azure/GCP)

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-5] Strong conceptual alignment - candidate's RTOS-inspired orchestrator, CI/CD understanding, and AI pipeline work match the role's AI orchestration vision. However, lacks enterprise CI/CD platform experience at scale, Jira automation integration, and formal Staff-level technical leadership track record. To improve: emphasize the orchestrator architecture decisions, highlight context engineering in the scoring pipeline, frame the variance reduction as measurement/governance. **Strengths:** Custom orchestrator with state management and scheduling, AI pipeline with measurable quality metrics, Context engineering (prompt tuning with PID-control concepts), LLM integration in production, Systems architecture thinking **Missing Required:** Staff/Principal level technical leadership experience, Large-scale regulated environment experience

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-5] Critical gaps across the board - role requires 8+ years shipping ML/LLM features for millions of users, experience with RLHF/DPO, SFT, and model alignment. Candidate has LLM API usage but no model training, fine-tuning, or alignment work. This is a research-engineering hybrid role requiring deep model internals expertise. To improve: cannot bridge without actual fine-tuning and model training experience. **Strengths:** LLM API integration, Prompt engineering, Production systems mindset **Critical Gaps:** 8+ years ML/LLM shipping experience, Model training and fine-tuning, Alignment strategies, Millions of users scale **Missing Required:** 8+ years engineering shipping ML, PyTorch proficiency, Fine-tuning experience, RLHF/DPO experience

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-5] Partial alignment on AI solution architecture concepts and LLM integration, but significant gaps in cloud platform depth (GCP required), AIOps pipeline experience, containerization at scale, and computer vision. Ford is enterprise with formal architecture processes. To improve: emphasize systems architecture decisions, add any GCP exposure, but enterprise cloud depth is the main gap. **Strengths:** LLM integration experience, API development, Systems design thinking, Cost optimization mindset **Critical Gaps:** Proven AI architecture experience at scale, GCP and cloud AI services depth **Missing Required:** Cloud platform expertise (GCP), Complete AI development cycle at scale, AIOps experience

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-5] Moderate alignment on infrastructure concepts, CI/CD understanding, and Linux. Strong gap in GCP-specific expertise (role prefers GCP), Kubernetes production experience, and formal DevOps/SRE track record. Candidate has Docker basics and automation mindset but lacks enterprise observability stack depth. To improve: emphasize any cloud deployment experience, Linux administration from server management, CI/CD from project deployments. **Strengths:** Linux server administration, Docker basics, CI/CD concepts, Git proficiency, Automation mindset, Production system operation **Missing Required:** Cloud platform expertise (GCP preferred), Kubernetes hands-on, IaC tools (Terraform)

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] This is a heavy enterprise SRE role requiring deep AWS IaC, Kubernetes, and massive distributed systems experience. While the candidate has good Linux and CI/CD basics, he lacks the heavy IaC and orchestration tools (Terraform, K8s) required for enterprise SRE. The ATS will likely gatekeep based on missing SRE titles and K8s. **Strengths:** Linux, Docker, CI/CD **Critical Gaps:** Enterprise Kubernetes/IaC **Missing Required:** Kubernetes, IaC

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-5] Alignment on Python, automation mindset, and AI tool usage. Gaps in AWS infrastructure depth (EC2, ELB, VPC, Lambda, Kinesis), Kubernetes scaling, and formal security/vulnerability management. The 'AI-native' angle is a plus - candidate uses AI tools. To improve: emphasize GitHub Actions if used, highlight any AWS exposure, frame the production deployment as DevOps-adjacent. **Strengths:** Python scripting, AI-native tool usage, Production deployment experience, Automation philosophy **Missing Required:** 4+ years DevOps enabling developers, AWS infrastructure experience, Kubernetes management

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] The role is specific to MLOps within the AWS data ecosystem (S3, EMR, Glue, SageMaker) using PySpark. The candidate builds lightweight, constraint-based LLM architectures, not heavy big-data Spark pipelines. The ATS will flag the absence of big data and SageMaker keywords. **Strengths:** CI/CD, Python **Critical Gaps:** Big Data / PySpark pipelines **Missing Required:** PySpark, AWS data stack

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-5] Partial alignment on Python scripting, SQL operations, and observability concepts. Candidate built dashboards conceptually but lacks Grafana/Prometheus/Elastic Stack depth, Kubernetes production support experience, and formal SRE methodology. To improve: emphasize any monitoring dashboards built, SQL troubleshooting experience, Linux log analysis. **Strengths:** Python/Bash scripting, SQL proficiency, Linux system knowledge, Production system operation **Missing Required:** 2+ years SRE/DevOps/Production Support, Observability stack experience, Kubernetes support experience

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] This job explicitly states 'Vaga afirmativa para mulheres' (Affirmative action for women). Based on the candidate's demographic data (Male), this is a hard filter and an automatic rejection by the ATS and HR. **Critical Gaps:** Demographic requirement

[ANALYSIS_REPORT] **LOW** [Opencode: opus-4-5] Critical gap in GPU cluster management and Volcano scheduler - these are highly specialized skills. Candidate has Python and Linux basics but lacks Kubernetes administration depth, GPU workload experience, and the specific tooling (Volcano, resource quotas for GPU). To improve: cannot bridge without actual GPU/Kubernetes infrastructure experience. **Strengths:** Python scripting, Linux basics, Automation mindset **Critical Gaps:** GPU cluster environment management, Volcano scheduler expertise, Kubernetes expert-level administration **Missing Required:** 3+ years DevOps/infrastructure experience, Expert Kubernetes administration, Volcano scheduler experience, GPU cluster management

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-5] Alignment on LLM concepts and general platform understanding. Role is Tier 1/2 support for AI platforms - less technical depth required than engineering roles. Kubernetes knowledge gap is the main issue. To improve: emphasize customer service orientation, LLM troubleshooting ability, willingness to learn K8s fundamentals. **Strengths:** LLM understanding and usage, Technical communication skills, Problem-solving orientation, Systems thinking **Missing Required:** Kubernetes knowledge, Cloud native technologies

[ANALYSIS_REPORT] **MEDIUM** [Opencode: opus-4-5] Nearly identical to Job 4381119714 (same role, same company). Strong conceptual alignment on AI orchestration, context engineering, and pipeline design. Same gaps: Staff-level title, enterprise CI/CD scale, regulated environment experience. The orchestrator project is the key differentiator. To improve: same as Job 4 - frame orchestrator as Staff-level architecture decision-making. **Strengths:** Custom orchestrator with scheduling and state management, AI pipeline quality metrics, Context engineering, LLM production integration **Missing Required:** Staff/Principal level technical leadership, Platform engineering experience

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] This is an SRE Specialist role focused on enterprise metrics (SLI/SLO/SLA), vendor management, and strict crisis management. While the candidate understands reliability conceptually, he lacks the enterprise-scale SRE tooling and titles expected for a 'Specialist' level. The ATS will likely reject based on missing formal SRE tenure. **Strengths:** Automation, Root cause analysis, System Architecture **Critical Gaps:** Enterprise SRE tenure **Missing Required:** SLO metrics management