Forward Deployed Engineering Manager
for section headings, - for lists,
for prose.
We must not include or . Just fragment.
Let's decide sections:
- About the role: Could include company description and practice description. Might be long but okay.
- Responsibilities: The work bullet list (own the full arc..., lead cross-domain..., drive rapid experimentation..., architect agentic solutions..., shape AI reinvention strategy..., define reusable reinvention blueprints...). Also maybe include "High-level Thinking:" as part of responsibilities? It says "High-level Thinking: Shapes reinvention strategy across client engagements, not just delivery execution. Identifies high-value use cases at program scale. Builds ROI backlogs and AI adoption roadmaps that align to commercial outcomes." That seems like a skill/responsibility. Could be under Responsibilities or Skills. Since we have a Skills section, we could put high-level thinking there. But we also have "You are: A skillful advisor..." which is more about candidate traits. That could be Skills or Qualifications.
Better to follow typical structure: About the role (company/practice), Responsibilities (the work), Requirements (minimum qualifications), Qualifications (bonus points), Skills (maybe high-level thinking and personal traits), Benefits, Pay, Schedule (travel). Ensure we don't repeat.
Let's extract each piece.
About the role: Combine the introductory paragraphs about Accenture and End-to-End Supply Chain & Engineering. We'll keep as prose.
Responsibilities: The bullet list under "The work:" plus maybe the high-level thinking? Actually high-level thinking is more about the role's expectations. Could be part of Responsibilities as well. But we have a Skills section; we could put high-level thinking there. Let's decide: We'll put high-level thinking under Skills.
Thus Responsibilities: list items:
- Own the full arc from business case to production: understand the client's operating model, identify the process friction and system interdependencies that block value, and build AI solutions that eliminate them — across ERP (SAP, Oracle), SCM platforms (Kinaxis, O9, Blue Yonder, Ariba), MES, and planning layers
- Lead cross-domain AI deployments at the functional interfaces — where planning, procurement, manufacturing, logistics, and engineering intersect — resolving the interdependencies that single-domain implementations miss
- Drive rapid experimentation from ambiguous business problem to working production system in days or weeks, grounded in deep knowledge of how supply chain and ERP transformations actually behave post-go-live
- Architect agentic solutions (agents, RAG, orchestration, multi-system workflow integration) that operate across the full enterprise stack: identity, data, governance, platform, and process layer
- Shape AI reinvention strategy with client CTO, CFO, and CISO — translating process and operating model complexity into fundable value architecture, ROI backlogs, and multi-year adoption roadmaps
- Define reusable reinvention blueprints and patterns — grounded in real deployment learnings — that scale across engagements and build the FDE practice
We need to keep the exact phrasing.
Requirements (minimum): Under "Here’s what you need:" list:
- Minimum 5 years of engineering experience with deep hands-on knowledge of enterprise SCM or ERP platform transformations (SAP, Oracle, Kinaxis, O9, Blue Yonder, or equivalent) including what breaks after go-live
- Minimum 1 year designing and deploying agentic AI solutions in production environments (agents, orchestration, RAG, context engineering)
- Minimum 2 years working with AI platforms (Anthropic, OpenAI, Vertex AI, or open source) including multi-provider pipeline architecture
- Deep design experience and fluency across one or several cross-domain processes including Idea to Retire, Source-to-Pay, Plan-to-Produce, Order-to-Cash, and Plan-to-Deliver with the ability to map how these processes intersect, where friction compounds, and how operating model gaps amplify system limitations.
- Bachelor's degree or equivalent (minimum 12 years) work experience. (If associate degree, must have a minimum of 6 years’ work experience)
We should keep as list.
Qualifications (bonus points): Under "Bonus points if:" list:
- Demonstrated ability to bridge strategy, operating model design, and business case development with executable AI architecture
- Experience leading engineering teams through delivery in client-embedded environments, with accountability for commercial outcomes — not just delivery milestones
- Credibility with CTO, CFO, and CSCO: you communicate deployment risk, operating model implications, and ROI in their language
- Full enterprise AI architecture across complex multi-stakeholder environments
- Multi-platform expertise/knowledge (at least two platforms)
- Value architecture at program scale identifies high-value use cases, quantifies ROI, aligns technical decisions to commercial outcomes
- Shapes reinvention blueprints and reusable patterns that scale across multiple client engagements
- Leads rapid experimentation at pace: ambiguous problems to working production system in days or weeks
We need to keep exactly.
Skills: Could include "You are: A skillful advisor..." paragraph describing personal traits, plus maybe high-level thinking. Let's capture:
"You are: A skillful advisor. You know how to make the supply chain work for clients, society, and our planet – ensuring input products and services are received responsibly without interruption. And, what’s more - you’ve got the real-life experience and analytical know-how to reduce complexity, optimize risk exposure/resiliency, and increase long-term profitability. You have energy and drive, along with personal resilience, a passion for serving clients, and a love of continual learning. You have a flair for breaking down challenges into logical issues and constructing clear reasoning and root-cause analysis — an aptitude you use to solve problems. You have both communication and people skills, and as a team leader, you’re a natural at appreciating diverse perspectives and bringing out the best in teams."
That's a prose description of skills/attributes.
High-level thinking: "High-level Thinking: Shapes reinvention strategy across client engagements, not just delivery execution. Identifies high-value use cases at program scale. Builds ROI backlogs and AI adoption roadmaps that align to commercial outcomes."
We could combine both into Skills section as prose and maybe a bullet list? But we can keep as prose.
Thus Skills section: include the "You are:" paragraph and the high-level thinking sentence(s). Could be two paragraphs.
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"
We should keep as prose.
Pay: Include compensation paragraph and salary ranges per location. The paragraph: "Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 10/08/2026." Then the table of locations and ranges. We need to preserve all substantive info. So we need to include that paragraph and the
for prose. We must not include or . Just fragment. Let's decide sections: - About the role: Could include company description and practice description. Might be long but okay. - Responsibilities: The work bullet list (own the full arc..., lead cross-domain..., drive rapid experimentation..., architect agentic solutions..., shape AI reinvention strategy..., define reusable reinvention blueprints...). Also maybe include "High-level Thinking:" as part of responsibilities? It says "High-level Thinking: Shapes reinvention strategy across client engagements, not just delivery execution. Identifies high-value use cases at program scale. Builds ROI backlogs and AI adoption roadmaps that align to commercial outcomes." That seems like a skill/responsibility. Could be under Responsibilities or Skills. Since we have a Skills section, we could put high-level thinking there. But we also have "You are: A skillful advisor..." which is more about candidate traits. That could be Skills or Qualifications. Better to follow typical structure: About the role (company/practice), Responsibilities (the work), Requirements (minimum qualifications), Qualifications (bonus points), Skills (maybe high-level thinking and personal traits), Benefits, Pay, Schedule (travel). Ensure we don't repeat. Let's extract each piece. About the role: Combine the introductory paragraphs about Accenture and End-to-End Supply Chain & Engineering. We'll keep as prose. Responsibilities: The bullet list under "The work:" plus maybe the high-level thinking? Actually high-level thinking is more about the role's expectations. Could be part of Responsibilities as well. But we have a Skills section; we could put high-level thinking there. Let's decide: We'll put high-level thinking under Skills. Thus Responsibilities: list items: - Own the full arc from business case to production: understand the client's operating model, identify the process friction and system interdependencies that block value, and build AI solutions that eliminate them — across ERP (SAP, Oracle), SCM platforms (Kinaxis, O9, Blue Yonder, Ariba), MES, and planning layers - Lead cross-domain AI deployments at the functional interfaces — where planning, procurement, manufacturing, logistics, and engineering intersect — resolving the interdependencies that single-domain implementations miss - Drive rapid experimentation from ambiguous business problem to working production system in days or weeks, grounded in deep knowledge of how supply chain and ERP transformations actually behave post-go-live - Architect agentic solutions (agents, RAG, orchestration, multi-system workflow integration) that operate across the full enterprise stack: identity, data, governance, platform, and process layer - Shape AI reinvention strategy with client CTO, CFO, and CISO — translating process and operating model complexity into fundable value architecture, ROI backlogs, and multi-year adoption roadmaps - Define reusable reinvention blueprints and patterns — grounded in real deployment learnings — that scale across engagements and build the FDE practice We need to keep the exact phrasing. Requirements (minimum): Under "Here’s what you need:" list: - Minimum 5 years of engineering experience with deep hands-on knowledge of enterprise SCM or ERP platform transformations (SAP, Oracle, Kinaxis, O9, Blue Yonder, or equivalent) including what breaks after go-live - Minimum 1 year designing and deploying agentic AI solutions in production environments (agents, orchestration, RAG, context engineering) - Minimum 2 years working with AI platforms (Anthropic, OpenAI, Vertex AI, or open source) including multi-provider pipeline architecture - Deep design experience and fluency across one or several cross-domain processes including Idea to Retire, Source-to-Pay, Plan-to-Produce, Order-to-Cash, and Plan-to-Deliver with the ability to map how these processes intersect, where friction compounds, and how operating model gaps amplify system limitations. - Bachelor's degree or equivalent (minimum 12 years) work experience. (If associate degree, must have a minimum of 6 years’ work experience) We should keep as list. Qualifications (bonus points): Under "Bonus points if:" list: - Demonstrated ability to bridge strategy, operating model design, and business case development with executable AI architecture - Experience leading engineering teams through delivery in client-embedded environments, with accountability for commercial outcomes — not just delivery milestones - Credibility with CTO, CFO, and CSCO: you communicate deployment risk, operating model implications, and ROI in their language - Full enterprise AI architecture across complex multi-stakeholder environments - Multi-platform expertise/knowledge (at least two platforms) - Value architecture at program scale identifies high-value use cases, quantifies ROI, aligns technical decisions to commercial outcomes - Shapes reinvention blueprints and reusable patterns that scale across multiple client engagements - Leads rapid experimentation at pace: ambiguous problems to working production system in days or weeks We need to keep exactly. Skills: Could include "You are: A skillful advisor..." paragraph describing personal traits, plus maybe high-level thinking. Let's capture: "You are: A skillful advisor. You know how to make the supply chain work for clients, society, and our planet – ensuring input products and services are received responsibly without interruption. And, what’s more - you’ve got the real-life experience and analytical know-how to reduce complexity, optimize risk exposure/resiliency, and increase long-term profitability. You have energy and drive, along with personal resilience, a passion for serving clients, and a love of continual learning. You have a flair for breaking down challenges into logical issues and constructing clear reasoning and root-cause analysis — an aptitude you use to solve problems. You have both communication and people skills, and as a team leader, you’re a natural at appreciating diverse perspectives and bringing out the best in teams." That's a prose description of skills/attributes. High-level thinking: "High-level Thinking: Shapes reinvention strategy across client engagements, not just delivery execution. Identifies high-value use cases at program scale. Builds ROI backlogs and AI adoption roadmaps that align to commercial outcomes." We could combine both into Skills section as prose and maybe a bullet list? But we can keep as prose. Thus Skills section: include the "You are:" paragraph and the high-level thinking sentence(s). Could be two paragraphs. 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" We should keep as prose. Pay: Include compensation paragraph and salary ranges per location. The paragraph: "Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 10/08/2026." Then the table of locations and ranges. We need to preserve all substantive info. So we need to include that paragraph and the