Applied AI Site Reliability Engineer II - PxE A&A

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. Must not include boilerplate like EEO etc. Must preserve all substantive info. We need to parse the posting. Sections likely: About the role (Role Overview), Key Responsibilities, Required Qualifications, maybe Benefits? Not present. Pay? Not present. Schedule? Not present (though mentions ability to work in local office min 3 days per week, travel 10%). That could be schedule? It's about work arrangement. Could be considered Schedule? The instruction: include a section ONLY when posting has real, specific content for it. The posting mentions "Ability to work in your local office at a minimum of 3 days per week" and "Ability to travel 10%". That's schedule/location info. Could be under a section like "Work Arrangement" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put schedule info under Schedule heading. Also maybe "Other" like travel, immigration sponsorship. Could go under Schedule or maybe Requirements? Probably Schedule. Also "Other: Ability to travel 10%... Limited immigration sponsorship may be available." That's other info; could be placed under Schedule as well or maybe under Requirements? Not exactly. We'll include Schedule heading with those details. Also "The team:" description could be part of About the role? Could be separate but not a standard heading. Could be included under About the role as prose. We need to preserve all substantive info. So we need to include Role Overview paragraph, then Responsibilities (list of responsibilities), then Required Qualifications (list), maybe Skills? The posting includes many skill items within qualifications. Could treat them as part of Qualifications. Or we could separate Skills heading for technical skills list. But we must not create thin sections. The qualifications list is extensive; we could keep as Qualifications. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. So no h3 for "Applied AI Site Reliability Engineer II". We'll start with About the role. Let's extract Role Overview paragraph: "As an Applied AI Site Reliability Engineer II , you will actively engage in your engineering craft, taking a hands-on approach to the reliability, performance, and operational integrity of high-visibility products and platforms and the environments they run in. Your expertise will be pivotal in keeping production safe, performant, and cost-effective, while driving tangible value for Deloitte's engineering investments. You will leverage your engineering craftsmanship across cloud platform engineering, observability, and performance and reliability engineering-together with applied AI fluency that lets you reliably operate AI and agentic workloads alongside the rest of the portfolio-consistently demonstrating your strong track record in operating high-quality, resilient systems at scale. The ideal candidate will be a dependable team player, collaborating with cross-functional teams to uphold production standards, safeguard environments, and support the admission of systems into production with confidence." That's prose. Then "Key Responsibilities:" followed by many bullet-like paragraphs. We need to turn each responsibility into list items. The responsibilities are grouped under headings like Outcome-Driven Accountability, Technical Leadership and Advocacy, Engineering Craftsmanship, Customer-Centric Engineering, Incremental and Iterative Delivery, Cross-Functional Collaboration and Integration, Advanced Technical Proficiency, Domain Expertise, Effective Communication and Influence, Engagement and Collaborative Co-Creation. Each has a paragraph. We'll treat each as a list item. We need to preserve all substantive info; we can keep the text as is inside

• . Then "The team:" paragraph. Could be part of About the role or separate. Might be better to include under About the role as additional prose. Then "The successful candidate will possess:" then list of interpersonal skills. That's maybe Requirements or Qualifications? It's more like soft skills. Could be under Requirements heading. But we already have Required Qualifications heading later. We could put interpersonal skills under Requirements (or Skills). The allowed headings include Requirements, Qualifications, Skills. We need to decide. The posting later has "Required Qualifications:" with bullet list of qualifications. That's clearly qualifications. Thus we can have: - About the role (includes Role Overview + The team paragraph) - Responsibilities (list) - Requirements (maybe interpersonal skills) - Qualifications (list of required qualifications) - Schedule (work arrangement, travel, immigration sponsorship) We must not create sections with filler. Ensure each has content. Now extract interpersonal skills: "Excellent interpersonal and organizational skills, with the ability to handle diverse situations, complex projects, and changing priorities, behaving with passion, empathy, and care." That's a sentence. Could be a list item under Requirements. Now Required Qualifications bullet list: many items. We'll turn each line into
• . Need to preserve all. Let's extract them: - A bachelor's degree in computer science, software engineering, data science, machine learning, or related discipline. - Experience is the most relevant factor. - 3+ years of software engineering and site reliability engineering experience operating large-scale, distributed, cloud-native systems in production, with experience in most of the following: Python, Go, Bash, Java, C#/.NET, SQL/NoSQL, Kubernetes, Terraform, ArgoCD, as well as CI/CD and observability stacks. - 2+ years of experience in site reliability or production engineering for large-scale systems-defining and owning SLIs, SLOs, and SLAs; error budgets; incident command and on-call; building and operating production observability (metrics, tracing, logging-e.g., OpenTelemetry, Prometheus, Grafana, Datadog, Dynatrace, Amazon CloudWatch, Azure Monitor, Google Cloud Operations, SolarWinds, Splunk); environment integrity and drift prevention across pre-production and production; and segregation-of-duties controls (least-privilege/RBAC, deploy approvals, secrets management) in partnership with security and risk. - 2+ years of experience with cloud-native engineering and cloud platform ownership on any of the cloud hyperscalers such as Azure, AWS, or GCP-including their AI/ML services such as Azure OpenAI, AWS Bedrock, or Vertex AI-plus container orchestration (Kubernetes, Docker), infrastructure-as-code, networking, and multi-environment management. - Prior experience operating AI/ML and agentic workloads in production-their reliability failure modes (drift, train/serve skew, output variance), MLOps/LLMOps, and the AI control plane (model/LLM gateway, guardrails) from the operability and performance side. - Prior experience with load and performance testing under simulated production traffic (e.g., LoadRunner, k6, or JMeter), chaos engineering (e.g., Azure Chaos Studio, AWS Fault Injector), capacity planning, autoscaling, and cloud/AI cost engineering (FinOps tooling/dashboards, including GPU/inference and token cost attribution). - Prior software engineering experience with the understanding of Business Context Diagrams (BCD), sequence/activity/state/entity relationship/data flow diagrams, OOP/OOD, data structures, algorithms, and code instrumentations, and AI-augmented spec-driven development. - Prior experience using methodologies & tools such as XP, Lean, DevSecOps, SRE, ADO, GitHub, SonarQube, MLflow, and agentic AI frameworks (e.g. LangFuse, LangSmith, or equivalent multi-agent orchestration tools) etc. to operate high-quality, resilient platforms and products at scale. Note: "Experience is the most relevant factor." is a sentence; we can keep as list item. Now Schedule section: "Ability to work in your local office at a minimum of 3 days per week", "Ability to travel 10%, on average, based on the work you do and products you build.", "Limited immigration sponsorship may be available." We'll put as list items. Now ensure we don't include boilerplate like EEO etc. Not present. Now produce HTML fragment. Structure:

  About the role

  Role overview paragraph...

  The team paragraph...

  Responsibilities

  • Outcome-Driven Accountability: ...
  ...

  Requirements

  • Excellent interpersonal and organizational skills, with the ability to handle diverse situations, complex projects, and changing priorities, behaving with passion, empathy, and care.

  Qualifications

  • A bachelor's degree in computer science, software engineering, data science, machine learning, or related discipline.
  ...

  Schedule

  • Ability to work in your local office at a minimum of 3 days per week.
  • Ability to travel 10%, on average, based on the work you do and products you build.
  • Limited immigration sponsorship may be available.
  Make sure to preserve all details exactly. Need to copy text precisely. Let's copy Role Overview paragraph exactly as given: "As an Applied AI Site Reliability Engineer II , you will actively engage in your engineering craft, taking a hands-on approach to the reliability, performance, and operational integrity of high-visibility products and platforms and the environments they run in. Your expertise will be pivotal in keeping production safe, performant, and cost-effective, while driving tangible value for Deloitte's engineering investments. You will leverage your engineering craftsmanship across cloud platform engineering, observability, and performance and reliability engineering-together with applied AI fluency that lets you reliably operate AI and agentic workloads alongside the rest of the portfolio-consistently demonstrating your strong track record in operating high-quality, resilient systems at scale. The ideal candidate will be a dependable team player, collaborating with cross-functional teams to uphold production standards, safeguard environments, and support the admission of systems into production with confidence." Note there is double space after "II ," but we keep as is. Now The team paragraph: "The team: US Deloitte Technology Product Engineering has modernized software and product delivery, creating a scalable, cost-effective model that focuses on value/outcomes that leverages a progressive and responsive talent structure. As Deloitte's primary internal development team, Product Engineering delivers innovative digital solutions to businesses, service lines, and internal operations with proven bottom-line results and outcomes. It helps power Deloitte's success. It is the engine that drives Deloitte, serving many of the world's largest, most respected companies. We develop and deploy cutting-edge internal and go-to-market solutions that help Deloitte operate effectively and lead in the market. Our reputation is built on a tradition of delivering with excellence." Copy exactly. Now responsibilities list items: need to copy each heading and its description. Let's extract each: Outcome-Driven Accountability: "Embrace and drive a culture of accountability for reliability, performance, and cost outcomes, measured in service-level objectives and error budgets, not raw uptime. Operate the products, platforms, and environments you support to meet their SLOs within budget, and track incident trends and toil to prioritize the work that most improves reliability-ensuring high-quality, lean operational designs that keep production safe and resilient." Technical Leadership and Advocacy: "Serve as the technical advocate for production reliability and operability, ensuring systems are admissible, performant, safe to run, and able to degrade gracefully when failure occurs. Uphold production standards, participate in the design of observability, performance and resilience testing, and operational tooling, and support the admission of systems into production-gating release on error budgets and automated reliability checks, and owning the readiness verification, environment integrity, and operational support that follow." Engineering Craftsmanship: "Maintain accountability for the operational integrity of production and pre-production environments, and for the production standards that systems are admitted against. Own SLOs and error budgets; build and operate production observability-cod