Senior Software Engineer II

Virta Health is hiring a Senior Software Engineer II to build and evolve its data engagement platform for Member Marketing and Coverage Eligibility. The role focuses on reliable, observable data processing and integrations, with end-to-end ownership of foundational infrastructure and collaboration across Product, data, and external partners.

Responsibilities:

• Design and own the data contracts and processing semantics that make identity, deployment context, eligibility, audience attributes, deduplication, and field persistence explicit and testable across the data lifecycle
• Build end-to-end observability and reconciliation that explains how source records become downstream outcomes — including data freshness, expected filtering, rejected records, deduplication, safe replay, and repair of historical state
• Lead technical discovery and delivery of high-impact work across Member Marketing and Coverage Eligibility, collaborating closely with Product, data, and external partners
• Partner with Product and Growth stakeholders to translate evolving audience and workflow requirements into reusable platform capabilities, keeping business policy cleanly separated from technical implementation
• Design for correctness and auditability in regulated workflows, including data provenance, consent and suppression controls, rollback, replay, and safeguards against incorrect or cross-customer data use
• Modernize legacy, file-based processes toward well-contracted, event-driven integrations with strong observability, resilience, and security
• Own systems end-to-end — from architecture through operations — driving improvements in reliability, partner experience, and long-term maintainability
• Apply an experiment mindset (Build-Measure-Learn) to validate assumptions and focus on outcomes over output, using AI-assisted tooling where it improves speed and quality without compromising correctness

Requirements:

• Strong backend engineering skills, with a track record of building and operating scalable, reliable systems in production — ideally involving APIs, event-driven architectures, or data integrations
• Experience designing data-intensive systems where correctness depends on explicit schemas, identity or entity resolution, incremental processing, idempotency, lineage, reconciliation, and recovery from partial failure
• A proactive, ownership-first mindset — you don't wait for direction; you surface problems, propose solutions, and drive them to completion
• High agency and autonomy — able to navigate ambiguity, set direction, and execute independently while keeping stakeholders aligned
• Demonstrated technical leadership — able to establish architecture and engineering standards across team boundaries, mentor senior engineers, and turn ambiguous business problems into a sequenced technical roadmap
• Experience with B2B or partner-facing data systems, such as file-based integrations, real-time data exchanges, or partner APIs
• Sound judgment about AI-assisted tooling — where it improves engineering velocity, data-quality investigation, documentation, and operations, and where deterministic controls are required for correctness and safety
• Strong collaboration and communication skills, especially in cross-functional environments involving Product, data, and external partners
• Typically 10 + years of software engineering experience, with demonstrated ability to operate at a senior level
• Experience in healthcare data domains, such as eligibility, claims, EHR, or member marketing — especially in regulated or partner-integrated environments
• Experience with customer-data, marketing-automation, or audience-activation platforms such as Braze, Segment, Salesforce Marketing Cloud, or comparable systems
• Prior work modernizing legacy data flows, including migrations from SFTP/file-based systems to API- or event-driven architectures
• Familiarity with data quality frameworks, lineage tracking, or automated anomaly detection in data pipelines
• Demonstrated use of AI/LLM-based tooling in engineering work — e.g., for test generation, documentation, data mapping, or observability
• Previous roles where you've had to influence without formal authority, or drive change across teams or systems you didn't own directly