HaloMD — VOB Platform

VOB is the first decision point in every arbitration case: routing a dispute to federal NSA/IDR or one of 21 state-specific processes, a call that determines every downstream deadline and filing rule. The pod needed a reliable frontend and backend to support verifiers making that call, plus a growing rules engine to reduce manual routing work over time.

Regulated healthcare domain with real patient and payer data, meaning every feature carried compliance weight beyond typical UX/engineering tradeoffs. As technical lead I owned delivery across both frontend and backend for the pod, while also being accountable for surfacing delivery risk to the client proactively rather than reactively.

Led a cross-functional pod building the rules-engine frontend (dynamic condition/action builders, rule-suggestion UI surfacing gap patterns from historical data) in React/TypeScript, backed by FastAPI services for case eligibility and rule-conflict detection. Coordinated schema alignment between frontend and backend as a first-class workstream rather than an afterthought, and introduced a recurring team status-report cadence to give the client early visibility into risks and blockers before they reached the daily sync.

Shipped incremental rules-engine capabilities (rule suggestion UI, dynamic field configuration) that moved routing decisions from fully manual toward assisted. Established a repeatable delivery-risk reporting process that surfaces blockers and QA findings to the client ahead of the daily standup, reducing end-of-sprint surprises.