Solutions Engineer

Key Responsibilities

• Pre-sales technical ownership: Join sales calls as the technical authority, run live demos, and scope proofs of concept with clear success criteria and a defined path to production.
• Integration and onboarding: Own the first 30 days of every new customer, writing sample code, and sitting in their repo until real traffic is flowing. Success is measured in time to first API call and time to production, not tickets closed.
• Keeping customers live: After launch, stay the technical point of contact, debugging latency, throughput, and streaming issues, escalating cleanly into engineering, and ensuring a problem never becomes a reason to leave.
• Expansion through depth: Look for the second and third use cases inside an account and help them build it.
• Turning deployments into proof: Every successful integration becomes a case study with real numbers behind it, from latency to cost to revenue impact, and produce the technical substance those numbers rest on.
• Being the bridge to engineering: See where the platform breaks before anyone else does, translate customer reality into prioritized, specific work, and fix the docs and samples yourself when that is faster than asking.

Skills, Knowledge and Expertise

• Can write production code, primarily in Python, and work inside a customer's codebase and build a working integration yourself without waiting on engineering.
• Have 3+ years in solutions engineering, sales engineering, forward-deployed engineering, or backend and infrastructure engineering with real customer exposure.
• Understand inference infrastructure, including GPUs, latency, throughput, streaming, and what actually breaks under load, and can explain a p99 to a founder and a business case to an engineer without losing either of them.
• Are commercially aware enough to know that a proof of concept without success criteria is really just a hobby, so you push for the decision instead of letting a pilot drift for months.
• Are fluent in both rooms, able to hold a technical design discussion with our engineers in the morning and a commercial conversation with a customer in the afternoon, and neither side should feel you are out of your depth.
• Are relentless, so when an integration stalls you change the approach, get on a call, or fly out rather than waiting for a reply that may never come.
• Thrive in ambiguity and speed, because we are early-stage and moving fast, and that should energize you rather than intimidate you.

Benefits

• Competitive SF salary and meaningful equity in an early-stage company backed by top investors
• Opportunity to define the technical GTM function from day one
• Direct access to founders and influence over product direction
• Visa sponsorship and relocation support
• Generous health, dental, and vision coverage