Job Description

Thousands of engineers rely on Mergify every day to ship code faster. We process millions of CI events, automate merge workflows, and help teams stop wasting time on broken pipelines. That's not a pitch, it's just our Tuesday.

We're a small, profitable, fully remote team based in France. No VC pressure, no growth-at-all-costs theater. Just a product that works, customers who pay, and a lot left to build. We're hiring a Staff Product Engineer to work directly with our CTO. You'll own major parts of the platform, shape technical decisions, and build features that you—and thousands of other developers—will use daily.

What’s it like to work at Mergify?

What does our tech stack look like?

You can read about our tech stack on this page →

What does the typical developer day look like?

As we’re a fully remote team, we stay in touch using Slack, Linear, GitHub and video calls. We like to have informal chat and to meet regularly to have some fun. We obviously use Mergify to automate our workflow, detect CI issues, and merge our code.

You’ll be writing features and code that you’ll be able to use every day.

How cool is that?

We follow agile principles and run our daily tasks using a kanban approach, inspired by shape-up. We run a weekly meeting where we assess what we’ve done the week before, and plan for the upcoming week. We use a light development process based on projects with a lot of automations, and run a standup meeting every day.

Every engineer is responsible for one or multiple projects, and get full autonomy and ownership on designing and building those from the ground up.

The role

You'll be the senior technical backbone of our product engineering team. That means:

• Owning big problems end-to-end. From design to shipping to iteration. No hand-offs, no waiting for specs.
• Building core platform features — test orchestration, CI observability, event-driven systems processing millions of events.
• Shaping technical direction alongside the CTO. Architecture decisions, system design, tradeoffs—you're in the room.
• Shipping fast and learning faster. We run short cycles inspired by Shape Up. You'll have full autonomy over your projects.
• Writing Python that matters. Our backend is Python + PostgreSQL. You'll write code that runs in production for thousands of teams.

This isn't a "senior engineer who attends more meetings" role. It's a builder role with real leverage.

What success looks like

First 90 days:

• You've shipped your first meaningful feature.
• You understand our codebase, our customers, and our bottlenecks.
• You've started forming opinions about what we should build next.

First 6 months:

• You've led multiple high-impact projects from idea to production.
• You've made technical decisions that stuck.
• The team moves faster because you're on it.

What we're looking for

• 10+ years of experience, with deep Python expertise in production systems.
• You've built and scaled things. Real systems, real users, real problems. Not just maintained them.
• You think in tradeoffs. Speed vs. craft, done vs. perfect, now vs. later. You know when to optimize for what.
• You communicate clearly. Complex ideas, simple words. You write well—because we're async-first and writing is how decisions get made here.
• You own outcomes, not just tasks. If something's broken, you fix it. If something's unclear, you clarify it. No "that's not my job."
• You've done remote before. Successfully. We're not going to teach you how to work autonomously.

Bonus: you've worked on developer tools, CI/CD systems, or infrastructure. You understand the users because you are one.

Why you Should Apply

• You’ll be writing features you actually use—because we use Mergify internally too
• You’ll work on a product that engineers love and rely on daily.
• You’ll join a small, senior team with high trust, deep focus, and minimal overhead.
• You’ll join a bootstrapped startup that grows every year.
• We offer competitive salaries.
• We offer best-in-class benefits.
• We offer flexible working hours.

You can read about our tech stack on this page →