Technical Solutions Engineer

About the Role

What You'll Do

• Serving as the primary technical resource for clients doing API-based and headless integrations with the Fabric platform, owning their integration success end to end without requiring R&D involvement in day-to-day client meetings
• Attending regular client calls to support architecture design, API implementation, and testing, translating complex technical requirements into guidance that both client engineers and non-technical stakeholders can act on
• Shipping minor API enhancements and configuration changes tailored to unlock specific, high-value client use cases, working within a clear scope that protects the core product roadmap
• Building and maintaining client-facing SDKs, boilerplate code samples, and API documentation to simplify the developer experience and enable self-service onboarding for new clients
• Partnering with the Solutions Design team to understand client requirements and translate them into technically sound integration approaches
• Debugging client integration issues independently, triaging what requires a product engineering fix versus what can be resolved at the API layer or through configuration
• Communicating API feature changes and rollouts to active client teams so no integration breaks quietly

Why You Might Be a Good Fit

• You are a client-facing engineer who actually codes: You have been the person clients call when their integration breaks, and you find that satisfying rather than draining.
• You translate fluently in both directions: You can hold a technical architecture conversation with a client engineering team in the morning and present a clean summary to their non-technical VP in the afternoon without losing either audience.
• You own outcomes, not just tasks: When a client is stuck, you investigate before escalating, and you treat handing a problem back over the wall as a last resort.
• You treat documentation and code samples as a force multiplier: You would rather build a well-documented SDK that enables ten clients to self-serve than answer the same integration question ten times.
• You are comfortable at the intersection of product and customer success: The role exists because Fabric needs one person who can do both, not two people doing half of each.

This Might Not Be The Right Fit If...

• You want to focus exclusively on the core product roadmap. This role exists specifically to absorb client work and keep it off the core engineering team, not to move you closer to it.
• You expect a commission structure and a traditional pre-sales SE model. There is no quota here; success is measured by client integration success, not deal velocity.
• You are uncomfortable with ambiguity in client requirements. Clients building headless solutions often cannot fully articulate what they need until they see options; you will need to help them get there.
• You prefer async-only work. This role involves regular, scheduled client-facing meetings and real-time debugging alongside client engineers.
• You need deep healthcare domain expertise to feel confident. The work here is API integration; clinical context helps but is not the foundation.

Your Qualifications

• 4+ years of experience in a technical client-facing role: solutions engineering, technical account management, implementation engineering, or developer relations, with real coding responsibility, not just demo delivery
• Strong proficiency in Ruby on Rails, the core language of Fabric's platform and the foundation for all API work
• Fluency with RESTful API design and integration patterns: authentication flows (OAuth 2.0, API keys), webhooks, pagination, error handling, and debugging each
• Experience building or contributing to client-facing developer resources: SDKs, code samples, or API documentation
• Strong written and verbal communication, including the ability to translate between engineering-level detail and business-level requirements in real time
• Demonstrated ability to independently debug complex integration issues, including working alongside client engineers in real time to isolate root causes

Bonus Points

• Exposure to HL7, FHIR, or EHR API integrations (Epic, Cerner, or similar)
• Experience with headless or composable architecture patterns in a B2B context
• Experience at a digital health, health tech, or health plan company
• Experience with API documentation platforms such as Stoplight, ReadMe, or the OpenAPI specification

The national pay range for this role is $140,000.00 - $170,000.00 per year. Actual compensation will be determined by factors such as the candidate's geographic market, experience, skills, and qualifications. Certain roles may also be eligible for additional compensation, including a comprehensive benefits package such as medical, dental, vision, unlimited PTO, and a 401(k) plan, stock options and bonuses. If your compensation requirement is greater than our posted range, please still consider applying; a determination can be made based on unique qualifications. Expected compensation ranges for this role may change over time.