Senior individual contributor responsible for the design, deployment, and operational excellence of the Temporal.io workflow orchestration platform powering Medicare claims automation. Owns the Temporal Server topology on GKE, the Python SDK worker framework, and the durable-execution patterns the migration depends on. Also owns the config interpreter — the generic Python workflow that reads versioned JSON/YAML configs produced by the canvas and executes them by dispatching to a library of pre-built activities. This is the bridge that turns canvas-authored workflows into running Temporal executions; no per-workflow Python is generated or hand-written for the common case. Operates as a hands-on technical authority, influencing architecture across teams without formal authority.
This role supports a strategic platform initiative within Medicare Claims Engineering to migrate the existing Automation Anywhere RPA portfolio onto a up-to-date, code-and-config-driven workflow platform built on Temporal.io,
Python/Playwright, and Google Kubernetes Engine (GKE). Workflows are visually authored on a custom React Flow canvas that emits versioned configs executed by Temporal workers. The platform operates under HIPAA governance.
Key Responsibilities
- Own the architecture of the Temporal Server cluster on GKE, including service topology, namespace strategy, persistence layer (Cloud SQL PostgreSQL with HA), and history shard sizing.
- Design and own the config interpreter: the generic Python workflow that loads canvas-authored JSON/YAML configs and dispatches to pre-built activities, eliminating the need for per-workflow Python codegen or hand-coded workflows in the common case.
- Own the activity library contract and the domain-plugin pattern that lets each trigger scenario register its SQL queries, scraping configuration, prompts, and SOAP envelopes without modifying shared executors.
- Design Python-based wo