Application demands are rapidly changing while the experience to design and operate infrastructure is rapidly diminishing. A new platform abstraction is needed to support agentic development, agentic applications, and an entirely new set of application workloads. We think Convex is the team and platform best placed to define this abstraction.

Convex works differently from the tools people are used to. The right way to build with it isn't always obvious, and increasingly the developer learning it is an agent rather than a person. Helping people and their agents make sense of something this new is still the domain of very talented humans, and we want you to be one of them.

Convex has assembled a team of engineers who have built and designed some of the largest platforms in the world, with exabytes of data, millions of transactions per second, and shipped desktop and mobile software onto billions of devices. We are a group of friendly, collaborative, and passionate people who love working in-person together in our office in San Francisco. We hire primarily in SF but have a few experienced folks working remotely in certain situations.

The Role:

We're looking for a Head of Developer Experience to own how developers and agents become great at building on Convex. You'll set the strategy, hold the point of view, and lead the team behind it. The docs, the writing, the developer narrative, and the advocacy your team takes to the community all flow from one thing: a real understanding of the product and a clear opinion on how people should build on it.

Some weeks you'll go deep with the engineering team on something we just shipped and turn it into docs a developer, or the agent writing their code, can pick up easily. Other weeks you'll step back to decide what story we're telling developers this quarter, where the docs are falling short, and what your team should focus on next. The best person for this is someone who's genuinely excited to move between all of it.

What You'll Do:

• Set the strategy and point of view for how developers and agents learn to be successful on Convex.

• Lead and grow the developer experience team, and build out documentation as a function over time.

• Own the Convex docs and the information architecture behind them, ensuring that Convex stays legible from a developer's first day to their most expert work, for humans and agents alike.

• Craft the writing and developer narrative that shape how people understand Convex, from our blog to the way we explain what we ship.

• Work closely with engineering and the founders to turn what we build into things people can learn from.

What Excites Us:

• You've written developer docs or technical content that real developers relied on, and you have the work to show for it.

• You've led a team before, ideally one doing developer-facing or content work, and know how to grow people and help them do their best work.

• You can code, or read it closely enough to keep every example honest.

• Genuine interest in how AI is changing the way software gets built, and a point of view on what developers and their agents need.

• Interest in working in-person at Convex's office in SF.

Ideal Characteristics

This is an attempt to outline some characteristics of people who tend to thrive at Convex. We have a high demand for deep thinking and clear communication, while also having the typical demands of a small startup.

Can they actually write?

Writing is the heart of this job. We're not looking for someone who can produce serviceable copy, but someone who can take something complicated and make it clear, with a structure that scans and a point of view that sticks. It's the rarest thing we're looking for and the hardest to fake.

Do they have a point of view?

The best developer content and the best developer experience both come from someone who has a clear idea of what good looks like and pushes for it. We want someone who can look at how developers build on Convex today, form a strong opinion about how they should, and then build the docs, the writing, and the team to make that real.

Can they go deep technically?

You don't have to be the strongest engineer in the room, but you do have to engage seriously with the technical material and earn the team's trust. Convex is genuinely deep, and hand-waving doesn't survive contact with a skeptical developer. It shouldn't survive contact with you first.

Can they build and lead a team?

This is a leadership role, so a big part of the job is getting great work out of other people, not just producing it yourself. That means hiring well, giving people real ownership, developing their judgment, and caring more about what the team ships than what you could have written on your own. The best leaders we've worked with are the ones who make everyone around them better.

Do they value simplicity and pragmatism?

We have a bias toward doing fewer things better. A lot of this job is telling what actually matters apart from what's merely nice to have, pointing the team at the former, and shipping it rather than polishing forever. It's a startup, and knowing what to leave undone matters as much as knowing what to build.

Do they bring energy to the room?

Startups are hard. Building something from nothing is hard. Driving forward progress despite uncertainty is hard. Shitting on stuff is easy and just brings everyone else down. We have a high bar for quality but also a high bar for being constructive, positive, and excited about making things better. We're meant to be having fun here.

Convex is the backend platform that keeps up with you and your agents.

Our mission is to fundamentally change how software is built on the Internet by empowering developers to create fast, reliable, and dynamic apps without a backend team. We provide a full-stack app platform carefully designed with database, compute and backend abstractions that allow developers and LLMs to move fast but also create products that scale and remain simple over their lifetime.

Convex has assembled a team that has built and designed some of the largest platforms in the world, and scaled companies to millions in revenue and thousands of employees. We’re a group of friendly, collaborative, and passionate people that love working in-person together in our office in San Francisco. We hire primarily in SF but have a few experienced folks working remotely in certain situations.

The Role:

Every week thousands of developers sign up for Convex, then start building and deploying on us. Some are kicking the tires. Some are quietly building the next big company. Your job is to help build the systems to find signal in the noise, and help us act. We’re looking for our first GTM Engineer to help us engage at just the right moment without being annoying about it.

You'll design, build, and ship the workflows and data infrastructure that turn product and market signal into pipeline, plus the internal apps and tools that compound our output. You'll walk in, audit what we have, decide what's missing, and start shipping.

Our users are developers, which makes this harder and more interesting than GTM engineering at most companies. Developers have antibodies against generic outbound, and the most valuable signal lives in product usage, not a lead form. We are deeply allergic to slop: the last thing the world needs is another ill-conceived cold email, and we won't ship one. Anything we send should be something a thoughtful person would be glad to receive. We’re not anti-AI by any means (helps us stay lean and move fast), and you'll be the person who keeps us on the right side of the line. The plays that work here are technical, specific, and earned, which is why we think the best version of this role is held by someone technical enough to build on Convex themselves.

What You'll Do:

• Turn Convex product usage into the GTM signal it should be: model which deploys are getting serious, surface intent the moment a team crosses a threshold, and route it to the right play or the right human automatically.

• Build agent + human-in-the-loop outbound that's genuinely useful, and keep it from ever becoming slop.

• Build the AI agents and internal tools that compound the commercial team's output as we grow.

• Audit the stack, generate your own backlog, and know when to reach for a point-and-click tool versus building something custom. Do the unglamorous data cleanup that makes all of it trustworthy.

• Write a bunch of cool GTM code on Convex itself. We dogfood.

• Measure your results and double down on what works best.

What Excites Us:

• A few years spent building revenue and automation systems, whether you got there through Revenue Operations, Sales Ops, growth engineering, or as a software engineer who drifted toward the commercial side. You don't need "GTM Engineer" on your resume; the title barely existed a year ago, and we care far more about what you've built than what it was called.

• Technical enough to build and wire systems together yourself. You don't have to be a career software engineer, but you're comfortable with APIs, data, and a bit of code (SQL, a scripting language, or TypeScript, which is what Convex itself is built in).

• Hands-on experience inside a modern GTM stack.

• Hands-on with AI in real work, not just in theory. You know where models are reliable and where they break, and you’re not afraid to fire up Claude Code or Codex to stand things up yourself rather than waiting on someone else.

• Systems thinking: you consider what happens at 10x volume, when an API goes down, or when the same account hits your queue five times in parallel, and you design for it instead of leaving debt for someone else to unwind.

• Bonus points for exposure to technical or developer-led sales motions, or genuine curiosity about Convex itself (building something small on it before you start wouldn't go unnoticed).

• Interest in working in-person at Convex's office in SF.

Ideal Characteristics

This is an attempt to outline some characteristics of candidates who tend to thrive at Convex. We have a high demand for both commercial judgment and the ability to actually build, while also having the typical demands of a small startup.

Do they think in systems, not tasks?

The job is not to do GTM work faster by hand. It's to build the machine that does it. We want someone who, handed a recurring manual process, instinctively reaches for the version that runs itself. Someone who has built things that kept working after they walked away, and who measures their impact in leverage created, not hours logged.

Can they earn a developer's trust?

Developer tools are different. Your users are technical, skeptical, and quick to spot inauthenticity. The plays that work for a business app fall flat here. We want someone who understands, in their bones, what it feels like to be a developer evaluating a product, and who builds GTM motions that respect that instead of spamming through it.

Are they a commercially oriented builder?

The best GTM engineers we've met are hybrids: they care about revenue and they can ship. Not a marketer who can't build, not an engineer who doesn't care whether the work moves the business. We want someone who lives in the middle and is genuinely good at both.

Do they value simplicity and pragmatism?

Simplicity is at the heart of all good systems, and GTM systems are no different. Don't come here to build a Rube Goldberg machine of fifty chained automations. Come here because you want to get really good at achieving great things in the simplest possible way

Do they bring energy to the room?

Startups are hard. Building something from nothing is hard. Driving forward progress despite uncertainty is hard. Shitting on stuff is easy and just brings everyone else down. We have a high bar for quality but also a high bar for being constructive, positive, and excited about making things better. We're meant to be having fun here.

Convex is transforming the way developers build applications.

Our mission is to fundamentally change how software is built on the Internet by empowering developers to create fast, reliable, and dynamic apps without a backend team. We provide a full-stack app platform carefully designed with database, compute and backend abstractions that allow developers and LLMs to move fast but also create products that scale and remain simple over their lifetime.

Convex has assembled a team of engineers who have built and designed some of the largest platforms in the world, with exabytes of data, millions of transactions per second, and shipped desktop and mobile software onto billions of devices. We are a group of friendly, collaborative, and passionate people that love working in-person together in our office in San Francisco. We hire primarily in SF but have a few experienced folks working remotely in certain situations.

The Role:

The Convex team has a lot of experience running large systems at scale, and as our customers and infrastructure grow, we’re looking for exceptional staff or principal-level engineers to help build and maintain what comes next. If you’re passionate about distributed systems and have experience designing and operating large-scale infra, we’d love to talk!

This is a hands-on role that moves between architecture and execution. You’ll work across core systems like our database and synchronization layer, and build out newer primitives like branching and analytics as they take shape. A lot of Convex’s platform requires serious design work where we can’t just follow best-practices since we’re the ones defining them. If you like the idea of designing a new storage layer that minimizes B-tree churn, or coming up with an API for managing ephemeral state that might disappear if a node restarts, or setting all that aside for a week and landing something simple and pragmatic because we’re a startup and need to ship, you’re going to like it here.

We value simplicity, leveraged work, and strong ownership. Our team is high-ownership and cares a lot about oncall but this isn’t an ops role - we want people who design and build things the right way… or as close as is possible at a startup.

You’ll work closely with the engineering team and CTO on some of the most important technical decisions at the company.

What You’ll Do:

• Design, build, and maintain Convex’s global cloud infrastructure.

• Investigate and improve the performance and reliability of our systems.

• Be self-directed in prioritizing the right projects to work on, in close collaboration with the engineering team and CTO (hi! this is me, James).

• Own architectural decisions that shape the long-term behavior of multiple core systems.

• Help establish technical direction and engineering standards as Convex grows.

• Work across the stack when needed, rather than being constrained to a single layer of infrastructure.

• Write a bunch of cool systems and database code.

• Occasionally put up with James asking if there’s a simpler more elegant solution to a problem.

What Excites Us:

• ~6+ years of experience in backend or systems engineering, though we care far more about depth of ownership and experience operating mission-critical systems than years alone.

• Experience building and scaling large systems, including owning systems through major scale transitions or building core infrastructure from scratch.

• Strong systems judgment: understanding tradeoffs and knowing when to keep systems simple versus when to invest in complexity.

• Experience working in fast-moving environments where requirements shift and many of the hardest problems are not fully specified upfront.

• Interest in working in-person at Convex's office in SF.

• Ability to write high quality code (knowledge of Rust is a plus, but you’ll figure it out).

• An enthusiasm for going deep to understand Convex systems and not be constrained to a certain layer of the stack.

Ideal Characteristics

This is an attempt to outline some characteristics of engineers who tend to thrive at Convex. We have a high demand for conceptual thought and architectural sensibilities, while also having the typical demands of a small startup.

Have they developed taste for excellence?

If someone has a few years of experience, it’s extremely valuable for them to have worked closely with a person, team, or organization that is truly excellent in any domain. Excellence can’t be learned passively since it requires being meaningfully better than the status quo. What we care about most, though, is whether they have developed a sense for what high-quality engineering looks like. This shows up in how they reason about systems, the standards they hold for their own work, and the kinds of tradeoffs they find acceptable. They should recognize that excellence is rare and that developing real engineering judgment requires years of deliberate work.

Are they a deep thinker?

Convex is a rejection of industry norms and a belief there’s a better way of building apps. This requires us to think for ourselves and chart our own course. Engineers here need to think deeply about why they’re solving problems and the long-term implications of their choices. If someone does something just because they were told to or because it’s a “best practice” they will probably not excel here.

Do they understand the demands of a user-facing live-site service?

We generally weigh experience on OLTP databases over OLAP or offline systems. Not just because it’s more relevant domain experience but it also involves a mindset that the system absolutely must work because there’s a critical user-facing application on the other side. Live-site experience brings an appreciation of how hard it is to keep a service running at all times and how important it is to build simple well-abstracted systems that are less likely to fail.

Do they value simplicity and pragmatism?

Simplicity is at the heart of all good systems, especially those that are able to scale and adapt to future needs. In addition to architectural simplicity, we also try to do the simplest thing to solve a given problem at Convex. Don’t come here because you want to write a consensus protocol or storage engine, even though sometimes we need to do these things. Come here because you want to get really good at achieving great things in the simplest possible way.

Do they bring energy to the room?

Startups are hard. Building something from nothing is hard. Driving forward progress despite uncertainty is hard. Shitting on stuff is easy and just brings everyone else down. We have a high bar for quality but also a high bar for being constructive, positive, and excited about making things better. We’re meant to be having fun here.

Do they have tenacity?

Working at Convex is rewarding and the workload isn’t crazy but our users come first and sometimes that means we need to be on-call. We sometimes (rarely), get paged at night and have to respond with dedication, sometimes need to dig deep to debug a tricky issue or solve a problem no one has solved before. There’s a camaraderie that comes from being in a team where everyone has tenacity, will step in to help each other out, and can be trusted to do the right thing.

*The salary range for this full-time position is > $240,000 + equity + benefits

Convex is transforming the way developers build applications.

Our mission is to fundamentally change how software is built on the Internet by empowering developers to create fast, reliable, and dynamic apps without a backend team. We provide a full-stack app platform carefully designed with database, compute and backend abstractions that allow developers and LLMs to move fast but also create products that scale and remain simple over their lifetime.

Convex has assembled a team of engineers who have built and designed some of the largest platforms in the world, with exabytes of data, millions of transactions per second, and shipped desktop and mobile software onto billions of devices. We are a group of friendly, collaborative, and passionate people that love working in-person together in our office in San Francisco. We hire primarily in SF but have a few experienced folks working remotely in certain situations.

The Role:

Convex is a backend platform but our key differentiator is an excellent client API and developer experience. We’ve invested huge efforts in our client libraries, development APIs and sync protocol to make Convex a joy to use for application developers. We’re looking to expand our team to develop the next version of the Convex API and help define what the modern application stack looks like.

If you’re an experienced TypeScript developer, care deeply about elegance and taste in API design, and believe that good platforms matter even more, not less, in an era of AI app development, then this is the job for you.

What You’ll Do:

• Design, build, and maintain Convex’s client libraries, sync protocol, and query APIs.

• Support new frameworks and keep track of new technologies in the app development space.

• Develop an understanding of what abstractions scale and compose well in our stack so we can build libraries that are not just easy to use but also simple over the lifetime of a project.

• Be self-directed to prioritize the right projects to work on, in close collaboration with the engineering team and CTO (hi! this is me, James).

• Help establish good practices and design guidelines as we scale up our team and systems.

• Write a bunch of cool client library code.

What Excites Us:

• Multiple years experience building APIs, client libraries or developer tools.

• Good understanding of best practices in the TypeScript, React, and web dev ecosystems.

• Experience or enthusiasm for scaling in a high growth startup environment.

• Interest to work in-person at Convex's office in SF.

• Ability to write high quality code (strong TypeScript experience a plus).

• An enthusiasm for going deep to understand Convex systems and not be constrained to a certain layer of the stack.

Ideal characteristics

This is an attempt to outline some characteristics of candidates that would make great engineers at Convex. We’re have a high demand for conceptual thought and architectural sensibilities, while also having the typical demands of a small startup.

Have they seen excellence?

If someone has a few years of experience it’s extremely valuable for them to have worked closely with a person, team or organization that’s truly excellent, in any domain. Excellence can’t just be learned passively since it requires being better than the status quo. The candidate doesn’t need to be excellent yet but they need to have an appreciation that it requires a lifetime of dedication.

Are they a deep thinker?

Convex is a rejection of industry norms and a belief there’s a better way of building apps. This requires us to think for ourselves and chart our own course. Engineers here need to think deeply about why they’re solving problems and the long-term implications of their choices. If someone does something just because they were told to or because it’s a “best practice” they will probably not excel here.

Do they understand the demands of a user-facing live-site service?

We generally weigh experience on OLTP databases over OLAP or offline systems. Not just because it’s more relevant domain experience but it also involves a mindset that the system absolutely must work because there’s a critical user-facing application on the other side. Live-site experience brings an appreciation of how hard it is to keep a service running at all times and how important it is to build simple well-abstracted systems that are less likely to fail.

Do they value simplicity and pragmatism?

Simplicity is at the heart of all good systems, especially those that are able to scale and adapt to future needs. In addition to architectural simplicity, we also try to do the simplest thing to solve a given problem at Convex. Don’t come here because you want to write a consensus protocol or storage engine, even though sometimes we need to do these things. Come here because you want to get really good at achieving great things in the simplest possible way.

Do they bring energy to the room?

Startups are hard. Building something from nothing is hard. Driving forward progress despite uncertainty is hard. Shitting on stuff is easy and just brings everyone else down. We have a high bar for quality but also a high bar for being constructive, positive, and excited about making things better. We’re meant to be having fun here.

Do they have tenacity?

Working at Convex is rewarding and the workload isn’t crazy but our users come first and sometimes that means we need to be on-call. We sometimes (rarely), get paged at night and have to respond with dedication, sometimes need to dig deep to debug a tricky issue or solve a problem no one has solved before. There’s a camaraderie that comes from being in a team where everyone has tenacity, will step in to help each other out, and can be trusted to do the right thing.

*The salary range for this full-time position is >$170,000 + equity + benefits