Sr. Software Development Engineer

Vatica + Cozeva: Shaping the Future of Value-Based Care  

Vatica Health’s merger with Cozeva brings together two industry leaders each recognized as Best in KLAS in their respective domains to transform how payers and providers collaborate to improve outcomes. This unique combination of people, process, and technology unites Vatica’s #1-rated risk adjustment platform with Cozeva’s #1-rated quality and population health platform, creating the most comprehensive point-of-care solution for advancing value-based care.  

Together, Vatica + Cozeva empower providers with an integrated suite of capabilities including advanced analytics, payer interoperability, and clinical services to optimize both patient and financial outcomes.  

For our current and future employees, this merger represents an exciting opportunity to be part of something bigger:  

• A broader mission to improve healthcare quality and equity.  

• A deeper platform of technology, data, and clinical insight.  

• Greater potential for personal and professional growth within a fast-growing, category-defining organization.  

Join us and be part of Cozeva, a Vatica Health company as we build the future of value-based care: better for providers, payers, and patients alike. 

Sr. Software Development Engineer 

We’re looking for a hands-on technical lead who can architect, guide, and build high-quality systems. You’ll lead by design and example — helping the team develop software that’s modular, maintainable, and interoperable. 

Our stack spans Node.js, React, MongoDB, healthcare data models, and AI-powered analytics. But we’re not tied to any one language — we’re looking for someone who can bridge stacks, not guard them. 

Responsibilities: 

• Lead technical design discussions and translate specifications into reliable implementations. 

• Review and mentor developers on writing maintainable, low-coupled, reusable modules. 

• Design integrations across heterogeneous systems (e.g., Java to Node.js bridges, FHIR/HL7 data pipelines). 

• Improve code quality, structure, and consistency across services. 

• Build internal tools, SDKs, or shared libraries that promote reusability and standardization. 

• Own system-level performance, scalability, and resilience. 

• Collaborate with PMs, QA, and architects to shape deliverables and timelines. 

• Identify risks, propose architectural improvements, and simplify complex systems. 

• Help nurture a learning culture — reviewing code, organizing discussions, and documenting patterns.