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 2 of 6
Filtered by newest stories across all roles and locations.
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.
Finding a Singapore-based Engineering Manager role took me about 14 weeks from first application to signed offer, and it was more of a grind than I'd anticipated. I sent out 38 applications in total, leaning heavily on job boards and company career pages in the early weeks, but the responses were inconsistent and the timelines stretched long. Singapore's market for EM roles felt tighter than I'd expected. Most postings drew strong local and regional candidates, and as someone considering relocation, I had to work harder to stand out. After a few weeks of slow traction, I shifted my energy toward in-person networking. That was the move that actually mattered.
The break came when I attended a regional leadership offsite where the CTO of a Singapore engineering scale-up was a keynote speaker. His talk was about scaling engineering organizations across Southeast Asia, exactly the problem space I'd been thinking about, so the conversation afterward felt natural rather than forced. I didn't pitch myself that day. Instead I waited two weeks, then followed up with a short document outlining what I'd genuinely want to learn about their org structure, their current team challenges, and how they thought about EM scope at their stage of growth. That document seemed to signal intent without being pushy, and it got me into the process. Nine rounds followed over several weeks: technical conversations, a take-home exercise focused on org design, a values interview with the founder that went deeper than I'd expected, and a few stakeholder calls with senior engineers I'd potentially be managing.
The final package came in at $165,000 USD. The base was honestly a bit below what comparable US-market EM roles were offering at the time, but the company included expat health insurance and covered SG relocation costs, which made the overall picture work. After 102 days and 9 interview rounds, I accepted. The process was long, but the networking-first pivot was what got me in the door.
An Instagram DM became a freelance project, and the freelance project became a full-time role three months later. I wouldn't have predicted any of those steps.
I'd been working as a freelance brand designer in Buenos Aires for two years. The work was inconsistent. Some months were fine. Some weren't. I'd been thinking about going back to a studio environment for the routine and the team, but most of the studios I wanted to work at were either based in São Paulo or paying in pesos at rates I couldn't make work.
One Buenos Aires design studio was different. They were small, six people, and they paid in USD via Deel because most of their clients were US-based. They had a public Instagram where they posted their work for a specific recurring client, a US-based health tech company. I'd been following them for about a year.
I had a thought. What if the studio would be open to a small spec project? I picked their main public client and rebuilt three concept variations of how I'd reposition the brand. I was honest with myself about it: this was speculative, the studio almost certainly hadn't asked for my opinion, and I was just going to send it as a portfolio piece, not a job application.
I DMed the founder. The message was three sentences. I'd been following the work, I'd built three variations of how I'd approach a brand refresh for the public client, did she have ten minutes to look at it? I attached a single Figma link.
She replied two hours later. The variations weren't what they were going to ship, she was direct about that, but they were the kind of work she wanted to be commissioning, and was I available for a one-off project they'd been needing to outsource? I was.
The project was a brand refresh for a different client. Three weeks of work. Five-figure fee, paid in USD. I shipped it on time. The client signed off without revisions, which is rare.
A month later the founder asked if I was open to a longer engagement. We agreed on a three-month rolling contract. After two months she asked if I'd consider going full-time. The role was permanent, paid in USD via Deel, and would mean working with the studio's existing six-person team rather than continuing as a contractor.
The offer was US$30,000 base. A number that doesn't look like much in dollar terms but works at the current exchange rate and is meaningfully better than what I'd have made independently. I asked for US$36,000, citing the depth of the work I'd already shipped and the cost of switching from contractor to employee structure. They came back at US$36,000.
I accepted. I'd sent two real applications during the entire search. Both went to job boards and both went unanswered. The Instagram DM was the application. I keep telling other designers that the studios you actually want to work at hire from their DMs, not from their job listings. They mostly don't believe me until they try it.
My move to Amazon's London office didn't start with a job application. It started with someone noticing my work. I hadn't been searching or refreshing job boards. I was heads-down, shipping features and trying to do the work well. Then a manager who'd seen what I built reached out directly and invited me to explore an SDE II transfer to London. That was when it hit me that the opportunity was real and I needed to take it seriously.
Once I committed, I spent a couple of weeks preparing before the three interview rounds began. I knew Amazon's loop would lean heavily on behavioural questions tied to the leadership principles, so I didn't build a wide, shallow bank of stories. Instead I picked a small set of genuinely strong examples from my recent work and mapped each one carefully to the principles I expected most: Bias for Action, Ownership, Deliver Results. My thinking was that a few deeply rehearsed stories, told with real specificity and confidence, would land better than improvising something new under pressure every time. I made sure I could walk through each example with a tight structure: the situation, what I decided, why I decided it, and what actually shipped or changed as a result.
Across the three rounds I reused those same core stories on purpose, tweaking the framing depending on what the interviewer was probing for. It felt almost too simple. But it worked. All three interviewers voted to hire, and I got the SDE II offer for the London role at £78,000. The on-site requirement was something I'd already factored in and was fine with.
The lesson I keep coming back to is that visible, high-quality work is its own kind of networking. I didn't send a single cold message or touch my profile. The opportunity came to me because of what I'd already shipped. That's worth more than most job-search tactics I've read about.
The recruiter ping came on a Thursday afternoon. By Tuesday I was on a call with the founders.
I'd been at my previous company for four years. I wasn't actively looking. My LinkedIn was up to date because that's just hygiene. About a hundred recruiter messages a year hit my inbox. Ninety-five I ignored, four got a polite "not right now", one sometimes turned into a real conversation.
This one was different. The opening message was four sentences. It named the company, the team, the specific PM problem they were trying to solve, and a line about why my background looked like a fit. No platitudes, no asking for a phone number, no asking me to update my résumé. The link went to a brief written description of the role and a salary band wide enough to include where I actually was.
I replied that day, asking for fifteen minutes to talk about scope. The recruiter was prompt and direct. The job was Senior PM on a payments-adjacent product at a Series B scale-up. Reporting to the head of product. Real ownership of a roadmap. The company had funding through 2027 in the bank.
The first interview was with the founder, on a Friday. He was the most prepared interviewer I've ever spoken to. He'd read my CV, looked up two of the projects on my profile, and read a blog post I'd written four years earlier. The questions were specific. By the end of the call I had a clear sense of what the role was, what the next quarter looked like, what the next year looked like, and what success at the six-month mark would look like.
The next round was a portfolio review with the head of product and one of the senior engineers. I walked through three projects. They cared less about the outcome and more about how I'd made the calls along the way: which trade-offs I'd flagged early, which I'd missed, what I'd done when a forecast was wrong.
The big round was the strategy doc. They handed me a three-page brief on a real product area and asked for a six-page response in a week: what I'd prioritise in the first 90 days, what I'd cut, what I'd defer, what I'd want to see in two metrics dashboards on day one. I spent two evenings on it. The six pages became eight, and then I cut it back to six.
The presentation was forty-five minutes with the two founders, the head of product, and a board member. They pushed hard on the first three priorities. The last twenty minutes was them walking through their own version of the brief and asking where mine differed and why.
The offer was $US 118,000 base plus refresh. I asked for the equity refresh up-front and another $10,000 on the base, citing the scope the founder had described. They came back with $128,000 and the refresh I'd asked for. The verbal offer was Friday. The signed papers were Tuesday. I was on the team three weeks later.
Four months. Five applications. One offer. The slowest job search I've ever run, and the one I'm most proud of.
I was a PhD candidate in statistics in Manchester. I'd been working on my thesis for about two years when I decided I needed to find commercial work. Partly because the funding situation had changed, partly because I'd realised, fairly late, that I wanted to leave academia.
I had no commercial experience. I had three published papers, one of which had been cited fifty times in a relatively small sub-field. I'd taught two undergraduate modules. I'd built a small simulation framework in R that nobody other than me used. The CV looked like a CV for a postdoc, not for a junior data scientist.
Cold emailing hadn't worked when I'd tried it for a week. I'd sent twelve emails to data teams in Manchester and London and gotten one polite reply.
The thing that worked was a public dashboard. I'd been wanting to learn dbt and Streamlit. I picked a topic, UK retail footfall, using publicly available data from one of the data trusts, and built a dashboard over six weekends. It wasn't elegant. It worked. I put it on a free Streamlit hosting tier and tweeted about it once.
About two months later the head of analytics at a mid-sized retailer in Manchester found the dashboard via a Google search while researching a specific footfall topic. He didn't contact me through the dashboard. He searched for my name, found my LinkedIn, and sent me a message asking if I was open to a junior data scientist role.
The interview process was three rounds over five weeks.
Round one was a technical screen with two senior analysts. They gave me a piece of their data, a retail transaction dataset, and four questions. I had a week. I sent back a six-page Jupyter notebook with the answers, three caveats, and a writeup. They'd been hoping for code rather than narrative. I gave them both.
Round two was a case study presentation. The brief was to take one of the answers from the take-home and turn it into a fifteen-minute presentation for a non-technical stakeholder. I rebuilt one section from scratch, simplified the visualisations, and presented to a panel of five: three analysts, the head of analytics, one product manager. The questions afterwards were specifically about what I'd cut and why.
Round three was a team chat with three other junior data scientists who'd be my peers. Less of an interview, more of an "is this person tolerable to work with" check.
The offer was £35,000 base, the higher end of the junior band. I asked for £38,000, citing the four months of search, the depth of the process, and a slightly higher quote I'd received from a competing offer. They came back at £38,000.
I accepted. I'd sent five formal applications in total. The one that worked was the one I hadn't really applied to.
I'll be honest about how rough it got: five months of searching, more than 400 applications across Indeed and LinkedIn, and a single interview to show for it. I started out cautiously optimistic. I had customer service experience, I was applying to remote roles that looked like a good fit, and I assumed something would land within a few weeks. It didn't. I kept a spreadsheet to track everything, and watching the row count pass 100, then 200, then 300 with no callbacks wore me down. I started doubting my resume, my cover letters, the whole approach. I rewrote the resume twice. I even applied to roles a step below my experience just to get any response. Still nothing. Some weeks I'd send 30 or 40 applications and hear back from none of them. The silence got exhausting in its own way.
Around the four-and-a-half-month mark, a Customer Service Representative posting on Indeed finally went somewhere. A screening call, then a full interview, the only one in the entire search. I thought it went well, but after months without feedback I honestly couldn't tell anymore. When the offer came in, it was below what I needed for the role to actually work financially. So I countered. I was scared to, because this was my one shot and I didn't want to lose it over a number. I spelled out exactly what I needed: $42,000. I gave my reasoning and sent it. Then they went quiet for what felt like forever, and I was sure I'd overplayed it and blown the only opportunity I'd had in five months.
Then they came back and met my number exactly. I accepted on the spot. I think the counter worked because I was specific and didn't apologize for asking. If you're in a search that feels hopeless right now, take this as a reminder: the numbers can stay ugly right up until the moment they don't. One interview was all it took, even after 400 noes.
Fresh out of a coding bootcamp, I treated the job hunt like a numbers game with a twist. I knew I didn't have a CS degree or years of experience to lean on, so the one edge I could build was making it personal. Instead of dropping resumes into application portals and watching them vanish into black holes, I cold-emailed real engineers and hiring managers at the companies I actually wanted to work at. I spent evenings tracking down contact details on LinkedIn, personal blogs, and GitHub profiles, then writing emails that referenced specific projects or posts so they didn't read like spam. I sent over 150 of those and got a 22% response rate, far better than anything the portals gave me.
Across roughly three months, I reached out to 291 companies total and turned that into 32 phone screens. Some weeks I had five or six calls stacked up, and I kept a spreadsheet tracking where each one stood. The rejection rate was brutal and relentless. Plenty of calls ended with "we're looking for someone more senior" or just went silent after what felt like a good conversation. There were stretches where I wondered whether the bootcamp had been a mistake. But the pipeline stayed full because I kept the outreach volume high even when my confidence wasn't.
The other thing that helped was how I sequenced my onsites. I scheduled interviews at companies I was less excited about first, so I could get the rust off, work through the nerves, and figure out where I was stumbling before walking into the rooms that mattered to me. By the time I interviewed at the company at the top of my list, I had 90 days of reps behind me and it showed. I landed a full-time software engineering role there at $95,000. The big takeaway: a personal email to a human beats a polished application into a void, and ordering your interviews from low-stakes to high-stakes is one of the most underrated edges a junior candidate can build.
I'd been applying selectively, only four applications over those two months, because I didn't want to waste time on roles that weren't actually interesting. Most of my search was quiet and slow, and honestly a little discouraging. Then I came across a Substack post by the CTO of a New York data company about their decision to refactor their entire data pipeline around dbt and Snowflake. The post was technical, specific, and honest about the tradeoffs they'd made. It wasn't marketing. It read like someone who actually lived inside the problem, and I recognized a lot of the same pain points from my previous role.
I spent a couple of evenings on a cold email. I didn't pitch myself generically. I referenced specific paragraphs from the post and linked a public GitHub repo I'd built for stream-to-batch reconciliation. The repo wasn't perfect, but it was real work: documented, tested, and directly relevant to what he'd described. I figured if he was the kind of engineer who wrote that post, he'd at least look at the code. Three days later he replied. No recruiter, no application portal, no automated acknowledgment. Just a direct response asking if I wanted to jump on a call that week.
The process ended up being four rounds over about nine weeks. The first call was conversational, more mutual vetting than a formal screen. The third and fourth rounds brought in the broader data team and covered system design and past-project deep-dives. But the second round was the one that stuck with me. It was framed as a live SQL pairing session, and it started that way, but somewhere around the thirty-minute mark we were both heads-down on an actual production query they were struggling with. We went ninety minutes. I didn't solve it completely, but how I reasoned through it mattered more than any clean answer would have.
The offer came in at $145,000, hybrid in New York. I accepted without hesitation.
The offer from an Austin startup came in on day 51. By then I'd been through five rounds of interviews and 22 applications I was working through at the same time. The process had been thorough: a technical screen, a take-home infrastructure scenario, two panel interviews with the platform engineering team, and a final conversation with the VP of Engineering. I was interested in the hybrid DevOps role. Austin made sense geographically, the team seemed sharp, and $132k base was competitive for where I was in my career.
Then I got to the equity portion of the offer letter. The package included 0.15% over four years with a one-year cliff. Not unusual on its face. But equity is only worth something if you can actually evaluate it. Any time stock is part of a comp conversation, I ask for the most recent 409A valuation and some visibility into dilution history. Not to be difficult. Those two documents tell you almost everything about whether the equity is real or just a number on paper. I sent a professional note to their CFO asking for exactly that before I'd sign anything.
What I got back was a runaround. The first response was vague and pointed me back to the offer letter itself, as if the strike price listed there was enough context. I followed up and asked again, specifically for the 409A and any cap table information they were willing to share. I got a flat refusal. No explanation, just a no. That was it for me. A company that won't share basic financial documentation with someone they're asking to take a four-year equity vesting commitment either has something to hide or a culture of opacity I don't want to be inside of.
I walked away from the offer. When I mentioned it to three engineering friends here in Austin over the following week, none of them were surprised. All three had heard nearly identical stories about the company within the past year. That told me everything about my decision.
22Applications
5Interviews
7 weeksSearch length
RecruiterSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.