Solutions Engineer
Summary
Solutions Engineer at Reactor, acting as a technical bridge between sales and engineering to scope, integrate, and deploy customer solutions, primarily using Python and real-time inference infrastructure.
This role sits between GTM and engineering. You will be one of the first GTM hires, working alongside sales and directly with the founders to take customers from their first technical call all the way to production traffic, then carrying everything you learn there straight back into the product. You will be the person customers call when it matters, the one who scopes the proof of concept, writes the integration code alongside their engineers, debugs a latency spike, and turns a working deployment into the case study that closes the next 3 deals.
- Pre-sales technical ownership: You join sales calls as the technical authority, running live demos and answering how real-time inference actually works, then scoping proofs of concept with clear success criteria and a defined path to production.
- Integration and onboarding: You own the first 30 days of every new customer, writing sample code and sitting in their repo until real traffic is flowing. Success here is measured in time to first API call and time to production, not tickets closed.
- Keeping customers live: After launch you stay the technical point of contact, debugging latency, throughput, and streaming issues, escalating cleanly into engineering, and making sure a problem never becomes a reason to leave.
- Expansion through depth: The teams that ship more end up using more, so you look for the second and third use case 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 you produce the technical substance those numbers rest on.
- Being the bridge to engineering: You see where the platform breaks before anyone else does, so you sit close enough to the engineering team to translate customer reality into prioritized, specific work, and you fix the docs and samples yourself when that is faster than asking.
- You can write production code, primarily in Python, and you are comfortable working inside a customer's codebase and building a working integration yourself without waiting on engineering.
- You have 3+ years in solutions engineering, sales engineering, forward-deployed engineering, or backend and infrastructure engineering with real customer exposure.
- You understand inference infrastructure, meaning GPUs, latency, throughput, streaming, and what actually breaks under load, and you can explain a p99 to a founder and a business case to an engineer without losing either of them.
- You 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.
- You 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.
- You 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.
- You thrive in ambiguity and speed, because we are early-stage and moving fast, and that should energize you rather than intimidate you.
- 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