DirectJobHub
Jobs · Georgia

Senior AI Ops / DevOps Engineer (FTE / Hybrid)

NTT DATA North America · Atlanta, GA · 4 wk ago
$98k–$163k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract content. The posting includes: - Intro: NTT DATA strives... (maybe not needed) - "We are currently seeking a Senior AI Ops / DevOps Engineer (FTE / Hybrid) to join our team in Atlanta, Georgia (US-GA), United States (US)." This is location info; could be part of About the role? Probably not needed as heading. - "Day To Day Job Duties" then a long paragraph describing duties. That's responsibilities. - Then "Basic Qualifications" list. - Then "Preferred / Nice To Have" list. - Then "Soft Skills & Mindset" list. - Then "Travel" line: "This position requires 3 days in office per the client/project requirement." That's schedule? Actually schedule: 3 days in office per week? Could be schedule. - Then "Degree" line: Bachelor’s degree... That's qualifications. - Then "Summary" paragraph. - Then Pay: "NTT DATA provides a reasonable range of compensation for U.S.-based positions. The starting pay range for this role is $97,725.00 - $162,580.00. Actual compensation will depend on a number of factors, including the candidate’s relevant experience, technical skills, and other qualifications. This position may also be eligible for incentive compensation based on individual and/or company performance." - Then Benefits: "This position is eligible for company benefits including medical, dental, and vision insurance with an employer contribution, flexible spending or health savings account, life and AD&D insurance, short and long term disability coverage, paid time off, employee assistance, participation in a 401k program with company match, and additional voluntary or legally-required benefits." - Then "About NTT DATA" paragraph (company description). Could be About the role? Actually About the role is about the job; About NTT DATA is company info. Might be considered About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summary of role). Responsibilities (day to day duties). Requirements (basic qualifications). Qualifications (maybe degree? but could combine). Skills (maybe preferred/nice to have + soft skills). Benefits, Pay, Schedule. We must not repeat job title as heading. Also not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can organize into sections. We must not include boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the EEO statements, the accessibility statements, the recruiter warning, etc. Also cut out the "About NTT DATA" maybe? It's not boilerplate; it's substantive about company. Could be included under About the role? But the heading "About the role" maybe expects description of the role, not company. However we could treat "About NTT DATA" as part of About the role? Might be okay. But we need to decide. We should include: - About the role: maybe a brief summary: "Senior AI Ops / DevOps Engineer (FTE / Hybrid) in Atlanta, GA. Role focuses on architecting AI-driven CI/CD, MCP integration, etc." Could combine the summary paragraph. But we must not invent; we can use the Summary paragraph as About the role. - Responsibilities: the Day To Day Job Duties paragraph (multiple sentences). Could break into
  • items? The instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. The duties are a paragraph; we could keep as

      . But we could also split into list items if they are separate duties. However the instruction says use list for any list of duties/requirements/benefits. The duties are enumerated via sentences but not explicit list. Safer to keep as

      (prose). However we could also convert each sentence to

    • but that might be inventing structure. Better to keep as

      . - Requirements: Basic Qualifications list (multiple bullet-like sentences). Use

      • . - Qualifications: Degree line maybe? Could be part of Requirements. But we have both Requirements and Qualifications headings. We could put Basic Qualifications under Requirements, and Degree under Qualifications. Or combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But headings are predefined; we can choose to include only those with content. Could include Requirements (basic qualifications + degree) and Skills (preferred/nice to have + soft skills). Then Benefits, Pay, Schedule. Let's decide: Sections: - About the role: include the summary paragraph (maybe also location). Use

        . - Responsibilities: Day To Day Job Duties paragraph(s). Use

        . - Requirements: Basic Qualifications list (the bullet points). Use

        • . - Skills: Preferred/Nice To Have list + Soft Skills & Mindset list. Could combine into one
          • (maybe separate subheadings? Not allowed). We'll just list all items. - Benefits: benefits paragraph. - Pay: pay range paragraph. - Schedule: Travel line (3 days in office). Could be schedule. We must not include headings with filler. All have content. Now we need to strip boilerplate: Remove the intro about NTT DATA strives..., the "We are currently seeking..." maybe part of About the role? Actually that line includes location and role. Could be part of About the role. We'll include location in About the role. We must remove the "About NTT DATA" company description? That's not boilerplate but maybe not needed for the role. Could be omitted as not directly about role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The About NTT DATA is substantive about company; but is it required? It's not about the role but about the employer. Might be considered substantive. However the headings we have don't include a company section. Could we add a heading "About the company"? Not in allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. So we must either incorporate that info into one of those sections or drop it. The instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid dropping content, but also says "Preserve ALL substantive information". So we must keep all substantive info. If we drop About NTT DATA, we lose substantive info. But we could incorporate it into About the role? That section is about the role, not company. However we could treat About the role as including company context? Might be a stretch but maybe acceptable. The instruction says use headings e.g. About the role, Responsibilities... It doesn't forbid adding other headings, but says "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a heading like "About NTT DATA" if we want. But the examples limited to those. Safer to stick to those headings and incorporate company info into About the role? Might be considered not accurate but we need to preserve info. Perhaps we can add a section "About the company" as a heading, but it's not in the examples; risk of being considered not following instruction. Better to incorporate into About the role as a brief note: "NTT DATA is a $30 billion business and technology services leader..." This is substantive about the employer, but could be considered part of About the role (the role at NTT DATA). I'll include it in About the role paragraph. Now we need to ensure we don't include duplicated lines, cookie/navigation/legal/EEO etc. Remove the EEO statements, the accessibility statements, the recruiter warning, the "NTT DATA recruiters will never ask for payment..." etc. Also remove the "For Pay Transparency information, please click here." etc. Also remove the "This contact information is for accommodation requests only..." etc. Also remove the "At NTT DATA, we are committed to staying flexible..." maybe not boilerplate but could be considered generic; but it's about work arrangements. Might be considered substantive? It's about hybrid work expectations. Could be part of Schedule? Actually schedule already covers 3 days in office. The flexible statement is generic; maybe we can drop as boilerplate-ish. Safer to drop. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

            About the role

            Senior AI Ops / DevOps Engineer (FTE / Hybrid) based in Atlanta, Georgia. NTT DATA is a $30 billion business and technology services leader, serving 75% of the Fortune Global 100. The ideal candidate is a senior hands-on DevOps engineer with strong cloud, automation, Kubernetes, and CI/CD expertise, combined with practical experience applying AI, LLM agents, and MCP-based integrations to modern engineering workflows. This role will help create a secure AI-driven delivery ecosystem that accelerates software engineering velocity while maintaining strong governance, reliability, auditability, and operational control.

            Responsibilities

            [the long duties paragraph]

            Requirements

            • Minimum 7+ years of experience in DevOps, Cloud Engineering, SRE, Platform Engineering, or Infrastructure Automation.
            • Minimum 4+ years of hands-on experience designing and managing CI/CD pipelines using GitHub Actions, GitLab CI, CircleCI, Jenkins, ArgoCD, or similar platforms.
            • Minimum 3+ years of experience managing scalable cloud environments in AWS, Azure, or GCP, with strong preference for AWS.
            • Strong hands-on experience with Kubernetes, Docker, and production container orchestration platforms such as EKS, AKS, or GKE.
            • Advanced proficiency with Infrastructure as Code tools such as Terraform, OpenTofu, Terragrunt, Pulumi, CloudFormation, or Crossplane.
            • Strong programming and scripting experience using Python, TypeScript, JavaScript, Bash, or Go.
            • Practical experience working with LLM APIs such as OpenAI, Anthropic, or similar enterprise AI platforms.
            • Experience with AI orchestration or agentic frameworks such as LangChain, CrewAI, LlamaIndex, or similar tools.
            • Strong understanding of the Model Context Protocol ecosystem and experience designing or integrating MCP clients and servers.
            • Experience integrating DevSecOps controls into CI/CD pipelines, including SAST, DAST, dependency scanning, container scanning, secrets scanning, and vulnerability management.
            • Strong knowledge of secret management and security tooling such as HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, or similar platforms.
            • Experience with observability, monitoring, logging, and alerting platforms such as Datadog, Prometheus, Grafana, CloudWatch, Splunk, Dynatrace, or ELK.
            • Familiarity with security and compliance frameworks such as SOC2, ISO27001, or enterprise audit control environments.
            • Ability to troubleshoot complex pipeline, infrastructure, deployment, and production issues across cloud-native environments

Similar jobs