Moving From Engineer to ML Engineering Manager

The move from individual contributor to engineering manager changes the scope of responsibility, but it does not erase technical work in every team. A current Google Engineering Manager, Borglet Machine Learning posting says the manager leads a team of software engineers, sets team priorities, develops a mid-term technical roadmap, guides system design, reviews code, and meets with individuals about performance, development, feedback, and coaching. This is one employer and team example, not a universal job description. As an ML engineer, success may be measured through the models, pipelines, or services you personally build. As a manager, outcomes increasingly depend on setting direction, clarifying ownership, hiring and developing people, managing performance, and helping the team make sound technical decisions. You may still write code or review architecture, depending on the organization, but personal implementation is not the only or necessarily primary measure of impact. Delegation is a core skill: a manager creates clarity and support so others can own work rather than retaining every difficult task. A transition plan can start with practice in adjacent responsibilities: mentor colleagues, run a project, improve team processes, and give clear feedback. Reflect on whether you want sustained people responsibility, not just a broader technical title. Ask the employer how the role balances people leadership with architecture or hands-on work. The right balance depends on team size, stage, and technical needs; no particular tenure or credential guarantees readiness for management.