Service Delivery Center, Workflow Platform Engineer - Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content; never emit heading with filler placeholder. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Location: Alpharetta, Dallas (maybe location info). Could be part of About the role? Might be a short paragraph.
- Intro: "At EY, we’re all in to shape your future with confidence..." etc. That's about the company, maybe part of About the role.
- "We are seeking an experienced Manager, Workflow Platform Engineering to lead teams delivering enterprise workflow, orchestration and intelligent automation platforms. The successful candidate will oversee engineering delivery, people development, platform governance, stakeholder alignment and the evolution of reusable workflow capabilities. This role is ideal for technology leaders who possess strong experience with at least one workflow, BPM, orchestration or low-code platform and can guide teams working across a broader ecosystem of enterprise automation technologies."
That's about the role.
- Then "Key Responsibilities" with subheadings: Workflow & Platform Leadership, Delivery, People & Stakeholder Management, Cloud & Engineering Excellence. Under each bullet list.
- Then "Required Qualifications": bullet list.
- Then "Workflow & Automation Platform Experience": subcategories: Open BPM & Orchestration Platforms, Low-Code Platforms, Business Process & Workflow Knowledge, Technology Leadership Knowledge, Messaging & Event Streaming, Cloud, DevOps & Infrastructure, Data Technologies, AI & Intelligent Automation - Preferred, Preferred Industry Experience.
- Then "What Will Make You Stand Out": bullet list.
- Then "What We Offer You": paragraph about compensation and benefits, base salary ranges, total rewards, flexible vacation policy.
- Then "Are you ready to shape your future with confidence? Apply today." etc. That's application instructions, which we need to remove.
- Then more boilerplate about EY values, equal opportunity, accommodation, etc. Remove.
Thus we need to produce sections: About the role (maybe combine intro and location), Responsibilities (maybe combine the key responsibilities bullet lists), Requirements (maybe combine Required Qualifications and Workflow & Automation Platform Experience? Actually "Requirements" could be qualifications; "Skills" could be the platform experience and knowledge; but we need to follow instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which to include based on content.
We have content for:
- About the role: intro paragraph + location.
- Responsibilities: the bullet lists under Key Responsibilities.
- Requirements: maybe the Required Qualifications (education, years experience, etc.) plus maybe "What Will Make You Stand Out"? That's more like preferred qualifications; could go under Skills or Requirements. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications? But we need separate headings if we have content.
We have Qualifications: maybe the Required Qualifications (education, years). Skills: the platform experience, knowledge, etc. Benefits: the What We Offer You paragraph includes benefits and compensation. Pay: we have base salary range details; we could put Pay section with salary ranges. Schedule: we have flexible vacation policy; maybe schedule info? Not explicit schedule like full-time, but we could infer flexible vacation policy as schedule? Might be better to omit Schedule if no explicit schedule. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state base salary range, benefits, flexible vacation policy. So we can have Pay, Benefits, and maybe Schedule (flexible vacation). However "Schedule" could be about work hours; not given. Could we treat flexible vacation as part of Benefits? Probably better to put under Benefits. Since we have Pay and Benefits, we can omit Schedule if no explicit schedule.
Thus sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and What Will Make You Stand Out? but that's more like preferred qualifications; could be under Requirements or Skills). Let's think: The posting has "Required Qualifications" (education, experience). Then "Workflow & Automation Platform Experience" (specific skills). Then "What Will Make You Stand Out" (preferred). Then "Preferred Industry Experience". So we could map:
- Requirements: Required Qualifications (education, years, etc.)
- Skills: Workflow & Automation Platform Experience + What Will Make You Stand Out + Preferred Industry Experience (these are skills/knowledge).
- Benefits: What We Offer You (benefits, vacation).
- Pay: base salary range.
We need to avoid thin sections; but we have enough content for each.
Now we need to format lists: For responsibilities, we have subheadings under Key Responsibilities: Workflow & Platform Leadership, Delivery, People & Stakeholder Management, Cloud & Engineering Excellence. Each has bullet points (some are sentences). We need to output
- for any list of duties/requirements/benefits. Should we keep subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid using headings inside sections? It says use for section headings (list). It didn't say we cannot use other headings like or . But to be safe, we can just output the responsibilities as a flat list? But we need to preserve all substantive information; we could keep the subheadings as or maybe. However the instruction says use
- for any list of duties/requirements/benefits, and
for prose. It doesn't forbid using headings inside; but we could incorporate subheadings as
...
then list.
Simplify: For each responsibility category, we can output a Category:
then - ...
. That preserves info.
Similarly for Required Qualifications: list items.
For Skills: we have many subcategories; we could output each as a Subcategory:
then - ...
.
For Benefits: we have paragraph about compensation and benefits, base salary range, total rewards, flexible vacation. We could split into Pay and Benefits sections.
Pay: base salary range details.
Benefits: medical/dental, pension/401k, paid time off, flexible vacation policy, holidays, etc.
We need to avoid filler like "commensurate with experience". Not present.
Now produce HTML fragment.
Let's draft.
First, About the role: combine location and intro.
Location: Alpharetta, Dallas
At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. We are seeking an experienced Manager, Workflow Platform Engineering to lead teams delivering enterprise workflow, orchestration and intelligent automation platforms. The successful candidate will oversee engineering delivery, people development, platform governance, stakeholder alignment and the evolution of reusable workflow capabilities. This role is ideal for technology leaders who possess strong experience with at least one workflow, BPM, orchestration or low-code platform and can guide teams working across a broader ecosystem of enterprise automation technologies.
That's prose.
Now Responsibilities Responsibilities
Then subcategories:
Workflow & Platform Leadership:
- Lead the delivery and evolution of enterprise-scale workflow and orchestration platforms.
- Guide teams developing reusable workflow components, connector frameworks, accelerators, SDKs and platform services.
- Oversee workflow lifecycle capabilities including deployment, versioning, monitoring, auditing and governance.
- Promote BPMN-based process automation, case management, business rules and event-driven workflow patterns.
- Partner with architects and senior engineers to support scalable, secure and multi-tenant platform designs.
Delivery, People & Stakeholder Management:
- Lead, coach and develop engineers across workflow, integration, automation and platform disciplines.
- Own delivery planning, resource alignment, dependencies, risks, quality and executive communications.
- Partner with product owners, business stakeholders, architecture, security and operations teams.
- Support hiring, onboarding, performance coaching and career development.
- Drive Agile execution, continuous improvement and predictable delivery outcomes.
Cloud & Engineering Excellence:
- Establish engineering standards for cloud-native services, APIs, event-driven systems and distributed platforms.
- Promote DevOps, CI/CD, Infrastructure-as-Code, observability and platform reliability practices.
- Provide oversight through architecture reviews, design reviews and technical governance forums.
- Ensure solutions meet enterprise standards for security, scalability, compliance and operational excellence.
We'll output each as Category:
then - ...
.
Now Requirements Requirements
List:
- Bachelor's or Master's Degree in Computer Science, Engineering, Information Technology or related discipline.
- 10+ years of software engineering, enterprise application delivery or platform engineering experience.
- 3+ years of engineering management, delivery leadership or equivalent team leadership experience.
- Experience leading enterprise-scale distributed-system or automation initiatives in Agile environments.
- Demonstrated ability to manage technical dependencies, stakeholder expectations and delivery risks.
Now Skills Skills
We have many subcategories.
Open BPM & Orchestration Platforms:
- Camunda 7 / Camunda 8, Flowable, Fluxnova or Temporal.
Low-Code Platforms:
- Pega Infinity, Appian, Microsoft Power Platform, ServiceNow Workflow Automation or IBM Business Automation Workflow.
Business Process & Workflow Knowledge:
- BPMN 2.0 and DMN concepts.
- Case Management and Human Task Management.
- Workflow Orchestration and Business Rules Management.
- Process Governance and Workflow Versioning.
- Event Correlation, Long-Running Transactions and Compensation Patterns.
Technology Leadership Knowledge:
- Application & Integration Technologies: Java, Python, Node.js or Go engineering ecosystems.
- REST APIs, GraphQL, gRPC and OpenAPI.
- Event-Driven Architecture and Enterprise Integration Patterns.
- Messaging & Event Streaming - experience with at least one Apache Kafka, Confluent Platform, RabbitMQ, IBM MQ or Azure Event Hubs.
- Cloud, DevOps & Infrastructure: Leadership or delivery experience with at least one cloud-native platform or container ecosystem: Kubernetes, OpenShift or Docker; Terraform, Helm or ArgoCD; Jenkins, GitHub Actions or GitLab CI/CD.
- Data Technologies: Experience overseeing solutions using at least one of the following: PostgreSQL, Oracle or SQL Server; Elasticsearch/OpenSearch, Redis or Cassandra.
- AI & Intelligent Automation - Preferred: Azure OpenAI or AWS Bedrock; LangChain, LangGraph, CrewAI or Semantic Kernel; Model Context Protocol (MCP); UiPath or Automation Anywhere; ABBYY, Intelligent Document Processing or OCR solutions.
Preferred Industry Experience:
- Banking, Financial Services or Capital Markets.
- Insurance or Healthcare.
- Public Sector or other highly regulated industries.
What Will Make You Stand Out:
- Experience leading Workflow-as-a-Service (WaaS) platforms.
- Experience scaling reusable workflow frameworks and connector ecosystems.
- Multi-tenant SaaS platform leadership experience.
- Process Mining exposure such as Celonis, Signavio or Camunda Optimize.
- Strong understanding of governance, compliance, audit and operational excellence frameworks.
We could combine "What Will Make You Stand Out" and "Preferred Industry Experience" under Skills as well.
Now Benefits Benefits
Paragraph: At EY, we harness our collective strength to empower you to shape your future with confidence through professional growth, personal
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content; never emit heading with filler placeholder. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Location: Alpharetta, Dallas (maybe location info). Could be part of About the role? Might be a short paragraph. - Intro: "At EY, we’re all in to shape your future with confidence..." etc. That's about the company, maybe part of About the role. - "We are seeking an experienced Manager, Workflow Platform Engineering to lead teams delivering enterprise workflow, orchestration and intelligent automation platforms. The successful candidate will oversee engineering delivery, people development, platform governance, stakeholder alignment and the evolution of reusable workflow capabilities. This role is ideal for technology leaders who possess strong experience with at least one workflow, BPM, orchestration or low-code platform and can guide teams working across a broader ecosystem of enterprise automation technologies." That's about the role. - Then "Key Responsibilities" with subheadings: Workflow & Platform Leadership, Delivery, People & Stakeholder Management, Cloud & Engineering Excellence. Under each bullet list. - Then "Required Qualifications": bullet list. - Then "Workflow & Automation Platform Experience": subcategories: Open BPM & Orchestration Platforms, Low-Code Platforms, Business Process & Workflow Knowledge, Technology Leadership Knowledge, Messaging & Event Streaming, Cloud, DevOps & Infrastructure, Data Technologies, AI & Intelligent Automation - Preferred, Preferred Industry Experience. - Then "What Will Make You Stand Out": bullet list. - Then "What We Offer You": paragraph about compensation and benefits, base salary ranges, total rewards, flexible vacation policy. - Then "Are you ready to shape your future with confidence? Apply today." etc. That's application instructions, which we need to remove. - Then more boilerplate about EY values, equal opportunity, accommodation, etc. Remove. Thus we need to produce sections: About the role (maybe combine intro and location), Responsibilities (maybe combine the key responsibilities bullet lists), Requirements (maybe combine Required Qualifications and Workflow & Automation Platform Experience? Actually "Requirements" could be qualifications; "Skills" could be the platform experience and knowledge; but we need to follow instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which to include based on content. We have content for: - About the role: intro paragraph + location. - Responsibilities: the bullet lists under Key Responsibilities. - Requirements: maybe the Required Qualifications (education, years experience, etc.) plus maybe "What Will Make You Stand Out"? That's more like preferred qualifications; could go under Skills or Requirements. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications? But we need separate headings if we have content. We have Qualifications: maybe the Required Qualifications (education, years). Skills: the platform experience, knowledge, etc. Benefits: the What We Offer You paragraph includes benefits and compensation. Pay: we have base salary range details; we could put Pay section with salary ranges. Schedule: we have flexible vacation policy; maybe schedule info? Not explicit schedule like full-time, but we could infer flexible vacation policy as schedule? Might be better to omit Schedule if no explicit schedule. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state base salary range, benefits, flexible vacation policy. So we can have Pay, Benefits, and maybe Schedule (flexible vacation). However "Schedule" could be about work hours; not given. Could we treat flexible vacation as part of Benefits? Probably better to put under Benefits. Since we have Pay and Benefits, we can omit Schedule if no explicit schedule. Thus sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and What Will Make You Stand Out? but that's more like preferred qualifications; could be under Requirements or Skills). Let's think: The posting has "Required Qualifications" (education, experience). Then "Workflow & Automation Platform Experience" (specific skills). Then "What Will Make You Stand Out" (preferred). Then "Preferred Industry Experience". So we could map: - Requirements: Required Qualifications (education, years, etc.) - Skills: Workflow & Automation Platform Experience + What Will Make You Stand Out + Preferred Industry Experience (these are skills/knowledge). - Benefits: What We Offer You (benefits, vacation). - Pay: base salary range. We need to avoid thin sections; but we have enough content for each. Now we need to format lists: For responsibilities, we have subheadings under Key Responsibilities: Workflow & Platform Leadership, Delivery, People & Stakeholder Management, Cloud & Engineering Excellence. Each has bullet points (some are sentences). We need to output
- for any list of duties/requirements/benefits. Should we keep subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid using headings inside sections? It says use
for section headings (list). It didn't say we cannot use other headings like
or . But to be safe, we can just output the responsibilities as a flat list? But we need to preserve all substantive information; we could keep the subheadings as or
maybe. However the instruction says use
- for any list of duties/requirements/benefits, and
for prose. It doesn't forbid using headings inside; but we could incorporate subheadings as
...
then list. Simplify: For each responsibility category, we can output aCategory:
then- ...
Subcategory:
then- ...
Location: Alpharetta, Dallas
At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. We are seeking an experienced Manager, Workflow Platform Engineering to lead teams delivering enterprise workflow, orchestration and intelligent automation platforms. The successful candidate will oversee engineering delivery, people development, platform governance, stakeholder alignment and the evolution of reusable workflow capabilities. This role is ideal for technology leaders who possess strong experience with at least one workflow, BPM, orchestration or low-code platform and can guide teams working across a broader ecosystem of enterprise automation technologies.
That's prose. Now ResponsibilitiesResponsibilities
Then subcategories: Workflow & Platform Leadership: - Lead the delivery and evolution of enterprise-scale workflow and orchestration platforms. - Guide teams developing reusable workflow components, connector frameworks, accelerators, SDKs and platform services. - Oversee workflow lifecycle capabilities including deployment, versioning, monitoring, auditing and governance. - Promote BPMN-based process automation, case management, business rules and event-driven workflow patterns. - Partner with architects and senior engineers to support scalable, secure and multi-tenant platform designs. Delivery, People & Stakeholder Management: - Lead, coach and develop engineers across workflow, integration, automation and platform disciplines. - Own delivery planning, resource alignment, dependencies, risks, quality and executive communications. - Partner with product owners, business stakeholders, architecture, security and operations teams. - Support hiring, onboarding, performance coaching and career development. - Drive Agile execution, continuous improvement and predictable delivery outcomes. Cloud & Engineering Excellence: - Establish engineering standards for cloud-native services, APIs, event-driven systems and distributed platforms. - Promote DevOps, CI/CD, Infrastructure-as-Code, observability and platform reliability practices. - Provide oversight through architecture reviews, design reviews and technical governance forums. - Ensure solutions meet enterprise standards for security, scalability, compliance and operational excellence. We'll output each asCategory:
then- ...
Requirements
List: - Bachelor's or Master's Degree in Computer Science, Engineering, Information Technology or related discipline. - 10+ years of software engineering, enterprise application delivery or platform engineering experience. - 3+ years of engineering management, delivery leadership or equivalent team leadership experience. - Experience leading enterprise-scale distributed-system or automation initiatives in Agile environments. - Demonstrated ability to manage technical dependencies, stakeholder expectations and delivery risks. Now SkillsSkills
We have many subcategories. Open BPM & Orchestration Platforms: - Camunda 7 / Camunda 8, Flowable, Fluxnova or Temporal. Low-Code Platforms: - Pega Infinity, Appian, Microsoft Power Platform, ServiceNow Workflow Automation or IBM Business Automation Workflow. Business Process & Workflow Knowledge: - BPMN 2.0 and DMN concepts. - Case Management and Human Task Management. - Workflow Orchestration and Business Rules Management. - Process Governance and Workflow Versioning. - Event Correlation, Long-Running Transactions and Compensation Patterns. Technology Leadership Knowledge: - Application & Integration Technologies: Java, Python, Node.js or Go engineering ecosystems. - REST APIs, GraphQL, gRPC and OpenAPI. - Event-Driven Architecture and Enterprise Integration Patterns. - Messaging & Event Streaming - experience with at least one Apache Kafka, Confluent Platform, RabbitMQ, IBM MQ or Azure Event Hubs. - Cloud, DevOps & Infrastructure: Leadership or delivery experience with at least one cloud-native platform or container ecosystem: Kubernetes, OpenShift or Docker; Terraform, Helm or ArgoCD; Jenkins, GitHub Actions or GitLab CI/CD. - Data Technologies: Experience overseeing solutions using at least one of the following: PostgreSQL, Oracle or SQL Server; Elasticsearch/OpenSearch, Redis or Cassandra. - AI & Intelligent Automation - Preferred: Azure OpenAI or AWS Bedrock; LangChain, LangGraph, CrewAI or Semantic Kernel; Model Context Protocol (MCP); UiPath or Automation Anywhere; ABBYY, Intelligent Document Processing or OCR solutions. Preferred Industry Experience: - Banking, Financial Services or Capital Markets. - Insurance or Healthcare. - Public Sector or other highly regulated industries. What Will Make You Stand Out: - Experience leading Workflow-as-a-Service (WaaS) platforms. - Experience scaling reusable workflow frameworks and connector ecosystems. - Multi-tenant SaaS platform leadership experience. - Process Mining exposure such as Celonis, Signavio or Camunda Optimize. - Strong understanding of governance, compliance, audit and operational excellence frameworks. We could combine "What Will Make You Stand Out" and "Preferred Industry Experience" under Skills as well. Now BenefitsBenefits
Paragraph: At EY, we harness our collective strength to empower you to shape your future with confidence through professional growth, personal
- for any list of duties/requirements/benefits, and