These salary negotiation tips work at any level: research the typical pay range for your role, level, and city before the conversation, then set three numbers — your target, your minimum, and your opening ask. Negotiate the full package, not just the gross salary, and let the company share a number first when possible. Justify your counter with market data and the value you bring rather than personal expenses, pause after naming your figure, and stay warm but firm. Finally, get the agreed package in writing before accepting, because verbal promises rarely survive onboarding.

Yes — salary negotiation in Germany is a normal and expected part of the hiring process, and initial offers are rarely the final number. Offers are usually quoted as gross annual salary (Bruttogehalt), so always clarify what is included: bonus, shift premiums, extra vacation days, and benefits. A counteroffer of roughly 5–10% above the offer is common, and candidates in demand — especially in tech, engineering, and product roles — can push higher. Anchor on the market rate for the role rather than your current salary, and negotiate politely but clearly; this almost never costs you the offer.

If you're working out how to negotiate salary with HR, start by treating it as a structured exchange, not a battle. When HR asks for your expectations early in the process, give a researched range based on the role and market, not your current salary. Ask about the complete package — base, bonus, benefits, relocation or learning budgets — so you can trade between components if the base is capped. If the offer is too low, ask how they arrived at the number and counter with market data instead of emotions. Keep the tone collaborative: the HR person you negotiate with today is often a colleague tomorrow.

Here's a salary negotiation with HR conversation example you can adapt. HR: "What are your salary expectations?" You: "Based on the market for this role and my experience, I'm looking at €68,000–€75,000 gross per year. What is the budgeted range for this position?" If HR then offers €65,000, respond: "Thank you — I'm genuinely excited about this role. Given my experience and the market data for this position, I was targeting €72,000. Is there flexibility to get closer to that, either through the base or the bonus?" This flow works because you ask for their range first, anchor with data, counter with a specific number, and show flexibility on components while holding your target.

A salary negotiation email should be short, positive, and specific. Open by thanking them and confirming your enthusiasm for the offer, state your ask with one clear number, and support it with one or two data points such as market ranges for the role and your relevant experience. If the base is fixed, propose an alternative like a signing bonus, extra vacation days, or an earlier salary review. Close by reconfirming that you want to make the role work, send it within a day or two of receiving the offer, and ask for the final package — every component — in writing before accepting.

The realistic answer to how much can you negotiate on salary is 5–15% on the base for most offers, and considerably more when you have competing offers, rare skills, or are switching industries. The exact room depends on the company's salary bands, internal equity with peers in the same role, and how urgently they need to fill the position. If the base is genuinely fixed, shift to the components — signing bonus, vacation days, remote flexibility, a title correction, or a six-month review with a defined raise. Knowing your walk-away point beforehand keeps you from accepting a number you'll resent.

Here's how to review your resume with ChatGPT: paste the job description alongside your resume and ask for a gap analysis first — for example, "Act as a recruiter hiring for this role and list the top 10 reasons you would reject this resume in 30 seconds." Then iterate bullet by bullet, asking it to rewrite duty-based lines as achievements with metrics and to surface keywords from the posting you've missed. Two cautions: ChatGPT can only work with the specifics you feed it, so supply your real numbers, and check that it hasn't invented or inflated anything. It's a strong first-pass tool for drafting, but it can't fully replace a recruiter's judgment on positioning — use AI for the rewrite and human review for strategy.

A resume review on LinkedIn usually refers to getting expert feedback on the CV you use for applications — either through LinkedIn's own career tools or, more commonly, by working with recruiters and career coaches who offer reviews through the platform. A good review looks beyond spelling: structure and scannability, ATS keyword match against your target job descriptions, and whether your bullets describe outcomes rather than duties. Before choosing a reviewer, check their background and testimonials, send your target role along with your resume, and prepare specific questions — the more context you give, the more specific the feedback. And remember your LinkedIn profile should tell the same story as your resume.

A CV review is a structured feedback pass on your CV by someone experienced, checking format, clarity, keyword match, and whether your achievements are quantified. In Germany, the CV (Lebenslauf) is the standard document — typically one to two pages, reverse-chronological, with clean and complete date lines and no unexplained gaps. Photos are no longer mandatory and many employers now prefer to skip them, but some still expect one, so check the norms in your industry. A proper review confirms that your CV meets these German conventions while still leading with measurable impact, because hiring managers everywhere skim for results first.

A blind resume review means the resume is evaluated with identifying details — name, photo, age, gender, sometimes even the university — removed, so only skills, experience, and achievements are judged. Some employers in Germany use anonymized applications to reduce unconscious bias, and job seekers can flip the idea to their advantage: strip your own details out and ask whether the content alone would impress a stranger. Recruiters also effectively review blind when scanning large candidate piles, which is why clear formatting and results-focused bullets matter far more than personal information.

A free resume review — through ATS checkers, AI tools, or feedback from friends and job clubs — is ideal for a first pass: it catches formatting issues, typos, and obvious keyword gaps. What a paid review adds is judgment from someone who has actually hired: whether your positioning fits the role you want, which bullets a hiring manager would skip, and what to cut entirely. The cost-effective approach is to fix the basics with free tools first, then invest in one expert review of the improved version, so you're paying for strategy rather than proofreading. If your resume consistently gets no interview invites, that's the clearest sign it needs experienced eyes.

The most common product manager interview questions fall into four broad buckets: product design ("How would you improve WhatsApp?", "Design an app for X"), product analytics ("Engagement dropped 10% — how do you diagnose it?", "Define success metrics for feature Y"), strategy and prioritization ("Should our company enter market Z?", "You can only build two of these five features — which do you cut?"), and behavioral questions ("Tell me about a conflict with engineering", "A time you influenced without authority"). Interviewers score the structure of your answer as much as the content, so practise clarifying the goal first, laying out an approach, prioritizing, and naming trade-offs out loud.

Most candidates need four to eight weeks of focused product manager interview prep at around five to eight hours per week; if you're moving from an adjacent role or targeting big tech, plan for two to three months. A practical split: start with frameworks for design, analytics, and strategy questions, then spend the bulk of the time drilling actual questions aloud, and finish with full mock interviews — ideally with someone who can give recruiter-style feedback, since solo reading hides the weak points that live interviews expose. Alongside practice, prepare five to seven behavioral stories you can adapt to different questions, and research the specific company's product and interview style.

A product manager interview coach earns their fee in specific situations: you're aiming at big tech where the bar and process are opaque, you've failed final rounds and don't know why, you need honest feedback on how you come across, or you're preparing on a tight timeline. Self-study with books and question banks covers the frameworks affordably, but someone who has actually hired product managers can tell you how interviewers evaluate and score answers — something books describe but feedback sessions demonstrate. The most cost-efficient approach is to self-study the basics first and then use one or two coaching sessions for mock interviews and targeted feedback.

The product manager interview at Google typically starts with a recruiter screen, followed by one or two phone or video interviews with PMs covering product design and analytics, and then an onsite loop of around four interviews spanning product design, analytics, strategy, and cross-collaboration or behavioral rounds. A distinctive part of Google's process is the hiring committee: your interviewers write detailed scored feedback, but the decision is made by a committee reviewing the full packet, not by a single interviewer. That means consistent, well-structured answers across every round matter — one great interview won't carry an inconsistent loop. Practise thinking aloud, structuring before answering, and handling "why" follow-ups, and treat the recruiter screen as a real evaluation rather than a formality.