Anti-ATS Evaluatorv1.3

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] The profile matches on Linux, automation, developer experience focus, and platform mindset but lacks direct Terraform module development and deep AWS platform engineering that are core to this role. ATS will pick up strong automation and infrastructure concepts yet down-rank due to missing Terraform/IaC keywords and absence of prior "Platform Engineer" titles. Fit improves if the person adds concrete Terraform projects, emphasizes AWS usage, and frames existing orchestration work as platform engineering and self-service enablement. **Strengths:** Strong Linux and systems-level thinking, Experience designing automation and orchestration for developers, Ability to document and translate complex technical workflows for teams **Missing Required:** Demonstrated Terraform/IaC expertise on AWS platform

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.1] The candidate aligns strongly with this Data Engineer role: Node.js backend, SQL/PostgreSQL pipelines, data modeling mindset, and extensive experience with data quality and operational debugging. ATS sees rich matches on backend services, data pipelines, databases, and remote Brazil location, but misses explicit TypeScript and formal governance/security tooling. Fit improves by labeling recent work explicitly as "Data Engineer", calling out Node/TypeScript where applicable, and describing data governance and security responsibilities. **Strengths:** Node.js and Go backend development with SQL databases, Hands-on design of data pipelines and operational reporting, Strong debugging and data quality remediation experience

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.1] The person brings strong SQL, data cleanup, forecasting, and KPI/reporting experience that aligns with ETL and data quality aspects of DW/BI. However, ATS will likely treat the absence of Tableau/Qlik/PLX and formal metadata/governance tooling as gaps against core requirements. Fit can be improved by surfacing any BI-like dashboards (even in Excel/Sheets), expanding ETL pipeline descriptions, and adding exposure to at least one mainstream BI tool. **Strengths:** Advanced SQL and data analysis background, Proven track record in data quality remediation and validation rules, Experience designing KPIs and operational dashboards **Missing Required:** Direct experience delivering DW/BI solutions using standard BI tools

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Hard filter: é um programa de estágio desenhado para estudantes (30h/semana), e o perfil não se encaixa nesse requisito demográfico. Mesmo com forte capacidade técnica (Go, scraping, SQL), um ATS enterprise tende a auto-rejeitar antes de pontuar skills. Para tentar algo similar, buscar vagas de Jr/Pleno (não estágio) e adaptar o resumo para “Software/Systems Engineer” com projetos recentes em produção. **Strengths:** Go in production, Automation and data pipelines, SQL/PostgreSQL **Critical Gaps:** Student-only internship requirement **Missing Required:** Student status / internship eligibility

[ANALYSIS_REPORT] **HIGH** [Copilot: GPT5.2] Boa aderência semântica a “traduzir requisitos de negócio”, SQL e construção de pipelines/fluxos (scraper + orquestrador + scoring + DB) com evidência recente. Falta sinal explícito de stack típica de Data Engineering enterprise (DW modeling, Airflow/dbt, cloud DWH, Spark), o que reduz ranking frente a candidatos “DE clássicos”. Para subir no ATS, adicionar bullets com modelagem dimensional, ELT/ETL, qualidade/linhagem de dados e uma seção “Data Engineering” com ferramentas específicas usadas. **Strengths:** SQL/PostgreSQL in production, Data pipelines + automation, Business-to-technical translation

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] The profile is very strong on backend (Go/Node/Python, REST APIs, databases, cloud basics) and communication, but the role demands deep hands-on experience with modern front-end frameworks and state management that is not present. ATS will heavily penalize missing React/Angular/Vue and Redux/MobX/Flux keywords for a "Senior Fullstack Engineer" title. To seriously target such roles, the person would need production-grade React/Vue work and to showcase it clearly. **Strengths:** Robust backend engineering with Go/Node/Python and REST APIs, Database design and optimization experience, Strong communication and client/stakeholder interaction skills **Critical Gaps:** Modern front-end framework expertise for highly interactive interfaces **Missing Required:** Demonstrated senior-level fullstack experience with strong front-end focus

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] This job blends advanced audio ML research (latent spaces, neural audio codecs, steerable speech models) with enterprise Lakehouse and Iceberg-based data engineering, none of which appear in the candidate’s background. While there is overlap on RAG pipelines, embeddings, and AI data systems, ATS will treat missing audio ML and Apache Iceberg/Lakehouse experience as major gaps. To approach roles like this, the person would need demonstrable neural audio, large-scale training, and Iceberg projects. **Strengths:** Experience with RAG pipelines and vector search, Strong AI/LLM integration and systems mindset, Background in data pipelines and security-conscious automation **Critical Gaps:** Specialized voice/audio ML research and codec experience, Enterprise Iceberg Lakehouse migration and optimization **Missing Required:** Production experience with large-scale audio ML systems and Iceberg-based Lakehouse data platforms

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] This research staff position is entirely focused on advanced audio ML problems such as latent space models, neural audio codecs, and generative speech, which are absent from the current profile. General LLM and RAG experience does not substitute for domain-specific audio research or large-scale training on speech datasets. Without concrete audio ML projects, ATS will assign a very low score. **Strengths:** Solid experience with LLM-based systems and embeddings, Ability to run rigorous experiments and validate results on smaller-scale AI problems, Strong systems and infrastructure thinking **Critical Gaps:** Deep research experience in voice/audio ML **Missing Required:** Proven track record building and publishing research in voice AI or audio ML

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] The person has strong experience designing AI-assisted systems, automation, and RAG-style workflows, overlapping partially with agentic AI and business workflow integration. However, there is no explicit background in owning large-scale ML models, advanced experimentation frameworks, or causal inference that an Applied Scientist II at a large company typically requires. Fit would be improved by demonstrating concrete ML models built, trained, and evaluated with clear metrics and closer alignment to AWS-scale data and experimentation. **Strengths:** Design of AI-assisted workflows and automation systems, Strong data analysis and quantitative background from finance/crypto, Experience with AWS fundamentals and LLM-based systems **Missing Required:** Demonstrated experience defining and shipping complex ML solutions in production environments

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] This role centers on training frontier-scale models across thousands of GPUs, optimizing distributed training systems, and advancing pre-training architectures, which are not present in the current background. The resume shows strong LLM API usage and systems architecture but no experience with large-scale model training, deep learning frameworks, or multi-node GPU infrastructure. Without substantial pre-training work, ATS will rank the application near the bottom. **Strengths:** Strong systems engineering and optimization mindset, Experience debugging and validating AI behavior in production through pipelines, Ability to design experiments and reason about performance and cost constraints **Critical Gaps:** Frontier-scale pre-training and GPU infrastructure expertise **Missing Required:** Demonstrated experience training and optimizing large AI models on distributed GPU systems

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Há match forte em LLM apps, RAG, embeddings e integração via APIs, com evidência recente e stack moderna. Porém a vaga é explicitamente P&D/Research com requisitos formais de titulação/anos em atividades de P&D, que o ATS tende a tratar como obrigatório e não inferível. Para melhorar, reescrever a experiência recente com framing de “pesquisa aplicada” (experimentos, métricas, baseline/ablation, documentação) e, se existir, listar publicações/relatórios técnicos e qualquer vínculo formal de P&D. **Strengths:** RAG + embeddings + vector search, LLM API integrations (Claude/Gemini/OpenAI), Production-grade automation and evaluation mindset **Missing Required:** Formal R&D/P&D experience requirement (10–14+ years) and/or advanced degree requirement

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] The candidate offers strong Linux, Bash, and Python skills plus general automation experience, all relevant to DevOps, but this Senior role is centered on Kubernetes cluster administration, Volcano GPU scheduling, and GPU workload optimization, none of which appear in the resume. ATS will not find critical keywords like Kubernetes, Volcano, or GPU cluster operations, heavily lowering the score. To align better, the person would need concrete Kubernetes cluster projects, ideally with GPU workloads, and to highlight them prominently. **Strengths:** Strong Linux and shell scripting abilities, Python automation experience, Background in optimizing systems for cost and performance **Critical Gaps:** Core Kubernetes/Volcano DevOps experience for AI compute clusters **Missing Required:** 2+ years of DevOps or infrastructure engineering in large-scale Kubernetes environments

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] This Senior DevOps role mirrors Job 11, again prioritizing Kubernetes, Volcano, and GPU infrastructure operations that are not represented in the resume. While Linux and scripting strengths are relevant, ATS will treat missing Kubernetes/Volcano and DevOps platform experience as major gaps. Without visible cluster and scheduler work, the overall match remains weak. **Strengths:** Linux, Bash, and Python automation experience, Ability to reason about performance and scheduling from a systems perspective, Background supporting AI-related workloads at smaller scale **Critical Gaps:** Hands-on Kubernetes/Volcano DevOps background for AI workloads **Missing Required:** Demonstrated DevOps experience in complex, large-scale Kubernetes environments

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] As a mid-level DevOps role, this position still demands substantial Kubernetes administration, Volcano experience, and GPU cluster operations that are currently absent from the resume. ATS will recognize Linux and scripting but not the required Kubernetes/Volcano stack or prior DevOps titles, keeping the score low. Alignment would require real-world Kubernetes cluster projects, preferably with GPU workloads, and clearer DevOps branding. **Strengths:** Python and Bash automation skills, Strong Linux background and performance sensitivity, Experience partnering with teams to improve workflows and utilization in smaller systems **Critical Gaps:** Practical Kubernetes and Volcano experience in production DevOps contexts **Missing Required:** 2+ years of DevOps or infrastructure engineering supporting large-scale Kubernetes environments

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] This mid-level DevOps role again prioritizes Kubernetes administration, Volcano GPU scheduling, and Python/UNIX shell automation in large-scale environments, which the current resume does not show. The person aligns on scripting and Linux but lacks Kubernetes/Volcano and explicit DevOps platform experience, leading ATS to assign a low score. Without visible cluster work, the match stays weak. **Strengths:** Automation with Python and shell scripting, Solid Linux systems understanding, Interest and experience in AI workloads that could later align with such platforms **Critical Gaps:** Production Kubernetes/Volcano DevOps experience for AI compute workloads **Missing Required:** Hands-on DevOps experience with Kubernetes-based GPU clusters in complex environments

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.1] This DevOps role again focuses on Kubernetes reliability, Volcano GPU scheduling, and Python/UNIX shell automation for AI and research compute platforms, which are not present in the profile. The resume matches on automation and Linux but lacks Kubernetes/Volcano and prior DevOps platform experience, leading ATS to down-rank it. Without concrete Kubernetes projects, there is a clear mismatch. **Strengths:** Strong automation skills with Python and Bash, Linux-first mindset and performance awareness, Background enabling AI workloads at smaller scale **Critical Gaps:** Practical experience operating Kubernetes/Volcano-based AI compute platforms **Missing Required:** Documented DevOps or infrastructure engineering experience in complex Kubernetes environments

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] ATS will reward Linux + Python/Bash automation and the demonstrated ability to build and operate production systems end-to-end. However, the JD demands expert Kubernetes administration plus hands-on Volcano + GPU cluster operations, which are not demonstrated (only listed generically). To improve, add concrete Kubernetes ops evidence (real cluster ownership, RBAC/quotas/PVC/NFS work) and only claim Volcano/GPU scheduling if there is real production experience. **Strengths:** Python + Bash automation, Strong Linux + production operations mindset, Go-based orchestration/state-machine systems thinking **Missing Required:** Volcano scheduler hands-on, GPU Kubernetes cluster operations, Expert Kubernetes administration (namespaces/RBAC/quotas/PVC/NFS) evidenced, 2+ years DevOps/infrastructure role (ATS-title match risk)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Strong alignment on Linux + Python/Bash automation and building operational systems. The role is explicitly centered on expert Kubernetes administration plus Volcano scheduling for GPU workloads, which is not evidenced in the resume. Improve by adding concrete K8s ownership details (RBAC/quotas/PVC/NFS incidents handled) and only include Volcano if actually used in production. **Strengths:** Python automation + scripting, Linux + deployment/operations experience, Systems/orchestration design (watchdogs, scheduling concepts) **Missing Required:** Volcano scheduler hands-on, GPU cluster operations (K8s + standalone nodes), Expert Kubernetes administration evidenced, 2+ years DevOps/infrastructure role (ATS match risk)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Senior expectations amplify the gap: the JD requires deep, hands-on Kubernetes administration plus Volcano scheduling and GPU cluster operations. The resume shows strong general infra/automation ability, but not the specific senior DevOps evidence (cluster ownership, observability, incidents, tuning at scale). Improve by adding measurable platform ops experience (SLOs, incidents, quotas, multi-node clusters, monitoring stack). **Strengths:** Linux + automation bias, Go + Python engineering capability, Operational mindset (watchdogs/state persistence concepts) **Missing Required:** Volcano hands-on, GPU cluster ops (K8s + standalone), Expert K8s administration evidenced, 3+ years DevOps/infrastructure role (ATS match risk)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] The automation + Linux strengths help, but the JD’s core is senior Kubernetes administration plus Volcano GPU scheduling in production. Those are not demonstrated, and senior roles penalize “listed but not shown” skills harder in ATS/human review. Improve by adding concrete K8s runbook/incidents, monitoring, and any real GPU scheduling outcomes if they exist. **Strengths:** Python + Bash automation, Linux + production deployment experience, Strong stakeholder communication for client-facing work **Missing Required:** Volcano hands-on, Expert K8s administration evidenced, GPU cluster ops evidenced, 3+ years DevOps/infrastructure role (ATS match risk)

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.2] ATS will like Go/Python/Docker, CI/CD familiarity, and the demonstrated ability to build real production systems quickly. The gaps are Terraform/IaC depth, GitLab CI/k8s tooling specifics, and explicit incident/outage postmortem experience (the role is incident-scenario driven). Improve by adding 2–3 concrete “incident narratives” (outage, scaling, secure deploy) and any Terraform/IaC artifacts (even small but real). **Strengths:** Go + Python engineering, Docker/Kubernetes-native concepts exposure, Strong systems thinking and automation bias **Missing Required:** Terraform (or equivalent IaC) evidenced, Hands-on DevOps/Backend years explicitly framed as such (ATS parsing risk)

[ANALYSIS_REPORT] **MEDIUM** [Copilot: GPT5.2] ATS will reward Python/Bash automation, Linux, CI/CD familiarity, and strong OAuth/OIDC knowledge (auth concepts transfer to IAM discussions). The role expects strong AWS + IaC + secrets/IAM depth for regulated data platforms, which isn’t evidenced beyond fundamentals. Improve by adding concrete AWS production scope (services used, scale, cost/security controls) and Terraform/IaC examples. **Strengths:** Python automation + scripting, OAuth2/OIDC understanding (auth patterns), Experience supporting AI/LLM-related workflows (integration + pipelines) **Missing Required:** Major cloud platform proficiency (AWS) evidenced, Infrastructure-as-Code (Terraform/CloudFormation) evidenced, IAM/secrets management depth evidenced, 5+ years cloud ops/DevOps/SRE explicitly evidenced (ATS risk)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Good match on Linux + Python/Bash automation and general infrastructure mindset. But the JD is tightly scoped to expert Kubernetes administration plus Volcano GPU scheduling and GPU cluster ops, which are not demonstrated. Improve by adding specific Kubernetes ownership (RBAC/quotas/PVC/NFS) and only claim Volcano/GPU scheduling if real. **Strengths:** Python + Bash automation, Linux + production system operation, Systems/orchestration engineering approach **Missing Required:** Volcano hands-on, GPU cluster ops evidenced, Expert K8s administration evidenced, 2+ years DevOps/infrastructure role (ATS-title match risk)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] Senior DevOps + Volcano/GPU scheduling requirements are not evidenced; ATS will treat generic Kubernetes listing as weak compared to proven cluster ownership. The resume is strong on Linux, automation, and systems design, but not on the exact senior Kubernetes/Volcano operational track record. Improve by adding real K8s operational achievements, monitoring stack, and incident handling if they exist. **Strengths:** Linux + automation, Go + Python proficiency, Operations-minded system design **Missing Required:** Volcano hands-on, GPU cluster ops evidenced, Expert K8s administration evidenced, 3+ years DevOps/infrastructure role (ATS match risk)

[ANALYSIS_REPORT] **LOW** [Copilot: GPT5.2] ATS will see some adjacency (Kubernetes/Docker awareness, AI tooling familiarity), but the JD is IBM Hybrid Cloud/Client Engineering-specific (OpenShift/ROKS/ROSA/ARO, watsonx deployments) and those signals are missing. Large-enterprise client engineering roles also penalize non-standard titles heavily. Improve only if there is real OpenShift/IBM stack work to add; otherwise it’s a mismatch. **Strengths:** General Kubernetes/Docker familiarity, Automation + systems mindset, AI/LLM integration exposure **Missing Required:** Hybrid Cloud platform experience (OpenShift ecosystem) evidenced, IBM software deployment (watsonx) evidenced, Client engineering pilot delivery experience evidenced