Partner Engineer, US

Gigs•San Francisco, CA

11h•$200,000 - $250,000•Hybrid

About The Position

At Gigs, we're building the operating system for mobile services—a platform that lets tech companies embed global connectivity into their products effortlessly. Just as Stripe lets any business add a payment button in seconds, Gigs empowers platforms to weave in connectivity—bridging the traditional world of telecom with modern tech. From fintechs launching mobile services to HR platforms offering work phone plans, we automate provisioning and remove telecom complexity. Our team of around 150 people across the US and Europe, backed by nearly $100 million in funding from Ribbit Capital, Google, and Y Combinator. As one of the fastest-growing tech companies, bringing together early-stage engineers, product builders, and business athletes from companies like Stripe, Airbnb, and Shopify. We’re tackling deep technical and regulatory challenges to make connectivity truly seamless. If you’re driven by curiosity, creativity, and the chance to shape the future of telecom, we’d love to hear from you.

Requirements

5+ years in solutions engineering, partner engineering, or professional services at a high-growth B2B or SaaS company. Experience spanning pre- and post-sales is a strong signal.
You've worked the full lifecycle. You've been in technical discovery calls before a deal is won and been the person who then had to deliver on what was scoped. You understand the difference between selling a capability and building it - and you've had to bridge that gap.
You understand B2B2C. You've worked in businesses where your customer's success depends on their users adoption - and you've felt the difference between a technically complete integration and a commercially successful one.
Technically fluent, not just technically aware. You can hold your own in a conversation with a staff engineer about API architecture, webhooks, and integration design - and then walk into a room with a CPO and translate it into product strategy.
A communicator who moves people. Your written and verbal communication is precise and persuasive. You can align a customer's C-suite, a sceptical engineering lead, and your own internal teams - sometimes in the same week.
Stage-aware. Gigs is a ~150-person company still defining how this function works at scale. You've operated in this kind of environment before and you don't just tolerate ambiguity - you organise it.

Nice To Haves

Experience in fintech, payments, or developer-platform businesses is stronger still.

Responsibilities

Own the deal from the technical side. Work alongside the BDM team on active pipeline - running discovery, validating feasibility, scoping integrations, and building the confidence that gets a deal across the line. You're the person the customer's CTO talks to before they sign.
Lead implementations end-to-end. Own each implementation as a project from kickoff through to go-live and beyond. You'll work directly with your customers' engineering and product teams, defining the right feature set, journeys, and architecture for their specific use case.
Make the B2B2C motion work. Understand how each customer will position and sell Gigs to their own users. Deeply understand what a high-converting consumer experience looks like, and hold your customer to that standard throughout the build. A live integration that doesn't drive consumer adoption is not a success.
Be the forward-deployed product lead. When a feature is blocking a launch, you'll identify it, articulate it, and work with both internal and external product and engineering teams to solve it. You're not just delivering a spec - you're helping shape what Gigs becomes.
Manage a portfolio of high-stakes projects. You'll run multiple customer engagements simultaneously across different verticals and geographies. You use AI to stay on top of complex, multi-threaded projects and know how to keep internal and external stakeholders aligned and moving.
Build the playbook. We're still early. You'll create the processes, templates, and frameworks that don't exist yet, and that future team members will build on. You're comfortable with that - in fact, you prefer it.