Engineering Manager

About the role  As an Engineering Manager, you lead one or two teams with a specific technical mission — front-end, middleware, back-end, data, or platform — giving both people and technical direction, and owning what your teams ship.  You set team-level technical direction within the wider architectural guardrails, grow strong engineers into stronger ones, and own delivery and operational outcomes — creating the conditions for your senior and staff engineers to provide technical leadership too. You operate agents yourself and lead our AI-native SDLC from the front. You report to your domain's senior engineering leader.  What this is not  A purely process or Scrum-master role, or a hands-off manager who sets no technical direction. You lead people and technology together, and stay technically close through design, pairing, incident response, reviews, technical investigation, and agent workflows — regular individual coding output is not the measure of the role.    The team  You lead one or two teams with a specific mission — for example front-end feature development, middleware, back-end services, data, or platform.  Delivers its part of the domain's roadmap.  Sets and upholds the technical standards for its domain.  Adopts the target architecture and our AI-native SDLC practices.  Sits within a approx 170-strong engineering organisation across Delft, Budapest, and Kaiserslautern.  What you'll do  Provide technical direction  Set technical direction and standards for your teams' domain, alongside your engineers.  Make and steward the key technical decisions; uphold quality, security, and operational stability.  Contribute to system and architecture decisions for your domain with the Enterprise Architects and your peers.  Grow the people  Coach and develop your engineers — including growing strong ones into senior and staff engineers.  Hire, and act on tough talent calls with clarity and care.  Own the delivery and the bar  Own your teams' roadmap commitments and delivery and operational outcomes; protect cycle time, quality, and operational stability.  Keep review sustainable in an agentic SDLC — ensure your teams do not create excessive review burden or unnecessary code, match agent autonomy to the risk of the task, and keep human accountability clear.  Raise the engineering bar for your domain; make standards explicit and inspectable.  Operate agents yourself — build the subagents, evals, and patterns your team reuses, and contribute them back to the shared libraries.  Technical environment  Claude Code is our current primary agentic engineering environment: agents may plan and execute within defined constraints and governed environments, while engineers stay accountable for problem framing, architecture, acceptance criteria, security, verification, and production outcomes.…