Staff Solutions Engineer - API Platform

About the Role

The Synchronizer API is the strategic core of NexHealth. The SaaS product was the wedge that gave us deep integration with thousands of practice management systems – the API is what we built that wedge for, and it’s where the next decade of the company gets built.

This role exists to scale that. You’ll be the founding senior Solutions Engineer on the API team – the technical anchor on our most important enterprise opportunities and the person who makes it possible to land them.

In this role, you will:

• Anchor our most strategic enterprise opportunities: partnering with Enterprise Sales across discovery, scoping, technical design, and implementation on the deals that matter most.
• Own complex integrations end-to-end: from first technical conversation through production launch, including the implementation phase where the hardest technical work happens.
• Accelerate growth in our highest-potential API customers: deepening technical partnership with the customers building the most ambitious products on top of our platform.

You'll work directly with senior leadership across Product, Engineering, and Go-to-Market – and you'll set the bar for the API Solutions function we'll build around you.

What You’ll Do

• Own the technical relationship on flagship deals. Run pre-sales discovery, scope Statements of Work, design integration architectures, and stay attached through implementation. 
• Translate customer workflows into reliable system designs. Map real-world workflows into data flows, endpoints, webhook patterns, retries, and ordering across heterogeneous EHR/PMS systems. Find the edge cases before they find production.
• Be the SME on the Synchronizer API. Advise customers on architecture, data modeling, integration patterns, reliability, and performance – the kind of guidance that comes from actually understanding what’s underneath the API.
• Build the artifacts that scale you. Reference architectures, prototype apps, sample code, integration guides, demo environments. Anything that compresses a customer’s time-to-value or removes you from the next conversation that doesn’t need you.
• Close the loop with Product and Engineering. Bring back signal, not noise, on what’s blocking enterprise adoption, what should ship next, and where the docs are lying. You’ll have a direct line to the people who can fix it.

How You’ll Work

• Project ownership, not ticket-taking. You run cross-functional programs end-to-end. SOWs, pilots, escalations – you drive them.
• First-principles debugging. You go deep on ambiguous issues, design novel solutions, and don’t hide behind "the docs say."
• Executive-grade communication. Same person, different audiences: a CTO on Tuesday, their senior engineer on Wednesday, our COO on Thursday. All three walk away clearer than when you started.
• Builder mindset. You’d rather ship a working prototype than write a deck about one. You leave behind tools, templates, and patterns that make the next person faster.

What You’ll Bring

• 7+ years in Solutions Engineering, Technical Account Management, Developer Relations, or a similar customer-facing technical role at a SaaS or API-first company.
• Hands-on fluency with REST APIs, JSON, OAuth2, and webhooks. You’re comfortable in logs, in someone else’s codebase, and on a shared screen with a customer’s engineer.
• A track record of owning complex, multi-month enterprise integrations end-to-end — not just the kickoff call.
• Demonstrated ability to translate between executives, engineers, and operators without losing precision.
• Comfort with ambiguity. The first version of this role, the first version of the playbook, the first version of the team — you want all of that.

Bonus points for

• Experience as the first or founding SE at a previous company.
• Background as a software engineer earlier in your career.
• Prior experience with healthcare data (EHR/PMS, HL7, FHIR) or other regulated/legacy data ecosystems.

What You Won’t Be Doing

• Managing a team – yet. This is a senior IC role. We expect to build a team around you, but you’ll earn that by shipping first.
• Doing tier-1 support. You’re focused on enterprise pre-sales and our highest-leverage customers, not the inbound queue.
• Sitting in meetings all day. We want someone who ships, not someone who presents.
• Selling a product that doesn’t work. The Synchronizer API is real, in production at scale, and the technical foundation our own SaaS is built on.