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.
Changing careers from software sales into product design was brutal by the numbers: 14 months, more than 200 applications, 205 rejections, 6 interviews, and in the end a single design offer, a product design internship at Braze in New York. I want to be honest about what that felt like before I get to the part where it works out.
I spent the first few months convinced I just needed a better portfolio. So I enrolled in a bootcamp, rebuilt my case studies from scratch, and watched endless teardowns of apps I'd never used. I was still working a software sales job through all of it, which meant most of my design work happened after 9 PM or on weekends. I applied through job boards obsessively: LinkedIn, Wellfound, Handshake, company career pages, refreshing confirmation emails like they meant something. Most of the time they meant an automated rejection two weeks later, or nothing at all. I kept a spreadsheet. Watching it climb past 100 applications and then past 150 without a single interview response made me question everything about the pivot. My portfolio, my bootcamp, my timing, whether product design was even the right move.
The six interviews I did get felt enormous, partly because they were so rare. I over-prepared for every one. Researching the company's product in detail, practicing design critiques out loud, writing down questions I actually wanted answered. The Braze process was thorough. Hybrid, New York-based, and the internship paid 60,000 USD annualized. None of that was guaranteed to go my way, and I knew it. I treated each round like it was my only shot, because statistically it basically was.
There's no clever hack here. I built a portfolio through a bootcamp, kept applying through a wall of rejection, and stayed consistent when the payoff wasn't visible yet. If you're mid-career-change and the rejections are piling up, this is what the unglamorous middle actually looks like. And it does end.
A friend recommended me. I wouldn't have gotten through the front door otherwise.
I'd been a security engineer at a London fintech for four years and had been thinking about leaving for two of them. The role had a clear ceiling, and there was no room to move sideways into application security, where I wanted to spend more time. I'd also been quietly homesick for Singapore, where I grew up, and had been talking with my partner about whether moving back made sense.
A close friend from university had joined a Singapore fintech as the platform lead the previous year. He'd told me, more than once, that I should apply if a role opened up. I hadn't, mostly because I'd been waiting for a moment when the move felt right. The moment arrived in spring. Two friends in London moved away within the same month and I ran out of reasons to stay.
I told the friend. He passed my CV directly to the security team's hiring manager. The recruiter screen happened the same week.
The process was five rounds across three weeks. It was the most thorough interview process I've ever been through.
Round one was an application security round. Two engineers gave me a real piece of their codebase, a payment authorisation flow, and asked me to identify three security issues and three operational risks. I had ninety minutes. I found two security issues quickly, missed the third, and identified four operational risks. The reviewer told me afterwards that the third security issue was the one they were watching for.
Round two was infrastructure security. Different two engineers, different scenario: a Kubernetes cluster with a specific IAM setup and a question about how a compromised pod would or wouldn't escalate. We talked through it for an hour.
Round three was incident response. They gave me a transcript of a real outage from six months earlier, lightly anonymised, and asked what I'd have done at each decision point. There were two specific moments where I'd have taken a different call. I named them. We talked about whether they were right.
Round four was a leadership round with the head of security. Less technical. Real questions about handling a difficult engineer, a politically sensitive disclosure, and a project where the right answer cost more than the team had budgeted.
The final round was with the CISO. Twenty minutes. He asked what would make me leave the company in two years. I told him.
The offer was US$140,000 base, Singapore comp, paid in USD via a regional entity. I asked for US$148,000, citing the depth of the process and a comparable London role I'd also been talking to. They came back at US$145,000. I accepted, because the package, including the cost-of-living difference and the fact that I'd be near my parents again, was meaningfully better than London.
The friend's referral was the entire reason this happened. I hadn't been able to break into their process when I'd cold-applied two years earlier.
Breaking into product management took me about five months, and the choice that mattered most was picking focus over a scattergun approach. Instead of applying to every PM opening I could find, I narrowed my search to the education sector, an industry I already had real experience in. That context paid off more than I'd guessed. When interviewers asked why a feature should exist or how to prioritize a roadmap, I could answer with actual conviction instead of inventing hypotheticals on the spot.
The portfolio came together almost in parallel with the applications. I started publishing product case studies online, working through real problems in edtech products I used or admired, writing out my thinking on user research, prioritization frameworks, and trade-offs. It was painstaking to put together, but it gave me something concrete to point to in conversations. Recruiters and hiring managers could read my reasoning before we even got on a call, which filtered me into serious conversations faster. Beyond the case studies, I leaned hard on LinkedIn, not just to apply but to genuinely network. I reached out to PMs already working in education and asked for feedback on my case studies and honest takes on what they looked for in junior candidates. Those conversations shaped how I interviewed more than any prep course did, and a few of those connections eventually became the direct referrals that opened the right doors. Nearly all of my meaningful opportunities came through networking rather than cold applications.
The 150 days felt long while I was living them. Twenty interviews across multiple companies in Bangalore meant a lot of repetition, a lot of rejection, and a few weeks where I genuinely questioned whether the transition was realistic. But by the end I had more than three offers to weigh, and I accepted one that felt right both on role scope and the hybrid setup. The salary came in around 18,000 USD a year, which for an Associate PM position felt like a fair starting point. Staying in an industry I already understood, and making my thinking visible in public, turned out to be a faster way in than starting from zero.
I'd been keeping a loose eye on the market for a few months when a friend who works at an Austin SaaS company mentioned my name to their VP of Marketing. No cold application, no evening spent tailoring a cover letter. The conversation just happened after I said over lunch that I was ready for something new. The VP reached out within a few days, and from that first email the process felt different from the automated-rejection cycle I was running in parallel across 27 other applications. Only one of those 27 led anywhere. This was it.
The process ran four rounds over about seven weeks. The first was a straightforward hiring manager screen: role expectations, my background, how I think about positioning and messaging. The second was a peer panel with two senior PMMs and someone from demand gen, and it was collaborative rather than interrogative. They wanted to know how I'd work alongside them, not just whether I could answer framework questions. The third round was the one that mattered most. A twelve-minute exec presentation on a competitor teardown of my choosing. I picked a company I'd already been watching out of pure curiosity, with a running doc of notes on their messaging shifts, pricing page changes, and launch cadences. I didn't dress it up. I walked through it the way I would if I were briefing an internal team before a launch, with a clear point of view and a recommendation at the end. That framing worked. The final round was a closer conversation with the CEO, more about culture fit and long-term ambition than anything technical.
The verbal offer came in at $100,000. When the recruiter used the word "flexible" in the same sentence as the number, I took it as an opening rather than courtesy and asked for $108,000, walking through my reasoning. They came back the next day and confirmed it. Accepted without hesitation.
I'd been at Microsoft until a couple of months before I started looking seriously. There was the return-to-office mandate, work that didn't interest me, leadership I'd lost faith in, and on-call rotations that were starting to affect my health. Eventually it all added up to a clear decision to leave. I didn't rush into applying everywhere, though. I spent two weeks getting my LeetCode back up first, focusing on the patterns that reliably come up at the top companies: dynamic programming, graph traversal, system design. It's not enjoyable, but I'd done it before and knew what to expect.
I only applied to a handful of companies, all through their career sites. Google was one of them. I applied directly through the website and heard back quicker than I thought I would. To my surprise, they skipped the phone screen and put me straight into a virtual onsite. Five interviews in one long day: coding rounds, system design, and a behavioral one. The interviewers were sharp and the questions were hard. I felt okay about most of it but left unsure, which is pretty much how everyone feels after a Google loop. Forty-two days after I applied, the offer showed up: over $360,000 in total comp for the first year, a hybrid role out of Seattle.
And I turned it down. It wasn't that anything was wrong with it; it was a serious number and I respected it. But I had other offers that came out ahead once I actually ran the math, and honestly, I'd stopped seeing Google as the automatic top pick it used to be. The pay isn't the industry leader anymore, the path for internal growth felt less clear than it did five years ago, and at least one other company offered better benefits and a team I'd clicked with during the process.
Saying no to a $360k Google offer still feels strange to write down, let alone to have done. But I'd left Microsoft because the environment was wrong for me, and taking a big-name logo over a better fit would've just been the same mistake again. Where I actually spend my days matters more than the brand on my badge.
Forty cold emails. Eight replies. Three real interview loops. One offer the same week as the final round. The numbers are clean because I tracked them on a spreadsheet from email one.
I was a recent graduate looking for my first sales role. No commercial experience, a degree that had nothing to do with sales, and a private suspicion that I'd be bad at the job for at least the first six months. I'd tried the job-board route for two weeks and gotten exactly one rejection back.
The pivot was almost embarrassingly simple. I made a list of forty SaaS companies in Austin I'd seen hiring SDRs in the previous month. I wrote one cold email template, three sentences, asking for a fifteen-minute intro chat about the role, not asking for a job. The first sentence I rewrote for each company specifically. I sent the forty emails over four days.
The first reply came back that afternoon. Eight people replied in total. Three of those turned into real interview loops. One was an Austin SaaS company.
Their process was the fastest. The intro chat was thirty minutes with the SDR manager. He'd read my email, my LinkedIn, and the one Notion page I'd linked, a writeup of an outreach experiment I'd run for a friend's startup as a favour. We mostly talked about that experiment. He asked what had worked, what hadn't, and what I'd do differently next time.
The second interview was a forty-five-minute role-play with the VP of sales. The scenario: thirty seconds to introduce myself on a cold call, ninety seconds to handle the first objection. We did three different versions. I bombed the first one. The second was OK. The third was actually good. He said he liked that I'd tried different openings rather than reusing the same one.
There was a third "interview" the same day with a senior SDR, less an interview than a conversation about the hours, the comp structure, and what the team was like at 7 PM on a Thursday. I asked direct questions and got direct answers.
The offer was US$58,000 base plus uncapped commission with a realistic OTE of US$80,000 in the first year. I asked specifically about the ramp and whether the OTE was based on a tenured rep or a first-year rep. They were honest: first-year reps usually hit about 80% of OTE, which would put me around US$64,000 all-in. I asked for a US$2,000 sign-on bonus and a slightly higher base. They came back with US$62,000 base and the sign-on. Realistic year-one comp: around US$78,000.
The lesson: the lowest-effort tactic worked. Forty cold emails took maybe four hours to write and send. Most got no reply. Eight was enough.
With no professional design experience and a bootcamp portfolio only a few months old, I decided to skip job boards entirely. Applying through the standard channels would just bury me under hundreds of more experienced candidates, so I went straight to cold outreach instead. I spent a couple of weeks researching Barcelona tech companies, reading their press coverage, scrolling through their product pages, and taking notes on what each one was actually building. I wanted every email I sent to read like it came from someone who genuinely cared about their work, not someone firing off a template at three in the morning.
I wrote to about 20 companies. Each email was genuinely personalised. I referenced something specific the company had been in the press for recently, mentioned what caught my attention about their product or design decisions, and linked to my bootcamp portfolio with a short note on a project I thought was relevant to what they were doing. Writing those emails took real time. Some I rewrote three or four times before I felt confident enough to hit send. I kept a simple spreadsheet to track who I'd contacted, when, and what I'd said, mostly to keep from going in circles, but it also helped me refine my approach as I went.
Twenty emails turned into two replies and two interviews. The first was with a founder, more of a broad conversation about the company's direction and how I thought about design problems. The second was with a senior UX designer who wanted to dig into my actual process and how I handled feedback. Both felt like real conversations rather than formal screenings, which I think came partly from how I'd framed the initial outreach. One of those two interviews led to an offer: a full-time hybrid role at Inqbarna in Barcelona at 28,000 EUR. I accepted without hesitation. Quality of outreach beat quantity by a mile, and those weeks of careful research turned out to be the most important part of the whole process.
Five years without a single interview will leave you rusty, and I knew passive review wouldn't fix that. So before I applied anywhere, I built a structured plan. I enrolled in an interview prep course, scheduled dozens of mock interviews with engineers I found through various platforms, and put serious time into system design. Not just reading about it. I whiteboarded distributed systems from scratch and stress-tested my explanations out loud. It took about two months before I felt like I was operating at the level the top-tier companies expect. Even then I wasn't sure it'd be enough.
I sourced interviews every way I could. I leaned on former colleagues for referrals, woke up dormant LinkedIn connections, answered inbound recruiter messages, and used a few lesser-known platforms that connect engineers straight with hiring teams. The goal was volume, because volume gives you leverage and calibration both. The first few onsites were rough. Not failures, but I could feel the gap between my prep and how I actually performed under pressure. By the fifth or sixth loop I started to settle. By the tenth I knew exactly how to pace a coding round, when to talk through my reasoning versus just write code, and how to structure a system-design answer so the interviewer could follow without getting lost. The whole thing became almost clinical.
I ended up with 7 offers out of 16 onsites, which still surprises me when I say it out loud. The spread of companies, comp packages, and team cultures gave me a clear picture of what I wanted. I accepted Airtable: full-time, hybrid, at $185,000. The role, the team's technical depth, and the product direction all lined up in a way the others didn't quite match. If you're coming back to the market after a long gap, here's what I'd tell you. Preparation compounds harder than you'd think, and mock interviews under realistic pressure are worth far more than another week of grinding problems alone.
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.
A recruiter from a specialist HR firm reached out to me directly. I hadn't applied anywhere near Intercom on my own. I was passively open to moves but hadn't started a formal search, so the timing caught me off guard. I'd submitted around six applications in total over the previous few weeks, mostly exploratory, but this one came inbound and felt more serious than the rest right away. The brief was specific: Intercom was scaling its engineering organisation from 200 to 400 people within 18 months and needed an HR Business Partner who could own that function end to end, not just support it from the sidelines.
The process ran across four interview rounds over 33 days, which felt considered rather than drawn out. First was a screen with the recruiter, mostly about my background partnering with technical organisations and my appetite for high-growth environments. Then I spoke with the CPO, who wanted to understand how I thought about people strategy at scale: levelling frameworks, internal mobility, manager capability building. The third round was with the Engineering VP, the hiring manager, and it got more operational. How I'd structure my first 90 days, how I'd approach a reorg, how I'd handle a situation where engineering leadership and HR priorities didn't align. I came prepared with examples for all of it.
The panel round with two senior engineers was the one that set me apart, I think. They didn't ask hypotheticals. They walked me through an actual disagreement they were having about a performance review for someone on their team and asked me to coach them through it live. That kind of session either lands or it doesn't. I stayed neutral, asked questions that helped them surface what they actually disagreed about, and got them to a shared framing before the hour was up. It felt real because it was real.
The offer came in at 72,000 EUR for a full-time hybrid role based in Dublin. I negotiated a four-day working week at the same salary before signing, which they agreed to. I accepted.
6Applications
4Interviews
5 weeksSearch length
RecruiterSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.