Lakshya

GCC, Site & Engineering Leadership

Delivery & Program Leadership

Leadership · where GCC work is organised

Portfolio, programme and delivery ownership across time zones. The role that makes distributed engineering actually work, and the one most often misunderstood as project administration.

Delivery leadership owns whether committed work arrives. In a GCC context that means owning it across a time-zone boundary, with dependencies on teams you do not manage and stakeholders who are asleep for most of your working day.

TimeWhat you are actually doing
08:00Overlap window planning. You get a few hours of overlap with headquarters and what goes into it determines what your teams are unblocked on for the next twenty-four.
10:00Dependency management. Three teams, one shared component, and a sequencing decision somebody has to make.
13:00Risk. Not a register nobody reads — the two risks that would actually change the plan, with owners and trigger conditions.
15:00Escalation. Something has been stuck for a week and the polite mechanisms have not worked.
16:30Reporting. Translating engineering reality into something a steering committee can act on, without either sandbagging or over-promising.

The decisive round

“A programme is going to miss its date. What do you do?”

Interviewer: “Six weeks out, you become confident the date will slip. Walk me through it.”

A weak answer. “I'd work with the teams to identify what can be accelerated, look at adding resources, and escalate to stakeholders if the date is still at risk.” ‘Adding resources’ six weeks out makes it later, and ‘escalate if still at risk’ means telling people late, which is the actual failure.

A strong answer. “The first thing I would do is tell people, and I would do it the day I became confident rather than the day it became undeniable. Six weeks of warning is a decision; two weeks is an announcement. The single biggest determinant of how badly a slip lands is when it is communicated.

Before that conversation I want three things. Why — specifically, not ‘it took longer than expected’. Was the scope wrong, was there an unforeseen dependency, did we lose people, did quality force rework? The cause determines whether the new date is credible. What is still achievable by the original date — because the useful conversation is almost never all-or-nothing; it is which subset ships and what that subset is worth. What the new date is, with a confidence level, and what would have to be true for it to hold.

What I would not do is add people. Six weeks out, onboarding cost exceeds contribution and it makes the date worse while looking like action.

Then the harder half: I would want to say what I would change so this is caught earlier next time. Usually the answer is that we were tracking output rather than remaining uncertainty, and the slip was visible in the data three weeks before anyone said it out loud. Fixing that is worth more than recovering this date.”

Communicating early, refusing to add people, and offering the subset rather than a binary. The last part -- what would have surfaced it sooner -- is what separates delivery leadership from status reporting.

Compensation

MarketBandNotes
United States$150k – $250k baseTechnical programme management sits above general delivery
India₹35L – ₹90L totalOne of the largest GCC job families and a common route into site leadership

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.

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 →The controlOne habit separates strong candidates from plausible ones more reliably than any technical depth.READ THE CHAPTER →

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