IT project manager is the role most often hired wrong in Indian IT staffing. Clients ask for a PM and actually want one of three very different people. One is a delivery manager who unblocks engineering teams and owns end-to-end launch. Two is a project coordinator who sends Monday status reports, maintains JIRA, and runs standups. Three is a program manager who coordinates multiple projects across vendors. Same title, three very different people, three different salary bands. This guide is written for the first — the senior IT PM who owns delivery on cross-functional, multi-vendor projects and earns 25 to 50 lakhs per annum in Bangalore, Pune, or Gurgaon. Before using this framework, have a clear conversation with the client about which version they actually need. The fastest signal for a real senior PM is how they talk about failure. Strong PMs volunteer a story about a project that slipped with specific early warning signals they missed. Weak PMs describe every project as a success or blame engineering.
At minimum two projects from kickoff through launch where they owned schedule, scope, stakeholder communication, risk register. Not "I attended standups and maintained JIRA." Ask for the specific project name, client, duration, team size, and budget.
Has worked with engineering, product, design, and business stakeholders simultaneously. Has handled a disagreement between product owner and engineering lead without kicking it upstairs. Has said no to a senior sponsor when scope creep threatened the launch date.
Spots a slipping milestone two weeks out, not two days out. Has a documented risk register with owners, impact, mitigation. Can walk through one specific risk they caught and mitigated before it became a crisis.
Does not need to write code but asks informed questions about architecture, dependencies, integration points. Does not become a bottleneck by requiring everything translated. Ideal: former engineer, BA, or QA who moved into PM.
Writes crisp weekly status updates with RAG status, decisions needed, risks called out. Ask for a redacted sample. PMs who can only communicate verbally in standups fall apart in distributed teams spanning Bangalore and the US.
Useful for enterprise clients (BFSI, government, large corporates) that require it on the RFP. Not a quality signal on its own — best PMs often lack certifications, weak ones have three each.
Some clients want PMs who also coach Agile practices — sprint planning, retrospectives, story sizing, backlog grooming. Worth a premium if both skills are genuine.
Has managed third-party vendors, offshore teams, or external contractors across time zones. Common in enterprise IT where the client coordinates Infosys, TCS, and a product vendor.
Has owned a P&L or T&M budget for a project above one crore rupees. Useful for senior roles where the client expects the PM to flag budget overruns before finance catches them.
Experience coordinating India-based delivery teams with US, UK, or EU sponsors. Knows the Tuesday-through-Thursday overlap discipline. High-value skill for ITES staffing.
Walk me through a project in the last 18 months that slipped its deadline. The timeline, the early warning signs you saw, what you did about them, and what the final outcome was.
What to listen for
Real timeline with specific early warning signs — a late dependency, unplanned leave, requirement clarification that dragged. Specific re-baselining or scope reduction conversation with the sponsor. Honest acknowledgment of what they would do differently.
How do you handle a senior stakeholder — CTO, VP, client exec — who keeps adding requirements mid-project?
What to listen for
Polite escalation through change-control. Impact analysis in writing — "adding X moves launch from March 15 to April 10 and costs 4 person-weeks." Does not absorb silently; does not push back rudely. Senior PMs say no diplomatically.
You have a 10-minute status update with a non-technical CEO who sponsors the project. Walk me through what you cover and in what order.
What to listen for
Top-down — headline RAG status, major milestone progress, top three risks, decisions needed from CEO, everything else on request. Strong PMs have templates. Weak ones start with "let me tell you what engineering did last week" and lose the CEO in minute two.
Your engineering lead estimates a feature will take three weeks. Your gut says it should be one. What do you do?
What to listen for
Asks the engineer to walk through the estimate — hidden complexity almost always explains the gap. Listens. Does NOT override. Senior PMs trust their engineers and escalate budget or scope, not estimates. Weak answer: "I would push back and get them to commit to one week."
Describe your approach to risk management. How often do you update the risk register, what goes on it, and who sees it?
What to listen for
Weekly or sprint-aligned cadence, not ad-hoc. Each risk has probability, impact, owner, mitigation, status. Shared with sponsors so there are no surprises. Strong PMs treat the register as a living artifact.
A developer tells you a three-day feature will now take two weeks due to an unexpected dependency. What happens next?
What to listen for
Impact on critical path, replanning the sprint, communicating to stakeholders proactively with new date, checking whether other work is blocked. Senior PMs do this within a day. Weak PMs wait until the next status meeting.
How do you decide what is explicitly out of scope for a project? Walk me through a recent example.
What to listen for
Cost-of-delay analysis, MVP framing, explicit out-of-scope list in the project charter. Strong example: "We cut multi-currency support because our research showed 94 percent of revenue was India and UK pounds."
You inherit a failing project on day one. Walk me through the first week.
What to listen for
Meet each stakeholder individually, read the last eight weeks of status updates, identify the top three risks with the team, rebaseline with the sponsor if needed. Does not announce changes in the first meeting. Listens before acting.
Score each candidate against these weighted criteria. Total: 100%.
| Criterion | Weight | Signal |
|---|---|---|
| Delivery track record | 30% | Multiple named projects shipped with specific outcomes, team sizes, durations. Has owned both successes and known failures. |
| Stakeholder management | 25% | Has wrangled difficult executives, demanding customers, misaligned vendors without escalating everything. Examples involve real names and real conflicts. |
| Risk and scope discipline | 20% | Has caught and mitigated real risks before crisis. Has said no to scope creep and documented the trade-off. Has a risk register template they can show. |
| Communication | 15% | Writes crisp status updates (ask for a sample). Adjusts depth for audience. Comfortable in both written and verbal modes. |
| Technical literacy | 10% | Asks informed questions about architecture, dependencies, deployment. Has working vocabulary without pretending to be an engineer. |
CV is all project titles and company names with zero outcomes, metrics, or specific decisions owned — classic "I was in the room" PM
Cannot name a single project in their career that slipped, was cancelled, or rebaselined — implausible above 3 years
Avoids ownership language — everything is "the team decided" with no individual fingerprint
Has never said no to a stakeholder request, which means they absorb all scope and slip every project
Claims Agile expertise but cannot define a sprint goal, distinguish epics from stories, or explain why daily standups are 15 minutes
Upload Project Manager CVs and let AI score every candidate against the same 42-point evidence rubric.
Try CVPRO Free