Role Clarity for Engineering Managers
Role clarity in engineering management means understanding how a manager differs from a tech lead and a staff engineer. A manager is accountable for people and outcomes, a tech lead guides technical decisions for a team, and a staff engineer influences technically across teams. The first 90 days are spent learning the team and building trust.
Stage: Transition to Management · Part of the Engineering Manager roadmap · Last reviewed 19 November 2026
What to learn in Role Clarity
- Distinguish the responsibilities of a manager, tech lead and staff engineer
- Decide honestly whether management or the senior individual contributor track fits you
- Plan a first 90 days of listening, learning the team and agreeing expectations
- Hold introductory 1:1s with every report and with your own manager
- Let go of hands-on coding without losing technical credibility
Role Clarity interview questions
What is the main difference between an engineering manager and a tech lead?
A tech lead is accountable for the technical direction and quality of a team's work, often while still coding. An engineering manager is accountable for the people, their growth, hiring, performance and delivery. Some companies combine the roles, but the responsibilities differ.
What should a new manager do in the first 30 days?
Listen more than change. Meet each report one on one, learn the team's goals, codebase health, processes and pain points, meet partners in product and design, and clarify expectations with your manager. Avoid large reorganisations until you understand why things work as they do.
Where Role Clarity fits in the Engineering Manager roadmap
Role Clarity belongs to the Transition to Management stage (intermediate level), which takes about 4 hours. A different job.
Other units in this stage
Back to the full Engineering Manager roadmap