Back to Search
Overview
Unavailable

This job may no longer be available

StaffInactive

Staff Software Engineer, Data Platform

Zocdoc

Zocdoc

Compensation

$180,000 - $275,000/year

New York, NY, United States; USA Remote
Hybrid
Posted March 10, 2026

Job Description

Our Mission

Healthcare should work for patients, but it doesn’t. In their time of need, they call down outdated insurance directories. Then wait on hold. Then wait weeks for the privilege of a visit. Then wait in a room solely designed for waiting. Then wait for a surprise bill. In any other consumer industry, the companies delivering such a poor customer experience would not survive. But in healthcare, patients lack market power. Which means they are expected to accept the unacceptable.

 

Zocdoc’s mission is to give power to the patient. To do that, we’ve built the leading healthcare marketplace that makes it easy to find and book in-person or virtual care in all 50 states, across +200 specialties and +12k insurance plans. By giving patients the ability to see and choose, we give them power. In doing so, we can make healthcare work like every other consumer sector, where businesses compete for customers, not the other way around. In time, this will drive quality up and prices down. 

 

We’re 18 years old and the leader in our space, but we are still just getting started. If you like solving important, complex problems alongside deeply thoughtful, driven, and collaborative teammates, read on.

 

Your Impact on our Mission:

We’re hiring a Staff Software Engineer (Data Platform) to define and lead the evolution of Zocdoc’s data platform at the intersection of data engineering and product engineering.

This role owns how data moves into, across, and out of our lakehouse and warehouse ecosystems. You’ll shape the contracts, access patterns, APIs, governance controls, and interoperability standards that enable teams to reliably produce and consume data at scale.

Unlike a traditional data engineering role, this position is focused on platform experience and data product design — building the frameworks, contracts, and service interfaces that make data trustworthy, compliant, and easy to use across both technical and non-technical stakeholders.

You will define how:

  • Product teams publish high-quality, validated data into the platform
  • Analytics and ML teams consume governed datasets with confidence
  • Reverse ETL and activation patterns safely operationalize data back into product systems
  • Access control, compliance, and governance are embedded into platform design by default

This is a highly cross-functional leadership role requiring deep data engineering expertise, strong product thinking, and the ability to influence standards across the organization.

You’ll enjoy this role if you are…

  • Passionate about designing data contracts and producer/consumer interfaces, not just pipelines.
  • Excited to build APIs, SDKs, and shared packages that product engineers adopt.
  • Motivated to define clear access patterns across warehouse, lakehouse, and downstream systems.
  • Energized by solving governance, schema evolution, and compliance challenges at scale.
  • Comfortable setting long-term architectural direction while still diving into implementation details.
  • Experienced in building a data product used broadly across both technical and non-technical stakeholders.
  • Excited about leveraging AI-assisted and agentic workflows to multiply engineering productivity.
  • Thoughtful about the guardrails, access controls, and governance required when enabling GenAI systems to interact with sensitive data.

Your day to day is…

  • Defining and evolving data contract standards across the company, including schema enforcement, versioning, and validation patterns.
  • Designing interoperable ingestion and publishing frameworks that enable upstream producers (e.g., product engineering teams) to integrate seamlessly with the data platform.
  • Building and standardizing APIs, libraries, or SDKs that simplify event logging, schema validation, and contract compliance.
  • Establishing best practices for schema registry usage and distributed schema validation across streaming and batch systems (e.g., Kafka-based systems).
pythongorustawsaibackenddataanalyticsproductdesign