Staff Software Engineer, Provider Engagement

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. We need to parse the posting. Let's extract sections: - About the role: The mission description? Actually "Our Mission" and "Your Impact on our Mission" maybe part of About the role. The posting includes "Our Mission" paragraph, then "Your Impact on our Mission". Could be considered About the role. We'll put that as About the role. - Responsibilities: The bullet list under "What You'll Do". Also later "Your day to day is…" includes more responsibilities. We'll combine. - Requirements/Qualifications/Skills: The "You'll be successful in this role if you have…" list includes experience, etc. Also "You'll enjoy this role if you are…" includes traits. Those could be Skills/Qualifications. We need to decide sections: maybe Requirements (experience), Skills (technical). But we can combine into Requirements and Skills. The instruction: prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills. But we need to avoid filler. Pay: The posting includes "NYC Base Salary Range $211,000—$285,000 USD". That's specific. So we can include Pay section. Benefits: There's a Benefits bullet list after "Benefits". So include Benefits. Schedule: Not mentioned explicitly. There's "Flexible, hybrid work environment". That's schedule? Could be considered Schedule. But we need real specific content: "Flexible, hybrid work environment at our convenient Soho location". That's schedule info. So we can include Schedule. Qualifications: Might be covered by Requirements. We could have Requirements (experience, technical) and Skills (traits). But to avoid many thin sections, maybe combine Requirements and Skills into one "Requirements" section. However the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. Could include Requirements and Skills separately if we have distinct content. Let's see: "You'll be successful in this role if you have…" includes experience, technical skills, etc. "You'll enjoy this role if you are…" includes personal traits, motivations. Those could be Skills. So we could have Requirements (experience, technical) and Skills (personal attributes). That seems reasonable. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Now we need to extract content for each. About the role: Combine "Our Mission" paragraph and "Your Impact on our Mission". Let's capture: 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 We're building Zocdoc's provider engagement platform — a system that understands where each practice is in their journey and delivers personalized experiences that deepen their relationship with our platform. Think: intelligent recommendations, engagement scoring, AI-assisted practice management, and a provider experience that makes Zocdoc essential to daily operations. As Staff Engineer, you'll own the technical architecture for core components of this platform. You'll design systems that integrate ML models built by our Data Science team, build the data pipelines that power personalization, and ensure our product surfaces can consume intelligence seamlessly. We'll put that as About the role. Responsibilities: Combine "What You'll Do" bullet list and "Your day to day is…" paragraph. What You'll Do list: - Own architecture for a major domain practice intelligence APIs, recommendation serving, orchestration layer, or AI-assisted management - Design data pipelines that compute engagement signals, aggregate practice profiles, and feed downstream systems - Integrate ML models built by Data Science into production model serving, feature pipelines, monitoring, and feedback loops - Define APIs and contracts between platform services and product surfaces - Lead complex cross-team projects and drive alignment on technical direction - Make build-vs-buy decisions for infrastructure components - Mentor engineers and raise the bar on system design and operational excellence Your day to day is… paragraph: Technical ownership of Zocdoc's Provider Engagement Platform, including roadmapping, prototyping, and leading 0-1 projects that span data infrastructure, ML integration, and product surfaces Designing and building the unified practice intelligence layer, aggregating fragmented data into real-time profiles that power personalization and recommendations Architecting event pipelines that capture engagement signals, compute health scores, and feed downstream ML models Integrating ML models built by Data Science into production systems, model serving, feature pipelines, monitoring, and feedback loops Defining APIs and contracts between platform services and product surfaces (homepage, in-product messaging, CRM, Sales tools) Making build-vs-buy decisions for infrastructure components (event systems, feature stores, in-product messaging platforms) Analyzing and decomposing complex product challenges to drive sound design decisions Working hands-on with your team and shipping production code using C#, React, and AWS technologies Collaborating with our agile team of dedicated engineers, product managers, designers, and data scientists Mentoring your peers and colleagues by giving thoughtful feedback, with the notion that helping others means learning and growing yourself We'll combine into a

• list. Ensure no duplication. Some items repeat (e.g., Integrate ML models, Defining APIs, Making build-vs-buy decisions, Mentor engineers). We can deduplicate but must preserve all substantive info; we can keep duplicates? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicates are still substantive but repeating may be okay. However we could keep both but it's repetitive. Might be okay but better to keep unique to avoid redundancy. However "Preserve ALL substantive information" could be interpreted as not omitting any info; duplicates are still info but repeating them doesn't lose info. It's okay to keep duplicates but might be considered unnecessary. I'd deduplicate to keep concise but still preserve all unique points. The duplicates are same meaning; we can keep one. Let's list unique responsibilities: - Own architecture for a major domain practice intelligence APIs, recommendation serving, orchestration layer, or AI-assisted management - Design data pipelines that compute engagement signals, aggregate practice profiles, and feed downstream systems - Integrate ML models built by Data Science into production model serving, feature pipelines, monitoring, and feedback loops - Define APIs and contracts between platform services and product surfaces - Lead complex cross-team projects and drive alignment on technical direction - Make build-vs-buy decisions for infrastructure components - Mentor engineers and raise the bar on system design and operational excellence - Technical ownership of Zocdoc's Provider Engagement Platform, including roadmapping, prototyping, and leading 0-1 projects that span data infrastructure, ML integration, and product surfaces - Designing and building the unified practice intelligence layer, aggregating fragmented data into real-time profiles that power personalization and recommendations - Architecting event pipelines that capture engagement signals, compute health scores, and feed downstream ML models - Defining APIs and contracts between platform services and product surfaces (homepage, in-product messaging, CRM, Sales tools) (more specific) - Making build-vs-buy decisions for infrastructure components (event systems, feature stores, in-product messaging platforms) (more specific) - Analyzing and decomposing complex product challenges to drive sound design decisions - Working hands-on with your team and shipping production code using C#, React, and AWS technologies - Collaborating with our agile team of dedicated engineers, product managers, designers, and data scientists - Mentoring your peers and colleagues by giving thoughtful feedback, with the notion that helping others means learning and growing yourself We still have duplicates: Mentor engineers appears twice (general and specific). We'll keep one maybe more detailed. We'll keep the specific: Mentoring your peers and colleagues by giving thoughtful feedback, with the notion that helping others means learning and growing yourself. Also "Define APIs and contracts between platform services and product surfaces" appears twice with more detail; keep the detailed one. "Make build-vs-buy decisions for infrastructure components" appears twice; keep detailed. Now we have list. Now Requirements: from "You'll be successful in this role if you have…" list: - 8+ years of software engineering experience with demonstrated technical leadership - Experience building data-intensive systems event pipelines, aggregation services, or real-time data serving - Comfort integrating ML into products you've worked with Data Science to take models from notebook to production - Strong API and data modeling skills you design schemas and interfaces that evolve gracefully - Ability to navigate ambiguity you break product vision into concrete technical milestones - Excellent communication you write clear design docs and explain tradeoffs to product partners - Track record of shipping you deliver high-quality systems, not just designs We'll put as
  • . Skills: from "You'll enjoy this role if you are…" list: - Inspired by the opportunity to positively impact the healthcare experience for millions of patients and providers - Passionate about building data-intensive platforms that power intelligent, personalized experiences at scale - Product-driven with a relentless focus on user needs, and excited to partner closely with cross-functional teams from early ideation through delivery - Energized by designing scalable platform systems data pipelines, APIs, and real-time services that power intelligent product experiences - A fervent champion of engineering fundamentals who enjoys driving adoption of best practices in code health, testing, and observability across teams - A leader who mentors and grows engineers, cultivates innovation, and drives cross-collaboration across multiple teams - A believer that diverse and inclusive teams and cultures are non-negotiable - An entrepreneur with strong ownership who can thrive in an ambiguous and fast-changing environment We'll put as
    • . Benefits: list after "Benefits". Let's extract: - Flexible, hybrid work environment at our convenient Soho location - Unlimited Vacation - 100% paid employee health benefit options (including medical, dental, and vision) - Commuter Benefits - 401(k) with employer funded match - Corporate wellness program with Wellhub - Sabbatical leave (for employees with 5+ years of service) - Competitive paid parental leave and fertility/family planning reimbursement - Cell phone reimbursement - Catered lunch every day along with beverages and snacks - Employee Resource Groups and ZocClubs to promote shared community and belonging - Great Place to Work Certified We'll put as
      • . Pay: "NYC Base Salary Range $211,000—$285,000 USD". Also mention "Base salary offered is determined by a number of factors including the candidate’s experience, qualifications, and skills. Certain positions are also eligible for variable pay and/or equity; your recruiter will discuss the full compensation package details." That's substantive. We'll include that. Schedule: "Flexible, hybrid work environment at our convenient Soho location" already in Benefits. But schedule could be that. However we already used that in Benefits. Might duplicate. But we could treat schedule as "Flexible, hybrid work environment". Since it's already in Benefits, we could still include Schedule section with that info. But that would duplicate. The