Staff Software Engineer - Collaborative Web Platform

About Pantheon

Pantheon brings together exceptional builders who take ownership, drive meaningful impact, and shape what's next for the web. We power more than 300,000 websites globally for organizations including Google, Princeton, Salesloft, Clorox, and the United Nations. Every day, thousands of developers and marketers use our WebOps platform to build, iterate, and scale WordPress, Drupal, and Next.js sites that reach billions of people worldwide. As an employer, we operate with the same philosophy that drives our product: foundation and freedom. Pantheon is a vibrant, remote-forward team of experts who care deeply about their craft and results. Here, you take ownership of work that matters, contribute alongside exceptional people, and see the impact you create.

The Opportunity

This is a rare chance to be at the ground floor of something genuinely new. Pantheon is building the next generation of web content infrastructure: a real-time, collaborative platform that redefines how teams create, publish, and manage content on the modern web.

This is a zero-to-one role. The product is early, the architecture is being defined, and the decisions you make will shape how thousands of developers and content teams experience the web for years to come. You will not be maintaining legacy systems or iterating on feature #1001. You will be inventing the foundational layer of a new product category: one that sits at the intersection of developer tooling, visual editing, and cloud-native content infrastructure.

Content management has been largely unchanged for two decades. CMSes were built for an era of documents and databases, not for the speed, collaboration expectations, or deployment patterns of today's web. Pantheon is uniquely positioned — with deep roots in the web platform, a global CDN, and a sophisticated branching platform already trusted by thousands of organizations — to build the content management experience that the modern web actually deserves.

If you've ever wanted to work on a problem that is technically hard, commercially meaningful, and genuinely unsolved, this is it.

The Role

As a Staff Engineer on this team, you will be a technical leader and hands-on builder in equal measure. You will work across the full stack — from the APIs and real-time synchronization services that power the platform's backend, to the visual editing interfaces and component systems that content teams interact with every day. You will partner closely with product and design to shape the architecture, make build-vs-buy decisions, define engineering standards, and accelerate a small, focused team toward meaningful milestones.

This role requires both breadth and depth. You are equally comfortable reasoning about distributed state management and crafting a delightful, low-latency editing experience in the browser. You understand that great infrastructure and great product experience are not in tension — they are the same problem viewed from different angles.

What You Need to Succeed 

Platform Architecture & Technical Leadership

• Design and own the architecture of a real-time content platform — including data models, sync protocols, API surface, and client-side state management.
• Drive technical decisions that balance developer ergonomics, operational simplicity, and long-term scalability across a cloud-native, multi-tenant environment.
• Define engineering standards for the team: API design conventions, testing strategy, performance budgets, and observability practices.
• Evaluate and select third-party services, libraries, and infrastructure components — with a clear framework for build vs. buy tradeoffs.

Full-Stack Product Development

• Build backend services that power collaborative editing, conflict resolution, and content delivery — operating reliably at scale across a distributed cloud infrastructure.
• Build frontend systems that enable visual, real-time editing experiences — including page builders and publishing workflows.
• Own the integration layer between the editing experience and the underlying platform: APIs, webhooks, and the developer-facing extension model.
• Contribute meaningfully to UX architecture — not just implementation — by collaborating with design on interaction models for novel, stateful editing flows.
&