Staff Platform Engineer, AI Enablement

Our Mission You call. You wait. You call again. In every other part of your life, you book in seconds. In healthcare, you’re blocked.

We’re here to give power to the patient.

For nearly 20 years, we’ve built the leading healthcare marketplace - helping tens of millions of people find and book the care they need. Now, we’re going further: building our infrastructure beyond Zocdoc’s marketplace to power access to care wherever patients search, from provider websites and insurance directories to search engines, AI platforms, and more.

Healthcare still lacks something every other major consumer industry takes for granted: a seamless way to go from seeking to getting . We don’t want to own the front door to care; there isn’t one. We want to make sure all of those doors open when patients are knocking.

Fixing healthcare starts with fixing access to it. And we’re still just getting started.

Your Impact on Our Mission

At Zocdoc, we’re on a mission to give power to the patient — and that starts with enabling every person at Zocdoc to build, ship, and leverage technology safely, confidently, and with leverage.

As a Staff Platform Engineer focused on AI Enablement, you will design, build, and evolve the foundational systems, tooling, guardrails, and paved roads that create leverage across our engineering organization and beyond — accelerating delivery while improving reliability, consistency, and developer experience. Critically, this role has a wider aperture than most platform roles: you will own AI enablement for both technical and non-technical stakeholders , building opinionated platforms and safe onramps that allow every builder at Zocdoc — regardless of their engineering background — to harness AI tools productively and securely.

This role sits within the Infrastructure organization. You will collaborate across the business to turn platform strategy into practical, adoptable solutions — working side by side with a parallel squad focused on the technical engineering audience, and bridging the gap between engineering-grade tools and the non-technical teams (People, Operations, Sales, Finance, and others) who increasingly build and depend on AI-powered workflows.

The role emphasizes hands-on technical leadership (~80%) with meaningful input into platform direction (~20%). Your work will abstract operational complexity, define guardrails for safe AI usage, improve testability and safety, and streamline the builder journey across both software-engineering and non-engineering surfaces.

You’ll Enjoy This Role If You…

• Enjoy building platforms that enable productivity, consistency, and autonomy for diverse audiences
• Enjoy learning and teaching others about leveraging AI-based technologies to achieve real-world results
• Are motivated by making other people more effective; not just shipping your own features
• Like designing cohesive developer and/or non-technical experiences that teams actually want to adopt
• Care deeply about empathy, usability, and reducing cognitive load
• Prefer solving real problems through thoughtful design, iteration, and collaboration
• Are comfortable translating complex technical concepts for non-technical stakeholders — and enjoy doing it
• Find satisfaction in building systems that scale predictably and help others succeed
• Thrive in environments with ambiguity, frequent change, and evolving prioritization — and bring clarity where there was none
• Are a natural collaborator

Your Day to Day

• Design and build platform services and solutions that are secure, scalable, and intentionally easy to use — including CI/CD pipelines, developer tooling, shared infrastructure patterns, and AI-powered developer workflows
• Contribute to the technical direction of Zocdoc’s internal developer platform, including paved roads, tooling, and shared workflows for both engineering and non-engineering builders
• Build and maintain opinionated platforms and guardrails that enable non-technical teams to safely create, share, and operationalize AI tools — without introducing security vulnerabilities, access control failures, or operational bottlenecks
• Define and evolve the software development lifecycle for non-traditional builders: access controls, credential management, testing patterns, on-call/support paths, and contribution workflows
• Collaborate across teams to understand real developer pain points and non-technical stakeho…