Project Manager
Frequently asked questions about hiring for the Project Manager role, plus the mistakes that most often derail it.
Common hiring mistakes for this role
The Project Manager role at a German SMB is poorly framed in 5 out of 10 cases, which produces mis-hires within 12 months and costly delivery delays. Four recurring traps:
Confusing Project Manager and Scrum Master
The Scrum Master is an agile coach with a narrow scope on a single team and on the agile process (stand-ups, retrospectives, removing impediments, velocity steering). The Project Manager carries the delivery responsibility across several teams and functions, with budget, risks, stakeholder management and escalation as the core of the role. The perimeters partly overlap but are not equivalent: a senior Scrum Master can learn multi-team orchestration, but without an explicit transition framing the mix produces frustration on the candidate side (too narrow a scope) or failure on the company side (the delivery responsibility is left undone).
Hiring a 100 percent consulting profile with no internal delivery responsibility
A profile from a consultancy (McKinsey, BCG, Bain, Roland Berger or more operational houses like Goetzpartners or Capgemini Invent) is often excellent in framing and analysis, but may struggle with escalation and delivery responsibility autonomously, without the net of a consulting team. At an SMB the Project Manager is the only escalation line, and the political pressure is not absorbed by a partner. Prefer a profile with at least one internal delivery experience (2 years minimum) after the consulting, or frame the delivery expectation in the interview (a practical case on escalation, not just framing).
Prioritizing certifications over a real delivery history
Certifications such as PMP, PRINCE2, Scrum Master or SAFe are useful signals but do not replace a real delivery history. A candidate with three certifications and only one led project of 50 k€ will not hold a 500 k€ project perimeter, however current the certification. Conversely a candidate with no certification but with 4 complete project cycles of 100 k€ to 500 k€ in regulated sectors often delivers the more solid base. Evaluate the CV on the number of fully completed projects, their size and the sector depth, not on a string of acronyms.
Not testing escalation maturity in the interview
Many recruiters assess the Project Manager on methodology knowledge (agile vs. waterfall, tools, plan mastery) and underestimate escalation maturity. Yet the Project Manager stands or falls with their ability to escalate early and honestly instead of masking problems. A technically brilliant profile that defers escalations produces late escalations, which are expensive at an SMB (a delayed delivery, a tense climate, a loss of trust with management). Systematically ask a behavioral question about a failed or rescued project and check the escalation decision in detail (the date of the first signs vs. the date of the escalation).