Anti-ATS Evaluatorv1.3

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] The candidate matches the LLM platform and retrieval concepts, Postgres, Docker, CI/CD, and vector similarity search, but the core stack here is C#/.NET on Azure, which is entirely absent. They show strong distributed systems thinking and production LLM work, yet nothing about ASP.NET Core, Azure Functions/Service Bus, Terraform, or deep Azure operational patterns. To improve for this kind of role, they would need either real .NET/Azure projects on the resume or a separate profile tailored around those technologies, which currently do not exist. **Strengths:** Production LLM platform experience with batching, caching, and cost control, PostgreSQL experience and data architecture skills, Clear understanding of retrieval, RAG, and evaluation concepts **Missing Required:** C#/.NET backend development experience, Strong ASP.NET Core API and background worker experience

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] The candidate aligns strongly with LLM understanding, prompt engineering, CI/CD, Docker, and cloud fundamentals, and has built production AI systems and automation. However, this role is explicitly about MLOps/AI infrastructure with Kubernetes (Kubeflow/Seldon/KServe), Prometheus/Grafana monitoring, CT pipelines, and several years of MLOps-specific experience, none of which appears on the resume. To improve, the candidate would need to add concrete experience (even personal or small production) with Kubernetes-based deployment, monitoring stacks, and explicit "MLOps" responsibilities. **Strengths:** Deep LLM and prompt engineering experience, CI/CD, Docker, and automation skills, Proven ability to design and run production AI-powered systems **Missing Required:** 4+ years experience specifically labeled as MLOps/ML Engineering/DevOps for AI infrastructure

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] This JD has nearly identical requirements to Job 3: strong alignment on LLM understanding, CI/CD, Docker, and automation, but explicit gaps on Kubernetes-based orchestration, Prometheus/Grafana monitoring, and CT pipelines. The candidate's experience running production LLM systems and orchestrators is adjacent to MLOps, but ATS will not equate that with the requested MLOps/Kubernetes stack. The resume should be updated to highlight any container orchestration, monitoring, and pipeline work as "MLOps" and add Kubernetes/monitoring exposure to be more competitive. **Strengths:** Production automation and infrastructure design experience, Hands-on LLM and generative AI work, CI/CD and Docker skills relevant to ML pipelines **Missing Required:** 4+ years professional experience focused on MLOps/AI infrastructure

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] Again, there is a strong match on LLM understanding, prompt engineering, CI/CD, Docker, and cloud fundamentals, but the JD centers on Kubernetes/Kubeflow/Seldon, Prometheus/Grafana, CT pipelines, and explicit MLOps/AI infra work over 4+ years. The candidate's portfolio demonstrates owning production AI systems and automation, but ATS will not see the missing Kubernetes and monitoring stack as equivalent. Strengthening the resume with any Kubernetes work, basic monitoring (even non-Prometheus) and explicitly labeling current pipelines as "MLOps" would move this closer to target. **Strengths:** Deep generative AI and LLM experience, CI/CD and automation mindset across systems, Experience integrating into business workflows and making AI reliable **Missing Required:** 4+ years explicitly in MLOps/ML Engineering/DevOps for AI

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] This variant of the MLOps Engineer role repeats the same core stack: CT pipelines, Docker+Kubernetes with Kubeflow/Seldon/KServe, Prometheus/Grafana, cloud AI infra, and several years of focused MLOps experience. The candidate is strong on Docker, CI/CD, LLMs, automation, and systems design but lacks explicit Kubernetes, ML-specific monitoring, and named MLOps platforms. To get closer, they should pursue and surface even small projects using Kubernetes for model serving, basic monitoring, and clearly label their current pipelines as MLOps/ML lifecycle automation. **Strengths:** Experience automating end-to-end systems with CI/CD and Docker, LLM and prompt engineering expertise, Ability to integrate into client teams and tackle complex systems **Missing Required:** 4+ years MLOps/Machine Learning Engineering/DevOps for AI infrastructure

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] Like Jobs 3 and 4, this MLOps Engineer role centers on CI/CD+CT, Docker+Kubernetes with Kubeflow/Seldon/KServe, Prometheus/Grafana, and cloud AI infrastructure. The candidate brings strong AI systems, Docker, CI/CD, and automation experience, but has no explicit Kubernetes, Kubeflow, Prometheus, or Grafana in their stack and no job titles labeled MLOps or ML Engineer. Improving competitiveness would require at least one clearly described project using Kubernetes for models and basic monitoring plus explicit "MLOps" language on the resume. **Strengths:** CI/CD and Docker experience applicable to ML deployments, LLM and generative AI expertise, Experience working on large, complex systems and automation **Missing Required:** 4+ years of professional MLOps/ML Engineering/DevOps focused on AI infrastructure

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] This role mirrors Job 5, emphasizing MLOps for AI infrastructure with Docker+Kubernetes, CT pipelines, Prometheus/Grafana, and cloud platforms, plus a strong ownership/attitude component. The candidate is well-aligned on LLMs, automation, CI/CD, Docker, and cloud fundamentals, but lacks explicit Kubernetes, Kubeflow/Seldon, Prometheus/Grafana, and formally labeled MLOps experience. To sharpen fit, the resume should present current AI infra work as MLOps (pipelines, monitoring, deployments) and, ideally, include at least one project using Kubernetes and basic monitoring tools. **Strengths:** Deep LLM, prompt engineering, and generative AI experience, CI/CD, Docker, and cloud fundamentals suitable for infra roles, Strong ownership mindset and experience working through difficult systems issues **Missing Required:** 4+ years of MLOps/Machine Learning Engineering/DevOps focused on AI infrastructure

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The candidate is a strong semantic fit for an AI analyst role: Python and SQL experience, ML-like projects (trading strategies, demand forecasting, job scoring), descriptive statistics and hypothesis testing (via the MITx MicroMasters), and experience turning business questions into data-driven systems. They also bring generative AI experience, cloud fundamentals, and some DevOps concepts (Docker, CI/CD), which align with desirable MLOps/productionization aspects. The main ATS gaps are lack of explicit deep learning frameworks (PyTorch/TensorFlow), no Salesforce CRM experience, and not naming ML frameworks, which should be added if any have been used. **Strengths:** Python and SQL experience with real-world analytics and automation, Experience designing and validating algorithmic strategies and forecasting models, Strong ability to discuss business needs and translate them into technical systems

[ANALYSIS_REPORT] **LOW** [2.5-Pro] The candidate is strong on the 'Engineering' and 'Architecture' aspects of the role, but lacks demonstrated experience with the 'Machine Learning' part as it's traditionally understood (e.g., predictive models). The job description is generic but implies a need for classic ML skills, which is a gap. He can deploy and operationalize systems, but not necessarily the specific models they are using. **Strengths:** System Architecture, Operationalizing complex systems, Collaboration **Missing Required:** Experience with various machine learning models

[ANALYSIS_REPORT] **LOW** [2.5-Pro] This application fails on two hard requirements. First, the role requires deep experience with core ML frameworks like TensorFlow and PyTorch, which the candidate lacks. Second, it's a hybrid role based in Rio de Janeiro, and the candidate is in São Paulo, making the on-site requirement impossible to meet. These factors result in an automatic rejection. **Strengths:** Python, AWS Fundamentals **Critical Gaps:** Core ML framework experience, Geographic location **Missing Required:** TensorFlow, PyTorch, AWS SageMaker, Rio de Janeiro based

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] The candidate has strong analytical and systems experience, including designing trading strategies, demand forecasting, and building a job scoring pipeline, which map to ML-thinking but not explicitly to the standard ML stack. The JD, however, emphasizes hands-on experience with ML libraries (classification/regression/segmentation), feature engineering, model tuning, A/B testing, deployment, monitoring, and pipelines using conventional tools, which are not explicitly listed. To improve, the resume needs clear mention of ML libraries, concrete supervised/unsupervised projects, and model deployment/monitoring details. **Strengths:** Experience in financial analytics and quantitative trading systems, Strong data preparation and forecasting background, Ability to translate business problems into algorithmic approaches **Missing Required:** Hands-on experience deploying and monitoring ML models in large-scale production environments

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] The candidate offers strong software/system design experience, end-to-end ownership of production systems, and some algorithmic and analytics work, which partially align with a senior ML Engineer/Data Scientist. However, the JD expects deep experience with ML algorithms, tools, and platforms, plus full-scale modeling over complex datasets, and none of the standard ML stack (scikit-learn, TensorFlow, PyTorch, etc.) appears on the resume. To be competitive, the candidate would need to showcase specific ML projects with named libraries, models, and deployment stories. **Strengths:** Robust software engineering and systems design background, Ability to own full lifecycle from scoping to production deployment for custom systems, Strong pattern-recognition and quantitative work through trading and operational analytics **Missing Required:** Senior-level data science/ML engineering experience with end-to-end client-facing ML solutions

[ANALYSIS_REPORT] **TOP** [2.5-Pro] This role is a perfect storm of the candidate's skills and experience. It requires designing multi-agent architectures, orchestrating them, optimizing prompts, and applying this to e-commerce. The candidate has done all of these things: his current role is in e-commerce, and his recent project involved building an agent orchestrator with prompt tuning. The alignment is exceptional. **Strengths:** Multi-agent architecture design, E-commerce domain experience, Prompt engineering and optimization

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] The candidate matches some pieces of this Staff ML/MLOps role—Python, Docker, CI/CD, cloud fundamentals, and operating production systems—but the JD is heavily centered on Kubeflow, MLflow, Airflow, SageMaker, Kubernetes, large-scale ML pipelines, and real-time model processing. None of those core MLOps tools or large-scale ML experiences are present, and there is no staff-level ML/MLOps track record. To approach this kind of role, they would need substantial, clearly documented experience building and operating ML pipelines with the named tooling or close equivalents. **Strengths:** Solid CI/CD, Docker, and infrastructure automation background, Experience managing production systems and state machines, Strong collaboration skills with technical and non-technical stakeholders **Missing Required:** Staff-level ML/MLOps ownership of complex pipelines and environments

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The candidate is a good semantic match for a Data Scientist Pleno: strong Python and SQL, full-lifecycle analytic projects (forecasting, trading strategies, job scoring), statistics and hypothesis testing from the MicroMasters, and experience building production systems and pipelines. They also bring generative AI, RAG, vector search, and automation, which align nicely with the role’s differentials around MLOps and RAG/vector DBs. The main ATS weakness is the absence of explicit Python data science libraries (Pandas, NumPy, scikit-learn) and visualization tools, which should be named if used. **Strengths:** End-to-end data project experience from problem framing to production system, Strong statistics and hypothesis testing foundation (MITx MicroMasters), Hands-on generative AI, RAG, and vector similarity search experience **Missing Required:** Named Python data science libraries as required by the JD

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The candidate fits well as a Data Engineer for Analytics & ML: mastery of Python and SQL in practice, experience with ML-like projects and automation, cloud fundamentals, Git, and especially strong experience with LLMs, prompt engineering, and generative AI APIs, which are explicitly requested. They also bring some MLOps-adjacent strengths (Docker, CI/CD, production deployment) even if not named with classic data tooling. The primary ATS weakness is again the missing explicit ML libraries (scikit-learn/XGBoost/TensorFlow) and formal data engineering tooling, which should be added where truthful. **Strengths:** Strong Python and SQL experience with real production systems, Hands-on LLM, prompt engineering, and AI agent/orchestration experience, Ability to design and implement data and ML pipelines end-to-end **Missing Required:** Named ML libraries (scikit-learn, XGBoost, TensorFlow or similar) as required by the JD

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The candidate is a good match for a mid-level Data Scientist focused on advanced analytics: they have extensive experience turning business problems into analytic systems, doing forecasting, designing algorithms, and building production pipelines that drive decisions. Their profile also fits the emphasis on strategic impact, model governance, and executive communication, given their experience translating between executives and engineers. ATS will, however, note the absence of explicit ML libraries and classic DS titles, which should be addressed where possible. **Strengths:** End-to-end project ownership from business framing to production, Strong analytics and forecasting background with measurable business impact, Exceptional business-technical translation and stakeholder communication **Missing Required:** Explicit Python data science stack as commonly expected for Data Scientist roles

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] Candidate lacks deep experience with traditional ML frameworks like TensorFlow or PyTorch. The resume focuses heavily on LLM API integration and prompt engineering rather than training mathematical models. The ATS will likely auto-filter due to the complete absence of a formal 'Machine Learning Engineer' or 'Software Engineer' title. **Strengths:** Python, Model evaluation concepts, Production deployment **Critical Gaps:** Traditional Machine Learning training, Model feature engineering algorithms **Missing Required:** TensorFlow, PyTorch

[ANALYSIS_REPORT] **LOW** [2.5-Pro] There is a major disconnect between the candidate's profile (Systems Architect, AI Infra) and this role (classical Machine Learning). The job requires experience with classification/regression models, statistical validation, and A/B testing—skills typical of a Data Scientist, which he does not possess. Furthermore, the 'Pleno' (mid-level) seniority does not match his 12+ years of experience. **Strengths:** Data preparation (transferable), Problem analysis (transferable) **Critical Gaps:** Role is for a classical ML practitioner, not an AI systems builder **Missing Required:** Experiência no desenvolvimento e validação de modelos de Machine Learning

[ANALYSIS_REPORT] **TOP** [2.5-Pro] This is an outstanding match. The role explicitly asks for a Senior ML Engineer to work on Supply Chain problems using Python, RAG, and embeddings, and to translate business problems into technical solutions. The candidate's resume shows deep, practical experience in all these areas, especially his foundational experience in Supply Chain which gives him a massive domain advantage. **Strengths:** Supply Chain domain expertise, Python and RAG implementation, Translating business problems into viable solutions

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] The role requires deep expertise in the C#/.NET Azure ecosystem, whereas the candidate operates in Go/Node.js/Python on AWS/Linux. While the applied AI and RAG concepts align perfectly, the backend language stack is a critical gap. Modifying the resume cannot bridge this fundamental stack mismatch. **Strengths:** PostgreSQL/pgvector, RAG/Retrieval concepts, Applied LLM production experience **Critical Gaps:** C#/.NET enterprise development, Azure cloud ecosystem **Missing Required:** C#, .NET, Azure

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] This is a heavy Data Science/Applied Research role requiring advanced degrees and causal inference mathematics. The candidate's background is mechatronics and practical operational engineering, not statistical research. The ATS will immediately filter based on the education and deep ML requirements. **Strengths:** Python, SQL, Business objective translation **Critical Gaps:** Master's/PhD Degree, 5+ years Applied ML experience, Advanced statistical modeling **Missing Required:** Master's/PhD degree, 5+ years Applied ML

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] This is a Senior Software Engineer position at Google. Big tech companies rigorously filter for formal Software Engineering experience and traditional CS fundamentals. The candidate's non-traditional title history and lack of previous big-tech tenure will result in immediate ATS rejection. **Strengths:** Technical leadership, Process optimization **Critical Gaps:** Formal Senior Software Engineer title history **Missing Required:** Senior Software Engineer experience

[ANALYSIS_REPORT] **LOW** [2.5-Pro] This is a pure Data Scientist role focused on building predictive models (churn, recommendation) with classical ML libraries (scikit-learn, XGBoost). This is a fundamentally different discipline from the candidate's expertise in systems architecture, automation, and AI infrastructure. He lacks the required statistical modeling and classical ML background, resulting in a critical gap and a near-zero score. **Strengths:** Python, SQL **Critical Gaps:** Data Science vs. Systems Engineering **Missing Required:** Proficiência em Python e SQL, Experiência com bibliotecas de ML (scikit-learn, XGBoost, TensorFlow, PyTorch)

[ANALYSIS_REPORT] **LOW** [gemini-3.1-pro-preview] The role specifically targets recommender systems and PyTorch model deployment. While the candidate has strong Python and FastAPI (inferred via Go webserver concepts) skills, the core domain of building recommendation algorithms is absent. The candidate is a systems integrator, not a recommendation modeler. **Strengths:** Python, API deployment, Independent work environment **Critical Gaps:** Recommender systems background, PyTorch **Missing Required:** Recommendation models, PyTorch