AI Engineer Lead

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We have content: Role Description, Job Description AI Engineer Lead Job Summary – We are seeking a skilled AI Engineer lead with AI and ML experience for Sunnyvale, CA location. Experience Required Minimum 8 to 10 years of experience as AI engineer lead. Responsibilities / Experience – list of responsibilities. Qualifications/Required Skills – list of qualifications. Preferred Skills – list. Behavioral Skills – list. About Mphasis – description. Other Details Salary range $63000 to $134500. We need to map to sections: About the role (maybe job summary + location + experience required). Responsibilities (list). Requirements (maybe experience required? but we have Qualifications/Required Skills and Preferred Skills and Behavioral Skills). Could combine Qualifications and Skills sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple headings as appropriate. We need to include sections only when posting has real specific content. We have content for About the role (job summary, location, experience required). Responsibilities (list). Qualifications/Required Skills (list). Preferred Skills (list). Behavioral Skills (list). About Mphasis (company description) maybe could be part of About the role? But we could put under "About the role" or separate "About the company". Not in list of allowed headings but we could put under About the role? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have Salary range -> Pay section. We have no explicit Benefits or Schedule info, so omit those sections. We have Requirements maybe could be the experience required (8-10 years). Could also include Qualifications as separate. But we have both Qualifications/Required Skills and Preferred Skills and Behavioral Skills. Could combine Qualifications and Skills? The instruction says prefer a few substantive sections over many thin ones. So we could combine Qualifications, Skills, Behavioral Skills into one "Qualifications" section, or separate "Qualifications" and "Skills". But we have both Qualifications/Required Skills and Preferred Skills and Behavioral Skills. Might be better to have "Qualifications" (required) and "Skills" (preferred + behavioral). However we need to avoid thin sections. Let's think: We have required qualifications list (Strong Engineering & Architecture Execution etc). Preferred skills list (Expertise with Claude Code etc). Behavioral skills list (Excellent Communication etc). Could combine all into one "Qualifications and Skills" section but headings limited to Qualifications or Skills. Could use "Qualifications" for required and preferred, and maybe include behavioral under same. Or we could have "Qualifications" (required) and "Skills" (preferred + behavioral). That seems reasonable. Thus sections: - About the role (job summary, location, experience required) - Responsibilities (list) - Qualifications (required qualifications list) - Skills (preferred skills + behavioral skills) - Pay (salary range) We must not include Benefits or Schedule. Now we need to format: Use

for each heading. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Must remove duplicated lines. Let's extract content precisely. Job Summary – We are seeking a skilled AI Engineer lead with AI and ML experience for Sunnyvale, CA location Experience Required Minimum 8 to 10 years of experience as AI engineer lead Responsibilities / Experience – list: - Lead service rationalization and decomposition across complex enterprise ecosystems - Design and build API-first, event-driven architectures - Contribute hands-on to domain services, integrations, and POCs - Enable service reuse through catalogs, standards, and governance - Drive incremental legacy modernization (strangler pattern) - Partner across global teams to influence a platform-first mindset - Build systems ready for AI agents, automation workflows, and future integrations Qualifications/Required Skills – list (looks like bullet points but not explicitly bullet; we need to parse): Strong Engineering & Architecture Execution Deep hands-on experience building and delivering production-grade systems in enterprise environments Expertise in microservices, APIs (REST/GraphQL), event-driven architecture (Kafka), and cloud platforms (AWS/Azure/GCP) Proven ability to move between architecture design, hands-on coding, and leading engineering teams with a pragmatic, delivery-focused mindset Service Decomposition & Enterprise Modernization Strong experience with domain-driven design (DDD), service decomposition, and distributed system design Hands-on track record breaking down monoliths/fragmented systems into reusable service layers Experience leading modernization efforts using incremental approaches (e.g., strangler pattern) with a focus on reuse, scalability, and clean service boundaries MCP Servers & Gen AI / Agent-Based Systems Proven experience building MCP server-based solutions and Gen AI agents from concept through production Strong understanding of designing systems for an agentic, AI-driven ecosystem Ability to integrate AI into service architectures and make platforms “agent-ready” for future automation and intelligence 4. Experience designing observability strategies: distributed tracing, structured logging, metrics dashboards Deep understanding of zero-trust architecture, API security, and identity federation Hands-on experience with CI CD pipeline design, GitOps workflows, and release engineering Ability to make and communicate well-reasoned architectural trade-offs. Note there is a "4." before Experience designing observability strategies. We'll keep as is. Preferred Skills list: Expertise with Claude Code or similar AI-assisted development tools Experience building service catalogs / internal developer platforms Background in highly distributed, multi-region enterprise environments Exposure to AI-driven automation workflows at scale Behavioral Skills list: Excellent Communication skills and collaboration skills Ability to propose and implement improvements in the system Ability to work with cross-functional stakeholders About Mphasis paragraph(s): Mphasis applies next-generation technology to help enterprises transform businesses globally. Customer centricity is foundational to Mphasis and is reflected in the Mphasis’ Front2Back™ Transformation approach. Front2Back™ uses the exponential power of cloud and cognitive to provide hyper-personalized (C=X2C2TM=1) digital experience to clients and their end customers. Mphasis’ Service Transformation approach helps ‘shrink the core’ through the application of digital technologies across legacy environments within an enterprise, enabling businesses to stay ahead in a changing world. Mphasis’ core reference architectures and tools, speed and innovation with domain expertise and specialization are key to building strong relationships with marquee clients. Other Details Salary range $63000 to $134500 We need to include About the role maybe incorporate About Mphasis? The heading "About the role" could include job summary and location and experience required. The About Mphasis description is about company; could be included under About the role or maybe we could add a separate section but not in allowed headings. Probably best to include it under About the role as part of role description (company context). So About the role section will contain job summary paragraph, location, experience required, and About Mphasis description. We must not repeat job title as heading. Good. Now produce HTML:

  About the role

  We are seeking a skilled AI Engineer lead with AI and ML experience for Sunnyvale, CA location. Minimum 8 to 10 years of experience as AI engineer lead.

  Mphasis applies next-generation technology to help enterprises transform businesses globally. Customer centricity is foundational to Mphasis and is reflected in the Mphasis’ Front2Back™ Transformation approach. Front2Back™ uses the exponential power of cloud and cognitive to provide hyper-personalized (C=X2C2TM=1) digital experience to clients and their end customers. Mphasis’ Service Transformation approach helps ‘shrink the core’ through the application of digital technologies across legacy environments within an enterprise, enabling businesses to stay ahead in a changing world. Mphasis’ core reference architectures and tools, speed and innovation with domain expertise and specialization are key to building strong relationships with marquee clients.

  Then Responsibilities:

  Responsibilities

  • Lead service rationalization and decomposition across complex enterprise ecosystems
  • Design and build API-first, event-driven architectures
  • Contribute hands-on to domain services, integrations, and POCs
  • Enable service reuse through catalogs, standards, and governance
  • Drive incremental legacy modernization (strangler pattern)
  • Partner across global teams to influence a platform-first mindset
  • Build systems ready for AI agents, automation workflows, and future integrations
  Qualifications:

  Qualifications

  • Strong Engineering & Architecture Execution
  • Deep hands-on experience building and delivering production-grade systems in enterprise environments
  • Expertise in microservices, APIs (REST/GraphQL), event-driven architecture (Kafka), and cloud platforms (AWS/Azure/GCP)
  • Proven ability to move between architecture design, hands-on coding, and leading engineering teams with a pragmatic, delivery-focused mindset
  • Service Decomposition & Enterprise Modernization
  • Strong experience with domain-driven design (DDD), service decomposition, and distributed system design
  • Hands-on track record breaking down monoliths/fragmented systems into reusable service layers
  • Experience leading modernization efforts using incremental approaches (e.g., strangler pattern) with a focus on reuse, scalability, and clean service boundaries
  • MCP Servers & Gen AI / Agent-Based Systems
  • Proven experience building MCP server-based solutions and Gen AI agents from concept through production
  • Strong understanding of designing systems for an agentic, AI-driven ecosystem
  • Ability to integrate AI into service architectures and make platforms “agent-ready” for future automation and intelligence
  • Experience designing observability strategies: distributed tracing, structured logging, metrics dashboards
  • Deep understanding of zero-trust architecture, API security, and identity federation
  • Hands-on experience with CI CD pipeline design, GitOps workflows, and release engineering
  • Ability to make and communicate well-reasoned architectural trade-offs
  Skills:

  Skills

  • Expertise with Claude Code or similar AI-assisted development tools
  • Experience building service catalogs / internal developer platforms
  • Background in highly distributed, multi-region enterprise environments
  • Exposure to AI-driven automation workflows at scale
  • Excellent Communication skills and collaboration skills
  • Ability to propose and implement improvements in the system
  • Ability to work with cross-functional stakeholders
  Pay:

  Pay

  Salary range $63000 to $134500

  We must not include Benefits or Schedule. Check for any boilerplate: We removed EEO, legal, etc. Also removed "Other Details" heading. Good. Now ensure no duplicate lines. All content present. Check that we didn't miss any substantive info: The job summary includes location and experience required. We included that. The About Mphasis description included. Responsibilities all present. Qualifications list includes all items. Note there is a "4." before Experience designing observability strategies; we kept as list item without the number? We wrote "Experience designing observability strategies