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.
56Stories
8Verified offers
15Countries
16 / 44Median / Mean applications
Latest job wins
56 stories · page 3 of 6
Filtered by newest stories across all roles and locations.
I'd been watching a US software company for a few months before I made my move. They were clearly building toward Latin America. Blog posts hinted at regional plans, a couple of Spanish-language social posts felt like they were testing the waters, and the job board listed nothing in the region yet. So rather than wait for a posting that might never come, I spent a weekend writing a one-page pitch aimed straight at their CEO. My argument was that expanding into LATAM without a Spanish-fluent full-stack developer embedded in the timezone was a real execution risk, and that I was the person to close that gap. I kept it tight, specific to their product, and sent it cold on a Tuesday morning.
He replied the same day, and we had a call scheduled within 48 hours. That response time told me the timing had landed. What followed was four rounds of interviews over about a month, in a format unlike anything I'd done before. The founder runs an async-first organization, so there were no synchronous technical interviews at all. Instead I recorded Loom walkthroughs of my approach to two architecture problems and submitted written exercises that had me think through a localization strategy for one of their core features. It was slower and more careful than a typical panel loop, but it suited the way I work. I had room to think things through rather than perform under artificial pressure, and I think that showed in my answers.
The offer came in at USD 65,000 for a full-time, on-site role in Buenos Aires, with quarterly meet-ups in Mexico City. The on-site structure made sense given the regional mandate. Being physically present in BA was the whole point of the pitch. At that salary in Buenos Aires the purchasing power is strong, so while the number isn't the ceiling of the market, the real-world value made it easy to accept. Thirty-one days from first email to signed offer. I accepted the same afternoon I got it.
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.
I'd been working as a backend engineer in India for a few years and felt like I'd hit a ceiling on the kind of exposure I was getting. I wanted to work in a different market, take on genuinely different engineering problems, and push myself past what I already knew. So I started targeting international roles specifically instead of just scrolling the usual local listings. I found a relocation-focused job platform that filtered for companies willing to sponsor and relocate candidates, and I spent a few evenings a week working through listings methodically. That's how Mercari in Tokyo showed up. I'd been following the company for a while. They were doing interesting things at scale, and the backend opening looked like a real fit. I applied through the platform and heard nothing for about ten days, which had me convinced it had gone nowhere.
When they did come back, the process ran in four structured rounds over roughly two months. The first was a live coding screen where I shared my screen and worked through problems in real time, the kind of session where your thought process counts as much as the final answer. The second was a deep technical interview with an engineer, focused on architecture decisions and how I reason about microservices: trade-offs, failure modes, how I'd scale a specific system under load. That one I enjoyed most. It felt like a real conversation between engineers, not a test. The third was a mixed technical and behavioural round with a hiring manager, leaning toward how I'd work within a team and handle ambiguity. The last round was with a VP and was mostly behavioural, though it also dug into how quickly I could get productive in an unfamiliar tech stack. Fair concern, given I'd be joining from a different market entirely.
My first interview was in early December and the offer came through in February. I accepted the full-time, on-site role at 55,000 USD and started getting ready for the actual move to Japan. It was the outcome I'd been working toward for a while, and as demanding as the process was, it felt worth it.
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.
The freelance piece I pitched in March became a full-time role in June. The thing that made it work was that I never asked them for a job.
I'd wanted to write for a Madrid magazine since I moved to the city four years earlier. They were a serious publication, long-form, edited, careful about facts, and they paid their writers, which is increasingly rare. I'd read every issue I could find for a year before I tried to do anything about it.
When I started job-hunting, it didn't go well. I sent thirty applications across three months, mostly to content roles at SaaS companies that wanted "blog posts" rather than journalism. I got two interviews, one of which was the most depressing forty-five minutes of the search. A content marketing manager told me, plainly, that the role was generating SEO content with the help of an LLM and that the human writer was there to "make it sound better".
I went home that night and decided to stop applying for content jobs and just write the kind of piece I wanted to be paid to write.
I picked two ideas I thought the magazine would actually publish. One was about a small Madrid neighbourhood that had been gradually transformed by remote workers. The other was an interview with a local food cooperative. I wrote three-paragraph pitches for each and emailed them to the editor.
She replied to one. The neighbourhood piece. She liked the angle, she'd been considering pitches on the same beat, and she was willing to commission a 1,500-word draft on spec. The fee was €200, paid within thirty days of publication.
I wrote it. Took ten days. The edit was thorough, she pushed back on three sections and I rewrote them. The piece ran in the May issue.
In late May, two months after the freelance piece had been agreed, the editor emailed me. They'd opened a permanent staff writer role and she wanted to talk before posting it. The shortlist was already her, the editor-in-chief and the publisher. The "interview" was a forty-minute conversation about the work I wanted to do, what I was reading, and one piece in the magazine I'd have edited differently.
The "test" was a 600-word writeup on a topic she gave me the next day. I had two days. I wrote eight hundred words, cut a hundred and fifty, sent it. They sent the offer two days later.
The offer was €26,000 base, which is staff-writer money in Spain and is fine. I asked for €30,000, citing the freelance work I'd already done for them and the fact that I'd be running their newsletter as part of the role. They came back at €28,000 plus a small monthly stipend for assignment travel. I accepted.
What worked: writing the kind of piece I wanted them to pay me for, before they were paying me. The freelance work was the interview. The actual interview was a formality.
I wasn't actively job-hunting when I came across Picnic. They turned up in a long-form article about startups going after food waste in Europe, and the mission grabbed me right away. The piece laid out how their model was cutting down on the surplus and spoilage that drag on traditional supermarkets. It was the specificity that got me. Not "sustainability" in some vague hand-wavy way, but a concrete operational problem with measurable impact. I stopped scrolling and read the whole thing. No recruiter had ever sent me anything that made me feel that way, so I went straight to their careers page that same evening and applied for a senior software engineer role through the site.
The process was thorough and well-run. Five interview rounds sounds like a lot on paper, but Picnic had clearly thought about what each stage was meant to test. There was a technical screen early on focused on systems design, which I liked because it got straight to the substance instead of burning an hour on trivia. The later rounds brought in engineers I'd actually be working with, and the conversations felt honest rather than performative. People told me about real tradeoffs they'd made and real mistakes they'd learned from. What stuck with me most was their stated promise to move from application to offer within four weeks. They kept it. That sounds like a small thing until you've spent months in a process that drags on with no communication and no respect for your time.
The offer came in at 70,000 EUR for a full-time, on-site role in Amsterdam, and I accepted without much back and forth. Relocating to the Netherlands was a big call, but by the time the offer landed I'd already pictured myself there. The whole thing reminded me of something I'd half-forgotten after years of passively scrolling job boards. Caring about what a company actually does is a remarkably efficient filter. It points you somewhere worth going.
After two years of teaching myself, freelancing, and blogging while raising my family, I finally felt ready to apply for a full-time role. Those two years weren't a straight line. 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 realized I'd gone about them the wrong way. But every misstep taught me something, and bit by bit my portfolio started to look like the work of someone who actually knew what they were doing.
When I finally started applying, I was selective about it. I sent four applications total: one straight to a company whose product I used and admired, and three through a job board via a recruitment agency. I wasn't firing off applications blindly. 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, in a way, I'd been preparing for it 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 instead of terrifying. When I tell people it only took four applications, they assume I got lucky. I didn't. The real work happened long before I sent a single application, and that's what turned two responses into one offer.
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.
—Applications
5Interviews
6 weeksSearch length
Company siteSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.