Operations Manager
Frequently asked questions about hiring for the Operations Manager role, plus the mistakes that most often derail it.
Common hiring mistakes for this role
The Operations Manager role at a German SMB is poorly understood in 6 out of 10 cases, which produces mis-hires within 12 months and costly turnover. Five recurring traps:
Confusing Operations Manager and Office Manager
The Office Manager runs the office (premises, office suppliers, general administration, expenses, internal events, logistical onboarding). The Operations Manager runs the cross-functional operation of the company (processes, tools, strategic suppliers, RevOps / FinOps / PeopleOps, structuring projects). The perimeters partly overlap but are not equivalent: a senior Office Manager can cover part of the Ops perimeter at a 30-employee SMB, but the jump past 60 employees or toward complex cross-functional topics (CRM redesign, stack audit, structuring the Finance function) requires a different profile. Blending the two in one ad produces either candidate frustration (too tactical a post) or company failure (structuring topics are left undone).
Hiring a too-senior COO for a 40-employee SMB
The mirror trap: recruiting an ex-COO or ex-head of operations of a large structure (200-500 employees) onto an Operations Manager post at a 40-employee SMB. The profile arrives with governance and structuring reflexes for an organization 5x larger and spends the first 6 months setting up oversized processes that the teams reject. Scope the seniority to the real profile: a mid-level Operations Manager (5-10 years of experience) operates better than a senior COO at an SMB under 80 employees. The COO is justified from 150-200 employees.
Hiring a 100 % consulting profile with no operational execution
A profile from a consulting firm (McKinsey, BCG, Bain, Roland Berger, or more operational firms such as Goetzpartners or PRIMA Consulting) is often excellent at scoping and analysis but can struggle with autonomous execution, without the safety net of a junior team. At an SMB the Operations Manager is alone on the majority of topics and has to deliver the project on top of the framing. Favor a profile with at least one internal operational experience (3 years minimum) after consulting, or scope the execution expectation in the ad and the interview (a practical execution case, not only scoping).
Defining the focus area too late or not at all
The Operations Manager post covers very different focus areas: RevOps (sales cadence, CRM reliability, forecast, Sales/Marketing/CS alignment), FinOps (financial reporting, budget tracking, SaaS stack optimization, procurement), PeopleOps (onboarding, HR tooling, feedback processes, steering team growth) or pure cross-functional (processes, suppliers, structuring projects). Recruiting without a defined focus area attracts heterogeneous applications and produces interviews where everyone talks about a different post. Define the dominant focus area in the ad itself (Operations Manager with a RevOps focus, or cross-functional Operations Manager with a RevOps share) and test on that focus area in the practical case.
Underestimating the weight of cross-functional communication
Many recruiters evaluate the Operations Manager on technical skills (tools, processes, numbers) and underestimate the relational dimension. Yet the Operations Manager spends 40-60 % of their time in cross-functional interaction with Sales, Engineering, Finance, HR and management. A technically brilliant profile who alienates their counterparts gets marginalized within 6 months (the functions served route around the Ops function). Weight the values and behavioral questions in the interview as heavily as the cases; cross-functional references (not only managerial) are indispensable.