All jobs
Cognizant logo

Hiring for Kogito Lead Developer

Cognizant · Posted 1 month ago

  • Chennai, Tamil Nadu, India (Hybrid)
  • Full-time
  • 6-8 yrs

About the role

Apache Kogito Workflow Developer / BPM Engineer

Experience: 6-8+ years of software development experience, including 3+ years in workflow/BPM implementations. Strong hands-on expertise with Apache Kogito, jBPM, Camunda, or similar BPM platforms, along with cloud-native application development on Kubernetes and GCP.

Key Skills

  • Apache Kogito, BPMN 2.0, DMN
  • Java, Quarkus, REST APIs
  • Workflow Orchestration & Business Process Management (BPM)
  • Microservices & Event-Driven Architecture
  • Git, Maven, CI/CD
  • Google Cloud Platform (GKE, Apigee X, Pub/Sub, Cloud SQL PostgreSQL, Cloud Storage)
  • Process Monitoring, Audit Trails & Workflow Governance

Responsibilities

  • Design and develop business workflows, approval processes, task routing, SLA management, escalations, and exception handling using Apache Kogito, BPMN, and DMN.
  • Build and maintain Kogito services using Java and Quarkus, ensuring scalable and resilient workflow execution.
  • Integrate workflows with React applications, Node.js microservices, REST APIs, Pub/Sub events, and enterprise systems.
  • Develop decision models, business rules, and DMN decision tables to automate and standardize business processes.
  • Implement workflow monitoring, audit trails, process versioning, recovery mechanisms, and governance standards.
  • Support workflow deployments, troubleshoot production issues, resolve performance bottlenecks, and ensure platform stability.
  • Collaborate with architects, business analysts, developers, QA, and DevOps teams throughout design, development, testing, and release cycles.

Preferred Skills

  • Enterprise workflow modernization initiatives
  • Workflow governance and compliance frameworks
  • Kubernetes operations and containerized deployments
  • Cloud-native design patterns and event-driven integrations
  • Experience in regulated or large-scale enterprise environments

Skills

Apache Kogito, BPMN 2.0, DMNJava, Quarkus, REST APIsWorkflow Orchestration & Business Process Management (BPM)Microservices & Event-Driven ArchitectureGit, Maven, CI/CDGoogle Cloud Platform (GKE, Apigee X, Pub/Sub, Cloud SQL PostgreSQL, Cloud Storage)

Quark9 guide

How to land this Hiring for Kogito Lead Developer role

Our notes for applicants, based on how software engineering hiring usually works.

Resume checklist for this job

Most companies screen resumes with an ATS before a person reads them. Make sure each skill you genuinely have appears in your resume in the same words the job uses.

Must have

  • Apache Kogito, BPMN 2.0, DMN
  • Java, Quarkus, REST APIs
  • Workflow Orchestration & Business Process Management (BPM)
  • Microservices & Event-Driven Architecture
  • Git, Maven, CI/CD
  • Google Cloud Platform (GKE, Apigee X, Pub/Sub, Cloud SQL PostgreSQL, Cloud Storage)
  • Write each bullet as action plus result: "Cut p95 latency from 800 ms to 200 ms by adding Redis caching"
  • Keep a skills line that matches the job's stack word for word, so ATS filters pick it up
  • Put your strongest one or two projects first, with links to code or the live product
Check your resume against this job free

What interviewers expect: experienced

Interviewers want depth and judgement: trade-offs you made, people you guided and results across a team. Prepare two or three stories with clear impact.

How software engineering interviews usually run

  1. An online coding test or a recruiter screen on your stack and projects
  2. One or two technical rounds on data structures, problem solving and your core language
  3. A system design or low-level design round for mid and senior roles
  4. A hiring manager round on ownership, teamwork and how you handle production issues

Questions worth preparing

  • Design a URL shortener. How would you scale reads, and where would you cache?
  • Find the first non-repeating character in a string. What is the time complexity?
  • Explain how you would debug an API that became slow after a release.
  • Describe the hardest bug you fixed and how you found it.

Every company runs its own process, so treat this as a likely shape, not a promise. Practise a mock interview on Quark9 and get scored feedback before the real one.