How to Become an Engineering Manager: First 90 Days, 1:1s and Hiring

The move from engineer to engineering manager is one of the biggest career changes in tech, and it often happens with little warning. One week you’re shipping features. The next, you’re responsible for 6 people’s growth, a hiring plan and a quarterly roadmap, and nobody is reviewing your pull requests because you’re not writing many.

This guide covers how people actually get into engineering management, what to prioritize in your first 90 days, how to run one-on-ones that matter and the hiring basics every new manager should learn early.

What an engineering manager does

An engineering manager (EM) is responsible for a team’s people, health and delivery. Engineers are measured mostly on their own technical work. Managers are measured on what the team achieves and how well the team grows.

Typical responsibilities include:

• People: One-on-ones, feedback, coaching, career development and performance reviews
• Hiring: Defining roles, interviewing, closing candidates and onboarding new hires
• Delivery: Working with product on priorities, removing blockers and keeping commitments realistic
• Team health: Sustainable pace, clear processes, psychological safety and handling conflict
• Communication: Representing the team to leadership and other teams, and bringing context back

Google’s Project Oxygen research, which studied what made its best managers effective, identified 10 behaviors and put “be a good coach” first. The list also includes empowering the team without micromanaging, creating a team environment that values everyone, communicating effectively, supporting career development, having a clear vision, having key technical skills and making strong decisions. Gallup’s workplace research similarly estimates that managers account for at least 70% of the variance in team engagement. The point is the same: as a manager, your impact flows through people.

Is engineering management right for you?

Management is a different job, not a promotion for being a great engineer. Before you pursue it, be honest with yourself.

Signs it may fit:

• You get satisfaction from helping teammates grow and succeed
• You naturally notice when someone is stuck or unhappy
• You’re comfortable with ambiguity, interruptions and fragmented days
• You’re willing to have hard conversations about performance
• You care about how the team works, not just what it builds

Signs to pause:

• Your main motivation is pay or status
• You’d miss deep coding work badly
• You avoid conflict at nearly any cost

Many tech companies offer a parallel individual contributor track where senior engineers can grow in scope and pay without managing people. Our guide to IC vs manager career tracks walks through that choice.

Paths into engineering management

For most people, the realistic route is internal. Start by becoming a strong tech lead, mentoring newer engineers and taking on small people-related tasks like running interviews or onboarding new hires.

Pay and job outlook

The US Bureau of Labor Statistics groups engineering managers under computer and information systems managers. For that occupation, BLS reports a median annual wage of $175,140 in May 2025 and projects employment to grow 16% from 2025 to 2035, much faster than average. BLS also notes that these roles typically require a bachelor’s degree and 5 years or more of related work experience. Pay varies widely by company size, location and level, so check current postings and your company’s leveling guide.

Your first 90 days as an engineering manager

Days 1 to 30: listen and learn

• Hold one-on-ones with every team member in your first week or 2. Ask what’s working, what’s frustrating, what they want from their career and what they need from you.
• Meet your key partners: product manager, designer, your own manager and leads of teams you depend on.
• Learn the current state: roadmap, commitments, on-call load, open incidents, team processes and known tech debt.
• Resist big changes. Your first job is understanding. Changing things too early damages trust.

Days 31 to 60: set direction and fix quick wins

• Clarify priorities with your product partner and share them with the team.
• Fix 1 or 2 obvious pain points your team raised, such as a broken process, an unclear on-call rotation or a recurring meeting nobody values.
• Establish your rhythms: weekly one-on-ones, team meetings, how you’ll share updates.
• Learn delivery metrics your organization uses, such as DORA metrics, and how sprint planning works on your team.

Days 61 to 90: build for the long term

• Start career conversations with each person and agree on 1 or 2 growth goals.
• Give feedback regularly, both positive and constructive, so nothing in a review is a surprise.
• Review hiring needs with your manager and learn your company’s hiring process.
• Ask for feedback on yourself from your team and your manager.

Key takeaway: In your first 90 days, your job is to listen, earn trust and set clear priorities. The code can wait; your people can’t.

How to run one-on-ones that matter

One-on-ones are the most important recurring meeting you’ll have as a manager. Done well, they catch problems early, build trust and drive growth.

Basics that work:

• Weekly or every 2 weeks, 30 minutes, at a consistent time. Avoid canceling. When you cancel, people hear “you’re not a priority.”
• It’s their meeting. Let them bring the agenda. Keep a shared doc of topics and follow-ups.
• Not a status update. Use standups or tools for status. One-on-ones are for growth, concerns, feedback and context.

Questions that open real conversations:

• “What’s the most frustrating part of your work right now?”
• “What’s something you’d like to be doing more of?”
• “Is there anything I could do differently to support you?”
• “Where do you want to be in 1 to 2 years, and how can this role help?”
• “Is there feedback you’ve been holding back?”

Watch for warning signs: sudden quietness, frustration with the same issue week after week or talk of burnout. Our guide on avoiding burnout in tech covers signs to look for.

Hiring basics for new engineering managers

Hiring may be the highest-leverage thing you do. A great hire lifts the whole team. A poor one can drain it for months.

Define the role clearly

Before posting, write down what this person will do in their first 6 to 12 months, which skills are must-haves versus nice-to-haves and what level you need.

Use structured interviews

Google’s re:Work guide on structured interviewing describes the approach as asking candidates a consistent set of relevant questions and assessing answers against clear criteria, using standardized rubrics, recorded feedback and trained interviewers. Google reports that structured interviews predict job performance better than unstructured ones and are perceived as fairer. Avoid brainteasers.

Keep interviews legal and fair

The EEOC advises that pre-employment questions should be limited to what’s needed to judge whether someone is qualified for the job, and employers are explicitly prohibited from asking about disability before making a job offer. Avoid questions about age, family plans, religion, national origin or other protected characteristics. Your HR or recruiting team should guide you on the rules where you hire, especially for remote employees in other states. This is not legal advice.

Assess what matters

Combine a technical exercise relevant to the real job with behavioral interview questions about collaboration, ownership and learning.

Plan onboarding before day 1

Have accounts, a buddy, a starter project and a 30-60-90 day plan ready. Our digital employee onboarding checklist helps.

Common mistakes new engineering managers make

• Staying the team’s best coder. Taking critical-path tickets makes you a bottleneck.
• Avoiding hard feedback. Small issues ignored become performance problems.
• Shielding the team from everything. Context helps people make good decisions.
• Saying yes to every request. Protecting focus is part of the job.
• Not getting support. Find a mentor, join a manager peer group or ask your own manager for regular coaching.

Where the path leads

Engineering management can lead to senior manager, director, VP of engineering and eventually executive roles. Some managers also return to individual contributor work, often with stronger communication and leadership skills. If you’re thinking further ahead, see our guide on how to become a CTO.

Conclusion

Becoming an engineering manager starts long before the title: mentoring, leading projects and showing you care about how the team works. Once you’re in the role, your first 90 days should focus on listening, steady one-on-ones and clear priorities. Learn to hire well early, because the team you build is the biggest result you’ll be measured on.

Sources

• BLS Occupational Outlook Handbook: Computer and Information Systems Managers — median pay (May 2025), 2025 to 2035 outlook, education and experience
• Google re:Work: Use structured interviewing — components and findings on structured interviews
• Google re:Work: The research behind great managers — Project Oxygen’s 10 manager behaviors
• Gallup: Manager development — manager share of variance in team engagement
• EEOC: Prohibited employment policies and practices — pre-employment inquiries and protected characteristics