Project Management interviews. 12 titles, each with its own model.
Each page shows the competency model, the questions that test it, what changes with seniority, and where candidates lose the interview.
Last reviewed
Every Project Management title
12 titlesWhat the report looks like for Project Management
- The situation in one sentence: where, what was short, and by how much.
- The decision that was yours rather than the team’s, and what you chose not to do.
- One number or one consequence that shows it worked.
Every competency is scored out of five with a line you actually said as evidence, and the weakest answers are rewritten as structure and specifics, never a script.
What Project Management interviewers keep scoring
Planning, scoping & estimation
Turns objectives into a deliverable plan: scope definition and exclusions, work breakdown, dependencies, realistic estimates, milestones and a critical path or release plan the team believes in.
Risk, issue & dependency management
Identifies risks early, quantifies and mitigates them, escalates issues with options, manages cross-team dependencies and does not let problems surface late.
Stakeholder management & communication
Manages sponsors, business owners, vendors and teams: sets expectations, reports status honestly, handles conflict and scope pressure, and keeps decisions flowing from the right people.
Delivery execution & control
Keeps the work moving: cadence of stand-ups, sprints or stage reviews, progress tracking against plan, change control, quality gates, budget tracking and course correction.
Agile & methodology fluency
Applies the right method for the context: Scrum or Kanban practices, PRINCE2 or PMBOK governance, hybrid approaches; facilitates ceremonies well and improves team flow rather than performing rituals.
Team leadership without authority
Gets results from people who do not report to them: aligns the team on goals, removes blockers, handles underperformance and conflict, and protects the team from noise.
Benefits & outcomes focus
Keeps the project tied to the business outcome: challenges scope that does not serve the objective, measures benefits after delivery and is honest when a project should be stopped or changed.
Requirements elicitation & analysis
Draws out what the business actually needs: interviews, workshops, observation and data analysis; separates needs from stated solutions; resolves conflicts and produces requirements that are testable and traceable.
Process mapping & improvement
Maps current-state processes accurately, finds waste, failure points and root causes, designs future-state processes and quantifies the improvement in time, cost, quality or risk.
Data analysis & evidence building
Uses data to define problems and test solutions: extracts and cleans data with SQL or Excel, analyses volumes, cycle times and error rates, and builds evidence-based business cases.
Solution design & documentation
Designs solutions with technical and business teams: user stories or specifications, process and data models, acceptance criteria, and documentation that developers, testers and users can actually use.
Stakeholder facilitation & influence
Brings together people with different interests: runs productive workshops, manages senior and resistant stakeholders, negotiates priorities and gets decisions recorded and honoured.