Lead the replacement of a critical financial processing function within a large US benefits organization, separating it from a legacy core system into a standalone application. The legacy source code is unavailable, so existing behavior must be reconstructed from database extracts, historical outputs, documentation, and SME workshops, then validated against historical results.

Responsibilities:

  • Lead discovery with product, business, and technology teams; assess the current architecture and propose the target technical approach.
  • Define team composition and the technical roadmap, then lead implementation, migration, and production cutover.
  • Reverse-engineer legacy business rules and design and validate complex financial logic, including fund allocation, interest recalculation, receivables, period close, and audit trails.
  • Own high-volume historical data migration, including profiling, transformation, reconciliation, exception handling, and parallel-run validation.
  • Design integration architecture and lead requirements and architecture discussions with technical teams and business stakeholders.
  • Stay hands-on in design, code, and reviews, and ensure secure, controlled production delivery.

Requirements:

  • Led a legacy replacement, carve-out, or system separation through production cutover, with personal ownership of design and migration.
  • Deep experience with financial transaction systems involving ledgers, fund or account allocation, reconciliation, period close, adjustments, and audit trails.
  • Strong backend architecture experience; .NET is preferred, while Java, Go, or other enterprise backend experience may be considered.
  • Significant data migration and integration architecture experience, including API and feed contracts, idempotency, retries, observability, and reconciliation.
  • Production experience with Kubernetes and CI/CD in regulated or security-conscious environments.
  • Strong client-facing communication skills and ability to work independently in a remote environment.

Nice to have: Experience with royalty or rights-based payments, pension or benefit plans, HIPAA-regulated environments, Azure DevOps, on-premises Kubernetes, or Next.js.

Conditions: Remote work with strong overlap with US Pacific Time. The engagement begins with discovery and continues through a multi-month build and production cutover. Candidates must comply with healthcare data privacy and security agreements.