Operations Manager

Ability to recount a full cycle: initial diagnosis (conversations with stakeholders, mapping the existing setup), design (alternatives, trade-offs, decision), rollout (training, communication, support), and monitoring (indicators, adjustments). Bonus: the candidate mentions what did not work and what was corrected. Anyone who describes a flawless, friction-free rollout is either showing too simple a case or a lack of critical perspective.

An owned trade-off stance: explicit decision criteria (business impact, risk, cost, feasibility), the ability to say no to a function by offering an alternative, clear communication of the decision to both parties. Anyone who describes finding a compromise without actually deciding shows an avoidance stance that produces skewed processes. Anyone who describes imposing a decision without consultation shows a weakness in cross-functional communication.

Maturity in the face of the ambiguity inherent to SMBs: the ability to reformulate the request to check understanding, propose a default interpretation with a validation request, and document the final decision to avoid recurrence. Bonus: the candidate set up a clarification ritual (weekly prioritization meeting, shared decision document) that reduces ambiguity at the source.

Scoping before execution: the candidate first identifies what can wait (ongoing, non-critical projects), what must be taken on immediately (monthly payroll, weekly cash, tax deadlines), and what must be outsourced (tax advisor, specialized interim solution). Bonus: they propose a realistic transition period (3-6 months) and a backfill plan. Anyone who accepts everything without scoping shows a lack of judgment and ends up in burnout.

A structured method: (1) usage audit per tool (active users vs. paid licenses, frequency of use, features used), (2) mapping of duplicates (two tools with the same function), (3) identification of underused tools as candidates for removal, (4) renegotiation of the contracts of the remaining tools. Bonus: the candidate mentions consulting the teams that use a tool before removing it (a tool that is underused on average can be critical for one team). Anyone who goes straight to cutting without an audit shows a lack of method.

Recognizing that both symptoms share the same root cause (degraded CRM hygiene) and that a single solution addresses both: documented standards, a weekly review cadence, clear ownership between Sales and CS on the fields, automations where human error recurs. Bonus: the candidate proposes an executive sponsor (Sales lead or COO) to carry the change, rather than trying to impose it alone from a cross-functional position. Anyone who answers with a CRM migration project has not understood that the tool is not the problem.

Ability to diagnose without complete data: the candidate first asks for context elements (growth pace, pain points felt by management, ongoing strategic projects), then proposes 3 priorities and distinguishes between urgent, important and structuring. Strong example answer: (1) set up a reporting and steering cadence, (2) audit the stack and the key processes, (3) one structuring project on the most painful function. Anyone who answers with a generic list (I would introduce OKRs) without using the context shows a lack of listening.

A systemic method with change support: (1) map the purchases of the last 12 months to understand volume per category and function, (2) define a simple validation threshold (for example 500 € without validation, 500-5000 € manager validation, more than 5000 € finance-lead or management validation), (3) a lightweight purchase-request tool (a form or a dedicated tool), (4) communicate the why before going live. Bonus: the candidate mentions not setting the threshold too low, to avoid creating friction on small purchases. Anyone who imposes a heavy process without preparation shows a weakness in change support.

Ability to build a structured business case: (1) map the current HR topics (recruiting, onboarding, payroll, labor law, performance reviews, training, conflicts) with current and projected volume, (2) opportunity costs (time spent by management and the office manager on these topics), (3) risk costs (legal mistakes, poor onboarding hygiene that worsens retention), (4) comparison with the cost of an HR officer (50-65 k€ plus employer contributions). Anyone who answers with an opinion and no numbers does not build a convincing case for leadership.

A healthy cadence depending on the focus area: daily (alerts, incidents, cross-functional support tickets), weekly (pipeline of operational projects, main KPI of each function served), monthly (budget review, status of supplier contracts, structuring metrics such as CAC, velocity, utilization). A distinction between leading indicators (activity, execution quality) and lagging indicators (budget, satisfaction). Anyone who lists 30 indicators or only looks at the monthly P&L misses the operational steering level.

Concrete familiarity with a modern stack: CRM (HubSpot, Salesforce, Pipedrive), expenses (Spendesk, Pleo, Circula, Mooncard), HR-light (Personio, HRWorks, Factorial, Lucca), document management (Notion, Confluence), accounting (DATEV, Lexware, Sage), reporting (Metabase, Looker, Tableau). Bonus: the candidate distinguishes the indispensable (CRM, accounting, payroll, expenses) from the optional depending on the phase (a BI tool only once data volume is sufficient). Anyone who pushes a single ecosystem (everything on HubSpot) without nuance shows an experience bias.

A structured method: (1) audit of the current process (who does what, on which tools, with which delays between steps), (2) identification of the bottlenecks (manual entry, late validation, delayed reconciliation), (3) possible automations (reconciliation via a modern tool, automatic categorization), (4) a review cadence with the tax advisor and the finance lead. Bonus: the candidate names a clear target (D+5 or D+7 maximum) and a realistic timeline to get there. Anyone who jumps to we need to change the accounting tool without diagnosing the process shows a tool-first reflex.

Recognition of how the role has evolved: the rise of the Ops function in scale-ups (a shift from a support to a strategic role), broadening toward RevOps / FinOps / PeopleOps, professionalization of tools (a modern SaaS stack), automation and AI on repetitive tasks. Anyone who still describes the role as the right hand of management without mentioning the cross-functional and structuring dimension shows a dated stance; anyone who talks about designing the operational system is at the right level.

A partnership stance: preparing topics in advance, anticipating needs, the ability to say no or propose an alternative when a leadership request collides with an operational priority. Bonus: the candidate names a topic where they pushed through a recommendation against a leader's initial opinion, and the outcome achieved. Anyone who describes a pure execution stance shows a weakness that leads to marginalization; anyone who describes a permanent power struggle has a fit gap with a partnership role.

Openness to upward and cross-functional feedback: signs of humility and coachability, central in a role exposed to several stakeholders. The ability to name a concrete example with the resulting behavior change. Anyone who speaks in generalities or cannot name a piece of difficult feedback does not hold the cross-functional position, where friction is unavoidable. Bonus: the candidate mentions having shared what they learned with others.