Full platform lifecycle: solution architecture → BPMN/DMN modelling → integration → observability → production operations → support processes
Production migration 8.6 → 8.8 with zero downtime in a live banking environment — one of the earliest such migrations on Camunda 8
Observability stack from scratch: Kibana dashboards for process health, Prometheus + Grafana for cluster and pipeline metrics, alerting and incident response
CI/CD for BPM: Helm charts, Argo CD, GitOps deployment of processes and platform components
Hands-on code: wrote Zeebe job workers (Java/Spring) for banking integrations myself, then trained team leads to build and own their workers — not a slideware architect
Integration & data architecture: synchronous and asynchronous integration patterns with external systems, Kafka where event-driven flow fit; designed PostgreSQL data stores beyond Elasticsearch, data retention rules, and all external interface contracts
Modern Camunda 8 practice: migrated custom Java job workers to the Camunda Connectors runtime (dedicated connectors pod) — less custom code, faster process changes
Team enablement: hired and mentored developers; trained analysts, DevOps engineers, and business users to run BPM without me — the platform outlives the consultant
Business-facing: translated business requirements into executable BPMN processes and DMN decision tables directly with department heads