> Markdown version of [/jobs/ext/3825540-senior-software-engineer-client-lifecycle](https://www.wearedevelopers.com/jobs/ext/3825540-senior-software-engineer-client-lifecycle). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Software Engineer - Client Lifecycle

- **Company:** Virta Health
- **Location:** San Francisco, CA, United States
- **Experience:** Expert
- **Salary:** $161,500.0 - $232,500.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Clinical Data Repository, Code Review, Open Access, Systems Development Life Cycle, Standard Sql, Salesforce.Com, TypeScript, Cloud Platform System, ReactJS, Backend, Event Driven Architecture, Front End Software Development, Zuora
- **Published:** October 18, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=22d07a7fbd31e5d5

## About the Role

* 5+ years building and operating backend services in production, in Go or another statically typed language
 * Experience with event-driven architectures and the failure modes that come with them - eventual consistency, ordering, idempotency, and systems that disagree with each other
 * Strong SQL, and comfort working across both application code and the analytics layer
 * You've owned a system where correctness had consequences outside the company - billing, payments, claims, ledgers, or regulated reporting
 * A track record of working directly with non-engineering stakeholders: turning a finance or operations problem into a design, and explaining the tradeoffs back
 * Experience with a major cloud platform (we use GCP)
 * Working with AI to accelerate development workflows and enhance the SDLC
 * Experience in frontend development with React and Typescript., * You have a strong sense of ownership and take initiative while empowering others to do the same
 * You prioritize positive impact over busy work
 * You have no ego and understand that everyone has something to bring to the table regardless of experience
 * You appreciate transparency and promote trust and empowerment through open access of information
 * You are evidence-based and prioritize data and science over seniority or dogma
 * You take risks and rapidly iterate

## Description

As a Senior Software Engineer on ReCon (Revenue & Contracts), you'll build the systems that turn care delivered into revenue recognized. ReCon owns Virta's quote-to-cash path end to end: how customer contracts and pricing are configured, how clinical events become billable episodes of care, how subscriptions and invoices are generated, how claims reach payors, and how we prove all of it reconciles across commercial, billing, and our clinical data. National health plans, PBMs, and large employers depend on the data we produce not just to pay us, but to bill their own clients - so correctness here is a customer-facing product, not back-office plumbing., * Lead projects end to end: take an ambiguous problem from a finance, RCM, or client-facing stakeholder, shape it into a design, drive it through review, and own it in production.

 * Build and extend the Go services behind Virta's quote-to-cash path - contract and pricing configuration, billable event generation, subscription and invoice management, and claims submission.
 * Make billing correctness provable. Expand the assertion and reconciliation framework that catches discrepancies across Salesforce, Zuora, and our clinical data before they ever reach a customer invoice.
 * Improve the reconciliation and billing data our health plan and employer partners depend on - not just to pay us, but to bill their own clients.
 * Design self-service tools so finance, RCM, and client operations can configure contracts, correct data, and run bulk changes without an engineer in the loop.
 * Apply AI where it earns its place.
 * Raise the bar around you through design and code review, and mentor engineers on the team., * First 30 days: Production PR merged and deployed; can whiteboard the money path unprompted; has independently found at least one thing that's wrong.
 * 60 days: A TDD survived architecture review; Stakeholders start to recognize you and work on building a future-looking feature/project with you.
 * 90 days: Owns an ambiguous problem and proceeds towards completion with a product mindset; another engineer's design got better because of your review.