Staff Solutions Engineer - API Platform

NexHealth is a company focused on accelerating innovation in healthcare by connecting patients, providers, and developers. They are seeking a Senior Solutions Engineer to anchor strategic enterprise opportunities, own complex integrations, and deepen technical partnerships with API customers.

Responsibilities:

• 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
• 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

Requirements:

• 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
• 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