Senior Product Engineer

Hello. We're Prismic.

Lisez l'aperçu de cette opportunité pour comprendre quelles compétences, y compris les compétences non techniques pertinentes et la maîtrise des logiciels, sont requises.

We believe the future is all about autonomous websites and hyper-personalised user journeys.

We're building the Autonomous Website Experience. Today you choose tools, model content, write code, and fix bugs by hand. Tomorrow you say what you want, and the system builds, fixes, and improves the site with you, from the first demo to the daily updates.

The Tools and Activation Team

Our mission: build the tools that let developers, marketers, and AI agents, use Prismic efficiently, and design the most frictionless onboarding for different personalities and personas.

We own two sides of that problem.

• 
  

• The tools. The CLI and MCP are how agents work with Prismic. An agent in Cursor, Claude, ChatGPT, or Codex should be able to do everything you can do in the UI, without guessing, getting stuck, or inventing glue code. The developer tooling is what closes the loop - how developers deliver slices and manage their day to day work. We make those surfaces reliable, complete, and efficient.

  
  

• The first mile. People don't just arrive from different places. They also arrive with different experience and different knowledge of Prismic. Everyone should be able to onboard. We design those paths for that range of people, and we are responsible for making them the best.
  

  
  

What we measure

We measure two things.

Activation with our tools. How many developers and agents activate with the MCP, whether they stay, and how often they come back.

Onboarding to production. How many people start with Prismic and deploy their website to production.

The problems you'd pick up

Here’s what’s actually on the table right now.

CLI and MCP that make humans and agents first‑class users of Prismic. The CLI is how agents set up projects, model content, and stay in the codebase. The MCP is how they read, edit, and operate on content. Together they should cover the full surface of the product, not a thin slice of it. The hard part is not exposing an API. It is making people and agents efficient: the right tools, the right defaults, the right errors, and a path that doesn't fall apart past the happy path.

Developer tooling that stays out of the way. This is how developers actually interact with Prismic day to day: scaffolding projects, modeling data, developing Slices and syncing with remote server. You would help shape that interactions so people can do their work without fighting the tool.

Onboarding that works for different people. People arrive from different sources and the arrive with very different experience. All of them should be able to onboard. You would help design those paths and keep them coherent.

Why this role is interesting

• 
  

• You build the technology, and you build it fast. We prototype quickly, learn from it, and keep what works. An idea goes from POC to something customers use without a long chain of handoffs.

  
  

• You talk to customers directly. Product Engineers here don't wait for a spec. You talk to users, decide what to build, ship it, and see whether it moved the numbers.

  
  

• Your users are humans and agents. Designing for developers, marketers, and AI agents at once is a new problem. There is no established playbook, so you help write it.

  
  

• Your impact is easy to see. Activation and websites in production are numbers you can watch move because of what you shipped.
  

  
  

Role

We're looking for a Senior Product Engineer to join the Tools and Activation Team.

We chose the title Product Engineer on purpose. We're not looking for someone who ships clean code against a spec. We want someone who owns the outcome: talks to users, decides what to build with product, ships it, and is accountable for whether it moved the numbers. It's less about handoffs and more about owning the work end to end.

This is an individual contributor role. You'll have a lot of autonomy over both product and technical decisions, while working closely with product, design, and the rest of the engineering team.

Are you the one?

This role leans backend. You will spend most of your time on services, APIs and CLIs. Frontend is part of the job when the path to activation lives in a UI, but it is not the centre of gravity.

Ideally, you:

• 
  

• Are a strong backend engineer in TypeScript, comfortable designing APIs and CLIs

  
  

• Have built developer-facing surfaces like CLIs or SDKs. You’re use