Staff Software Engineer | Developer Experience

You will join the Developer Experience track, whose customers are DeepL's own engineers. Every change that reaches our products, from a research prototype to a production release, travels through the platform, pipelines and workflows this track owns. Our job is to make that journey fast, safe and obvious, so that engineers spend their time on the problems only they can solve. We treat developer experience as a product, not a support function.

Responsibilities

Own technical direction for a significant part of the Developer Experience mandate; Lead initiatives that lift developer productivity across multiple engineering teams; Design and build the workflows and tooling that carry a change through the software development lifecycle, from local development through review to release; Lead our work on AI across that lifecycle; Treat internal developers as customers and grow a community around developer experience; Define standards that hold across the track and drive migrations to them; Mentor engineers across the track and raise the technical bar of the group; Share in operating what we build, including a sustainable on call rotation for the services and tooling other teams rely on.

Requirements

A software engineering background, in any language, with real depth in at least one; Time in a product team, shipping to external customers; Genuine passion for developer experience; Enthusiasm for figuring out where AI creates real leverage in how software gets built; A track record of technical ownership spanning several teams; The judgement to trade the ideal solution for one you can ship and iterate on, and the tenacity to keep going.

Nice to have

Measuring developer productivity credibly, through DORA, developer surveys, or your own defensible approach; Having built or operated AI-assisted developer tooling: code review, agents, MCP servers, or evaluation of any of the above; Experience building an internal developer platform or portal, especially with Backstage; Community building you can point to. Open source maintainership, a guild or community of practice, developer advocacy, or any place you have grown adoption and ownership rather than mandated it; GitLab or comparable CI and CD at scale, and build system work on large polyglot codebases. Runner fleets, pipeline performance, caching and artifacts, and compile and test time optimisation.

Benefits

Diverse and internationally distributed team; Open communication, regular feedback; Hybrid work, flexible hours; Virtual Shares; Regular in-person team events; Monthly full-day hacking sessions; 30 days of annual leave; Competitive benefits