Engineering Manager Interview India 2026: IC to EM Transition, 1:1s, Performance, and Hiring

Engineering Management fundamentals:

1. Why the IC to EM transition is difficult: As an IC, your output is your code, your designs, your technical decisions. You are measured on your individual technical contribution. As an EM, your output is your team's output. You succeed when your engineers grow, when the team delivers consistently, and when the people on your team are engaged and effective. This requires a fundamentally different skill set: patience (impact takes weeks or months to manifest), comfort with ambiguity (you will not always have a clear answer), and the ability to hold problems without immediately solving them (your instinct is to fix things; the EM's job is often to help the engineer fix it themselves).

2. Common mistakes in the first 90 days: - Taking over the technical work: when the team struggles with a technical problem, the new EM's instinct is to dive in and solve it. This stalls the team's technical growth and undermines the EM's transition out of the IC role. - Skipping 1:1s: new EMs often deprioritise 1:1s in favour of 'real work'. This is backwards: 1:1s are the primary mechanism for building trust and detecting problems early. - Changing too much too fast: the new EM observes inefficiencies and wants to fix them immediately. Change takes relationship capital that a new EM has not yet built. Listen first; change second. - Treating the team as a resource pool: assigning work without knowing the engineers' career goals, strengths, and growth areas. Engineers who feel unseen disengage.

3. The first 90-day plan: First 30 days: listen. Talk to every engineer on the team (1:1s), your manager, cross-functional partners (PM, Design, Data), and key stakeholders. Understand what is working, what is not, and what the team cares about. Do not make any changes. First 60 days: form hypotheses. Based on what you heard, identify 2-3 things that, if improved, would have the most impact. Share your hypotheses with the team and your manager. Get feedback. Days 61-90: act on the highest-confidence improvement. Make one change at a time; measure the impact; iterate.

EM team management:

1. 1:1 structure: Frequency: weekly for full-time direct reports; bi-weekly for contractors or part-time. Duration: 30-60 minutes. Ownership: the 1:1 belongs to the engineer, not the manager. The engineer sets the agenda. The manager's job is to listen, ask good questions, and unblock. Topics to cover across 1:1s: what is on the engineer's mind right now (blockers, frustrations, wins), career development (what skills does the engineer want to develop?), feedback (both from and for the engineer), team dynamics (how is the engineer experiencing the team culture?). Things to avoid in 1:1s: status updates (use async tools or team standups for that), the manager talking more than the engineer.

2. Team rituals: Sprint planning: the team plans the next sprint together; the EM facilitates but does not assign work. Daily standup: the team synchronises daily; the EM listens and removes blockers mentioned. Retrospective: the team reflects on the process; the EM facilitates but does not dominate; action items are owned by team members, not the EM. Team all-hands: monthly or quarterly; EM shares context on the team's direction, company context, and recognises individual contributions.

3. Giving feedback: Timely: give feedback as close to the event as possible (not in the quarterly review). Specific: describe the specific behaviour (not 'your code quality is poor' but 'in the last two PRs, the tests were missing for the error paths; this caused production bugs twice this quarter'). Impact: describe the impact of the behaviour on the team, product, or customers. Curious: ask why before assuming (sometimes the behaviour has a reason the EM did not know about). Private: corrective feedback always in private; positive feedback can be public.

4. Building psychological safety: Psychological safety (Google's Project Aristotle finding: the most important factor for team effectiveness) is the belief that you can speak up, make mistakes, and disagree without fear of punishment. EM behaviours that build it: admitting your own mistakes publicly, visibly responding positively when someone raises a concern, celebrating learning from failures (not just celebrating successes), following up on feedback given in 1:1s and retrospectives.

EM performance management:

1. Performance calibration: At most Indian product companies, performance is evaluated on a 2-point or 3-point scale (Meets Expectations, Exceeds Expectations, Below Expectations). Calibration sessions: EMs meet to discuss their engineers' performance and ensure consistency across the organisation (avoid grade inflation where every EM says their engineers are 'exceeding'). The EM's job in calibration: advocate for their engineers with evidence (specific examples of impact, not vague impressions), and accept calibration feedback from peers (if the team's overall output is below expectations, the EM is part of the calibration too).

2. Performance improvement plans (PIPs): A PIP is a formal document that defines: the specific performance gaps (with examples), the improvement targets (what 'meeting expectations' looks like), the timeline (typically 30-90 days), the support the EM will provide. PIPs are documentation of a problem that has typically been going on for 2-3 months without improvement after informal feedback. They protect the engineer (clear expectations, a fair chance to improve) and the company (due process before termination). The goal of a PIP is improvement, not documentation for termination; EMs who design PIPs with hidden impossibility are acting in bad faith.

3. The 'brilliant jerk' problem: A high-performing engineer who treats colleagues poorly (dismisses ideas, takes credit for others' work, creates a toxic atmosphere). The EM's response: do not tolerate the behaviour because of the technical output. Have a direct conversation (describe the specific behaviour and its impact on the team). Give a clear expectation (the behaviour must stop). Follow up. The brilliant jerk creates 5x more damage to the team's culture and output than the value they add; their continued presence signals to the team that good behaviour is optional.

4. Managing up: EMs must communicate effectively with their own manager (the Director or VP of Engineering). Key EM-to-manager communication: team status (current, accurate, no sugar-coating), risks (early warning of things that might go wrong; escalate early, not when the problem is already on fire), what you need (headcount, tooling, a decision from the VP that is blocking the team).

EM hiring and compensation:

1. Hiring as an EM: Requisition writing: work with the recruiter to write a job description that accurately describes the role and attracts the right candidates (overly generic JDs attract volume, not quality). Resume screen: look for: demonstrated scope (did the candidate work on problems that match the role's level?), signal over noise (accomplishments described with impact, not just responsibilities), progression (consistent growth over time). Technical screen: ensure the technical bar for your team is maintained; do not hire candidates below the bar because of time pressure. Culture-add (not culture-fit): ensure the team is becoming more diverse, not just hiring clones of the existing team.

2. Levelling engineers: Levelling: determining the appropriate seniority level (L3, L4, L5, L6) for a hire. Pitfalls: over-levelling (hiring an L5 for an L3 role; the engineer is bored and leaves) or under-levelling (hiring an L3 for an L5 role; the engineer fails because the bar is too high). Level calibration: compare candidates across recent similar hires; be consistent. Compensation negotiation: the EM is typically not the final decision-maker on compensation but should advocate for competitive offers for strong candidates.

3. Engineering Manager salary in India: New EM (0-2 years EM experience, team of 4-6): 30-60 LPA. EM (2-5 years, team of 6-10): 50-100 LPA. Senior EM (5+ years, team of 10-15): 80-150 LPA. Director of Engineering (manages multiple teams, 15-40 engineers): 120-250 LPA. Companies: FAANG India (Google, Amazon, Meta) pay the highest EM compensation in India; Indian product companies (Flipkart, Swiggy, PhonePe, Razorpay) pay 30-50% below FAANG India; IT services companies pay significantly below product companies for comparable EM scope.

4. EM vs Staff Engineer career choice: EM: manage a team of 5-10 engineers; people development, team health, delivery, hiring; your output is measured by your team's output. Staff Engineer: senior technical IC; large-scale architecture and cross-team technical leadership; your output is your technical impact. Financial: at FAANG India, EM and Staff Engineer (L6) salaries are similar. At Indian product companies, Staff Engineer IC track is slightly better compensated. Which path: if you energise when helping people grow and enjoy the human side of building products, EM is right. If you energise when solving deeply technical problems and influencing technical strategy, the Staff Engineer path is better. Reversibility: transitioning back from EM to IC is common and accepted; do not feel locked in by the choice.