Platform Engineer

Overview

THE REALITY If an 11pm Slack message that says "the integration's down, and the customer demos it to 20,000 reps tomorrow morning" would ruin your night instead of get you moving, don't apply. You'll own our public APIs and the integrations that connect Hyperbound to every CRM, dialer, and comms tool our customers already live in. Nobody hands you a fully scoped ticket.

What you'll do

• On the API side, you own design, versioning, and long-term maintainability end to end.
• Every internal team and every external developer building against us is building against decisions you made.
• On the integrations side, you're solving the genuinely hard problems: data consistency across systems that were never designed to talk to each other, rate limits that kick in at the worst possible moment, synchronization that has to hold up when a customer's CRM has a bad day.
• You'll work directly with the founding team to decide what gets built next and which partnerships actually move the business, not in a quarterly planning doc, in the room.
• Deep experience with API design patterns, versioning, and building for the long haul, not just the next release
• Real fluency in OAuth 2.0, OpenID Connect, and the rest of what it takes to secure data moving between systems you don't control
• Time spent in the weeds of other companies' APIs, enough to know that every SaaS platform lies to you a little differently
• A track record of owning something end to end somewhere that moved fast and didn't have a lot of guardrails Bonus points if you've been at a startup before, maybe even started one, you've run production systems on AWS with real CI/CD, or you've shipped something you're still a little proud of talking about.

Requirements

• Practical experience with Go, AWS, RAG.
• Relevant academic or project background for a Platform Engineer role.
• Strong written and verbal communication in English.
• Comfortable working on-site in San Francisco.

Skills