Hyperbound

Machine Learning Engineer

San Francisco, California, United StatesFull timePosted 5 days ago
Apply on Hyperbound →

Sign in to see who you know at Hyperbound.

We’re probably not the right fit for you.

THE REALITY

We're in the office five days a week in San Francisco. We move fast and expect a lot. We’re most effective when everyone is in the same room, thinking out loud, catching each other's mistakes early.

You'll own your models end to end, training through production. We trust you to handle that. You'll spend most of your time working fine-tuning and running open source models in production, pushing models on-device, and building the evaluation frameworks that tell us whether a change actually worked instead of trusting our gut.

This will probably be one of the hardest jobs you've had. We think it'll also be one of the more exciting ones, and we'll be here right alongside you.

Sound exciting? Good. We’re excited too.

WHAT WE'RE BUILDING

Hyperbound is the Revenue Activation Platform, the agentic operating system for sales. We don't just record what happens on a call, we change what happens next, turning real selling behavior into targeted roleplays, coaching, and workflow changes that make reps better without adding a single layer of management overhead.

Founded in 2023 out of YC (S23), we're 45 people now, Series A, $18M raised total. Last quarter we doubled headcount, revenue nearly doubled with it, and net revenue retention landed above 300%. Teams at LinkedIn, Workday, and Intel run their sales orgs on us.

THE ROLE

You'll build and ship the models underneath Hyperbound's roleplay, scoring, and coaching products: real systems sitting on real sales calls. That means owning the full lifecycle, from training and fine-tuning through getting a model into production and keeping it working once it's there.

You will fine-tune and deploy open source models where they give us more control over cost, latency, or what the model can actually do. Some of it means getting models running on-device, wherever a customer's latency or privacy requirements demand it, with all the tradeoffs around quantization and d...