AI Native Software Engineering Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (maybe combine "We are" and "You are" and "The Work"?), Responsibilities, Requirements (maybe "Here’s What You Need:"), Qualifications (maybe same as Requirements? but we need to avoid duplication). Skills maybe from bonus points? Benefits, Pay, Schedule.
We must not create sections with filler. So we need to see if we have actual content for each.
- About the role: we have description of company and role: "We are: A forward-thinking services company..." and "You are: An AI Native Engineer..." and "The Work: You’ll embed directly with clients..." That seems substantive. So we can put that under About the role.
- Responsibilities: we have a list under "Responsibilities:" with bullet points. Good.
- Requirements: we have "Here’s What You Need:" list with minimum years etc. That's requirements.
- Qualifications: maybe we could separate education: "Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate Degree, must have minimum 6 years work experience)". That's qualification. Could also include bonus points as Skills? But we have "Bonus Points If:" which could be Skills or Qualifications. The instruction says we can have Skills section. So we could put bonus points under Skills.
- Benefits: we have "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture". That's substantive.
- Pay: we have compensation info with salary ranges per location. That's substantive. So we can include Pay section.
- Schedule: we have travel may be required, amount varies 0-100%. That's schedule? Could be considered schedule (travel). Also maybe no explicit schedule like full-time/part-time. But we have travel info. So we can include Schedule section with that.
We must not include boilerplate: EEO, accommodation request, equal opportunity statement, other employment statements, etc. Must remove those.
Also must not include duplicated lines. Ensure we preserve all substantive info from the sections we keep.
We need to format using for headings, - for lists,
for prose.
We must not include markdown code fences. Just raw HTML.
Let's extract content.
About the role: combine:
"We are: A forward-thinking services company at the forefront of AI-native innovation. We partner with enterprise clients to create next-generation, agent-powered workflows engineered to scale in real-world settings. Our engineers embed deeply with customers, moving projects beyond experimentation into operational reality.
You are: An AI Native Engineer with a minimum of 5 years of experience building cloud-native solutions, and deep expertise in designing and deploying agentic systems, especially for enterprise environments. You are a critical thinker that thrives in ambiguity, delivering concrete results by designing, building, and running custom AI agents that augment workflows and scale across modern infrastructure. You’ll help shape the playbook for how enterprises adopt and scale AI-native engineering globally.
The Work: You’ll embed directly with clients — acting as both technologist and trusted advisor. You’ll partner with stakeholders to define use cases, rapidly prototype, and deploy agentic workflows that are robust, secure, and operational in complex enterprise domains. Often, these will be completely net new platforms and systems that need to be stitched together in our clients' environments alongside our Ecosystem partners."
We need to preserve all substantive info; we can keep as paragraphs.
Responsibilities: list items:
- Agent Architecture and Engineering: Design and engineer enterprise-ready AI agents encompassing retrieval, orchestration, policy-based routing, tool invocation, evaluation harnesses, and lifecycle observability.
- AI Platform Integration: Develop abstraction layers across AI providers (Anthropic, Google, OpenAI, etc. ) to enable seamless integration and enablement.
- Cloud-Native Engineering: Leverage containerization (Kubernetes, Docker), microservices, serverless, event-driven architectures, CI/CD, and observability to deliver scalable AI-native systems.
- Domain-Specific Workflows: Tailor and deploy agentic applications across verticals — e.g., finance, healthcare, retail — addressing domain-specific processes via intelligent automation.
- Client Engagement: Conduct design workshops, POCs, and code-with sessions to shape data-driven agent workflows with stakeholders, fostering trust and adoption.
- Measure & Improve: Define and use key metrics, test harnesses, and evaluation plans to measure agent accuracy, latency, safety, and cost effectiveness.
- Knowledge Sharing: Craft reusable patterns, documentation, and best practices to influence internal assets and client roadmaps.
- Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements.
Note: Travel note appears under Responsibilities originally but we might move to Schedule. However it's under Responsibilities block. But we can keep it there or move. The instruction: we should not duplicate. If we put travel under Schedule, we should not duplicate under Responsibilities. The original had travel note after Knowledge Sharing as a separate sentence. It might be considered part of Responsibilities but we can treat as Schedule. To avoid duplication, we should move it to Schedule and remove from Responsibilities. Let's check: The text: "Knowledge Sharing: Craft reusable patterns, documentation, and best practices to influence internal assets and client roadmaps. Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements." So travel note is separate sentence after Knowledge Sharing. We'll treat as Schedule.
Thus Responsibilities list ends at Knowledge Sharing.
Requirements: "Here’s What You Need:" list:
- Minimum of 3 years engineering experience with cloud-native systems (APIs, microservices, containerization, serverless).
- Minimum of 1 year expertise in designing and deploying agentic solutions (agents, orchestration, context engineering, RAG, workflows) in production environments.
- Minimum of 2 years experience with AI platforms — OpenAI, Claude, Vertex AI, plus open-source models — including building abstraction layers to manage multi-provider pipelines.
- Minimum of 5 years experience programming in Python, Java, or equivalent; familiarity with evaluation tooling, logging, monitoring, and agent observability.
- Minimum of 5 years experience deploying to production — CI/CD, infrastructure as code (Terraform, Helm), monitoring, and debugging.
- Minimum of 5 years experience with client communication and collaboration, including being capable of leading technical workshops and delivering under ambiguity.
- Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate Degree, must have minimum 6 years work experience)
We should keep as list.
Qualifications: maybe we could separate education but it's already in requirements. Could we have Qualifications section for degree? But we might duplicate. Better to keep Requirements as is and not have Qualifications separate unless we have distinct content. The instruction says we can include sections only when posting has real specific content. We have qualifications (degree) but it's already in requirements. Could we make Qualifications for degree and maybe "Bonus Points If:" as Skills? Let's think.
We have "Bonus Points If:" list:
- You’ve served as an Agentic AI Engineer in an Enterprise environment
- Additional AI certifications or agentic tool experience is a plus.
- You’ve defined or worked with enterprise-grade architectures for compound AI systems, orchestration frameworks, or agent registry/stream-based architectures.
- You understand the AI-native paradigm — blending cloud-native with generative model architectures — optimizing for performance, modularity, and efficiency.
- You’ve delivered solutions across multiple industries (e.g., finance, healthcare) by tailoring agentic workflows to industry needs
These could be Skills.
Thus we can have:
- About the role (prose)
- Responsibilities (ul)
- Requirements (ul)
- Skills (ul) for bonus points
- Benefits (ul or prose)
- Pay (maybe a table? but we can use ul for location ranges)
- Schedule (p for travel)
We must not include sections with filler. All have content.
Now we need to ensure we don't include boilerplate like EEO etc. We'll strip those.
Now produce HTML.
Structure:
About the role
... paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture
Pay
- California: $94,400 to $316,300
- Cleveland: $87,400 to $253,000
- Colorado: $94,400 to $273,200
- District of Columbia: $100,500 to $291,000
- Illinois: $87,400 to $273,200
- Maine: $80,400 to $232,800
- Maryland: $94,400 to $273,200
- Massachusetts: $94,400 to $291,000
- Minnesota: $94,400 to $273,200
- New York: $87,400 to $316,300
- New Jersey: $100,500 to $316,300
- Virginia: $87,400 to $291,000
- Washington: $100,500 to $291,000
- for lists,
for prose. We must not include markdown code fences. Just raw HTML. Let's extract content. About the role: combine: "We are: A forward-thinking services company at the forefront of AI-native innovation. We partner with enterprise clients to create next-generation, agent-powered workflows engineered to scale in real-world settings. Our engineers embed deeply with customers, moving projects beyond experimentation into operational reality. You are: An AI Native Engineer with a minimum of 5 years of experience building cloud-native solutions, and deep expertise in designing and deploying agentic systems, especially for enterprise environments. You are a critical thinker that thrives in ambiguity, delivering concrete results by designing, building, and running custom AI agents that augment workflows and scale across modern infrastructure. You’ll help shape the playbook for how enterprises adopt and scale AI-native engineering globally. The Work: You’ll embed directly with clients — acting as both technologist and trusted advisor. You’ll partner with stakeholders to define use cases, rapidly prototype, and deploy agentic workflows that are robust, secure, and operational in complex enterprise domains. Often, these will be completely net new platforms and systems that need to be stitched together in our clients' environments alongside our Ecosystem partners." We need to preserve all substantive info; we can keep as paragraphs. Responsibilities: list items: - Agent Architecture and Engineering: Design and engineer enterprise-ready AI agents encompassing retrieval, orchestration, policy-based routing, tool invocation, evaluation harnesses, and lifecycle observability. - AI Platform Integration: Develop abstraction layers across AI providers (Anthropic, Google, OpenAI, etc. ) to enable seamless integration and enablement. - Cloud-Native Engineering: Leverage containerization (Kubernetes, Docker), microservices, serverless, event-driven architectures, CI/CD, and observability to deliver scalable AI-native systems. - Domain-Specific Workflows: Tailor and deploy agentic applications across verticals — e.g., finance, healthcare, retail — addressing domain-specific processes via intelligent automation. - Client Engagement: Conduct design workshops, POCs, and code-with sessions to shape data-driven agent workflows with stakeholders, fostering trust and adoption. - Measure & Improve: Define and use key metrics, test harnesses, and evaluation plans to measure agent accuracy, latency, safety, and cost effectiveness. - Knowledge Sharing: Craft reusable patterns, documentation, and best practices to influence internal assets and client roadmaps. - Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements. Note: Travel note appears under Responsibilities originally but we might move to Schedule. However it's under Responsibilities block. But we can keep it there or move. The instruction: we should not duplicate. If we put travel under Schedule, we should not duplicate under Responsibilities. The original had travel note after Knowledge Sharing as a separate sentence. It might be considered part of Responsibilities but we can treat as Schedule. To avoid duplication, we should move it to Schedule and remove from Responsibilities. Let's check: The text: "Knowledge Sharing: Craft reusable patterns, documentation, and best practices to influence internal assets and client roadmaps. Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements." So travel note is separate sentence after Knowledge Sharing. We'll treat as Schedule. Thus Responsibilities list ends at Knowledge Sharing. Requirements: "Here’s What You Need:" list: - Minimum of 3 years engineering experience with cloud-native systems (APIs, microservices, containerization, serverless). - Minimum of 1 year expertise in designing and deploying agentic solutions (agents, orchestration, context engineering, RAG, workflows) in production environments. - Minimum of 2 years experience with AI platforms — OpenAI, Claude, Vertex AI, plus open-source models — including building abstraction layers to manage multi-provider pipelines. - Minimum of 5 years experience programming in Python, Java, or equivalent; familiarity with evaluation tooling, logging, monitoring, and agent observability. - Minimum of 5 years experience deploying to production — CI/CD, infrastructure as code (Terraform, Helm), monitoring, and debugging. - Minimum of 5 years experience with client communication and collaboration, including being capable of leading technical workshops and delivering under ambiguity. - Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate Degree, must have minimum 6 years work experience) We should keep as list. Qualifications: maybe we could separate education but it's already in requirements. Could we have Qualifications section for degree? But we might duplicate. Better to keep Requirements as is and not have Qualifications separate unless we have distinct content. The instruction says we can include sections only when posting has real specific content. We have qualifications (degree) but it's already in requirements. Could we make Qualifications for degree and maybe "Bonus Points If:" as Skills? Let's think. We have "Bonus Points If:" list: - You’ve served as an Agentic AI Engineer in an Enterprise environment - Additional AI certifications or agentic tool experience is a plus. - You’ve defined or worked with enterprise-grade architectures for compound AI systems, orchestration frameworks, or agent registry/stream-based architectures. - You understand the AI-native paradigm — blending cloud-native with generative model architectures — optimizing for performance, modularity, and efficiency. - You’ve delivered solutions across multiple industries (e.g., finance, healthcare) by tailoring agentic workflows to industry needs These could be Skills. Thus we can have: - About the role (prose) - Responsibilities (ul) - Requirements (ul) - Skills (ul) for bonus points - Benefits (ul or prose) - Pay (maybe a table? but we can use ul for location ranges) - Schedule (p for travel) We must not include sections with filler. All have content. Now we need to ensure we don't include boilerplate like EEO etc. We'll strip those. Now produce HTML. Structure:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture
Pay
- California: $94,400 to $316,300
- Cleveland: $87,400 to $253,000
- Colorado: $94,400 to $273,200
- District of Columbia: $100,500 to $291,000
- Illinois: $87,400 to $273,200
- Maine: $80,400 to $232,800
- Maryland: $94,400 to $273,200
- Massachusetts: $94,400 to $291,000
- Minnesota: $94,400 to $273,200
- New York: $87,400 to $316,300
- New Jersey: $100,500 to $316,300
- Virginia: $87,400 to $291,000
- Washington: $100,500 to $291,000