Project Management Interviews – keeping it on track

Over the years in recruiting project professionals I have found one of the key pieces of feedback from clients is that candidates have been unclear answering questions at interview. Often starting off with an example of when they did XYZ and going off on a tangent so not covering the response effectively. This is easy enough to do when the pressure is on and you are trying to convey a great deal of information.

The key to answering the question rather than missing the point is to think about what you have been asked and think about an example which clearly demonstrates the skill being questioned. Preparation before an interview is required, by taking the job description and looking at the list of requirements you can gauge the types of questions which will be asked and from there you can think about your examples.

  • Set the scene – give enough information for the interviewer to understand what it is you were delivering / supporting or the task in hand
  • Talk about your actions – I know we work in teams on projects but the interviewer wants to know what you did, so avoid talking about what we did and talk about what you did!
  • The outcome – what actually happened, talk about the result so the interviewer can understand how effective your actions were.

Here is an interview question and response to demonstrate how to structure your responses:

Interviewer: “Give me an example of when you have dealt with widely dispersed stakeholders?”


“When I was managing the new IT desktop roll out of Windows 7 at XXXX I was responsible for a number of technical teams based at head office and out at various divisions across the UK. The stakeholders were internal people such as a board member (the sponsor), head of IT (head of programmes), senior project managers and teams based at 4 different locations and external stakeholders such as the software development company project managers and technical teams.

I created a stakeholder map which clearly identified all the stakeholders in order of importance and a plan which covered communications. It became apparent that I would need to meet the key stakeholders on a regular basis to ensure project milestones were clear and everyone involved could gain a clear perspective of where we were in the plan and highlight any bottle necks which couldn’t be addressed at my clearance level.

The result meant that I had bi-weekly meetings with key stakeholders and regular “on the ground” reporting from workstream leads to ensure the work was being completed in a timely fashion whilst checking against the benefits to keep the senior management team on board with operations.”

The above example is rather generic but you get the idea – setting the scene to give the interviewer enough insight into what was being delivered and then talking through who the stakeholders are to demonstrate your understanding of who stakeholders are and how to harness a communications plan followed by the end result is giving the interviewer the right kind of information without going into chapter and verse and detracting away from the question and more importantly the answer.

Adopting this approach to your examples is good practice and also can help you when talking through achievements on your CV.