Cofounder

Location: San Francisco Bay AreaFormat: In-office 4 days a week with flexibility for the occasional remote days

Majordomo Mission

Every generation of software creates a new operational layer. Operating systems abstracted hardware. Cloud abstracted infrastructure. Observability abstracted production systems. These categories emerged because software reached a point where every company was solving the same operational problems independently.

Every company building production AI will eventually solve these problems. The only question is whether they'll solve them independently or build on a common operating layer. Building with LLMs is becoming increasingly accessible. Operating them in production isn't. Teams are making daily decisions about evaluation, routing, latency, cost and reliability, often by stitching together internal tooling. The question is whether every AI company should have to build these capabilities.

We think every production AI system will eventually depend on a control plane. We'd rather build it than wait for someone else to. Majordomo will offer engineering teams the confidence to deploy, evaluate and continuously improve AI applications without building the operational infrastructure themselves.

Majordomo is a portfolio company of super{set}, a venture studio that conceives, funds and builds AI-native companies from formation through scale. We work alongside founders as operators, helping shape companies from day one.

We're building in a category that's still taking shape. Many of the decisions that will define how production AI is operated haven't been made yet. The opportunity is to shape how production AI is operated and help define the category.

The Role

We believe the next generation of infrastructure companies will be built by founders who refuse to separate engineering, product and customers into different conversations. As a Cofounder, you'll help build the company as much as the product, from early customer conversations and product direction to company building. You'll spend your time moving between customers, product and engineering, turning customer insight into products developers choose to depend on. You'll help decide what we build, why it matters, and how we bring it to market. You'll collaborate with some of the industry's most experienced builders, who have spent the last two decades building and scaling enterprise infrastructure companies.

Some days you'll be reviewing architecture. Other days you'll be sitting with customers trying to understand why they didn't adopt something you thought they'd love. We don't see these as different jobs. We think they're all part of building products developers trust.

Our ideal candidate is technically strong enough to earn the respect of engineers, curious enough to let customer conversations change their thinking, and pragmatic enough to know that great products are built through iteration, not certainty. You'll thrive in the ambiguity of building a company from scratch, making consequential decisions across product, engineering, customers and the business long before anyone writes the playbook.

Why This Role Matters

The technical challenge is only part of what we're solving. The harder challenge is earning the trust of developers. Infrastructure products become successful when developers stop evaluating them and start depending on them.

That trust is earned through hundreds of product decisions that rarely make release notes. An API that feels obvious. Documentation that answers the next question before it's asked. A workflow that simplifies instead of adding complexity. A customer conversation that changes the roadmap because it revealed something fundamental.

The companies that define infrastructure categories don't just build better products. They change what developers come to expect. At Majordomo, you'll help define that standard. Many of the decisions that will shape this category haven't been made yet. As a Cofounder, you'll help make them, shaping the product, the company, and ultimately how production AI is built. You'll have an outsized influence on those decisions. The choices you make in the early days won't just shape Majordomo. They'll shape what developers come to expect from AI infrastructure.

What You'll Own

You'll help define what developers should expect from AI infrastructure:

One week, you may be sitting with customers trying to understand why something that made perfect sense internally feels confusing externally. The next, you'll be deep in architecture discussions. Around here, we don't see those as different jobs.

What Success Looks Like

In the first 6–9 months, you will have:

What You Bring

Must Have

Nice to Have

You've probably done one or more of these:

The Opportunity

If you've ever found yourself looking at AI infrastructure and thinking, "This is how it should work…". Let's talk.