Lead Infrastructure Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have Responsibilities (Key Responsibilities). Requirements/Qualifications (Required Qualifications). Preferred Qualifications maybe under Skills? Could be separate but we can include under Skills or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Required and Preferred Qualifications into a Qualifications section with sublists? But we need to preserve all substantive info; we can have two subsections under Qualifications? However headings only h3; we could have Qualifications
then inside we can have ? Not allowed? Only h3 for section headings; but we can still use or for subheadings. Better to keep separate sections: Responsibilities, Requirements, Qualifications, Skills, About the role? Actually About the role could be company overview? But we have Company Overview and About NTT DATA. Could combine as About the role? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include those headings only if we have content. We have Responsibilities (yes). Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe list of skills like scripting, IaC, etc). About the role could be Company Overview? But we also have About NTT DATA which is about company. Could treat as About the role? Might be redundant. However we need to preserve all substantive info; we can include About NTT DATA as a paragraph under About the role? Or we could make a section About NTT DATA but not in allowed headings; but we could still use About NTT DATA
though not in list but maybe okay? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Safer to stick to those examples. So we need to map content to those headings.
We have:
- About the role: could be a brief description of the role (maybe from Job Description intro). The posting includes "Job Description:" then bullet points. Could use a paragraph summarizing role: Systems Integration Advisor (Lead Infrastructure Engineer). We'll include a
describing role.
- Responsibilities: list of duties from Key Responsibilities (multiple bullet points). We'll output
- each.
- Requirements: Required Qualifications (list). We'll output
- .
- Qualifications: Preferred Qualifications (list). We'll output
- .
- Skills: maybe we can extract skills like scripting, IaC, GitOps, etc. But we already have them in qualifications. Could combine but we need to avoid thin sections. Perhaps we skip Skills section and put skills within Qualifications. But instruction: Prefer a few substantive sections over many thin ones. So we could have only About the role, Responsibilities, Requirements, Qualifications (combining required and preferred), and About NTT DATA? But About NTT DATA not in list; maybe we can treat as About the role? Actually About the role could include company overview. But we have both Company Overview and About NTT DATA. Could combine them into About the role section.
Thus sections:
About the role
Company overview + role description.
Responsibilities
...
Requirements
...
(Required Qualifications)
Qualifications
...
(Preferred Qualifications)
We should not include Benefits, Pay, Schedule as not present.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the EEO statements, accessibility link, etc. Also remove "Req ID: 387345" maybe minor metadata; we can fold into a short or drop it. Probably drop it.
We need to preserve all substantive information: responsibilities, required qualifications, preferred qualifications, impact of the role, about NTT DATA, company overview.
We also have "Impact of the Role" section; we could include that as part of About the role or as a separate section? Not in list but could be included under About the role as paragraph.
Thus About the role paragraph will include: Company Overview description, role title, location, impact.
Let's craft.
Company Overview: "NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now. We are currently seeking a Systems Integration Advisor to join our team in irving, Texas (US-TX), United States (US)."
Impact of the Role: "As a Lead Infrastructure Engineer, you will directly shape the reliability, scalability, and usability of our infrastructure platforms. Your work will accelerate Kubernetes adoption, expand automation, and improve engineering productivity across the organization. Through modern IaC, GitOps practices, and self‐service capabilities, you will help deliver a secure, efficient, and developer‑friendly platform that supports mission‑critical workloads."
About NTT DATA: description of NTT DATA.
We'll combine these into About the role paragraph(s). Could be multiple
tags.
Now Responsibilities: list each bullet from Key Responsibilities.
Let's extract them:
- Build and maintain Kubernetes platforms, including cluster operations, add‐ons, curated Helm charts, and deployment standards.
- Develop reusable infrastructure modules and templates using Terraform, Ansible, or similar IaC tools.
- Support hybrid cloud infrastructure (Azure or GCP) following established architectural guidelines.
- Contribute to workload migration initiatives from virtual machines to containerized environments.
- Implement declarative, API‐driven infrastructure patterns aligned with GitOps workflows.
- Automate provisioning, configuration, and platform lifecycle tasks to reduce manual operations and improve stability.
- Leverage observability tooling (Prometheus, Grafana, logs, tracing) to improve performance monitoring and incident response.
- Participate in on‐call rotations, root‐cause analysis, and reliability‐focused improvements.
- Maintain cluster security, RBAC, policy enforcement, and compliance controls in collaboration with security teams.
- Design and implement GitOps workflows using tools such as ArgoCD or RHACM.
- Build and maintain self‐service platform capabilities (APIs, templates, automation pipelines) to reduce friction for development teams.
- Integrate infrastructure automation with CI/CD systems (GitHub Actions, Tekton, etc.).
- Provide guidance and onboarding support to teams adopting Kubernetes, including documentation, templates, and golden paths.
- Mentor junior engineers and contribute to knowledge‐sharing across the engineering organization.
- Participate in code reviews, architecture discussions, and cross‐team collaboration.
- Work closely with networking, security, and application teams to deliver compliant and scalable solutions.
That's all.
Now Required Qualifications list:
- 5+ years of experience in infrastructure, platform engineering, or DevOps roles (or equivalent via education, training, or military experience).
- 2+ years of hands‐on Kubernetes experience (cluster operations, deployment tooling, troubleshooting).
- 3+ years of experience with IaC tools such as Terraform, Ansible, or Tekton.
- 3+ years working with GitOps principles and tools (ArgoCD, GitHub Actions, RHACM).
- Experience with container orchestration, hybrid cloud platforms (Azure, GCP), and Linux systems.
- Proficiency in scripting (Python, Bash, PowerShell).
- Experience designing or consuming RESTful APIs and integrating automation into platform workflows.
- Solid understanding of networking fundamentals, security best practices, and compliance considerations.
Preferred Qualifications list:
- Familiarity with service mesh technologies (Istio, OSSM).
- Exposure to image management tooling (Packer, Image Builder).
- Experience with developer portals (Backstage) or internal platform tooling.
- Background building platform engineering or cloud‑native enablement solutions.
- Experience with observability stacks (Prometheus, Grafana, Splunk).
- A developer‑first mindset focused on reducing friction and streamlining delivery.
Now we need to output HTML fragment only.
We'll wrap sections in maybe not required. Just output headings and content.
Let's craft:
About the role
NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now. We are currently seeking a Systems Integration Advisor to join our team in Irving, Texas (US-TX), United States (US).
As a Lead Infrastructure Engineer, you will directly shape the reliability, scalability, and usability of our infrastructure platforms. Your work will accelerate Kubernetes adoption, expand automation, and improve engineering productivity across the organization. Through modern IaC, GitOps practices, and self‑service capabilities, you will help deliver a secure, efficient, and developer‑friendly platform that supports mission‑critical workloads.
NTT DATA is a $30 billion trusted global innovator of business and technology services. We serve 75% of the Fortune Global 100 and are committed to helping clients innovate, optimize and transform for long term success. As a Global Top Employer, we have diverse experts in more than 50 countries and a robust partner ecosystem of established and start‑up companies. Our services include business and technology consulting, data and artificial intelligence, industry solutions, as well as the development, implementation and management of applications, infrastructure and connectivity. We are one of the leading providers of digital and AI infrastructure in the world. NTT DATA is a part of NTT Group, which invests over $3.6 billion each year in R&D to help organizations and society move confidently and sustainably into the digital future.
Responsibilities
- Build and maintain Kubernetes platforms, including cluster operations, add‑ons, curated Helm charts, and deployment standards.
- Develop reusable infrastructure modules and templates using Terraform, Ansible, or similar IaC tools.
- Support hybrid cloud infrastructure (Azure or GCP) following established architectural guidelines.
- Contribute to workload migration initiatives from virtual machines to containerized environments.
- Implement declarative, API‑driven infrastructure patterns aligned with GitOps workflows.
- Automate provisioning, configuration, and platform lifecycle tasks to reduce manual operations and improve stability.
- Leverage observability tooling (Prometheus, Grafana, logs, tracing) to improve performance monitoring and incident response.
- Participate in on‑call rotations, root‑cause analysis, and reliability‑focused improvements.
- Maintain cluster security, RBAC, policy enforcement, and compliance controls in collaboration with security teams.
- Design and implement GitOps workflows using tools such as ArgoCD or RHACM.
- Build and maintain self‑service platform capabilities (APIs, templates, automation pipelines) to reduce friction for development teams.
- Integrate infrastructure automation with CI/CD systems (GitHub Actions, Tekton, etc.).
- Provide guidance and onboarding support to teams adopting Kubernetes, including documentation, templates, and golden paths.
- Mentor junior engineers and contribute to knowledge‑sharing across the engineering organization.
- Participate in code reviews, architecture discussions,
for subheadings. Better to keep separate sections: Responsibilities, Requirements, Qualifications, Skills, About the role? Actually About the role could be company overview? But we have Company Overview and About NTT DATA. Could combine as About the role? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include those headings only if we have content. We have Responsibilities (yes). Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe list of skills like scripting, IaC, etc). About the role could be Company Overview? But we also have About NTT DATA which is about company. Could treat as About the role? Might be redundant. However we need to preserve all substantive info; we can include About NTT DATA as a paragraph under About the role? Or we could make a section About NTT DATA but not in allowed headings; but we could still use About NTT DATA
though not in list but maybe okay? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Safer to stick to those examples. So we need to map content to those headings.
We have:
- About the role: could be a brief description of the role (maybe from Job Description intro). The posting includes "Job Description:" then bullet points. Could use a paragraph summarizing role: Systems Integration Advisor (Lead Infrastructure Engineer). We'll include a
describing role. - Responsibilities: list of duties from Key Responsibilities (multiple bullet points). We'll output
- each.
- Requirements: Required Qualifications (list). We'll output
- .
- Qualifications: Preferred Qualifications (list). We'll output
- .
- Skills: maybe we can extract skills like scripting, IaC, GitOps, etc. But we already have them in qualifications. Could combine but we need to avoid thin sections. Perhaps we skip Skills section and put skills within Qualifications. But instruction: Prefer a few substantive sections over many thin ones. So we could have only About the role, Responsibilities, Requirements, Qualifications (combining required and preferred), and About NTT DATA? But About NTT DATA not in list; maybe we can treat as About the role? Actually About the role could include company overview. But we have both Company Overview and About NTT DATA. Could combine them into About the role section.
Thus sections:
About the role
Company overview + role description.
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
or drop it. Probably drop it. We need to preserve all substantive information: responsibilities, required qualifications, preferred qualifications, impact of the role, about NTT DATA, company overview. We also have "Impact of the Role" section; we could include that as part of About the role or as a separate section? Not in list but could be included under About the role as paragraph. Thus About the role paragraph will include: Company Overview description, role title, location, impact. Let's craft. Company Overview: "NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now. We are currently seeking a Systems Integration Advisor to join our team in irving, Texas (US-TX), United States (US)." Impact of the Role: "As a Lead Infrastructure Engineer, you will directly shape the reliability, scalability, and usability of our infrastructure platforms. Your work will accelerate Kubernetes adoption, expand automation, and improve engineering productivity across the organization. Through modern IaC, GitOps practices, and self‐service capabilities, you will help deliver a secure, efficient, and developer‑friendly platform that supports mission‑critical workloads." About NTT DATA: description of NTT DATA. We'll combine these into About the role paragraph(s). Could be multiple
tags. Now Responsibilities: list each bullet from Key Responsibilities. Let's extract them: - Build and maintain Kubernetes platforms, including cluster operations, add‐ons, curated Helm charts, and deployment standards. - Develop reusable infrastructure modules and templates using Terraform, Ansible, or similar IaC tools. - Support hybrid cloud infrastructure (Azure or GCP) following established architectural guidelines. - Contribute to workload migration initiatives from virtual machines to containerized environments. - Implement declarative, API‐driven infrastructure patterns aligned with GitOps workflows. - Automate provisioning, configuration, and platform lifecycle tasks to reduce manual operations and improve stability. - Leverage observability tooling (Prometheus, Grafana, logs, tracing) to improve performance monitoring and incident response. - Participate in on‐call rotations, root‐cause analysis, and reliability‐focused improvements. - Maintain cluster security, RBAC, policy enforcement, and compliance controls in collaboration with security teams. - Design and implement GitOps workflows using tools such as ArgoCD or RHACM. - Build and maintain self‐service platform capabilities (APIs, templates, automation pipelines) to reduce friction for development teams. - Integrate infrastructure automation with CI/CD systems (GitHub Actions, Tekton, etc.). - Provide guidance and onboarding support to teams adopting Kubernetes, including documentation, templates, and golden paths. - Mentor junior engineers and contribute to knowledge‐sharing across the engineering organization. - Participate in code reviews, architecture discussions, and cross‐team collaboration. - Work closely with networking, security, and application teams to deliver compliant and scalable solutions. That's all. Now Required Qualifications list: - 5+ years of experience in infrastructure, platform engineering, or DevOps roles (or equivalent via education, training, or military experience). - 2+ years of hands‐on Kubernetes experience (cluster operations, deployment tooling, troubleshooting). - 3+ years of experience with IaC tools such as Terraform, Ansible, or Tekton. - 3+ years working with GitOps principles and tools (ArgoCD, GitHub Actions, RHACM). - Experience with container orchestration, hybrid cloud platforms (Azure, GCP), and Linux systems. - Proficiency in scripting (Python, Bash, PowerShell). - Experience designing or consuming RESTful APIs and integrating automation into platform workflows. - Solid understanding of networking fundamentals, security best practices, and compliance considerations. Preferred Qualifications list: - Familiarity with service mesh technologies (Istio, OSSM). - Exposure to image management tooling (Packer, Image Builder). - Experience with developer portals (Backstage) or internal platform tooling. - Background building platform engineering or cloud‑native enablement solutions. - Experience with observability stacks (Prometheus, Grafana, Splunk). - A developer‑first mindset focused on reducing friction and streamlining delivery. Now we need to output HTML fragment only. We'll wrap sections in maybe not required. Just output headings and content. Let's craft:
About the role
NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now. We are currently seeking a Systems Integration Advisor to join our team in Irving, Texas (US-TX), United States (US).
As a Lead Infrastructure Engineer, you will directly shape the reliability, scalability, and usability of our infrastructure platforms. Your work will accelerate Kubernetes adoption, expand automation, and improve engineering productivity across the organization. Through modern IaC, GitOps practices, and self‑service capabilities, you will help deliver a secure, efficient, and developer‑friendly platform that supports mission‑critical workloads.
NTT DATA is a $30 billion trusted global innovator of business and technology services. We serve 75% of the Fortune Global 100 and are committed to helping clients innovate, optimize and transform for long term success. As a Global Top Employer, we have diverse experts in more than 50 countries and a robust partner ecosystem of established and start‑up companies. Our services include business and technology consulting, data and artificial intelligence, industry solutions, as well as the development, implementation and management of applications, infrastructure and connectivity. We are one of the leading providers of digital and AI infrastructure in the world. NTT DATA is a part of NTT Group, which invests over $3.6 billion each year in R&D to help organizations and society move confidently and sustainably into the digital future.
Responsibilities
- Build and maintain Kubernetes platforms, including cluster operations, add‑ons, curated Helm charts, and deployment standards.
- Develop reusable infrastructure modules and templates using Terraform, Ansible, or similar IaC tools.
- Support hybrid cloud infrastructure (Azure or GCP) following established architectural guidelines.
- Contribute to workload migration initiatives from virtual machines to containerized environments.
- Implement declarative, API‑driven infrastructure patterns aligned with GitOps workflows.
- Automate provisioning, configuration, and platform lifecycle tasks to reduce manual operations and improve stability.
- Leverage observability tooling (Prometheus, Grafana, logs, tracing) to improve performance monitoring and incident response.
- Participate in on‑call rotations, root‑cause analysis, and reliability‑focused improvements.
- Maintain cluster security, RBAC, policy enforcement, and compliance controls in collaboration with security teams.
- Design and implement GitOps workflows using tools such as ArgoCD or RHACM.
- Build and maintain self‑service platform capabilities (APIs, templates, automation pipelines) to reduce friction for development teams.
- Integrate infrastructure automation with CI/CD systems (GitHub Actions, Tekton, etc.).
- Provide guidance and onboarding support to teams adopting Kubernetes, including documentation, templates, and golden paths.
- Mentor junior engineers and contribute to knowledge‑sharing across the engineering organization.
- Participate in code reviews, architecture discussions,
- .
- Skills: maybe we can extract skills like scripting, IaC, GitOps, etc. But we already have them in qualifications. Could combine but we need to avoid thin sections. Perhaps we skip Skills section and put skills within Qualifications. But instruction: Prefer a few substantive sections over many thin ones. So we could have only About the role, Responsibilities, Requirements, Qualifications (combining required and preferred), and About NTT DATA? But About NTT DATA not in list; maybe we can treat as About the role? Actually About the role could include company overview. But we have both Company Overview and About NTT DATA. Could combine them into About the role section.
Thus sections:
- .
- Qualifications: Preferred Qualifications (list). We'll output