Service Delivery Center, Workflow Platform Backend Engineer - Senior
for sections like 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 (page already shows it). Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract substantive content: location, description, responsibilities, required qualifications, workflow & automation platform experience, business process & workflow knowledge, software engineering skills, integration technologies, messaging & event streaming, cloud devops & infra, data technologies, AI & intelligent automation (preferred), preferred industry experience, what will make you stand out, what we offer (benefits, compensation, etc). Also location: "Location: Alpharetta, Dallas". Actually says "Location: Alpharetta, Dallas". Might be two locations? We'll include location in a short
.
We need to decide sections: maybe "About the role" (intro paragraph), "Responsibilities" (list), "Requirements" (list of required qualifications), "Qualifications" maybe overlapping? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some. We need to avoid filler sections.
We have specific content for:
- About the role: The paragraph about EY, mission, seeking Senior Workflow Platform Engineer, description of role.
- Responsibilities: bullet list under "Key Responsibilities" with subheadings: Workflow & Platform Engineering, Integration & Automation, Cloud & Engineering Excellence. We can flatten into a list of responsibilities.
- Requirements: "Required Qualifications" bullet list: Bachelor's or Master's degree, 7+ years software engineering, 3+ years workflow/orchestration/BPM/low-code, experience delivering enterprise-scale distributed systems in Agile.
- Qualifications: maybe we can treat "Workflow & Automation Platform Experience" etc as qualifications/skills. Could be separate "Skills" section.
- Skills: list of specific technologies: platforms, languages, integration tech, messaging, cloud devops, data technologies, AI & intelligent automation (preferred), preferred industry experience.
- Benefits: "What We Offer You" includes compensation ranges, benefits (medical/dental, pension/401k, paid time off, flexible vacation, holidays, etc). Also mention base salary ranges per location.
- Pay: we have salary ranges; we could put under Benefits or separate Pay section. Since we have actual salary ranges, we can create a Pay section.
- Schedule: not mentioned; no schedule info (like full-time, remote). Not present, so we should not create Schedule section.
We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly Qualifications separate? But we have Required Qualifications; we could label that as Requirements. Skills could be separate.
We need to ensure we don't repeat job title. Use
for each section heading.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO statement, accommodation instructions, etc. Also remove "Apply today..." and application instructions like "limit yourself to two applications within a six-month period", "EY accepts applications...", "For those living in California, please click here...". Also remove the "EY | Building a better working world" paragraph etc. Also remove the final paragraphs about EY building a better working world, equal employment opportunities, accommodation, etc. Also remove the "Are you ready to shape your future with confidence? Apply today." etc.
We need to keep location, intro paragraph about EY mission, responsibilities, required qualifications, workflow & automation platform experience, business process & workflow knowledge, software engineering skills, integration technologies, messaging & event streaming, cloud devops & infra, data technologies, AI & intelligent automation (preferred), preferred industry experience, what will make you stand out, what we offer (compensation and benefits). Also maybe include "What Will Make You Stand Out" as part of Skills or a separate section? Could be under Skills or a separate "Preferred Qualifications". But we have headings list includes Skills; we could put standout items under Skills as well.
We need to avoid duplication. Some content repeats: e.g., "Experience building Workflow-as-a-Service (WaaS) platforms." etc.
We need to preserve all substantive info; we can combine similar items but not lose detail.
Let's extract sections:
Location: "Location: Alpharetta, Dallas". We'll put in a
maybe before sections.
About the role: Paragraph: "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 a highly skilled Senior Workflow Platform Engineer to help design, build and scale enterprise workflow, orchestration and intelligent automation platforms. The successful candidate will contribute to reusable workflow services, API-driven integrations, event-driven architectures, AI-powered automation capabilities and cloud-native platform services. This role is ideal for engineers who possess deep expertise in at least one workflow, BPM, orchestration or low-code platform and are excited to work across a broader ecosystem of technologies supporting enterprise-wide automation initiatives."
That's the intro.
Responsibilities: Under "Key Responsibilities" we have three categories with bullet points.
We'll flatten into a list:
- Design and implement enterprise-scale workflow and orchestration services.
- Develop reusable workflow components, connector frameworks, accelerators, SDKs and platform services.
- Build workflow lifecycle management capabilities including deployment, versioning, monitoring, auditing and governance.
- Support BPMN-based process automation, case management, business rules and event-driven workflows.
- Contribute to multi-tenant, highly scalable workflow platform architectures.
- Design integrations with enterprise applications, APIs, messaging systems, cloud services and external platforms.
- Implement API-first and event-driven integration patterns.
- Enable intelligent automation capabilities using AI services, document processing solutions and automation platforms.
- Develop reusable connectors and integration patterns that can be leveraged across multiple business solutions.
- Build cloud-native microservices and distributed systems.
- Contribute to DevOps, CI/CD, Infrastructure-as-Code, observability and platform reliability practices.
- Participate in architecture reviews, code reviews and technical mentoring activities.
- Ensure solutions meet enterprise standards for security, scalability, compliance and operational excellence.
That's all.
Requirements: Under "Required Qualifications":
- Bachelor's or Master's Degree in Computer Science, Engineering, Information Technology or related discipline.
- 7+ years of software engineering experience.
- 3+ years of workflow, orchestration, BPM, low-code or automation platform experience.
- Experience delivering enterprise-scale distributed systems in Agile environments.
We could also include "Workflow & Automation Platform Experience" as a requirement but it's more specific; we could treat as Skills.
But we have a separate section "Workflow & Automation Platform Experience" which lists specific platforms. That is more like required skills/experience. We'll treat that under Skills or Requirements? The instruction says use headings for Requirements, Qualifications, Skills. We could put the degree/experience under Requirements, and the platform experience under Qualifications or Skills. Let's decide:
- Requirements: degree, years experience, Agile experience.
- Qualifications: maybe the specific platform experience (Open BPM & Orchestration Platforms, Low-Code Platforms). Could be under Qualifications.
- Skills: the rest: programming languages, integration technologies, messaging, cloud devops, data technologies, AI & intelligent automation (preferred), preferred industry experience, what will make you stand out.
But we also have "Business Process & Workflow Knowledge" which could be under Skills.
We need to avoid too many thin sections; prefer a few substantive sections. Maybe combine Qualifications and Skills into one "Qualifications & Skills" section. But the instruction says we can use those headings if we have content. We could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's many but each has substantive content.
We must not create sections with filler. All have content.
Let's outline:
About the role
...
Responsibilities
- ...
...
Requirements
- Bachelor's or Master's Degree in Computer Science, Engineering, Information Technology or related discipline.
- 7+ years of software engineering experience.
- 3+ years of workflow, orchestration, BPM, low-code or automation platform experience.
- Experience delivering enterprise-scale distributed systems in Agile environments.
Qualifications
- Hands‑on experience with at least one of the following Open BPM & Orchestration Platforms: Camunda 7 / Camunda 8, Flowable, Fluxnova, Temporal.
- Or hands‑on experience with at least one of the following Low‑Code Platforms: Pega Infinity, Appian, Microsoft Power Platform, ServiceNow Workflow Automation, IBM Business Automation Workflow.
But we also have Business Process & Workflow Knowledge, Software Engineering Skills, Integration Technologies, Messaging & Event Streaming, Cloud DevOps & Infrastructure, Data Technologies, AI & Intelligent Automation (Preferred), Preferred Industry Experience, What Will Make You Stand Out.
We could incorporate those into Skills section.
Thus:
Skills
- 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.
- Software Engineering Skills: Programming languages – experience with at least one of Java (preferably Spring Boot), Python, Node.js, Go.
- Integration Technologies: REST APIs, GraphQL, gRPC, OpenAPI, Event‑Driven Architecture, Enterprise Integration Patterns.
- Messaging & Event Streaming: experience with at least one of Apache Kafka, Confluent Platform, RabbitMQ, IBM MQ, Azure Event Hubs.
- Cloud, DevOps & Infrastructure: experience with at least one of Kubernetes, OpenShift, Docker, Terraform, Helm, ArgoCD, Jenkins, GitHub Actions, GitLab CI/CD.
- Data Technologies: experience with at least one of PostgreSQL, Oracle, SQL Server, Elasticsearch/OpenSearch, Redis, 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
for prose. Do NOT repeat job title as heading (page already shows it). Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: location, description, responsibilities, required qualifications, workflow & automation platform experience, business process & workflow knowledge, software engineering skills, integration technologies, messaging & event streaming, cloud devops & infra, data technologies, AI & intelligent automation (preferred), preferred industry experience, what will make you stand out, what we offer (benefits, compensation, etc). Also location: "Location: Alpharetta, Dallas". Actually says "Location: Alpharetta, Dallas". Might be two locations? We'll include location in a short
. We need to decide sections: maybe "About the role" (intro paragraph), "Responsibilities" (list), "Requirements" (list of required qualifications), "Qualifications" maybe overlapping? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some. We need to avoid filler sections. We have specific content for: - About the role: The paragraph about EY, mission, seeking Senior Workflow Platform Engineer, description of role. - Responsibilities: bullet list under "Key Responsibilities" with subheadings: Workflow & Platform Engineering, Integration & Automation, Cloud & Engineering Excellence. We can flatten into a list of responsibilities. - Requirements: "Required Qualifications" bullet list: Bachelor's or Master's degree, 7+ years software engineering, 3+ years workflow/orchestration/BPM/low-code, experience delivering enterprise-scale distributed systems in Agile. - Qualifications: maybe we can treat "Workflow & Automation Platform Experience" etc as qualifications/skills. Could be separate "Skills" section. - Skills: list of specific technologies: platforms, languages, integration tech, messaging, cloud devops, data technologies, AI & intelligent automation (preferred), preferred industry experience. - Benefits: "What We Offer You" includes compensation ranges, benefits (medical/dental, pension/401k, paid time off, flexible vacation, holidays, etc). Also mention base salary ranges per location. - Pay: we have salary ranges; we could put under Benefits or separate Pay section. Since we have actual salary ranges, we can create a Pay section. - Schedule: not mentioned; no schedule info (like full-time, remote). Not present, so we should not create Schedule section. We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly Qualifications separate? But we have Required Qualifications; we could label that as Requirements. Skills could be separate. We need to ensure we don't repeat job title. Use
for each section heading.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO statement, accommodation instructions, etc. Also remove "Apply today..." and application instructions like "limit yourself to two applications within a six-month period", "EY accepts applications...", "For those living in California, please click here...". Also remove the "EY | Building a better working world" paragraph etc. Also remove the final paragraphs about EY building a better working world, equal employment opportunities, accommodation, etc. Also remove the "Are you ready to shape your future with confidence? Apply today." etc.
We need to keep location, intro paragraph about EY mission, responsibilities, required qualifications, workflow & automation platform experience, business process & workflow knowledge, software engineering skills, integration technologies, messaging & event streaming, cloud devops & infra, data technologies, AI & intelligent automation (preferred), preferred industry experience, what will make you stand out, what we offer (compensation and benefits). Also maybe include "What Will Make You Stand Out" as part of Skills or a separate section? Could be under Skills or a separate "Preferred Qualifications". But we have headings list includes Skills; we could put standout items under Skills as well.
We need to avoid duplication. Some content repeats: e.g., "Experience building Workflow-as-a-Service (WaaS) platforms." etc.
We need to preserve all substantive info; we can combine similar items but not lose detail.
Let's extract sections:
Location: "Location: Alpharetta, Dallas". We'll put in a
maybe before sections.
About the role: Paragraph: "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 a highly skilled Senior Workflow Platform Engineer to help design, build and scale enterprise workflow, orchestration and intelligent automation platforms. The successful candidate will contribute to reusable workflow services, API-driven integrations, event-driven architectures, AI-powered automation capabilities and cloud-native platform services. This role is ideal for engineers who possess deep expertise in at least one workflow, BPM, orchestration or low-code platform and are excited to work across a broader ecosystem of technologies supporting enterprise-wide automation initiatives."
That's the intro.
Responsibilities: Under "Key Responsibilities" we have three categories with bullet points.
We'll flatten into a list:
- Design and implement enterprise-scale workflow and orchestration services.
- Develop reusable workflow components, connector frameworks, accelerators, SDKs and platform services.
- Build workflow lifecycle management capabilities including deployment, versioning, monitoring, auditing and governance.
- Support BPMN-based process automation, case management, business rules and event-driven workflows.
- Contribute to multi-tenant, highly scalable workflow platform architectures.
- Design integrations with enterprise applications, APIs, messaging systems, cloud services and external platforms.
- Implement API-first and event-driven integration patterns.
- Enable intelligent automation capabilities using AI services, document processing solutions and automation platforms.
- Develop reusable connectors and integration patterns that can be leveraged across multiple business solutions.
- Build cloud-native microservices and distributed systems.
- Contribute to DevOps, CI/CD, Infrastructure-as-Code, observability and platform reliability practices.
- Participate in architecture reviews, code reviews and technical mentoring activities.
- Ensure solutions meet enterprise standards for security, scalability, compliance and operational excellence.
That's all.
Requirements: Under "Required Qualifications":
- Bachelor's or Master's Degree in Computer Science, Engineering, Information Technology or related discipline.
- 7+ years of software engineering experience.
- 3+ years of workflow, orchestration, BPM, low-code or automation platform experience.
- Experience delivering enterprise-scale distributed systems in Agile environments.
We could also include "Workflow & Automation Platform Experience" as a requirement but it's more specific; we could treat as Skills.
But we have a separate section "Workflow & Automation Platform Experience" which lists specific platforms. That is more like required skills/experience. We'll treat that under Skills or Requirements? The instruction says use headings for Requirements, Qualifications, Skills. We could put the degree/experience under Requirements, and the platform experience under Qualifications or Skills. Let's decide:
- Requirements: degree, years experience, Agile experience.
- Qualifications: maybe the specific platform experience (Open BPM & Orchestration Platforms, Low-Code Platforms). Could be under Qualifications.
- Skills: the rest: programming languages, integration technologies, messaging, cloud devops, data technologies, AI & intelligent automation (preferred), preferred industry experience, what will make you stand out.
But we also have "Business Process & Workflow Knowledge" which could be under Skills.
We need to avoid too many thin sections; prefer a few substantive sections. Maybe combine Qualifications and Skills into one "Qualifications & Skills" section. But the instruction says we can use those headings if we have content. We could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's many but each has substantive content.
We must not create sections with filler. All have content.
Let's outline:
About the role
...
Responsibilities
- ...
...
Requirements
- Bachelor's or Master's Degree in Computer Science, Engineering, Information Technology or related discipline.
- 7+ years of software engineering experience.
- 3+ years of workflow, orchestration, BPM, low-code or automation platform experience.
- Experience delivering enterprise-scale distributed systems in Agile environments.
Qualifications
- Hands‑on experience with at least one of the following Open BPM & Orchestration Platforms: Camunda 7 / Camunda 8, Flowable, Fluxnova, Temporal.
- Or hands‑on experience with at least one of the following Low‑Code Platforms: Pega Infinity, Appian, Microsoft Power Platform, ServiceNow Workflow Automation, IBM Business Automation Workflow.
But we also have Business Process & Workflow Knowledge, Software Engineering Skills, Integration Technologies, Messaging & Event Streaming, Cloud DevOps & Infrastructure, Data Technologies, AI & Intelligent Automation (Preferred), Preferred Industry Experience, What Will Make You Stand Out.
We could incorporate those into Skills section.
Thus:
Skills
- 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.
- Software Engineering Skills: Programming languages – experience with at least one of Java (preferably Spring Boot), Python, Node.js, Go.
- Integration Technologies: REST APIs, GraphQL, gRPC, OpenAPI, Event‑Driven Architecture, Enterprise Integration Patterns.
- Messaging & Event Streaming: experience with at least one of Apache Kafka, Confluent Platform, RabbitMQ, IBM MQ, Azure Event Hubs.
- Cloud, DevOps & Infrastructure: experience with at least one of Kubernetes, OpenShift, Docker, Terraform, Helm, ArgoCD, Jenkins, GitHub Actions, GitLab CI/CD.
- Data Technologies: experience with at least one of PostgreSQL, Oracle, SQL Server, Elasticsearch/OpenSearch, Redis, 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
. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO statement, accommodation instructions, etc. Also remove "Apply today..." and application instructions like "limit yourself to two applications within a six-month period", "EY accepts applications...", "For those living in California, please click here...". Also remove the "EY | Building a better working world" paragraph etc. Also remove the final paragraphs about EY building a better working world, equal employment opportunities, accommodation, etc. Also remove the "Are you ready to shape your future with confidence? Apply today." etc. We need to keep location, intro paragraph about EY mission, responsibilities, required qualifications, workflow & automation platform experience, business process & workflow knowledge, software engineering skills, integration technologies, messaging & event streaming, cloud devops & infra, data technologies, AI & intelligent automation (preferred), preferred industry experience, what will make you stand out, what we offer (compensation and benefits). Also maybe include "What Will Make You Stand Out" as part of Skills or a separate section? Could be under Skills or a separate "Preferred Qualifications". But we have headings list includes Skills; we could put standout items under Skills as well. We need to avoid duplication. Some content repeats: e.g., "Experience building Workflow-as-a-Service (WaaS) platforms." etc. We need to preserve all substantive info; we can combine similar items but not lose detail. Let's extract sections: Location: "Location: Alpharetta, Dallas". We'll put in a
maybe before sections. About the role: Paragraph: "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 a highly skilled Senior Workflow Platform Engineer to help design, build and scale enterprise workflow, orchestration and intelligent automation platforms. The successful candidate will contribute to reusable workflow services, API-driven integrations, event-driven architectures, AI-powered automation capabilities and cloud-native platform services. This role is ideal for engineers who possess deep expertise in at least one workflow, BPM, orchestration or low-code platform and are excited to work across a broader ecosystem of technologies supporting enterprise-wide automation initiatives." That's the intro. Responsibilities: Under "Key Responsibilities" we have three categories with bullet points. We'll flatten into a list: - Design and implement enterprise-scale workflow and orchestration services. - Develop reusable workflow components, connector frameworks, accelerators, SDKs and platform services. - Build workflow lifecycle management capabilities including deployment, versioning, monitoring, auditing and governance. - Support BPMN-based process automation, case management, business rules and event-driven workflows. - Contribute to multi-tenant, highly scalable workflow platform architectures. - Design integrations with enterprise applications, APIs, messaging systems, cloud services and external platforms. - Implement API-first and event-driven integration patterns. - Enable intelligent automation capabilities using AI services, document processing solutions and automation platforms. - Develop reusable connectors and integration patterns that can be leveraged across multiple business solutions. - Build cloud-native microservices and distributed systems. - Contribute to DevOps, CI/CD, Infrastructure-as-Code, observability and platform reliability practices. - Participate in architecture reviews, code reviews and technical mentoring activities. - Ensure solutions meet enterprise standards for security, scalability, compliance and operational excellence. That's all. Requirements: Under "Required Qualifications": - Bachelor's or Master's Degree in Computer Science, Engineering, Information Technology or related discipline. - 7+ years of software engineering experience. - 3+ years of workflow, orchestration, BPM, low-code or automation platform experience. - Experience delivering enterprise-scale distributed systems in Agile environments. We could also include "Workflow & Automation Platform Experience" as a requirement but it's more specific; we could treat as Skills. But we have a separate section "Workflow & Automation Platform Experience" which lists specific platforms. That is more like required skills/experience. We'll treat that under Skills or Requirements? The instruction says use headings for Requirements, Qualifications, Skills. We could put the degree/experience under Requirements, and the platform experience under Qualifications or Skills. Let's decide: - Requirements: degree, years experience, Agile experience. - Qualifications: maybe the specific platform experience (Open BPM & Orchestration Platforms, Low-Code Platforms). Could be under Qualifications. - Skills: the rest: programming languages, integration technologies, messaging, cloud devops, data technologies, AI & intelligent automation (preferred), preferred industry experience, what will make you stand out. But we also have "Business Process & Workflow Knowledge" which could be under Skills. We need to avoid too many thin sections; prefer a few substantive sections. Maybe combine Qualifications and Skills into one "Qualifications & Skills" section. But the instruction says we can use those headings if we have content. We could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's many but each has substantive content. We must not create sections with filler. All have content. Let's outline:
About the role
...
Responsibilities
- ... ...
Requirements
- Bachelor's or Master's Degree in Computer Science, Engineering, Information Technology or related discipline.
- 7+ years of software engineering experience.
- 3+ years of workflow, orchestration, BPM, low-code or automation platform experience.
- Experience delivering enterprise-scale distributed systems in Agile environments.
Qualifications
- Hands‑on experience with at least one of the following Open BPM & Orchestration Platforms: Camunda 7 / Camunda 8, Flowable, Fluxnova, Temporal.
- Or hands‑on experience with at least one of the following Low‑Code Platforms: Pega Infinity, Appian, Microsoft Power Platform, ServiceNow Workflow Automation, IBM Business Automation Workflow.
Skills
- 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.
- Software Engineering Skills: Programming languages – experience with at least one of Java (preferably Spring Boot), Python, Node.js, Go.
- Integration Technologies: REST APIs, GraphQL, gRPC, OpenAPI, Event‑Driven Architecture, Enterprise Integration Patterns.
- Messaging & Event Streaming: experience with at least one of Apache Kafka, Confluent Platform, RabbitMQ, IBM MQ, Azure Event Hubs.
- Cloud, DevOps & Infrastructure: experience with at least one of Kubernetes, OpenShift, Docker, Terraform, Helm, ArgoCD, Jenkins, GitHub Actions, GitLab CI/CD.
- Data Technologies: experience with at least one of PostgreSQL, Oracle, SQL Server, Elasticsearch/OpenSearch, Redis, 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