Lead Software Engineer - Camunda

TymblHub; Hyderabad; On-site; INR 3,660,000 - 4,050,000; Full time

Job summary

Epam Systems seeks a Lead Software Engineer to own the Camunda 8 solution architecture and lead cross‑team migration across complex processes in Hyderabad. You will align process design, security models, integrations, and cutover strategy with vendors and internal teams.

You will drive Camunda 8 delivery, enforce standards, and guide migration through parallel-run and full redesign. Strong BPMN/DMN skills and leadership are required.

Qualifications

• 10–15 years of software engineering experience.
• Proven Camunda 8 delivery in large enterprise environments.
• Strong BPMN 2.0, DMN/FEEL and Camunda Forms skills.
• Experience migrating legacy BPM to Camunda via parallel-run cutover patterns.
• Ability to lead technical discussions with architecture boards.

Responsibilities

• Define and own the Camunda 8 target solution architecture for in-scope processes.
• Drive end-to-end migration across complexity tiers and cutover strategies.
• Enforce engineering standards, quality metrics, and best practices across teams.
• Coordinate with third-party vendors for platform and infrastructure setup.
• Support UAT validation, defect resolution, and knowledge transfer to BPM Admins.

Skills

Camunda 8

Zeebe

BPMN 2.0

DMN/FEEL

REST APIs

Leadership

Tools

Operate

Tasklist

Connectors

PostgreSQL

Job description

# Lead Software Engineer - CamundaEpam SystemsPosted on October 2, 2026---Experience8 - 12 yrsSalary (CTC)₹36.6L - ₹40.5LJob LocationHyderabad, IndiaVacancy1DesignationLead Software EngineerJob TypeNot specified---## Job DescriptionWe are seeking a **Lead Software Engineer - Camunda** to define and own the Camunda 8 solution architecture and lead end-to-end migration execution across complexity tiers. You will align process design, security models, integrations, and cutover strategy with cross-functional teams and vendors. Apply now to help deliver enterprise-grade BPM modernization.**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* Set and enforce Camunda engineering standards, quality metrics, and best practices across the Development POD* Lead complexity-tiered migration execution across AI-assisted generation, draft-plus-manual redesign, and full REST-based redesign* Design and validate the parallel-run and cutover strategy per process including routing, shared integration layer, and decommission triggers* Coordinate with the third-party vendor responsible for Camunda platform and infrastructure setup to align application-layer and platform-layer design* Validate integration points with existing REST APIs via the Integration Layer in coordination with the API team* Own the reference data migration approach for process definitions, DMN tables, forms, business dictionaries, and lookup tables* 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*** 10-15 years of overall software engineering experience* Proven Camunda 8 delivery experience in enterprise environments* Strong team management skills and ability to lead technical discussions with client architecture boards* Proven migration leadership experience moving legacy BPM platforms to Camunda using parallel-run cutover patterns* Strong Camunda 8 platform knowledge including Zeebe, Operate, Tasklist, and Connectors* Solid BPMN 2.0, DMN/FEEL, and Camunda Forms skills**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