Director of Software Engineering
Usercentrics
| Company | Usercentrics |
| Category | Engineering |
| Location | Munich |
| Remote | Hybrid |
| Employment | Full-time |
| Level | Director |
| Salary | Not stated by the employer |
| Posted | 30 Jul 2026 |
| Last verified | 7 Aug 2026 |
| Source | Employer ATS (workable) |
Description
Director of Software Engineering Hybrid (minimum of 2-3 days a week from the office) Shape the Future of Privacy Usercentrics is a global leader in data privacy and privacy-led marketing solutions. We believe there is no need for a trade-off between growth and privacy compliance. Our vision is to unlock the potential of data privacy to empower a thriving digital ecosystem. We work with companies to create a healthy balance between data-driven business and privacy-led marketing for every size of enterprise. Our customers build trust with their users through improved transparency and control to drastically improve marketing and monetization, while achieving full privacy compliance. We are actively looking for a Director of Software Engineering to lead a group of multiple engineering teams within our Product & Engineering organization. This is a hands-on leadership role and you'll own delivery, technical health, and people development for the teams under you, while partnering with the rest of engineering leadership on cross cutting priorities. We're building a more AI-native engineering organization, and this role is central to making that real within the teams you lead. How We Work: AI-Native by Default Usercentrics is actively pushing AI adoption across engineering for real efficiency gains. This isn't background context, it's a working expectation. As a Director, you're expected to actively drive AI-native ways of working within your teams: adopting AI-assisted development where it genuinely helps, and building the judgment in your teams to use it well rather than uncritically. This is a real, current expectation on how you'll run your teams from day one, not an aspirational nice-to-have. What You Will Do Own your group's outcomes Own delivery predictability for your group from roadmap input through estimation, execution, and shipped results. Own the technical health of the systems your teams are responsible for, including how technical debt and scaling risk are identified, prioritized, and worked down over time. Own the growth and performance of the managers and engineers in your group, including developing your managers into stronger people leaders themselves. Solve ambiguous, systemic problems Turn a vague or partially defined problem, a struggling system, a scaling wall, an under-resourced area into a concrete, sequenced plan, rather than waiting for it to be fully defined for you. Diagnose root cause, not just symptoms: work out whether an underperforming or overloaded team's real issue is headcount, skill composition, process, or scope and act on the right one. Build and maintain a realistic view of what your teams can commit to, communicate trade offs honestly to stakeholders, and close the gap when estimates and reality diverge. Lead people and influence outcomes Treat developing the management layer under you as a primary responsibility, teaching judgment, not just assigning tasks. Work fluently with Product, other engineering groups, and company leadership on cross-team priorities where you can't rely on direct authority. Bring engineering-informed judgment into roadmap prioritization you're expected to help shape what gets built and when, not just execute what's handed to you. Stay technically grounded You won't be writing production code day to day, but you're expected to understand your teams' systems well enough to follow the implications of technical decisions, engage credibly in design discussions and incidents, and ask the right questions before problems become expensive. Connect team-level work to company-level goals, making sure your teams' priorities visibly contribute to the broader organization rather than operating in a silo.