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 5 of 6
Filtered by newest stories across all roles and locations.
It took eight hard months, 135 applications, and interviews with 15 different companies before I finally landed my first developer job as a Frontend Engineer. The arc of those 240 days reads almost cinematic now, but living through it was grinding and slow. The first few months I did what most bootcamp grads do: blasted out applications through job boards, tailored nothing, and wondered why I kept getting ghosted. I think I sent around 80 that way before I accepted the strategy wasn't working.
The shift that changed things was dropping generic listings entirely and going straight to people. I started doing cold outreach to senior engineers and engineering managers on LinkedIn, keeping the messages short, specific, and built around something real I'd noticed about their product or stack. Most never replied, but the ones who did opened doors the job board route never would have. That's how the offer that mattered came through. Alongside the outreach, I started treating every surface of my professional presence like a product I had to ship. The portfolio got rebuilt twice, the resume got stripped down until every line earned its spot, and I wrote and rewrote a two-sentence pitch until I could say it without thinking.
I also made a rule for myself: between every round of applications I had to build or meaningfully extend a project. It kept my skills moving, but more practically it meant every interview I walked into had something new to talk about. I got rejected a lot. Some stung more than others, especially the ones that went three or four rounds deep. By month six I was genuinely questioning whether this would happen at all.
When the hybrid offer finally came in at $72,000 and I said yes, it was almost anticlimactic. No fanfare, just a PDF in my inbox and a very quiet exhale. Those 135 noes were the price of one yes, and I'd pay it again.
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.
I'd been following a Mexico City design studio on Instagram for almost a year before I worked up the nerve to do anything about it. Their CDMX-Roma client work kept showing up on my feed, and every time it did I'd save the post, screenshot it, and think "someday." The editorial sensibility, the way they handled typography on physical installations, the restraint. It was exactly the kind of studio I wanted to learn inside of. By then I'd sent two other cold outreach attempts to studios in the city, both completely unanswered, so I knew a plain "I love your work, here's my portfolio" message wasn't going to cut it.
I spent an afternoon looking through their recent open briefs and picked the one I had the strongest instinct about. Instead of a long cover message, I put together three quick concept sketches responding directly to the brief. Nothing overproduced, just clean directional thinking. I attached them to a short DM to the founder and kept the message to maybe four sentences. He replied the same day. I don't think I fully believed it was real until I'd re-read the notification twice. He invited me in for an in-person studio visit at their Roma Norte space, which went well enough that they offered me a paid trial week at their full day rate rather than some unpaid evaluation arrangement. That mattered to me, and I made note of it.
The trial week was intense. I got dropped into an active editorial project, given real feedback in real time, and expected to contribute rather than observe. By the end of the week, two weeks after that first DM, they offered me the junior designer role full-time on a hybrid schedule. The salary is fair for a junior role in Mexico City, and the studio actively credits junior designers in published portfolio work, and that kind of visibility at this stage is worth a lot to me. 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.
After about six weeks of quietly exploring the market, I'd sent out roughly fifteen applications across Sydney's tech sector before the right break came through. A former client, someone I'd worked closely with on an integration project a couple of years back, reached out unprompted and said he'd flagged my name to the Solutions Engineering manager at a Sydney B2B SaaS company. I hadn't even considered them seriously before that conversation, but the hybrid setup and the scope of the role made it worth pursuing properly.
The process ran over six rounds across about forty-five days, and I won't pretend the pacing didn't wear on me. The early stages were fairly standard: an initial screen with HR, a technical discovery call, then a deeper architecture whiteboard session where I had to walk through a multi-tenant cloud migration scenario with two senior engineers pushing back on my assumptions. I felt reasonably confident after those. But round five was a panel with cross-functional stakeholders, and the tone shifted noticeably. They were clearly assessing how I'd handle internal politics, not just technical complexity.
Round six was the one that mattered. A sixty-minute mock customer demo, except their actual sales team was in the room, watching in silence. About fifteen minutes in, someone broke character and hit me with a hard CFO-style objection: budget authority questions, timeline scepticism, the kind of thing designed to knock you off your prepared flow. I acknowledged the concern directly, parked the slide I was on, and reframed the value case around risk reduction rather than feature set. It went sideways a second time near the end, when a "procurement lead" challenged our integration assumptions. I recovered by being honest about the constraint rather than bluffing through it. That moment of transparency was apparently what the hiring manager called out in the debrief.
The offer came two days later: a base of $140,000 AUD plus a sign-on bonus equal to one month's base. I accepted without hesitation.
I graduated in the spring and walked straight into one of the roughest hiring markets I'd seen described in any of the forums I was reading to prep. It didn't dent my optimism at first. I built a spreadsheet, set up job alerts across a few major boards, and started firing off applications. Over about three months I sent close to 200: tailored cover letters for some, quick-apply submissions for others when the listing was clearly a long shot. The rejections came in waves, sometimes five or six in a single afternoon, and a few roles just went silent after a first-round screen.
I made it to the interview stage at five companies. Four ran the standard process: a recruiter call, then one or two rounds of timed algorithmic problems. I'd been grinding practice problems for weeks, but there's a specific kind of pressure that hits when you're solving a graph traversal question while a stranger watches a timer count down, and I didn't always perform the way I knew I could. Those four ended without an offer. By month two the weight of it was getting to me. I was refreshing my inbox more than I should have, second-guessing whether I'd picked the right field at all.
The fifth company was different from the first message. The listing mentioned a project-based interview format, which I almost scrolled past because I assumed it was marketing language. It wasn't. The interviews were genuinely conversational. We walked through real engineering decisions, talked about tradeoffs I'd navigated in my capstone project, and got into how I approached debugging something I'd never seen before. It felt less like a performance and more like a preview of the actual job. The offer came in on-site, full-time, at 72k, with relocation assistance, profit sharing, and unlimited vacation. After months of quiet rejections, the relief was physical. My honest takeaway: keep applying through the noise, but pay close attention to the companies whose process actually gives you room to show what you can do.
I'd been passively browsing roles for about six weeks and sent out roughly eighteen applications before anything serious came through. Most went quiet after the first email. Then a recruiter messaged me on LinkedIn about an Engineering Manager position at a London software company, fully remote, based out of London, and the conversation felt different right away. She'd clearly read my profile rather than fired off a template, and the way she described the team's challenges mapped closely to work I'd actually done. I agreed to move forward the same day.
The process ran four rounds over about six weeks. First was a hiring manager screen covering my background and management philosophy, fairly standard, maybe forty minutes. The second round was cross-functional, with a product lead and a design manager sitting in, focused heavily on how I'd handled competing priorities between engineering and other disciplines. That one took more prep than I'd expected, and I spent a couple of evenings pulling together concrete examples with real numbers attached. Third round was people-management scenarios with a senior engineer on the team. I assumed it would be the lighter conversation. It wasn't.
The fourth round with the CTO was the one I'd been warned about, and it earned the reputation. Instead of abstract hypotheticals, they'd reconstructed three situations that had actually played out in their engineering org the previous quarter: a production incident with unclear ownership, a mid-sprint scope change driven by a large customer, and a retention conversation with a high performer who'd started interviewing elsewhere. For each one they gave me context, asked how I'd have handled it, then pushed back hard on my reasoning. It was the most rigorous interview I've sat through, and I left unsure whether I'd done enough.
The offer came a few days later at a solid base, but I pushed back and negotiated an additional eight thousand pounds. Accepted at £110,000. Forty-two days from that first LinkedIn message to a signed offer.
Two weeks. Three rounds. One offer. The fastest hire I've ever been involved in, on either side of the table.
I wasn't job-hunting. I'd been at my previous company for two years as the second DevOps hire. I liked the team. The infrastructure was a mess, but a manageable mess, and I'd been making it less of one every quarter.
A former colleague, someone I'd worked with five years earlier at a very different company, had moved to a Dublin cloud company eight months prior as the engineering manager for the platform team. We'd stayed loosely in touch. On a Monday morning in late autumn he pinged me on Slack: "we're hiring a senior DevOps person for my team, you'd be perfect for it, can we talk?"
I said yes mostly out of curiosity. I had no plans to leave, but I was happy to hear what they were doing.
The first call was him, forty-five minutes. No formal recruiter screen. He walked me through the team, the stack, the on-call rotation, the salary band, the team's biggest current pain (a Kubernetes upgrade that had been deferred for six months), and what they hoped to ship next quarter. By the end I had a clearer picture of the role than I'd had of any role I'd interviewed for in the previous year.
Round two was the head of platform and one other senior engineer. Sixty minutes, structured as an "infrastructure design" conversation. They presented a real problem they were working through, how to handle blue-green deployment for a stateful service with a managed database, and asked me to think out loud. I'd thought about variants of it before. We disagreed on one specific point about traffic shifting, and the conversation got more interesting there.
Round three was an "incident response" round with two engineers. They walked me through a real outage from two months earlier, slowly, runbooks open, and asked what I'd have done at each decision point. There were a few places I'd have gone differently. I said so. They were pleasant about it.
The final round was twenty minutes with the CTO. He asked two real questions: what would make me leave a company, and what would make me leave this one specifically. I told him.
The offer arrived the next morning. €82,000 base. Same as their advertised band, no negotiation needed, because they'd told me the band on the first call and asked specifically whether it worked for me. I'd said yes then. I said yes again now.
The whole process, from first Slack message to signed offer, was fourteen days. It worked because every round was someone who'd actually read about me, had a clear question they wanted answered, and respected my time. The recruiter screen never happened. No take-home. No gimmicks. It was the best interview process I've ever been through, and I think the only reason it worked was that an internal person was vouching for me from minute one.
1Applications
3Interviews
2 weeksSearch length
ReferralSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.