They decide how to commit the team's capacity, when to protect how it works, when to address performance, and what organisational cost to accept to keep commitments over the long term.
An Engineering Manager is neither an experienced developer who has been promoted nor a facilitator of ceremonies. They hold a human and operational system: people have to grow, responsibilities have to be clear, commitments have to stay credible, and difficulties must not rest permanently on a few indispensable individuals.
The difference between someone occupying the role and someone genuinely holding it shows when interests stop being aligned. Sometimes you have to slow a release to let an exhausted team recover, address underperformance despite a good personal relationship, move someone well-liked but badly placed, or recognise that an organisation designed for one team no longer works with several.
The boundary with neighbouring roles is clear. The Product Owner decides which value to pursue and in what order. The Engineering Manager decides what capacity can be committed, under what conditions, and with which human or technical risks attached. The Technical Account Manager carries the operational relationship with the client; the Engineering Manager neither owns it nor answers for it.
Market benchmarks
The Engineering Manager title covers very different realities on the French market. Some organisations want a hands-on lead still heavily involved in the technical work; others already expect a manager of managers able to structure several teams.
Genuinely solid profiles are fewer than the job titles suggest. Many candidates were promoted from a Tech Lead track without ever having faced sustained underperformance or a hard staffing decision. The scarcity is sharpest for people who can hold technical credibility, people development and organisational performance at the same time.
Context
In an IT services firm, the assessment gives more room to staffing, skill availability, changes of engagement, and the tension between contractual commitment and protecting the teams. The Engineering Manager has to understand the client's reality without becoming the commercial owner of the account.
Level 1
Team lead
They hold one team within a defined scope. They run one-to-ones, give feedback, address performance difficulties, develop skills and make collective commitments legible. They know protecting a team does not mean shielding it from expectations: they make those expectations explicit and step in before the other members quietly compensate.
Click to read
Level 2
Manager of several teams
They no longer steer only people: they steer the interactions between teams. They clarify responsibilities, reduce dependencies, harmonise what needs harmonising and preserve local autonomy on the rest. They do not measure performance by adding up local results: a team that ships fast while degrading operations is not performing at system level.
Click to read
Level 3
Head of engineering
They design the conditions under which several teams and several managers can decide without continually depending on them. They arbitrate structure, capacity, investment and the split of responsibilities. The higher level is not the person who knows more management practices: it is the person who settles a trade-off and names the cost they accept — delaying a strategic initiative, closing a role that has become unnecessary, or accepting a temporary drop in velocity to rebuild something durable.
Click to read
The heart of the role remains the ability to grow people, hold them accountable and, when needed, address performance. A good organisation does not make up for avoiding hard human decisions.
The Engineering Manager has to make delivery predictable without turning pressure into permanent overload. Performance is assessed as a durable collective result, not as a run of exceptional pushes.
How teams are composed, how seniority is distributed, and how responsibilities and dependencies are arranged largely determine what the organisation can actually deliver.
The role requires enough technical credibility to understand the risks and challenge the options, without taking the place of Tech Leads, staff engineers or architects.
A management decision that is neither understood nor applicable fails. This category measures the ability to deal with conflict and signs of disengagement before they turn into resignations or incidents.
The method in action
The scorecard at a glance — hover an axis
Management, delivery & client relations