Engineering Manager | Customisation Hub

A good translation is accurate. A translation an organisation can actually publish has to use their words, follow their style, and sound like them. That is what this team builds. Customisation used to be a feature inside our translator. It is now a pillar of an enterprise platform. A customer's terminology, style rules and translation memory apply to documents and presentations, run inside multi step translation flows, and feed quality evaluation that understands which customisations were applied. It is one of the clearest reasons large organisations choose DeepL and stay with us. We own that surface end to end: glossaries and terminology, style rules, style profiles and translation memory, along with the sharing and administration that let an organisation govern all of it. We work alongside a research team who build the models that apply a customer's voice to the translation itself, which makes this one of the more genuinely collaborative engineering roles at DeepL.

Responsibilities

Lead, grow and develop a small, senior full stack team, and set its technical direction across services and the customer-facing web experience.; Own the customisation surface end to end: terminology and glossaries, style rules, style profiles, translation memory, and the sharing and administration around them.; Shape the product, not just deliver it. Work with your product manager and designer to define how customisation should actually feel to use, and bring a point of view of your own rather than waiting for a specification.; Challenge what we are shipping. The biggest wins available here are the unglamorous ones: making it possible to organise, find and trust a large set of customisations rather than being buried by them. We want someone who spots those and argues for them.; Take responsibility for whether customers use what we build, not just whether we ship it. Find out where people drop out of the journey and close those gaps.; Reduce the setup burden. Make configuring customisation something an administrator can do confidently on their own rather than something that needs weeks of guided onboarding.; Partner with our research colleagues to bring adaptive, context-aware personalisation from prototype into a product customers trust, including the transparency that lets them see why a translation was personalised.; Look after customer-owned assets properly. Glossaries and translation memories are what our customers have invested most in, and they need to be safe, portable and correctly scoped.; Work across research, product, design, platform, identity and go-to-market teams, and turn what customers are hitting into engineering priorities leadership can act on.

Requirements

You have worked closely with product and design to define user experience, not just to receive requirements from it. You can point to a product decision that was better because you were in the room.; You challenge the brief. You have talked a team out of building the wrong thing, or into building something nobody had asked for, and you can explain how you made the case.; You have managed engineers on a customer-facing B2B product, and you can describe what changed for those customers as a result.; You are technically solid enough to earn the trust of very experienced engineers. You will not be the deepest person in the room on every topic, and you do not need to be, but you do need to hold your own in a design discussion.; You have owned an adoption or engagement problem and moved the number. You know the difference between shipping a capability and getting people to use it.; You are comfortable leading a full stack team spanning backend services and a customer-facing web experience, and you do not quietly favour one.; You have worked alongside a research or applied science team on a jointly developed feature, and you know how to make that handover work in both directions.; You prioritise ruthlessly. The surface here is wide for the size of the team and you would rather do three things properly than eight partially.; You are based in London, or willing to be, and comfortable working from the office two days per week.

Nice to have

experience with terminology management, translation memory or localisation workflows, or with enterprise administration surfaces such as sharing, roles and entitlements.

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