Solutions Engineer

We’re building a new healthcare clearinghouse

Stedi is the only headless clearinghouse and RCM engine. Headless means every part of our product is accessible via API. Developers and AI agents build their own interface on top of it. By offering modern, AI-ready APIs alongside traditional real-time and batch EDI processes, we enable both healthcare technology businesses and established players to exchange mission-critical transactions. Our clearinghouse product and customer-first approach have set us apart. Stedi was ranked by Ramp as one of the fastest-growing SaaS vendors.

Stedi has lightning in a bottle: engineers and designers shipping products week in and week out; a lean business team supporting the company’s infrastructure; a passion for automation and eliminating toil; and $142 million in funding from top investors like Stripe, Addition, USV, Bloomberg Beta, First Round Capital, and more.

To see what we ship, watch the 2026 Stedi Keynote. To learn more about how we work, watch our founder Zack’s interview with First Round Capital.

What we are looking for

We’re growing our Solutions Engineering team. Our customers are building on a clearinghouse, which means their first months with Stedi are a technical project: mapping their use case to our APIs, testing submissions and reading what comes back, and getting to production volume without surprises. How well that goes decides whether a customer ever realizes the value they bought.

As a Solutions Engineer, you will be the technical counterpart to our sales and account management teams, ensuring that they have everything they need to make customers successful with Stedi. You’ll work with customers from their first integration call through to running full production volume. You’ll also build the demos, guides and internal documentation that empowers the rest of customer-facing team to answer technical questions without you, and you’ll be the conduit back to Product when the answer is “we don’t do that yet”. The work moves fast, spans a lot of surface area, and has a real impact - on our customers, our revenue, and our roadmap.

Who you are

• You are technical. You understand and have experience using and integrating APIs, and have a familiarity with data formats and standards such as JSON, X12, and other flat file formats.
• You are proactive by default . You don’t wait for a ticket. You decide which customers need attention and when, usually before they ask, based on what you can see in their data and where they are in their ramp.
• You have a product mindset. You go beyond helping customers with the task at hand. You are able to intuitively understand product gaps and are able to articulate those to the engineering and product teams, and ensure those requirements satisfy the customer’s needs.
• You have deep customer empathy and have experience in customer-facing roles. You can understand a customer’s needs and quickly establish credibility by getting into the weeds on technical areas of a product to ensure they’re getting the most value. You keep customers at the center of your work and always prioritize customer relationships.
• You have subject matter expertise in revenue cycle management or are excited to learn. Bonus points if you have experience working at an RCM company and understand the full cycle of how healthcare technology companies run eligibility checks, submit claims, check claim status, and reconcile ERAs.
• You do what it takes to get the job done. You are resourceful, self-motivating, self-disciplined, and don’t wait to be told what to do. You put in the hours.
• You are exceptional at staying on top of many open threads simultaneously. You are hyper-responsive, organized, and thorough.
• You move fast. We move fast as an organization. Our median response time to customers during business hours is 3.4 minutes. This requires an ability to match our pace and not get lost by responding with urgency (both externally to customers and internally to stakeholders), communicating what you are working on, and proactively asking for help or feedback when you need it.

What you’ll do

• Serve as the technical counterpart on pre-sale deals. Ask the questions that qualify the opportunity, determine what the use case actually requires, explain to the customer what kind of integration this will be, and which product gaps have to be closed before we can deliver.
• Own technical design during the proof-of-concept phase. Establish use cases and requirements, clear blockers, and make sure customers have what they need to test their integration and interpret the results.
• Coordinate payer list matching and run insurance discovery batch tests, then share and interpret the results so customers can see what good looks like.
• Drive ramping customers to expected transaction volume on the expected timeline. Build the migration plan, track actual volume against what was sold, and identify and clear the root causes of processing errors.
• Build the internal material that makes new functionality sellable: feature overviews, positioning and talk tracks, demos, best-practice writeups, and qualification criteria. Answer functionality questions for the customer-facing team, or track down the person who can.
• Represent customers to Product. Write the one-pagers that define customer problems, shape requirements, and co-own a customer-driven feature backlog, including how much customer weight sits behind each request.

We’ve been made aware of individuals impersonating the Stedi recruiting team. Please note:

• All official communication about roles at Stedi will only come from an @stedi.com email address , or from our official identification verification partner, Persona, @frompersona.com.
• If you’re unsure whether a message is legitimate or have any concerns, feel free to contact us directly at Ver el correo electrónico en codingjobboard.com.

We appreciate your attention to this and your interest in joining Stedi.

At Stedi, we’re looking for people who are deeply curious and aligned to our ways of working. You’re encouraged to apply even if your experience doesn’t perfectly match the job description.