Metrics question

What is the best metric to track projects in that are in a tight schedule.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

Start a mock interview on this question · Mock interview from a job description

What this question tests

Basic project-execution metric literacy: knowing which schedule metric actually predicts risk versus which just looks reassuring.

How to approach it

  1. Clarify what 'tight schedule' means here: a fixed launch date with real slip risk.
  2. Reject vanity metrics like percent of tasks closed, since that hides whether the critical path is on track.
  3. Propose schedule variance on the critical path: days ahead or behind plan for the sequence of tasks that actually gates launch.
  4. Pair it with a leading indicator: weekly burn-down rate of remaining critical-path work.
  5. Add a risk metric: number of open blockers or dependencies past their due date.
  6. State the guardrail: don't let schedule pressure hide quality, so track defect count alongside.

What a strong answer includes

Common mistakes

Likely follow-up questions

More metrics questions

More questions from T-Mobile

Learn the skill behind it

Chapters of the AI PM course that teach what this question tests.

Preparing for a specific role?

Book summaries for this kind of question

Browse all 4,000+ questions in the bank