Backend Software Engineer II- Data Platform

Team: All Teams

Location: United States

Commitment: Full Time- Exempt

Workplace Type: remote

Vida is looking for a Backend Software Engineer II to help build the data platform that supports much of Vidas business. Our team builds the systems that turn data from health plans, employers, and other partners into reliable information that Vidas products and operations can use. That includes member identity, eligibility, billing, partner integrations, and the data foundations behind reporting and analytics. You will work on backend services and data-intensive systems, primarily in Python, and take features from design through production. You will start with well-defined problems and grow toward owning services and technical decisions independently.

Responsibilities:

Build backend services that ingest, validate, reconcile, and serve data from external partners.
Develop systems for member identity, eligibility, billing, and other core business domains.
Design APIs, asynchronous workflows, and data pipelines used across Vida.
Make systems resilient to incomplete, duplicated, delayed, and inconsistent real-world data.
Build safe ways to retry, replay, and recover data when something goes wrong.
Improve the reliability, observability, testing, and performance of production systems.
Work with Engineering, Product, and Operations to figure out what needs to be built when the requirements are incomplete or messy.
Additional responsibilities as needed.

Qualifications:

Bachelors degree at a minimum.
2+ years of professional experience building backend software.
Strong programming fundamentals- we primarily use Python.
Experience working with relational databases and SQL.
Experience building systems that process, transform, or move significant amounts of data.
A solid understanding of testing, debugging, APIs, and common distributed-system failure modes.
Experience deploying or operating software in a cloud environment.
Good instincts around correctness, including validation, idempotency, retries, and edge cases.
The ability to get into an unfamiliar codebase, understand how it works, and improve it without making it more complicated.
Clear written communication and an ability to explain technical decisions and tradeoffs.
You do not need previous healthcare experience or experience with every technology we use.

Preferred:

Data-intensive backend systems, ETL/ELT pipelines, or event-driven architectures.
PostgreSQL, analytical warehouses, or data modeling.
Infrastructure as code, containers, or workflow orchestration.
Identity resolution, entity matching, eligibility, claims, or other healthcare data.
Regulated or security-sensitive production environments.