Lakshya

GCC, Site & Engineering Leadership

Engineering Manager — first line

Leadership · 336 postings

The most common leadership entry point, and a genuinely different job rather than a promotion from senior IC.

First-line engineering management is where most people discover that the skills that made them a strong senior engineer are not the ones the new job needs. The interview is designed to find out whether you know that.

TimeWhat you are actually doing
09:00Three one-to-ones. Not status — status is in the tracker. These are about whether someone is stuck, bored, or about to leave, and you will only find out if you have built the relationship before you needed it.
11:00Unblocking. A dependency on another team has stalled for a week. Your job is to make the call the engineer cannot make, or to go and have the conversation they should not have to have.
13:00Planning. Translating a roadmap item into work the team can start, which mostly means deciding what is not in scope.
14:30A performance conversation. The hardest recurring part of the job, and the one candidates most often have no story for.
16:00Reviewing a design, and resisting the urge to design it yourself.

The decisive round

“Tell me about someone who was underperforming.”

Interviewer: “Walk me through a time you managed an underperformer.”

A weak answer. “I had an engineer who was missing deadlines. I gave regular feedback, set clear expectations and a performance improvement plan, and unfortunately they eventually left the company.” Process narrated with no diagnosis. It does not say what was actually wrong, which is the only interesting part, and 'eventually left' quietly avoids saying whether that was the right outcome.

A strong answer. “The one I learned most from, I got wrong first.

An engineer's output had dropped over about two months. My initial read was motivation, and I did the standard thing — clearer goals, more frequent check-ins. It did not help, and in hindsight it made things worse because it added scrutiny to someone already struggling.

What I had not done was ask a direct enough question. When I eventually did — not ‘is everything okay’ but ‘something has changed, and I would rather understand it than guess’ — it turned out they had moved onto a part of the system nobody had handed over properly, and had spent six weeks not asking for help because they thought the expectation was that they should already know it.

The fix was structural: an explicit handover, a named person to ask, and I changed how we onboard people onto unfamiliar areas so it was not dependent on someone being confident enough to admit they were lost.

What I take from it is that I now treat a sudden drop as a signal about the system or the situation until proven otherwise, rather than about the person. I have since managed someone out, and that was the right call — but I got there having genuinely ruled out the things that were mine to fix, which is what made it defensible to them and to me.”

Diagnosis over process, an admission of a wrong first read, a structural fix rather than a personal one, and evidence they can also manage someone out when it is right. Candidates who have only ever been kind, or only ever been decisive, both fail this.

  • Have three specific people stories: someone you grew, someone you managed out, and someone you got wrong. The third is the one that lands.
  • Know your attrition, specifically regretted attrition, and what you changed.
  • Have a hiring story — a bar you held under pressure to fill a seat.
  • Be honest about how much you still code. Both ‘none’ and ‘as much as before’ are wrong answers; the first suggests you have lost credibility with the team, the second that you have not let go.

Red flags

Manager of one or two. Not a management role; it is a tech lead with a title, and the next move from it is harder, not easier.

No hiring authority and no say on compensation. You will own outcomes without the levers that produce them.

Player-coach with a full IC load. Common, and it means the management half will be done badly at nights and weekends.

Compensation

MarketBandNotes
United States$180k – $280k baseFrequently at or slightly below Staff IC at the same company
India₹45L – ₹90L totalThe most common leadership posting in Indian GCCs

What this role tests

Themes, and where to learn them

These chapters are shared across every role that tests them, so preparation here compounds rather than being spent once.

Discovery before solutionThe decisive round in three separate archetypes, with the lowest pass rate of any stage.READ THE CHAPTER →Measuring what resists measurementNamed in 59% of AI postings and 42% of platform postings. Almost nobody studies it deliberately.READ THE CHAPTER →Failure and incident narrativeEvery archetype asks for this story. The outage is the setting; the decisions are the content.READ THE CHAPTER →

Practice questions across all themes →  ·  Back to GCC, Site & Engineering Leadership →