Lead Software Engineer - Camunda

EPAM Systems; Bengaluru; On-site; INR 4,000,000 - 7,000,000; Full time

Job summary

EPAM Systems is seeking a Lead Software Engineer in Bengaluru to own Camunda 8 architecture and drive end-to-end BPM migration delivery across defined complexity tiers. You will coordinate security models, integrations, and parallel-run cutovers with internal stakeholders and vendors.

The role requires 10–15 years of software engineering experience and proven Camunda 8 delivery. You will lead technical discussions with architecture boards and mentor junior engineers in a fast-paced setting.

Qualifications

• 10-15 years of end-to-end software engineering experience.
• Proven enterprise delivery experience with Camunda 8.
• Strong ability to lead teams and facilitate client architecture discussions.

Responsibilities

• Define and own the target Camunda 8 solution architecture for in-scope processes.
• Enforce Camunda engineering standards, quality metrics, and best practices across the team.
• Deliver migration execution across multiple complexity tiers with parallel-run cutovers.
• Plan and validate parallel-run and cutover strategies per process.
• Coordinate with third-party Camunda vendor for platform and infra setup.
• Verify integration points with existing REST APIs.
• Oversee data migration for process definitions and DMN tables.
• Manage cross-team dependencies between POD, Solution Architecture and Service Store.
• Support UAT validation and defect resolution; contribute to runbooks.

Skills

Camunda 8

Team Leadership

Architecture Design

BPMN 2.0

REST APIs

Tools

Camunda Platform

PostgreSQL

OIDC (Okta/Microsoft Entra)

Job description

We are seeking a Lead Software Engineer to lead Camunda 8 architecture ownership and execute end-to-end BPM migration delivery across defined complexity tiers. You will coordinate security models, integrations, process design, and parallel-run cutovers with internal stakeholders and vendors.

Responsibilities

• Define and own the target Camunda 8 solution architecture for in-scope processes aligned to the Logical Data Model and ABAC/PBAC access control model
• Implement and enforce Camunda engineering standards, quality metrics, and best practices across the Development POD
• Deliver complexity-tiered migration execution across AI-assisted generation, draft-plus-manual redesign, and full REST-based redesign
• Plan and validate the parallel-run and cutover strategy per process including routing, shared integration layer, and decommission triggers
• Partner with the third-party vendor responsible for Camunda platform and infrastructure setup to align application-layer and platform-layer design
• Verify integration points with existing REST APIs via the Integration Layer in collaboration with the API team
• Own the reference data migration approach for process definitions, DMN tables, forms, business dictionaries, and lookup tables
• Manage and resolve cross-team technical dependencies between the Development POD, Solution Architecture, and the Service Store
• Support UAT technical validation and defect resolution and provide input to runbooks and knowledge transfer to BPM Admins and IT Operations
• Contribute to backlog sizing and complexity assessment using defined criteria such as steps, integrations, rules complexity, and data model complexity

Requirements

• End-to-end software engineering experience spanning 10-15 years
• Proven enterprise delivery experience with Camunda 8
• Strong capability in team leadership and facilitating technical discussions with client architecture boards
• Demonstrated migration leadership moving legacy BPM platforms to Camunda using parallel-run cutover patterns
• Advanced Camunda 8 platform knowledge across Zeebe, Operate, Tasklist, and Connectors
• Solid understanding of BPMN 2.0, DMN/FEEL, and Camunda Forms

Nice to have

• TIBCO BPM migration experience
• Experience with OIDC providers such as Microsoft Entra ID or Okta in Camunda contexts
• Working knowledge of Camunda deployment architecture including HA and PostgreSQL as secondary storage