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.
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.
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.
I'd been working in QA for three years, splitting my time between manual testing and building out automation suites, mostly in Selenium and then Playwright once that became our team's preferred tool. When I decided to move, I wanted something fully remote and ideally a step up in responsibility. I set a rough target of around 25 roles and spent about two weeks working through listings on Indeed and LinkedIn Jobs, filtering hard for remote positions in the UK. Some ads were clearly outdated or vague about the actual stack, so I skipped those and focused on companies where the listing gave me enough detail to write a genuinely tailored cover letter. By the end I'd sent out 24 applications and was bracing for the usual silence.
The Manchester software company that hired me was different from the start. They replied within 48 hours, which honestly caught me off guard. I'd already half-forgotten applying. Instead of a recruiter call, their first reply came with a take-home task attached. They sent over a Figma file of a checkout flow and a staging URL, and asked me to write structured test cases covering the key scenarios, then build a small Playwright suite to automate the critical path. It was a realistic, well-scoped brief, not one of those tasks that quietly expands into eight hours of work. I spent an evening on the test cases, thinking through edge cases like empty cart states and failed payment responses, then wrote the Playwright scripts the next morning. I kept the structure clean and added a short README explaining my decisions.
Two video calls followed. The first was technical. A senior engineer walked through my submission with me, asked why I'd prioritised certain scenarios, and we talked through how I'd scale the suite as the product grew. The second was a team-fit conversation with the engineering lead, much more relaxed, focused on how I collaborate with developers and product when bugs surface late in a sprint. At the end of that second call they offered me the role: QA Engineer, fully remote, £38,000. I accepted without hesitation. Start to offer was nineteen days, which felt almost unrealistically fast after some of the drawn-out processes I'd heard about from friends.
By the end of June I'd been job-hunting for three months. The numbers weren't great. I'd sent 64 applications through job boards and LinkedIn Easy Apply, and I'd heard back from three. Two rejected me at the résumé stage. The third moved me to a recruiter screen and then went silent for six weeks.
I was a backend engineer at a small fintech, but the team had shrunk twice in the previous year and I'd stopped learning anything new. The plan was to land somewhere serious about payments specifically. The problem was that every application I sent looked like every other one sitting in the same inbox. My CV was the same CV everyone else had. My cover letters were rephrased versions of the JD.
The breakthrough wasn't a tactic. It was a person. A friend I'd worked with two companies ago had joined GoCardless eight months earlier on the payments team. We had drinks. I described what I was after, somewhere serious about payments infrastructure, not too big, with engineers who weren't allergic to writing about how the system worked. He asked a few questions about my recent work on idempotency keys and then said he could pass my CV straight to the hiring manager.
The recruiter call landed two days later. Thirty minutes, mostly logistics: salary range, notice period, why I was looking. She'd read my friend's note, and the questions felt aimed at me specifically rather than at a stack of similar candidates.
The technical loop ran across two weeks. Two coding interviews, one a production-style task on their toy ledger, one a more standard data-structures hour. A system design round where I walked through a webhook delivery system with retries, signing and ordering guarantees. That round went well partly because I'd built something similar before and partly because I'd actually thought about the problem before the interview rather than during it.
The final round was a forty-five minute conversation with the engineering director. It wasn't really an interview. He wanted to know what I wanted to be doing in two years, what I'd push back on if I disagreed with a technical call, and how I'd handled the worst on-call rotation of my career.
The offer arrived a week later: £67,000. Fair, but a few percent below where I'd pinned my expectations. I asked, in writing, whether there was room to move on the base, walking through the responsibilities of the role and a competing late-stage conversation. They came back forty-eight hours later at £72,000. I accepted the next morning.
Two things I'd do differently if I started over. First, I'd have started the conversation with my friend three months earlier, not three months in. Second, I'd have written about my work publicly long before I needed to. The few public references the recruiter found of mine were closed-source and helped less than the conversations did.
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.
The recruiter call came out of nowhere. The reason it came out of nowhere was that I'd answered a customer's question on Highbeam's community forum eighteen months earlier and had completely forgotten about it.
I'd been a solutions engineer at a mid-sized software company in Toronto for four years. Happy enough, but I'd been keeping an eye on roles at companies whose products I actually used. Highbeam was on that list. I'd been a power user for two years and had spent enough time in their community forum to know who the active people were.
The forum answer was about how to integrate Highbeam with a specific data warehouse setup. There was no good answer in their docs. I'd built a workaround for my own team and posted a writeup with code samples. About twenty people upvoted it. One person emailed me afterwards to say thanks. Then I forgot about it.
A year and a half later, a recruiter at Highbeam reached out. She'd been searching the forum for active community members who might fit a solutions engineer opening, found my writeup, and looked up my LinkedIn. The opening message was specific. She named the writeup, the role, and the salary band. She didn't ask for a CV in the first message. That came in the second.
The first call was forty-five minutes with the recruiter. She'd read my LinkedIn and knew what I'd been doing at my current company. The salary band she'd quoted was meaningfully better than what I was on, and that's the part that got me to take the second call.
Round two was a technical chat with the SE manager. Sixty minutes. We talked through how I'd handle three real customer scenarios. It was a genuinely useful conversation, the kind where I learned something about their product I hadn't known.
Round three was a customer demo. I had a week to prepare. The brief: imagine the customer is a fintech evaluating Highbeam against two competitors, you've got thirty minutes, walk us through a demo that addresses their specific concerns, detailed in this brief. I built a real demo on their free tier with a synthetic dataset. It ran forty minutes including questions. Two of the four people on the panel said it was the best demo they'd seen in the role's interview process.
Round four was a "tell me about your worst customer" round with two senior SEs. I had a real story.
Round five was the head of customer success. Thirty minutes, mostly cultural.
The offer was CA$100,000 base plus a quarterly bonus tied to retention metrics. I asked for CA$108,000, citing the depth of the process and the demo round specifically. They came back at CA$105,000 plus an additional week of vacation. I accepted.
If there's a lesson, it's this. The writeup I posted eighteen months earlier was more useful than any CV I've ever written. It worked because it was specific, public, and answered a real question.
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.
Eighty-seven applications. Three interviews. One offer. The most boring job search you'll ever hear about, and that's mostly the point.
I was an accountant with seven years of experience in Berlin. I was looking for a senior role in industry, finance lead at a scale-up, after spending most of my career in mid-tier accounting firms. I knew what I wanted, I knew the salary band, and I had a clear picture of which kinds of companies would have the right mix of structure and chaos.
I sent eighty-seven applications across nine weeks. I tracked each one in a spreadsheet: date, company, role title, source, response. The response rate was 38%. Most of those were polite rejections. Twenty-one moved to a recruiter screen. Six moved to a hiring-manager interview. Three moved to a final round.
A Berlin scale-up was one of the three. I'd applied through their careers page. The role description was clear and specific in a way most JDs aren't. They listed the team, the systems, the current pain points, and the salary band. The salary band is what pulled me into the application. Most German JDs don't list one, and the fact that they did made me think the company was probably more sane to work at than the median.
The recruiter screen was forty minutes. The recruiter had read my CV carefully. She asked specific questions about a transition I'd run at my last firm and what I'd learned from it. The conversation was professional and unremarkable, which is the highest compliment I can pay a recruiter screen.
The hiring-manager interview was with the finance lead I'd be reporting to. Sixty minutes. We walked through three real situations they were working through: the integration of an acquired company's books, a multi-currency reporting question, and a deferred-revenue policy question. I had real opinions on all three. We disagreed on one. The conversation got better at that point.
The second hiring-manager interview was a more technical screen, a cash-flow modelling exercise on a real anonymised dataset. Two hours, take-home. I sent back a clean model with assumptions documented in a separate tab. They asked about three of the assumptions. I had an answer for each.
The final round was with the CFO. Thirty minutes. He wanted to know what I'd been wrong about in my last role and what I'd done about it. I had a real example.
The offer was €50,000 base. Below market for the role. The JD had listed a band of €48,000 to €60,000, so I was on the lower end. I asked for €55,000, citing seven years of experience. They came back at €54,000 plus a remote-first arrangement, where the JD had said hybrid two days a week. I accepted.
There's no clever lesson here. Sometimes the boring approach works. The thing I'm proud of is that I tracked every single application from start to finish, knew where I stood every week, and wasn't surprised when an offer came.
87Applications
3Interviews
2 monthsSearch length
Job boardSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.