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.
55Stories
8Verified offers
15Countries
16 / 38Median / Mean applications
Latest job wins
55 stories · page 3 of 6
Filtered by newest stories across all roles and locations.
Changing careers from software sales into product design was brutal by the numbers: 14 months, more than 200 applications, 205 rejections, 6 interviews, and one offer: a product design internship at Braze in New York.
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 the odds said it nearly was.
I had been a security engineer at a London fintech for four years, and I had been thinking about leaving for two of them. The role had a clear ceiling, and there was no way to move sideways into application security, where I wanted to spend more time. I was also homesick for Singapore, where I grew up, and my partner and I had been talking about whether moving back made sense.
A close friend from university had joined a Singapore fintech as the platform lead the year before. He had told me more than once that I should apply if a role opened. I did not, mostly because I was waiting for the moment when the move felt right. That moment came in spring. Two friends in London moved away in the same month, and I ran out of reasons to stay.
I told my friend. He passed my CV directly to the hiring manager of the security team. The recruiter call happened the same week.
The process was five rounds across three weeks.
Round one was about application security. Two engineers gave me a real piece of their codebase, a payment authorisation flow, and asked me to find three security problems and three operational risks. I had ninety minutes. I found two security problems quickly, missed the third, and found four operational risks. Afterwards the reviewer told me that the third security problem was the one they were watching for.
Round two was about infrastructure security. Two different engineers, a different scenario: a Kubernetes cluster with a specific IAM setup, and a question about whether a compromised pod could escalate. We talked about it for an hour.
Round three was incident response. They gave me the transcript of a real outage from six months before, lightly anonymised, and asked what I would have done at each decision point. There were two moments where I would have decided differently. I said so. We talked about whether I was right.
Round four was a leadership round with the head of security. Less technical. Real questions about managing a difficult engineer, about a politically sensitive disclosure, and about a project where the right answer cost more than the team had budgeted.
The last 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, a Singapore package, paid in USD through a regional entity. I asked for US$148,000 and explained the depth of the process and a comparable London role I was also talking to. They came back at US$145,000. I said yes, because with the difference in cost of living, and with my parents nearby again, the package was clearly better than London.
Two years earlier I had cold-applied to the same company and never got into their process.
I had been working as a backend engineer in India for a few years, and I felt I had reached a limit in the kind of work I was seeing. I wanted to work in a different market, with different engineering problems, and to learn more than I already knew. So I looked for international roles instead of only reading the usual local listings. I found a job platform focused on relocation, which filters for companies that sponsor visas and pay for the move, and I spent a few evenings each week going through the listings methodically. That is how I found Mercari in Tokyo. I had been following the company for some time. They were doing interesting things at scale, and the backend opening looked like a good fit. I applied through the platform and heard nothing for about ten days, and I was sure the application was dead.
When they answered, the process had four structured rounds over about two months. The first was a live coding session where I shared my screen and solved problems in real time, the kind of session where your reasoning matters as much as the final answer. The second was a deep technical interview with an engineer, about architecture decisions and about how I think through microservices: trade-offs, failure modes, how I would scale a specific system under load. That one I enjoyed most. It felt like a real conversation between engineers. The third was a mixed technical and behavioural round with a hiring manager, mostly about how I work inside a team and how I handle uncertainty. The last round was with a VP and was mostly behavioural, but it also covered how quickly I could become productive in an unfamiliar tech stack. That was a fair question, because I was joining from a different market.
My first interview was at the beginning of December and the offer arrived in February. I accepted the full-time, on-site role at 55,000 USD and started to prepare for the move to Japan.
I had wanted to write for a Madrid magazine since I moved to the city four years before. They were a serious publication, long-form, properly edited, careful with facts, and they paid their writers, which is rare. I read every issue I could find for a year before I did anything about it.
When I started looking for a job, it did not go well. I sent thirty applications in three months, mostly for content roles at SaaS companies that wanted "blog posts" and not journalism. I got two interviews. One of them was the most depressing forty-five minutes of the whole search. A content marketing manager told me directly that the job was producing SEO content with an LLM, and that the human writer was there to "make it sound better".
That night I went home and decided to stop applying for content jobs. Instead I would write the kind of article I wanted to be paid for.
I chose two ideas that I thought the magazine would really publish. One was about a small Madrid neighbourhood that remote workers had slowly changed. The other was an interview with a local food cooperative. I wrote a pitch of three paragraphs for each one and emailed them to the editor.
She answered about one of them, the neighbourhood article. She liked the idea, she had been thinking about other pitches on the same subject, and she offered me a 1,500-word draft on spec. The fee was €200, paid within thirty days after publication.
I wrote it. It took ten days. The editing was thorough. She disagreed with three sections and I rewrote them. The article was published in the May issue.
In late May, two months after we agreed the freelance article, the editor emailed me. They had opened a permanent staff writer position and she wanted to talk to me before they published it. The shortlist was already her, the editor-in-chief and the publisher. The "interview" was a conversation of forty minutes about the work I wanted to do, what I was reading, and one article in the magazine that I would have edited differently.
The "test" was a 600-word article on a subject she gave me the next day. I had two days. I wrote eight hundred words, cut one hundred and fifty, and sent it. They sent the offer two days later.
The offer was €26,000 base, which is a normal staff writer salary in Spain and is acceptable. I asked for €30,000. I explained the freelance work I had already done for them, and that the role included running their newsletter. They came back at €28,000 and a small monthly payment for travel for assignments. I took it.
I was not looking for a job when I found Picnic. They appeared in a long article about startups working on food waste in Europe, and the mission interested me immediately. The article explained how their model reduces the surplus and the spoilage that cost traditional supermarkets so much. The details are what convinced me: a concrete operational problem with measurable impact. I stopped and read the whole article. No recruiter message had ever made me feel like that, so the same evening I went to their careers page and applied for a senior software engineer role.
The process was thorough and well organised. Five interview rounds sounds like many, but Picnic clearly knew what each stage was for. There was a technical screen early, about systems design, which I liked because it went directly to the substance instead of spending an hour on trivia. The later rounds included the engineers I would work with, and the conversations felt honest. People told me about real trade-offs they had made and real mistakes they had learned from. The thing I remember most is that they promised to go from application to offer in four weeks. They did it.
The offer was 70,000 EUR for a full-time job in Amsterdam, on site. Moving to the Netherlands was a big decision, but when the offer arrived I had already imagined myself there. I took the offer.
After two years of teaching myself, freelancing, and blogging while raising my family, I felt ready to apply for a full-time role. There were months where I wondered if I was cut out for this, weeks where the kids were sick and I barely opened my laptop, and more than a few projects I dropped halfway through once I realised I'd gone about them the wrong way. But every misstep taught me something, and my portfolio started to look like the work of someone who knew what they were doing.
When I finally started applying, I was selective about it. I sent four applications in total: one straight to a company whose product I used and admired, and three through a job board via a recruitment agency. I put real time into each one: tailoring the cover letter, making sure the portfolio was clean and loaded quickly, and double-checking that the code I linked to was something I was proud of. Two of those four came back with interview invitations. The first one moved fast, and within a couple of weeks I had an offer: a fully remote frontend developer role based in the UK, paying £30,000 a year. I accepted without much hesitation.
The interview felt manageable because I'd been preparing for two years. I'd talked about my work at meetups and conferences, written up my thinking on my blog, and taken on freelance clients who asked hard questions. So by the time I sat down with the hiring team, explaining my decisions and walking through my code felt natural.
Breaking into product management took me about five months, and focus was the choice that mattered most. I stopped applying to every PM opening I could find and narrowed my search to the education sector, where I already had real experience. That context paid off more than I had guessed. When interviewers asked why a feature should exist, or how to prioritise a roadmap, I could answer from experience instead of inventing examples on the spot.
The portfolio came together at the same time as the applications. I started publishing product case studies online, working through real problems in edtech products I used or admired, and writing out my thinking on user research, prioritisation frameworks and trade-offs. It was slow work, 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 got me into serious conversations faster. I also used LinkedIn a lot, for networking as much as for applying. I got in touch with PMs already working in education and asked them for feedback on my case studies, and for honest opinions on what they wanted from junior candidates. Those conversations shaped how I interviewed more than any preparation course did, and a few of those connections became the referrals that opened the right doors. Almost every real opportunity I got came through people rather than through cold applications.
The 150 days felt long while I was living them. Twenty interviews across several companies in Bangalore meant a lot of repetition, a lot of rejection, and a few weeks when I asked myself whether the move was realistic. But by the end I had more than three offers to weigh, and I took the one that felt right on both the scope of the role and the hybrid arrangement. The CTC came to around US$18,000 a year, which for an Associate PM position felt like a fair starting point.
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.
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 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.
I'd left Microsoft because the environment was wrong for me. Taking the Google offer would have been the same mistake.
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 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 a SaaS company in the healthcare niche.
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 favor. 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 $58,000 base plus uncapped commission with a realistic OTE of $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 $64,000 all-in. I asked for a $2,000 sign-on bonus and a slightly higher base. They came back with $62,000 base and the sign-on. Realistic year-one comp: around $78,000.
Forty cold emails took four hours to write and send. Most got no reply.
40Applications
3Interviews
4 weeksSearch length
Cold outreachSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.