Operations Manager
Job description, salary, sourcing, 15 interview questions and a 30/60/90 plan to hire an Operations Manager in a German SMB.
Compiled by the Join team from public data and our hiring experience.
Updated
At a glance
- Median salary€60,000€50,000 – €75,000
- Time to fill50–80 days
- Experience5–10 years
How to hire an Operations Manager for your SMB
Before you write the job posting, settle three questions. They determine which profile you actually need and avoid the most common scope mistakes at German SMBs. The Operations Manager is often the 2nd or 3rd leadership hire after the founders, and the hire shapes the company’s operations for the long term.
Question 1: Operations Manager, Office Manager or COO? The three roles partly overlap but are not equivalent. The Office Manager runs the office (premises, office suppliers, general administration, internal events, logistical onboarding). The Operations Manager runs the cross-functional operation of the company (processes, tools, strategic suppliers, structuring projects). The COO (Chief Operating Officer) defines the overall operational strategy and sits on the leadership team; they are justified from 150-200 employees. Blending the three in one ad attracts poorly matched applications and costs time. Specify the function in the title itself: Operations Manager (m/w/d), not a versatile Ops and administration profile, which says nothing.
Question 2: Which focus area? At an SMB the perimeter of an Operations Manager varies considerably depending on the most painful function at the time of hiring: 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 with no clear dominant. List the dominant focus area and the expected perimeter explicitly in the ad. A RevOps profile does not have the same reflexes or master the same tools as a FinOps profile; recruiting without a definition attracts heterogeneous applications and produces interviews where everyone talks about a different post.
Question 3: Which team to lead? At a German SMB the Operations Manager can be a sole individual contributor or lead a small team (1-5 people: an Ops assistant, a dual-study student, an internal accountant, an Office Manager). The nature of the role changes with the configuration: alone, they spend 80 % of their time on execution and 20 % on cross-functional scoping; with a team, the ratio flips to 40 % execution and 60 % coordination. Specify the expected configuration in the ad and test the managerial dimension in the interview if it exists. An SMB under 60 employees rarely needs a constituted Ops team; a sole Operations Manager is enough.
If the three answers converge on a mid-level Operations Manager (5-10 years of experience) for an SMB with 30-200 employees and a defined focus area, move on to the ad template below.
JD template
Operations Manager (m/w/d) at a German SMB
[Company name], an SMB in [industry] based in [city], [X] employees, [X] M€ revenue, is looking for an Operations Manager to steer the cross-functional operation with a focus on [RevOps / FinOps / PeopleOps / cross-functional].
Your role
As Operations Manager you steer the cross-functional operation of the company (processes, tools, strategic suppliers, structuring projects) with a focus on [RevOps / FinOps / PeopleOps / cross-functional] for a workforce of [30-200] growing employees. You report to [management / COO / finance lead] and work in close partnership with the owners of the functions (Sales, Engineering, Finance, HR).
Key responsibilities
- Design and steer the key cross-functional processes (procurement, expenses, onboarding, reporting) in partnership with the functions concerned, from diagnosis to rollout and indicator tracking.
- Audit and steer the operational SaaS stack: tool selection, contract negotiation, tracking of real usage, identification of duplicates and underuse.
- Steer the company’s strategic suppliers (beyond the pure office): IT, accounting, HR, legal and ad-hoc consulting providers. Contract audit, renegotiation of renewals, selection of new providers.
- [If RevOps focus] Guarantee CRM reliability, run a weekly forecast cadence with Sales, structure Sales / Marketing / Customer Success alignment.
- [If FinOps focus] Steer the monthly financial reporting calendar, track budget per function, optimize SaaS stack costs, structure the procurement process.
- [If PeopleOps focus] Structure onboarding and offboarding, roll out HR-light tooling (Personio, HRWorks, Factorial, Lucca), run the calendar of performance reviews and feedback.
- Build and maintain a calendar of recurring operational obligations (contract renewals, filings, budget deadlines) and flag sensitive topics in time.
- Run an operational steering cadence: a weekly review with management, a monthly cross-functional review with the owners of the functions.
Profile
- Required: 5-10 years of operational experience at an SMB or scale-up with 30-200 employees; a proven ability to run a cross-functional structuring project end to end (scoping, design, rollout, measurement); mastery of at least one tool per key category (CRM, expenses, HR-light, document management).
- Desired: specialization in the expected focus area (RevOps, FinOps or PeopleOps); experience at a fast-growing scale-up (transition from 30 to 100+ employees); prior experience in operational consulting (Goetzpartners, PRIMA Consulting or comparable), followed by at least 3 years of internal experience.
- Disqualifying: no internal operational experience (100 % consulting profile); ex-COO seniority from a structure 5x larger than the target SMB; rejection of modern tools or a pure execution stance with no ability to make cross-functional trade-offs; instability (several 12-month stints in a row).
What we offer
- Gross annual compensation: fixed [50-75] k€ depending on experience and perimeter. No structural variable component; a possible annual bonus of 5-10 % on OKR attainment depending on company practice.
- Model: [full-time, hybrid 2-3 days / week on-site, based in city].
- Benefits: [company pension, job ticket or bike leasing, meal allowance, vacation days, home-office policy, professional development budget].
- Stack: [CRM, expense tool, HR-light tool, accounting, BI if applicable].
Salary band
Base salary, gross annual
- 25th percentile
- €50,000
- Median
- €60,000
- 75th percentile
- €75,000
Gross fixed salary per year for an Operations Manager with 5-10 years of experience at a German SMB (30-200 employees). Munich, Frankfurt and Hamburg pull the range up by 10-15 %; rural regions and the East pull it down by 5-10 %. Profiles with a strong focus-area specialization (RevOps, FinOps, PeopleOps) or with hyper-growth scale-up experience sit at the top of the range. The role has no structural variable component; some SMBs pay an annual bonus of 5-10 % on OKR attainment, but the practice remains a minority.
Sources: Stepstone Gehaltsdaten Operations Manager Deutschland 2026; Destatis Verdiensterhebung (April 2025); kununu Gehaltscheck Operations Manager 2025
Where to source this role
LinkedIn
€200-400 / month (Job Slots)The deepest pool for Ops profiles in Germany, with a high density of Operations Managers from scale-ups and consulting firms. Very effective for active sourcing (InMails) on employed profiles who are not actively looking. For an Operations Manager, 50-70 % of qualified applications typically come from LinkedIn when you source actively. Recruiter Lite or Premium sharpen targeting considerably.
XING
ProJobs from €195 / monthStill strong for Ops roles in German Mittelstand SMBs outside the tech and startup scene. Especially relevant in NRW, Bavaria and Baden-Württemberg, and for profiles over 35 who are more often active on XING than on LinkedIn. If you recruit in a classic Mittelstand sector (mechanical engineering, industry, wholesale), XING is often on par with LinkedIn; for modern scale-ups in Berlin, LinkedIn is clearly superior.
Stepstone
From €995 / 30 daysThe largest classic job market in Germany with a broad applicant pool. For Operations Manager profiles you get strong volume, mostly from a Mittelstand background with administrative depth; slightly less signal than LinkedIn in the scale-up and RevOps/FinOps segment. A good complement for volume and reach when filtering is handled operationally. Expect 30-50 % additional qualified applications via Stepstone when the ad runs for 30 days.
Evaluation playbook
The Operations Manager role reveals itself across five evaluation stages. The operational trade-off case (stage 4) is central: without a concrete scenario on a cross-functional trade-off, it is hard to tell a profile that designs processes apart from one that only talks about them.
Stage 1: CV review
Look for consistency between the size of the structures served (30-200 employees is the German SMB range) and the type of topics steered (processes, tools, suppliers, cross-functional projects). Discount: 100 % consulting profiles with no internal operational phase (often strong on scoping and weak on execution), 100 % administration profiles with no scoping ability, and a string of 12-month stints as an Operations Manager (repeated scope mismatch). Check the type of topics steered: a CV that lists administration, support, coordination without mentioning tool steering or supplier audits describes an Office Manager, not an Operations Manager.
Stage 2: Phone screen (30 min)
Three questions only: (1) Describe your current scope (team size, focus area RevOps / FinOps / PeopleOps / cross-functional, topics steered), (2) Which cross-functional trade-off project did you run independently this year? (tests autonomy and scoping maturity), (3) Why a change now? (clear narrative vs. unfocused). Outcome: go/no-go in a 5-minute debrief, no longer.
Stage 3: Structured interview (90 min)
Work through the 15 questions below, alternating behavioral, situational, case, technical and values. At least 2 interviewers (ideally management or leadership plus someone from Finance or Ops), independent scoring before the debrief. Insist on the case questions: trade-offs between functions are the core of the role, and candidates who talk abstractly without touching concrete numbers do not hold the position in practice.
Stage 4: Operational trade-off case (90 min)
Give the candidate a realistic situation in advance: for example an audit of the operational stack (15 SaaS tools, 80 k€ annual cost, 3 underused tools to make trade-offs on) or a project to redesign the expense process with cross-functional impact on Finance, HR and Sales. Expect a two-page written document plus 60 min of discussion. Assess method, prioritization and the quality of the clarifying questions asked beforehand. A good Operations Manager asks 5-8 clarifying questions before answering.
Stage 5: References (structured check)
Call two references: a former managing director or COO and a former cross-functional peer (Finance, Sales, HR). Ask both the same 4 questions: What is she/he strongest at? Where would you hire someone complementary? Would you hire them again tomorrow, why or why not? A concrete example of a difficult cross-functional trade-off they handled? The fourth question delivers the most signal: an Operations Manager who cannot recount a difficult cross-functional trade-off through references has probably played it safe everywhere.
Structured interview questions
BehavioralProcess thinking Describe the last cross-functional process you designed from scratch (expenses, onboarding, procurement, reporting). What was the need, which method did you follow, and what had become of it 6 months later?
What a strong answer surfacesAbility 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.
BehavioralTrade-off autonomy Tell me about a moment when you had to make a trade-off between the conflicting demands of two functions (for example Sales and Finance, or HR and IT). How did you decide?
What a strong answer surfacesAn 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.
BehavioralTrade-off autonomy Describe a situation where management gave you an ambiguous instruction, or one that contradicted an earlier instruction. How did you handle it?
What a strong answer surfacesMaturity 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.
SituationalTrade-off autonomy Management tells you at 5 p.m. that the finance lead is resigning and that you will temporarily take on payroll, accounting and cash management on top of your current topics. You have 48 hours to propose a plan. What do you do?
What a strong answer surfacesScoping 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.
SituationalTool judgment Your operational stack includes 18 SaaS tools for 80 employees, annual cost 120 k€. Management wants to cut 30 % in 6 months without weakening productivity. How do you proceed?
What a strong answer surfacesA 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.
SituationalProcess thinking The Sales and Customer Success teams have complained for 3 months that the CRM does not reflect the reality of the accounts. In parallel, the finance lead complains that the forecast is not reliable. What is your plan?
What a strong answer surfacesRecognizing 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.
CaseProcess thinking German SMB with 60 employees, 8 M€ ARR, 3 main functions (Sales 20, Engineering 25, Ops/G&A 15). No finance lead, no COO. Management asks you to define your 3 priorities for the first 6 months. What do you propose, and why these 3 rather than others?
What a strong answer surfacesAbility 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.
CaseCross-functional communication You arrive and find that no procurement process exists: every function orders directly, invoices arrive scattered, no upfront validation above a threshold. Which 90-day plan structures this without alienating teams used to their autonomy?
What a strong answer surfacesA 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.
CaseOperational rigor Management asks you to quantify the hidden cost of the missing dedicated HR function in the SMB (60 employees, planned growth from 60 to 90 in 12 months). How do you build the analysis?
What a strong answer surfacesAbility 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.
TechnicalOperational rigor Which indicators do you look at daily, weekly, monthly to steer operations? Why that cadence?
What a strong answer surfacesA 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.
TechnicalTool judgment Describe the ideal operational stack for a growing German SMB with 80 employees (Sales 30, Engineering 30, Ops/G&A 20). Which tools are indispensable and which are optional in your view?
What a strong answer surfacesConcrete 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.
TechnicalOperational rigor You arrive and find that monthly financial reporting takes 15 days after month-end to produce, with discrepancies between P&L and budget. Which 60-day plan makes it reliable and speeds it up?
What a strong answer surfacesA 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.
ValuesCross-functional communication What is your reading of the Operations Manager role in 2026 at a German SMB? What has changed, in your view, compared to 5 years ago?
What a strong answer surfacesRecognition 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.
ValuesCross-functional communication Describe your relationship with the leadership teams you have served. How do you find the balance between executing their requests and being able to challenge their intuitions?
What a strong answer surfacesA 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.
ValuesCross-functional communication Describe a piece of difficult feedback you received about your work from a leader or a cross-functional peer. How did you take it, and what did you change?
What a strong answer surfacesOpenness 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.
How to recognize a great hire
| Trait | Below bar | On bar | Above bar |
|---|---|---|---|
| Process thinking | Reactive to requests, case by case; no structured method for framing a new topic. Solves without diagnosing. Processes put in place are cumbersome or abandoned after a few months. | A clear scoping method: diagnosis before solution, alternatives weighed, change support planned. Processes that hold for 12 months and are adopted by the teams concerned. | The methodological reference in the company: able to design a cross-functional process end to end (mapping, design, rollout, measurement) and adapt it based on the results. The processes designed outlive their own presence. |
| Trade-off autonomy | Asks for validation on every cross-functional trade-off; avoids conflict by systematically going through management. Does not master the escalation process. Functions served complain about decision slowness. | Decides autonomously on the usual trade-offs; knows how to flag in time the topics that exceed their scope. Communicates decisions clearly and with reasons to both parties. | Recognized by management and peers as a reliable arbiter. Functions served prefer to go through them rather than through management, because the decision comes faster and better argued. Able to hold a position against a leader with diplomacy. |
| Cross-functional communication | Communicates mainly with management or a close circle. Avoids direct exchange with operational staff or uses a procedural tone that blocks. Functions served feel a lack of listening. | Can explain decisions and processes to all functions served in appropriate vocabulary. Holds a collegial relationship with Sales, Engineering, Finance, HR. Runs useful cross-functional meetings that are kept. | The relational reference in the company: functions served raise friction spontaneously and early, because trust is established. Able to defuse a conflict between two functions without leaving collateral damage. |
| Tool judgment | Pushes the best-known or newest tool with no prior diagnosis. Does not distinguish critical tools from convenience tools. Risk of over-tooling (exploding stack) or under-tooling (degraded productivity). | Evaluates tools against a clear set of requirements (volume, integrations, cost, learning curve). Can say no to a popular tool that does not serve the need. Masters the indispensable tools of a modern SMB. | Able to audit an existing stack, identify duplicates and underuse, and propose a reasoned evolution plan. Distinguishes structuring tools (CRM, accounting, payroll) from convenience tools (BI, automation) depending on the SMB phase. |
| Operational rigor | Topics regularly slip through (forgotten contract renewals, late reporting, budget tracked in scattered ways). Lacks visibility on ongoing obligations and commitments. No kept steering cadence. | A regular cadence on indicators and obligations; deadlines met on recurring topics. Detects and flags deviations before they become problems. Documentation of decisions and processes kept current. | No topic slips through without explicit flagging; management can go 3 weeks without looking at operations and need not fear a nasty surprise. Able to take vacation without leaving ticking time bombs, and to hold a steering cadence end to end. |
30 / 60 / 90 day success plan
By day 30
- Full audit of operations: mapping the key processes (procurement, expenses, onboarding, reporting), the SaaS stack (tools, costs, real usage) and the main suppliers
- Documented 1:1 with each leader and each owner of the functions served (Sales, Engineering, Finance, HR) to identify pain points and felt priorities
- Identification of the 2-3 quick wins that can be delivered in the next 60 days (for example renegotiating a visible supplier contract, removing an underused tool, formalizing a simple recurring process)
- First diagnosis to management with 3 hypotheses for structuring priorities for the next 6 months
By day 60
- First project to redesign a cross-functional process delivered (for example the procurement process, the expense process or the financial reporting calendar)
- Quick wins identified at T+30 delivered and measured (quantified savings, time gained, satisfaction of the teams served)
- Operational steering cadence set up: a weekly review with management, a monthly cross-functional review with the owners of the functions
- Structuring 6-month plan validated with management on the 2-3 deep projects to carry (stack redesign, RevOps/FinOps/PeopleOps structuring, organization of the Ops function)
By day 90
- Stable operational cadence held for 6-8 weeks (no recurring topic slips through, steering indicators current, deadlines met)
- First structured monthly reporting to management on operations: budget, contracts, ongoing projects, any alerts, indicators of the functions served
- First structuring project in execution with clear milestones and success indicators shared with management
- Formal review meeting with management: development axes identified for the next 90 days, any hires or reinforcements to anticipate
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.
Frequently asked questions
What does an Operations Manager earn at an SMB in Germany?
The reference range for an Operations Manager with 5-10 years of experience at a German SMB (30-200 employees) is 50-75 k€ gross annual salary (median around 60 k€). Munich, Frankfurt and Hamburg pull the range up by 10-15 %; rural regions and the East pull it down by 5-10 %. Profiles with a strong focus-area specialization (RevOps, FinOps, PeopleOps) or hyper-growth scale-up experience sit at the top of the range. The role has no structural variable component; some SMBs pay an annual bonus of 5-10 % on OKR attainment.
What is the difference between an Operations Manager, an Office Manager and a COO?
The Office Manager runs the office (premises, office suppliers, general administration, internal events, logistical onboarding) and at an SMB often carries a first share of HR. The Operations Manager runs the cross-functional operation of the company (processes, tools, strategic suppliers, RevOps / FinOps / PeopleOps, structuring projects) and is often the 2nd or 3rd leadership hire after the founders. The COO (Chief Operating Officer) defines the overall operational strategy, leads several Operations Managers or functions and sits on the leadership team; they are justified from 150-200 employees. Blending the three roles in one ad systematically produces a scope mismatch.
Which focus area for an Operations Manager at a German SMB?
Three main 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). A 4th configuration is pure cross-functional: processes, suppliers, structuring projects with no clear dominant. The choice depends on the most painful function in your SMB at the time of hiring. Recruiting without a defined focus area attracts heterogeneous applications and produces mis-hires within 12 months.
How long does it take to hire an Operations Manager in Germany?
Expect 50-80 days between posting the ad and signing the contract for a mid-level post. The timeline lengthens with multi-stage selection (3 interviews plus a practical case plus references) and at year-end. Cutting below 50 days usually comes at the expense of the practical-case stage, which markedly lowers hiring quality on a post where cross-functional scoping ability is central. On a senior profile (more than 10 years of experience) or with a strong specialization (RevOps), the timeline can reach 90-120 days.
What legal requirements apply to Operations Manager job postings in Germany?
Three central requirements: (1) a gender-neutral job title with (m/w/d) or colon spelling (§ 11 AGG), (2) the obligation of pay transparency in the ad or before the first interview (EU Pay Transparency Directive 2023/970, implementation by 7 June 2026), (3) transparency about the use of AI tools for pre-selection and guaranteed human oversight (EU AI Act, from 2 August 2026). Questions about age, origin, marital status and religion are not permitted in the interview (AGG § 1 ff.).
Should an Operations Manager work on-site, hybrid or remote?
Full remote is possible if the team served works remotely itself and the cross-functional steering cadence (weeklies by video plus 1:1 with each function owner) is held consistently. In practice, at a German SMB hybrid 2-3 days on-site remains the standard; the cross-functional nature of the role benefits from physical presence to defuse friction and pick up weak signals. Full on-site is justified when the team works entirely from one location or the company culture relies strongly on presence. Specify the model in the ad to avoid expectation mismatches.