Search real stories by role, salary, location, source of hire, interview process and what finally worked. Use these stories to understand the market before your next application or offer negotiation.
The case study went up on a Tuesday afternoon. By Thursday morning I had three replies in my LinkedIn inbox.
I'd been thinking about job-hunting for a while without doing anything about it. The plan had always been polish the portfolio first, then start applying. After two months of polish that clearly wasn't converging on a finished portfolio, I tried the opposite: pick one project, write it up properly, post it publicly, and let people tell me whether it was good enough.
The project was an onboarding redesign for a fintech I had nothing to do with. I'd been a customer and noticed three friction points. Over a long weekend I prototyped a flow that fixed two of them, built a Figma file with annotated frames, and posted a 600-word writeup on LinkedIn explaining the trade-offs.
N26 replied within a day. Their head of design said the writing was the part that had stopped her. Most case studies she sees are visual evidence with no reasoning attached, and she wanted to talk to designers who could think about trade-offs out loud.
The first call was 45 minutes with the head of design. We didn't talk about N26 specifically until the last ten minutes. Most of it was her asking how I'd handled specific decisions in past projects: when I'd disagreed with a PM, when I'd shipped something I knew was a compromise, what I'd learned the hard way about onboarding metrics. A real interview, not a "tell me about yourself" one.
Round two was a portfolio walkthrough with two designers from the team. Sixty minutes, three case studies. They cared about the in-between decisions. Why this typeface and not the obvious one. Why I'd recommended killing a feature instead of fixing it. The questions kept circling back to constraints rather than craft.
Round three was a paid take-home: redesign their settings flow, document the trade-offs in a written summary, time-boxed at five hours. I treated it as a real project, didn't over-polish, and shipped exactly what fit in five hours. The summary was three paragraphs on what I'd cut, why, and what I'd do next with a full week.
The final round was a 30-minute conversation with the CTO. Not a values check disguised as a chat, but a real conversation about the role, the team, what they'd ship over the next quarter, and whether I'd stay for two years. He was the most direct interviewer of the loop.
The offer was €58,000. I asked once for a bump on the base, citing the scope they'd described in the final round. They came back the same day with the same number plus a sign-on that covered relocation. I accepted.
I sent 18 applications during this whole search. Three were the immediate replies to the case study post. The rest went to companies I'd targeted because their product overlapped with the case-study domain. Volume wasn't the lever. Specificity was.
Over about five months I applied to roughly 50 positions, almost all through LinkedIn, with a handful via Glassdoor. No networking events, no warm introductions, no carefully crafted cover letters. Just a well-put-together profile, a clean CV, and a lot of scrolling through job alerts on Sunday evenings. I'd always assumed that breaking into a better-paid in-house Legal Counsel role would mean knowing someone on the inside, or at least having a former colleague put in a word. That assumption was costing me confidence I didn't need to lose.
The process took around 150 days from first application to accepted offer, which felt agonisingly slow at the time. There were weeks where nothing moved at all, and I genuinely wondered whether I was pitching myself at the right level or aiming at the right sectors. Out of 50 applications I got three interviews, which sounds like a low conversion rate, but each one was for a role I'd read carefully and felt I could do well. I didn't spray applications around. I made sure my experience matched the specifics in the listing before I applied. The third interview process was where everything clicked. The role was hybrid, based in the UK, and came with a salary of £60,000, a meaningful step up from where I'd been. There were also travel perks built into the position that I hadn't even thought to look for when I started. I accepted without hesitation.
A few things stand out as genuinely useful. Reading the job listing properly, not just skimming it, meant I could speak directly to what they wanted once I was in the room. Not having a referral clearly didn't disqualify me, so I'd push back on anyone who thinks LinkedIn applications are a black hole. And when the salary conversation started, I didn't undersell myself. I knew what the role was worth, and I held that line. It paid off.
The whole thing took about six weeks from the first message to a verbal offer, and on most measures it looked like a win. Eighteen applications into my search, six interview rounds with Mews, and a Senior Product Manager offer at €96k base plus equity for a fully remote role out of Amsterdam. On paper, exactly what I'd been aiming for.
The interviews were polished. The hiring manager kept coming back to ownership, to giving PMs real authority over the roadmap, to moving fast without the usual enterprise drag. I left each round feeling energized. The equity conversation was straightforward, the base hit my number, and the remote setup meant I could stay put. I was close to signing without thinking much harder about it.
Before I did, though, I spent a couple of evenings on LinkedIn cross-referencing people who'd held PM roles at Mews in the last two years. I found two former PMs and sent short, direct messages saying I had an offer and asking for fifteen minutes. Both replied within a day, which probably told me something on its own. What they said lined up too closely to wave off. The roadmap got rewritten roughly every six weeks, not because the market had moved but because senior leadership kept reversing decisions they'd already handed down. Two PMs had quit in the single quarter before my offer, neither of them as part of any planned transition. One of them told me she'd spent her last month rebuilding a spec she'd already shipped once. That detail stuck with me more than the rest.
I declined the next day. I kept the message short and professional and gave no specific reason. Finding something else took longer than I'd hoped after that, and there were a few weeks where I questioned the call. I never regretted it, though.
Around six weeks before I landed this role, I was riding a frustrated energy after wrapping up a particularly rough phase of migrating our legacy product, roughly 200,000 lines of React code, to React 19 with concurrent features enabled. Most write-ups I'd seen about React 19 glossed over the hard parts, so I wrote an honest LinkedIn post instead: what we migrated, how we approached the concurrent rendering rollout, which assumptions blew up in our faces, and the two weeks we spent hunting down subtle tearing bugs in our data-fetching layer. I didn't expect much. It was a long, technical post with code snippets and a fair amount of "here's what we got wrong."
Within a week I had three inbound recruiter pings. I was also running my own search in parallel, 14 applications total across Amsterdam-based and remote-friendly companies, but the inbound interest felt different in quality. One Amsterdam software company stood out immediately. Their recruiter referenced specific paragraphs from the post in the first message, which told me someone technical had actually read it before reaching out. The process reinforced that. Instead of a LeetCode round or a whiteboard session on binary trees, they asked if I'd do a code review on a real piece of their own codebase, with explicit consent from the team that owned it. I spent about three hours on it, left comments the way I would for a colleague, and explained the tradeoffs rather than just flagging issues. It felt like actual work, which made it much easier to stay engaged through all five rounds.
The offer came 42 days after that first message. The base was 82,000 EUR, full-time and fully remote. I negotiated two things before signing: remote-first as a formal policy rather than a tolerance, and a four-day workweek instead of the standard five. Both landed. I accepted without hesitation.
I didn't have a relevant degree, and I won't pretend the search was easy. I'd come to Germany as an international worker hoping to break into tech, with a self-taught frontend skill set and a portfolio I'd built through online courses and personal projects. From the outside it probably looked like a long shot. From the inside it felt like one too. The rejections piled up fast. We're talking hundreds. Some were automated no-replies, some were polite one-liners, and a few were detailed enough to sting. Every time a promising application went cold, I had to talk myself out of reading too much into it.
What kept things moving was persistence and casting a wide net through the right channels. I was active on LinkedIn, Xing, and Germany's Make-it-in-Germany program, which exists specifically to help international workers find their way through the local job market. LinkedIn was where I got the most traction. I tightened up my profile, started connecting with recruiters directly, and put my portfolio links front and center. I tried to treat each rejection as a data point, not a verdict. If my HTML and CSS projects weren't getting attention, I pushed harder on JavaScript. If a cover letter wasn't landing, I rewrote it. Slow, unglamorous work, but methodical.
Eventually I got through to a company willing to look past the unconventional background. The interview process had four rounds, covering everything from a technical skills screen to a cultural fit conversation, and each one felt like a real test of how far I'd actually come. When the offer finally arrived, it was for a full-time junior frontend developer role in a hybrid setup at 45,000 EUR a year, and I accepted without hesitation. If you're trying to break into tech abroad without traditional credentials, the rejections aren't a verdict on you. Patience and volume, through the right platforms, got me there.
I finished the bootcamp in March with zero commercial experience and a portfolio that felt embarrassingly thin. I spent the next few weeks applying to anything with "junior" or "graduate" in the title: 47 applications total over about two and a half months, mostly through LinkedIn. The response rate was brutal. Most companies ghosted me, a few sent automated rejections within hours, and I started to wonder whether a bootcamp certificate was worth anything at all in a market full of CS graduates.
The thing that changed everything was a side project I almost didn't publish. I'd built a small open-source tool on top of the Spotify API that generates personal listening stats. Nothing revolutionary, but I was proud of how I'd structured the code and documented it. I posted a Show HN on Hacker News mostly to get feedback, and it took off unexpectedly. Around 200 stars in the first month, some nice comments about the architecture, and a handful of people opening issues and pull requests. I was refreshing the GitHub notifications like a slot machine. About two weeks after the post, an engineer at a Madrid startup starred the repo and then DMed me on LinkedIn, saying the queue management pattern I'd used had caught his attention and that they were hiring.
The interview process was three stages. First was a technical call where we walked through the project together and talked about how I'd handle scaling it. Then a take-home: build a small queue worker that processes async jobs with retry logic, which felt very much like day-to-day work rather than a whiteboard puzzle. Finally a relaxed team chat with two senior engineers, more of a culture conversation than an interrogation. The whole thing took about two weeks once it started.
The offer came in at €26k, which feels low for Madrid, and I negotiated briefly without much movement. But the company is an almost entirely senior team, and they pair-program with juniors deliberately, which to me is worth more right now than an extra few thousand euros. I accepted.
47Applications
3Interviews
2 monthsSearch length
LinkedInSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.