Project Manager
JOIN Solutions AG
Get more replies from employers
Send a job-specific resume in minutes.
Benefits offered by this job
Job summary
JOIN Solutions AG in Deutschland sucht einen erfahrenen Projektmanager für die Steuerung von 1–3 Kernprojekten mit Budget zwischen 100 k€ und 1 M€ pro Projekt. Sie berichten an Führungskräfte, arbeiten eng mit Workstream- und Funktionsleitungen zusammen und lenken die bereichsübergreifende Abstimmung.
Sie bringen 3–7 Jahre Projekterfahrung in SMB/Scale‑ups mit interner Lieferverantwortung mit, beherrschen ein Steering‑Tool‑Set (z. B.
Qualifications
- 3-7 Jahre Erfahrung im Projektmanagement in SMB/Scale‑up/Beratung.
- Nachweisliche Führung von 2–4 Projekten mit Budgets 100k€–1M€.
- Beherrschung eines Steering-Toolstacks (Jira/Asana/Linear/Monday/Notion) und Reporting.
Responsibilities
- Frame new projects with sponsors and function leads: goals, scope, budget, risks, success indicators und governance.
- Steer laufende Projekte mit wöchentlicher Cadence; monatliches Steering mit Sponsoren.
- Aktives Leadership des Risikoregisters: Identifikation, Owner, Maßnahmen, wöchentliche Reviews.
Skills
Education
Tools
Job description
Before you write the job posting, settle three questions. They determine which profile you really need and help you avoid the most common scope mistakes at German SMBs. The Project Manager is often the first hire in delivery governance after the function leads, and the hire shapes the company’s project practice for the long run.
Question 1: Project Manager, Scrum Master or programme lead? The three roles partly overlap but are not equivalent. The Scrum Master works closely 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 programme lead steers a portfolio of several projects and often leads several Project Managers; the role is justified at a minimum of 5-7 parallel projects or from programmes over 2 M€. Mixing the three in one ad attracts poorly fitting applications and costs time. Specify the function already in the title: Projektmanager:in (m/w/d), not a multi-purpose profile of PM and agile coach, which says nothing.
Question 2: Which project typology and which method? At an SMB the project mix varies considerably: regulated projects with hard stage gates (banking, insurance, pharma, public sector) require waterfall-driven steering; exploratory tech projects require agile steering with Scrum or Kanban; cross-functional multi-team rollouts require hybrid methods with an agile core and waterfall governance at the interfaces. List the dominant project type and the expected methodology explicitly in the ad. A profile from the classic waterfall world does not have the same reflexes as a profile from an agile tech background; recruiting without a definition attracts heterogeneous applications and produces interviews in which everyone talks about a different role.
Question 3: Which multi-team responsibility? At a German SMB, the Project Manager can be the sole lead of a project with 5-15 people, or steer several parallel projects with workstream leads in each team. The nature of the role changes with the configuration: on a single project they spend 60-70 % of the time on execution and 30-40 % on stakeholder management; on several parallel projects the ratio inverts to 30-40 % execution and 60-70 % coordination and escalation management. Specify the expected configuration in the ad and test in the project case for the orchestration dimension, if it exists. An SMB with fewer than 60 employees rarely needs multi-project steering; the sole Project Manager on 1-2 projects is enough.
If the three answers converge on a mid-level Project Manager (3-7 years of experience) for an SMB with 30-200 employees and a defined project typology, use the template below.
[Company name], an SMB in [industry] based in [city], [X] employees, [X] M€ revenue, is looking for a Project Manager to steer [1-3] key projects with a focus on [regulated waterfall projects / agile tech projects / cross-functional multi-team rollouts].
As Project Manager you carry the delivery responsibility for [1-3] key projects with a budget between [100 k€ and 1 M€] per project, with teams of [5-15] people across the functions [engineering, sales, finance, HR]. You report to [management / the programme lead / the function leads] and work in close partnership with the workstream leads and function leads.
- Frame new projects with sponsors and function leads: goals, scope, budget, risks, success indicators and governance.
- Steer the running projects with a weekly cadence in the team, a fortnightly review with function leads and a monthly steering committee with sponsors.
- Actively lead the risk register: identification, assessment, clear owners, mitigation plan, a weekly review and proactive escalation of the top-3 risks to sponsors.
- Written status reports before every steering committee with an explicit status (green, amber, red) per workstream and clear decision requests.
- Multi-team orchestration across the functions involved with a documented dependency map and proactive interface steering.
- Maintain the escalation path: early notice of sensitive topics to sponsors and to the disciplinary managers of the team members when engagement is lacking.
- Structure the closure phase of each project: acceptance with sponsors, a hypercare phase after go-live, a lessons-learned document and the transition into the run responsibility of the functions.
- Essential: 3-7 years of experience in project management in an SMB, scale-up or consulting context with internal delivery responsibility; a demonstrated ability to lead at least 2-4 projects between 100 k€ and 1 M€ budget fully; command of at least one steering tool stack (Jira, Asana, Linear, Monday or Notion) and the associated reporting practice.
- Desired: a recognized certification (PMP, PRINCE2, Scrum Master, SAFe) depending on the project typology; experience in a regulated sector (banking, insurance, healthcare, industry) if relevant; prior experience in operational consulting (Goetzpartners, Capgemini Invent or comparable), followed by at least 2 years of internal delivery experience.
- Disqualifying: no internal delivery responsibility (a 100 percent consulting profile with no escalation experience); a pure Scrum Master profile with no multi-team orchestration; a tendency to mask problems instead of escalating early; instability (several 12-month stints in a row with no clear handovers).
- Gross annual compensation: fixed [50-80] k€ depending on experience and project scope. No structural variable share; a possible annual bonus of 5-10 % on achieved project milestones per company practice.
- Model: [full-time, hybrid 2-3 days / week on-site, based in [city]].
- Benefits: [a company pension, a job ticket or bike leasing, a meal subsidy, vacation days, a home-office policy, a training budget incl. PMP or PRINCE2 certification].
- Stack: [Jira, Confluence, Notion, Slack, and where applicable sector-specific tools].
Base salary, gross annual
25th percentile €50,000
Median €62,000
75th percentile €80,000
Gross fixed salary per year for a Project Manager with 3-7 years of experience at a German SMB (30-200 employees). Berlin, 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 recognized certification (PMP, PRINCE2, Scrum Master) or with experience in regulated sectors (banking, insurance, healthcare, industry) sit at the top end. The role has no structural variable share; some SMBs pay an annual bonus of 5-10 % on achieved project milestones, but the practice stays a minority.
The deepest pool for project-management profiles in Germany, especially strong in the scale-up and tech segment and at consultancies. Very effective in active sourcing (InMails) to profiles with a recognized certification (PMP, PRINCE2, Scrum Master). For a Project Manager, typically 45-65 % of qualified applications come through LinkedIn when you source actively. Recruiter Lite or Premium markedly improves targeting, especially for profiles with sector depth (banking, industry, healthcare).
Still strong for Project Manager positions in German Mittelstand SMBs outside the tech scene. Especially relevant in NRW, Bavaria and Baden-Württemberg, and for profiles over 35 with an industry or banking background who are more active on XING than on LinkedIn. If you recruit in a classic Mittelstand sector (mechanical engineering, industry, wholesale, insurance), XING is often on par with LinkedIn. For modern scale-ups with agile methods, LinkedIn stays superior.
The largest classic job market in Germany with a broad applicant pool. For Project Manager profiles, strong volume, especially from a classic waterfall background (PMI, PRINCE2) and Mittelstand experience. Slightly less signal than LinkedIn in the agile tech segment. A good complement for volume and reach. Expect 30-50 % additional qualified applications through StepStone when the ad runs for 30 days.
In project management, referrals from your own network are among the most reliable sources, because the role relies heavily on trust and cross-functional credibility. Activate the network of management, the function leads and the existing Project Managers with a concrete request brief (profile, experience, sector, location) and a transparent referral premium (€500-2,000 after passing probation). Expect 15-25 % of hires through this channel in an active Mittelstand network.
The Project Manager role reveals itself across four evaluation stages. The project case (stage 3) is central: without a concrete scenario on a multi-team project orchestration, it is hard to tell a profile that steers projects from one that only talks about projects.
Look for coherence between the size of the projects steered (budget, team size, duration) and the sector. A Project Manager with 3-7 years of experience should have led 2-4 projects between 100 k€ and 1 M€ budget with 5-15 people. Discount: 100 percent consulting profiles with no internal delivery responsibility (often strong in framing and weak in escalation), pure Scrum Master profiles with no multi-team orchestration (too narrow a scope for a real Project Manager), and a string of 12-month stints with no clear handovers. Check the type of methods: anyone who lists only waterfall or only agile will struggle at an SMB that swings between both modes.
Three questions only: (1) Describe the last project you led independently from start to delivery (scope, team, budget, duration), (2) What was the hardest risk you recognized and handled on that project? (tests risk maturity and the ability to anticipate), (3) Why are you looking for a change now? (a clear narrative vs. scattered). Outcome: go or no-go in a 5-minute debrief, no more. Discount: anyone who cannot tell a concrete risk story has probably reduced the role to plan tracking.
Give the candidate a realistic situation in advance: for example orchestrating a cross-functional rollout (a new travel-expense solution across finance, HR and IT for 80 employees in 3 months) or taking over a delayed project with a 4-week delay and a tense climate. Expect a three-page written document plus 60 min of discussion on the case, followed by 60 min of structured interview on the 15 questions below. At least 2 interviewers (ideally management or the programme lead plus someone from a delivery function), independent scoring before the debrief.
Call two references: a former managing director or programme lead and a former cross‑functional peer (a function lead from a project team). 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 escalation or a rescued project? The 4th question delivers the most signal: a Project Manager who cannot tell of a rescued delivery through references has probably only led simple projects or masked problems.
Describe the last complex project you led independently from initiation to delivery. Which stakeholders were involved, which method did you follow, and what did you have to adjust along the way?
What a strong answer surfaces
Ability to tell a complete cycle: framing (goals, scope, budget, risks), mobilization (team, stakeholder map, governance), execution (steering cadence, risk management, escalation), delivery (acceptance, hypercare, lessons learned). Bonus: the candidate mentions what did not work and what was adjusted. Anyone who describes a flawless course with no friction shows either too simple a case or a lack of critical eye.
Tell me about a project that clearly went off the rails (delay, budget overrun, scope drift). What was the cause, when did you recognize it, and how did you react?
What a strong answer surfaces
Early recognition and owned escalation: explicit early‑warning signals (missed milestones, deviating velocity, weakening stakeholder responses), a clear escalation decision with management, a response plan with trade‑offs (reduce scope, reinforce the team, postpone the date). Bonus: the candidate names the date of the escalation and compares it with the date of the first signs. Anyone who describes a smooth rescue with no escalation shows a tendency to mask problems, which gets expensive at an SMB.
Describe a situation where you had to lead a team without disciplinary authority over its members. How did you ensure engagement and delivery?
What a strong answer surfaces
Maturity in leadership without hierarchy: building credibility through expertise and clarity of goals, clear agreements on mutual availability, an escalation path with the disciplinary managers when engagement is lacking, recognizing contributions in the company. Bonus: the candidate describes a friction situation with a team member and how they resolved it without escalation. Anyone who only talks about formal authority or pure likeability does not hold the cross‑functional position in practice.
Management informs you 4 weeks before the planned delivery that the date is non‑negotiable, although the plan shows a 6‑week delay. What do you do?
What a strong answer surfaces
Owned arbitration instead of blind compliance: the candidate presents management three options with trade‑offs (reduce scope by X, reinforce the team by Y, lower quality on certain components), asks for an explicit decision, documents it and communicates it to the teams. Bonus: they name the risks of each option (quality risk, burnout risk, adoption risk). Anyone who simply drives the team to overtime without putting trade‑offs on the table shows a lack of framing maturity.
Two function teams (for example engineering and marketing) on the same project pass the ball back and forth and nothing moves forward. The next milestone delivery is in 10 days. How do you proceed?
What a strong answer surfaces
A structured unblocking method: (1) bilateral conversations with both sides to understand each one’s perception of the blocker, (2) a joint clarification session with a clear decision frame (what must be delivered by when, by whom), (3) escalation to the disciplinary managers of the people involved if the clarification fails. Bonus: the candidate names the need to document the problem in writing before escalating. Anyone who either shouts at both sides or immediately calls management shows a weakness in cross‑functional communication.
You take over a project that is 4 weeks behind, with a nervous sponsor. Your first 14 days as the Project Manager on this project: what exactly do you do?
What a strong answer surfaces
A diagnosis-first posture: (1) reading the existing deliveries, plans and risk register, (2) 1:1 with all team members and key stakeholders in the first week, (3) re‑framing the remaining plan with realistic assumptions, (4) escalating an honest situation assessment to the sponsor with three options. Bonus: the candidate resists the temptation to promise solutions in the first week and communicates clearly that the diagnosis phase needs 2 weeks. Anyone who promises a rescue plan in the first 3 days shows a dangerous reactive reflex.
A German SMB with 100 employees, you are the Project Manager for the migration to a new ERP system. Budget 250 k€, duration 9 months, affecting finance, sales, operations and engineering. You are to present your steering plan: governance, cadence, risks, success indicators. What do you propose?
What a strong answer surfaces
A structured steering plan: (1) governance on 3 levels (an operational weekly sync with workstream leads, a monthly steering committee with function leads and management, an ad‑hoc escalation mechanism), (2) a risk register with 5‑8 identified top risks (master‑data quality, adoption, interface delay, collective agreement, tax compliance), (3) success indicators as a mix of delivery milestones and business effects. Bonus: the candidate names the importance of a change‑management track and a hypercare phase after go‑live. Anyone who answers with a pure Gantt chart has reduced the role to plan tracking.
You lead 3 parallel projects (each 4‑6 months in duration, 3‑5 people per team) for the same management. In week 7 all three are critical at the same time (different causes, but a simultaneous need to escalate). How do you prioritize?
What a strong answer surfaces
Ability to prioritize without panic: (1) explicit criteria (business impact per project, reversibility of the risks, external dependencies and deadlines), (2) communication to management with a clear prioritization recommendation and a request for validation, (3) operational trade‑offs on the less‑priority projects (slowing down, delegation to workstream leads, a partial pause). Bonus: the candidate names when they ask for reinforcement (an additional junior PM, a programme lead, external consulting). Anyone who wants to rescue all three projects at once without prioritizing shows a lack of strategic maturity and ends in burnout.
Management asks you to structure the company's project portfolio for the next 12 months. 18 running or proposed projects, 9 function leads, scarce resources. How do you build the analysis, and what do you propose as governance?
What a strong answer surfaces
Portfolio‑management maturity: (1) a mapping of all projects with size (budget, people, duration), business impact (revenue, cost, risk reduction, compliance) and maturity (idea, framed, in execution), (2) a prioritization matrix (impact vs. effort or the Kano model) for explicit discussion with management, (3) a proposal for portfolio governance (a quarterly portfolio review, a monthly steering committee per large project, clear stop criteria). Bonus: the candidate names the need to pause or stop projects instead of starting everything in parallel. Anyone who answers with a flat list, with no prioritization logic, has not understood that a portfolio lives on trade‑offs.
Which tools do you use for project steering, reporting and stakeholder communication? Why these and not others?
What a strong answer surfaces
Concrete familiarity with a modern tool stack: project tracking (Jira, Asana, Linear, Monday, Notion), roadmapping (ProductBoard, Aha, Jira Roadmaps), reporting (Confluence, Notion, a dedicated dashboard), risk register (often in Confluence or Notion), communication (Slack, Microsoft Teams, targeted email). Bonus: the candidate distinguishes the essential (tracking, reporting, risk register) from the optional, depending on phase and methodology. Anyone who pushes a single tool for everything (everything in Jira) without nuance shows an experience bias; anyone who answers with no tool rationale shows a lack of reflection.
Which methodology do you prefer among waterfall, Scrum, Kanban, SAFe and hybrid? Why, and how do you adapt it to the context?
What a strong answer surfaces
Methodical maturity without dogma: the candidate explains that the method follows the project type (regulated projects and hard deadlines: rather waterfall with stage gates; exploratory tech projects: rather Scrum or Kanban; multi‑team programmes: hybrid with an agile core and waterfall governance at the interfaces). Bonus: they name a concrete project where the choice of method was changed, and why. Anyone who pushes a single method for all contexts (always Scrum, always SAFe) shows lack of adaptability; anyone who strings together buzzwords without explaining the application shows surface‑level knowledge.
How do you structure a risk register? Which risk types do you look at per project phase, and at what cadence is it reviewed?
What a strong answer surfaces
A structured risk method: (1) categorization (technical, organizational, stakeholder, regulatory, financial, supplier‑related), (2) assessment with probability and impact, (3) a clear owner and mitigation plan per risk, (4) a weekly review in the team and a monthly review in the steering committee. Bonus: the candidate names the distinction between active risks (currently monitored), passive risks (accepted) and materialized risks (now issues, handled differently). Anyone who describes a risk register as an Excel table with no owner has reduced the practice to theory.
In your view, what is the difference between a good Project Manager and an excellent one?
What a strong answer surfaces
Recognition of delivery substance over method: good Project Managers keep the plan and the cadence; excellent ones anticipate risks, escalate in time, protect the teams from noise, make hard trade‑offs and deliver even in hostile contexts. Bonus: the candidate names the ability to give an honest diagnosis even when it is unpopular. Anyone who talks about certifications, tools or methodology mastery without mentioning the human and political dimension shows too narrow a reading of the role.
Describe your relationship with the sponsors and managements you have served. How do you find the balance between executing their requirements and the ability to question their assumptions?
What a strong answer surfaces
A partnership posture: preparing topics in advance, clear written status reports before steering committees, the ability to say no or propose an alternative when a request collides with the project reality. Bonus: the candidate names a topic where they pushed through a recommendation against a sponsor's original opinion, and the result achieved. Anyone who describes a pure execution posture shows a weakness that leads to marginalization; anyone who describes a permanent power struggle has a fit problem with a partnership role.
Describe a piece of difficult feedback you received on your project leadership. How did you take it, and what did you change?
What a strong answer surfaces
Openness to upward and lateral feedback: a sign 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 the learning with others.
Below bar
On bar
Above bar
Multi‑team orchestration
Multi‑team orchestration Steers a single team or a single workstream; a lack of visibility on the dependencies between teams. Escalations come late, when the interfaces are already blocked. Steering committees revolve around activity instead of trade‑offs. Holds 2-4 teams or workstreams in parallel with a documented dependency map and weekly synchronization. Recognizes interface risks in time and steers steering committees that produce decisions. Function teams feel clear delivery expectations. Orchestrates a programme of several projects with cross‑functional governance. Function teams prefer to coordinate through them, because the decisions come fast and well argued. Able to rescue an interface without escalation to management.
Risk management The risk register serves as a filing cabinet, rarely reviewed. Escalations come when the risk has already materialized. No anticipation of the early‑warning signals; reacts to problems instead of preventing. An actively kept risk register with clear owners and a weekly review. Escalates the top-3 risks proactively to the sponsor with mitigation options. Deliveries hold the plan or slip with a documented rationale. Systematically anticipates the non‑obvious risks (political, organizational, regulatory) on top of the technical ones. Has a reputation for an honest diagnosis to management, even when it is unpopular. Brings projects over the line that others would have given up on.
Stakeholder communication
Stakeholder communication Status reports describe activity instead of delivery status. Sponsors are surprised by delays. Function teams complain about unclear requests or contradictory instructions. Clear written status reports before every steering committee with an explicit status (green, amber, red) and decision requests. Maintains a collegial relationship with sponsors and function leads. Facilitates useful meetings without noise. A relational reference in the company: sponsors let themselves be guided by their diagnosis, because trust is established. Able to deliver a difficult message so that the next stage continues without follow‑on damage. Turns the steering committee into a decision forum instead of a reporting forum.
Delivery rigor
Delivery rigor Plans are ambitious but rarely hold. Recurring delays, scope drifts and budget overruns with no clear diagnosis. No documented closure process; lessons learned not institutionalized. Plans hold in 70-80 % of cases or slip with a documented rationale. A weekly steering cadence held consistently. A closure phase with hypercare and a lessons‑learned document at the end of each project. Plans hold consistently or are re‑framed with lead time. The closure phase becomes a reference in the company: lessons learned are translated into other projects. No project slips through without an explicit diagnosis and sponsor validation.
Leadership without disciplinary authority
Leadership without disciplinary authority Relies on formal requests or sponsor escalation to get deliveries. Is perceived by team members as a tracker instead of a lead. Team engagement declines over the course of the project. Builds credibility through expertise and clarity of goals. Communicates clear mutual expectations with team members and their disciplinary managers. Team engagement holds until closure. Recognized by team members as their operational lead, although the disciplinary line lies elsewhere. Able to lead a team through a difficult phase (escalation, pivot, hypercare) without a loss of trust. Profiles who have worked with them twice gladly follow them again.
- Complete audit of the running or to‑be‑taken‑over project perimeter: reading the plans, deliveries, risk register and status reports of the last 3 months
- Documented 1:1 with all team members, function leads and key sponsors to identify the pain points and felt risks
- Identification of the 2-3 structuring risks or quick wins that must be addressed in the next 60 days
- First diagnosis to management with a clear situation assessment (green, amber, red per workstream) and proposed adjustments
- Steering cadence set up and held for 4 weeks: a weekly team sync, fortnightly function reviews, a monthly steering committee
- An actively kept risk register with clear owners and verifiable mitigation plans for the top-5 risks
- First next milestone delivered or deliberately re‑framed with a documented rationale, validated by the sponsor
- First structuring tooling or process update (a risk‑register format, a status‑report template, a steering‑committee agenda) introduced and validated with the function teams
- A stable steering cadence held for 6-8 weeks with consistent written status reports before every steering committee
- At least one milestone delivery successfully completed with a documented closure phase (acceptance, hypercare, lessons learned)
- Visibility on a 90‑day plan with realistic assumptions and explicit risks communicated in the steering committee
- A formal review with management: identified development areas for the next 90 days, any reinforcements (an additional workstream lead, external consulting) to anticipate
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:
- 01Confusing 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).
- 02Hiring 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).
- 03Prioritizing 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.
- 04Not 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).
- What does a Project Manager earn at an SMB in Germany?
The reference range for a Project Manager with 3-7 years of experience at a German SMB (30-200 employees) is 50-80 k€ gross annual salary (median around 62 k€). Berlin, 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 recognized certification (PMP, PRINCE2, Scrum Master) or with experience in regulated sectors (banking, insurance, healthcare, industry) sit at the top end. The role has no structural variable share; some SMBs pay an annual bonus of 5-10 % on achieved project milestones.
- What is the difference between a Project Manager, a Scrum Master and a programme lead?
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). 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 programme lead (Programme Manager or Director of Project Management) steers a portfolio of several projects with cross‑functional governance and often leads several Project Managers; the role is justified at a minimum of 5-7 parallel projects or from programmes over 2 M€. Mixing the three roles in one ad systematically produces a scope mismatch.
- Do you need a PMP or PRINCE2 certification as a Project Manager in Germany?
Not necessarily. Certifications such as PMP, PRINCE2, Scrum Master or SAFe are useful signals and often expected in regulated sectors (banking, insurance, public sector, pharma). In scale‑ups and tech SMBs, a real delivery history (the number of fully led projects, their size, the sector depth) counts considerably more than a string of acronyms. Evaluate the CV on substance, not on the certification list. A candidate with no certification but with 4 complete project cycles of 100 k€ to 500 k€ often delivers a more solid base than a candidate with three certifications and one led project of 50 k€.
- How long does it take to hire a Project Manager in Germany?
Expect 45-65 days between posting the ad and the signed contract for a mid‑level role. Timelines lengthen with multi‑stage selection (3 interviews plus a project case plus references) and at year‑end. Cutting below 45 days usually comes at the expense of the project‑case stage, which markedly worsens hiring quality for a role where the ability to escalate and frame is central. For a senior profile (more than 7 years of experience) or with a pronounced sector specialization (regulated), timelines can reach 75-95 days.
- Should a Project Manager work on‑site, hybrid or remote?
Full remote is possible if the teams served work remote themselves and the steering cadence (weeklies by video plus 1:1 with each function lead) is held consistently. In practice, hybrid 2-3 days on‑site remains the standard at a German SMB; the cross‑functional nature of the role benefits from physical presence to defuse friction and catch weak signals. Fully on‑site is justified when the team works entirely sedentarily or the company culture relies heavily on presence. Specify the model in the ad to avoid expectation mismatches.
- What legal requirements apply to Project 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, family situation and religion are not permitted in the interview (§ 1 ff. AGG).
Job postings and contract documents must be gender‑neutral (§ 11 AGG). Concretely: Projektmanager (m/w/d) or Projektmanager:in are permitted; Projektmanager (m/w) is not enough. Violations can trigger compensation claims of up to three months' salary.
EU Directive 2023/970 on pay transparency enters national law on 7 June 2026. Obligation: the salary range must be communicated at the latest before the first interview, ideally directly in the job posting. Asking about the candidate's current or previous salary is prohibited from that date.
The usual probation period for a Project Manager is 6 months (§ 622(3) BGB), with a two‑week notice period during probation. In a fixed‑term contract under the Part‑Time and Fixed‑Term Employment Act (TzBfG), the fixed term must be agreed in writing; a fixed term without a material reason is capped at 2 years (§ 14(2) TzBfG). For Project Managers the open‑ended hire is the standard, since the role is not project‑temporary but structural.
If your sector is bound by a generally binding collective agreement (e.g. the metal and electrical industry, banking, insurance, IT services in parts), it often sets minimum salary, special payments, working time and notice periods bindingly. Check the applicable sector agreement before fixing compensation. For Project Managers at non‑tariff‑bound SMBs (the common case) free agreement is possible.
If you use an AI tool to pre‑select or score applications, the EU AI Act (applicable from 2 August 2026) classifies this use case as high‑risk. Obligations: transparency towards applicants, logging of decisions, effective human oversight. A fully automated rejection without human oversight triggers employer liability.
Run this hire in Join Source, screen, and interview in one place.
In which language should we get back to you?
We'll get back to you within one business day.
Please try again in a moment.
'/%3e%3cpath%20d='M101.744%2012.4726L102.894%2016.1947L99.0021%2013.2201L101.744%2012.4726ZM105.3%208.40937H100.488L99.0026%203.59473L97.5116%208.41047L92.7%208.40385L96.5965%2011.3834L95.1055%2016.1942L99.0021%2013.2196L101.408%2011.3834L105.3%208.40992V8.40937Z'%20fill='white'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_5593_1381'%20x1='90'%20y1='9.44471'%20x2='99'%20y2='9.44471'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%2300AD70'/%3e%3cstop%20offset='0.998594'%20stop-color='%2300B67A'/%3e%3cstop%20offset='1'%20stop-color='%23DCDCE6'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e){kind=small}
