Half the people who call themselves GTM engineers have never shipped production code. This job is for the other half.

The Reality

This is a software engineering role that happens to point straight at revenue. You'll write and ship production code, own the systems you build, and be measured by whether the revenue engine runs better because of your work. If your background is engineering that never got to touch the business, this is the role where it finally does. If it's been RevOps where you were quietly the most technical person in the org and nobody ever let you build properly, same.

We're in the office five days a week in San Francisco. A company moving this fast catches its own mistakes sooner with the whole team in one room, thinking out loud at a whiteboard.

This will probably be one of the harder jobs you've had. It should also be one of the more interesting ones, because the revenue problems you'll be solving here will be the catalyst for our continued hyper growth.

Sound exciting? Good, we are too :)

The Role

You'll build the systems the go-to-market org runs on: lead routing and enrichment, pipeline and forecasting tooling, scoring and deal-desk workflows, and the data layer that ties it all into one source of truth. This is production engineering: services and code you own, integrated across our CRM, product, and billing data, built to hold up as we scale. Where a no-code tool is genuinely the right call, use it; the bar is that you can build the real thing when that's what the job needs.

There's a part of this job most GTM engineers never get. You'll dogfood Hyperbound on Hyperbound: our own reps run on Practice, Perform, and Kota, so the internal systems you build plug straight into the product we sell, and what you learn building them feeds back into the roadmap. You'll work closely with the founders and GTM leadership, act as part engineer and part systems designer for the revenue org, and have real say in what we build, not just how.

The Team

We're assembling a cracked team of builders, operators, and people who close. We've hired from our competition, brought on former founders, and pulled in early customers who loved the product enough to come build it.

The engineers here are builders first. Some have started their own companies. Nobody is precious about their code, and nobody hides behind "not my team's problem"; people see something broken and fix it. Someone is usually demoing something they shipped that morning, and the whiteboards get erased and rewritten all day. You can feel it when a team actually believes in what it's building, and that's very real here. It's also not a mattress-under-your-desk startup: plenty of people have kids, people leave to make dinner, and they come back the next morning and ship. High standards don't require burnout.

We've doubled in size since this photo was taken a few months ago

When we close a real milestone we celebrate for real; after our Series A we took the whole team to Bali.

Ownership and Equity

You own the outcome end to end: the systems you build, the revenue they move, and everything that happens after they ship. No process shields you from the responsibility, and none of it shields you from the credit either. Equity here is real, with real secondary opportunities, and we want the people who build this early to end up meaningfully rewarded for it.

Compensation and Benefits

Compensation: $160K-$200K+ based on experience + equity

Benefits: medical, dental, vision, 401k

Unlimited PTO

Commuter benefits

Paid lunch and dinner in the office

The Interview Process

We move fast: an intro call, a technical conversation with a build component alongside the people you'd actually work with, and a final conversation with the founders. We've closed roles in as little as one to two weeks when it's the right fit on both sides.