Staff Software Engineer

About Gigs

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 100 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.

Things We Care About

We are building in a highly complex space and tackling a massive problem. We want people who lean in when things get hard.

• Speed. We move and we ship. We set bold deadlines and treat every week like it matters.


• Ownership. If you see something broken, fix it. We don't wait for permission.


• Customer Obsession. Our customers' product is our product.


• Ambiguity. We're building frontier technology in a complex domain. You'll need sound judgement and good instincts to make decisions without complete information.


• First principles. We don't ask how things have been done before. We ask why they were done that way at all.

Our Challenges

Our job is solid software engineering, not hype engineering. Carrier APIs differ a lot across countries, providers and regulatory regimes. Provisioning, porting, and eSIM lifecycle management happen in real-time with hard SLA requirements. Usage tracking, billing, and payments span multiple currencies and jurisdictions. Our systems need to be observable, operable, and resilient. When a carrier integration fails at 3am in a market far away, we need to know about it before the customer does.

Ours is a world where decades-old carrier protocols meet eSIMs, IoT, satellite connectivity, and the road to 6G. We are bridging that gap; making the old world programmable for the new one. We’re a platform company solving real, durable problems that don’t disappear when the hype cycle turns.

Our engineering team is doubling in 2026. In the next step of our journey, we’re building out a senior IC track, hiring multiple staff and principal engineers, because the challenges we’re solving today are only getting deeper. New markets, new connectivity paradigms, and an architecture that needs to carry us for years, not quarters.

Who You Are

You’ve seen what good and bad look like. You bring experience of operating at scale (technological or organizational) and you know systems and practices that hold up under pressure both from experience and literature. We’re looking for someone who can work across teams, connecting the technical dots between them. Someone who spots domain boundary problems before they become production incidents, and who builds the patterns and processes that the teams around them adopt and keep.

What you will do

• Design and evolve cross-cutting architectures (event-driven systems, multi-carrier integrations, multi-tenant platform patterns) and establish the governance and review practices to keep them coherent as we grow


• Raise the bar on operational excellence. Not just the systems (observability, SLOs, graceful degradation) but the processes and culture around incident response, on-call, and production ownership


• Find the places where AI changes the work, primarily in our platform and engineering practices, and push those forward


• Mentor senior engineers and help define what the senior IC growth path looks like at Gigs


• Ship production code and shape technical strategy with our engineering leadership

What we are looking for

You’ve seen what good and bad look like. You bring experience of operating at scale (technological or organizational) and you know systems and practices that hold up under pressure both from experience and literature. We’re looking for someone who can work across teams, connecting the technical dots between them. Someone who spots domain boundary problems before they become production incidents, and who builds the patterns and processes that the teams around them adopt and keep.

What We Expect on Day 1 (and in the Interviews)

• Experience developing, running, and maintaining distributed systems and event-driven architectures at scale


• Strong operational instincts. You think about observability, failure modes, alerting, and graceful degradation as first-class concerns, not afterthoughts. You’ve built systems that are debuggable by someone who didn’t write them


• Experience navigating and rationalizing polyglot environments


• Excellent communication skills with experience operating in an a international organisation


• Experience with agentic AI development. You’ve worked with LLMs beyond code completion, understand agentic patterns, and have opinions on when AI is the right tool and when it isn’t


• Track record of driving technical outcomes across teams without direct authority. You persuade through credibility and evidence, not rank


• Engineers around you got better because you were there, and you can point to specifics

Nice to Have

• Experience in telecom, payments, or multi-market API platforms


• Familiarity with any of our stack (Ruby, Go, TypeScript, Python)


• Experience at companies during a similar scaling phase (50 → 200 engineers)


• Background in domain-driven design or platform/product boundary work