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 5 of 6
Filtered by newest stories across all roles and locations.
I had been following a design studio in CDMX on Instagram for almost a year before I was brave enough to write to them. Their client work in Roma kept appearing in my feed, and every time it did I saved the post, took a screenshot, and thought "someday". I liked how simple they kept everything, and the way they used type on printed signs and installations. It was the kind of studio where I wanted to learn. I had already sent cold messages to two other studios in the city and neither one answered, so I knew that a normal "I love your work, here is my portfolio" message was not going to work.
I spent one afternoon reading their recent open briefs and chose the one I felt most sure about. I did not write a long cover message. Instead I made three quick sketches with ideas for that brief, rough and not finished, and sent them to the founder in a short DM of four sentences. He answered the same day. I read the notification twice before I believed it was real. He invited me to visit the studio in person, at their space in Roma Norte. The visit went well, and they offered me a trial week and paid me their full day rate for it. Many studios ask you to work that week for free. That mattered to me.
The trial week was hard. They put me on a real project that was already running, gave me feedback while I worked, and expected me to help from the first day. Two weeks after my first DM, they offered me the job full time, with a hybrid schedule.
The credit made my decision. The studio puts the names of junior designers on the work it publishes, and right now that is worth more to me than more money somewhere else. I said yes immediately.
It took eight hard months, 135 applications, and interviews with 15 different companies before I landed my first developer job as a Frontend Engineer. The first few months I 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. 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 questioning whether this would happen at all.
When the hybrid offer came in at $72,000 and I said yes, it was anticlimactic. A PDF in my inbox and a quiet exhale.
The recruiter call came out of nowhere. I'd answered a customer's question on Highbeam's community forum eighteen months earlier and had 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 resume 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 making, 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 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. They came back at CA$105,000 plus an additional week of vacation. I signed.
The writeup I posted eighteen months earlier was more useful than any resume I've ever written. It worked because it was specific, public, and answered a real question.
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 most of my career in mid-size accounting firms. I knew what I wanted, I knew the salary range, and I had a clear idea of which companies would have the right balance between structure and chaos.
I sent eighty-seven applications in nine weeks. I recorded every one in a spreadsheet: date, company, role title, source, answer. The response rate was 38%. Most of the answers were polite rejections. Twenty-one went to a recruiter call. Six went to an interview with a hiring manager. Three went to a final round.
A Berlin scale-up was one of the three. I applied through their careers page. The role description was clear and specific, which most job descriptions are not. They listed the team, the systems, the current problems, and the salary range. I applied because of the salary range. Most German job descriptions do not show one, and the fact that they did made me think the company was probably better to work for than the average.
The recruiter call was forty minutes. She had read my CV carefully. She asked specific questions about a system change I had managed at my last firm and what I learned from it. The conversation was professional and without surprises, which for a recruiter call is the best compliment I can give.
The interview with the hiring manager was with the finance lead who would be my boss. Sixty minutes. We went through three real situations from their work: the integration of the accounts of an acquired company, a question about multi-currency reporting, and a question about their deferred-revenue policy. I had real opinions about all three. We disagreed about one. After that the conversation became better.
The second interview with the hiring manager was more technical, a cash-flow modelling exercise with real anonymised data. Two hours, at home. I sent back a clean model, with my assumptions written in a separate tab. They asked about three of the assumptions. I had an answer for each one.
The final round was with the CFO. Thirty minutes. He wanted to know what I had been wrong about in my last job, and what I did about it. I had a real example.
The offer was €50,000 base. That is below the market for this role. The job description had shown a range of €48,000 to €60,000, so I was at the bottom. I asked for €55,000 and explained my seven years of experience. They came back at €54,000 and a remote-first arrangement, although the job description had said hybrid, two days per week. I signed.
There is no clever lesson here. Sometimes the boring method works. I am proud that I tracked every application from the beginning to the end, that I knew my situation every week, and that I was not surprised when an offer came.
I finished the bootcamp in March with no commercial experience and a portfolio that felt very thin. For the next weeks I applied to anything with "junior" or "graduate" in the title: 47 applications in about two and a half months, mostly through LinkedIn. Almost nobody answered. Some companies never replied at all, a few sent automatic rejections after a few hours, and I started to ask myself if a bootcamp certificate was worth anything in a market full of computer science graduates.
The thing that changed everything was a side project that I almost did not publish. I had built a small open-source tool on the Spotify API that creates personal listening statistics. Nothing revolutionary, but I was proud of the structure of the code and of the documentation. I posted a Show HN on Hacker News, mostly to get feedback, and it grew much more than I expected. About 200 stars in the first month, some good comments about the architecture, and a few people opening issues and pull requests. I checked my GitHub notifications again and again, all day. About two weeks after the post, an engineer at a Madrid startup starred the repository and then sent me a DM on LinkedIn. He said the queue management pattern I used had interested him, and that they were hiring.
The interview process had three stages. First a technical call, where we went through the project together and talked about how I would scale it. Then a take-home exercise: build a small queue worker that processes async jobs with retry logic, which felt like normal daily work and not like a whiteboard puzzle. Finally a calm conversation with two senior engineers, more about culture than a test. The whole process took about two weeks once it started.
The offer was €26k, which is low for Madrid. I negotiated a little, without much result. But the team is almost all senior people, and they pair-program with juniors on purpose, and for me right now that is worth more than a few thousand euros more. I said yes.
After about six weeks of quietly looking, 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, got in touch unprompted and said he'd put my name forward to the Solutions Engineering manager at a Sydney B2B SaaS company. I hadn't given them a serious look before that conversation, but the hybrid setup and the scope of the role made it worth having a crack at.
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 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 confident enough after those. But round five was a panel with cross-functional stakeholders, and the tone shifted. They were assessing how I'd handle internal politics as much as 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, 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. The hiring manager called out that moment of transparency in the debrief.
The offer came two days later: a base of AU$140,000 plus a sign-on bonus equal to one month's base. I took it.
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 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 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 straight away. She'd clearly read my profile rather than fired off a template, and the way she described the team's challenges matched work I'd actually done. I agreed to go ahead 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 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. They'd reconstructed three situations that had actually played out in their engineering team 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. I pushed back and negotiated another eight thousand pounds, which took it to £110,000. Forty-two days from that first LinkedIn message to a signed offer.
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, a fella 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 kept in touch, loosely. On a Monday morning in late autumn he messaged 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 out of curiosity. I had no plans to leave and 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 rota, 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 knew more about the role than about any job I'd interviewed for that year.
Round two was the head of platform and one other senior engineer. Sixty minutes, set up 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 versions 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 sound 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 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 been through. The reason it worked was that someone inside was vouching for me from the start.
Welcome to the Jungle worked exactly as it promised. It put me in front of the right person.
I had updated my profile about a year before this with a clear summary of what I wanted. An internal recruiter role, mid to senior, in a consulting firm or an agency, French-speaking but French not obligatory. After that I left the profile alone. Every six months I updated it when something changed in my career.
The talent team at a Paris recruiting firm wrote to me at the end of February. The first message was three sentences. They were hiring an internal recruiter, the role was focused on hiring senior consultants, and they wanted to know if I was interested. I answered yes within an hour, because the description matched my profile summary almost word for word.
The first call was with the head of talent. Forty-five minutes. Most of the time she described the firm's hiring process honestly, including the parts that did not work, and asked what I would do differently in the first ninety days. I told her. She disagreed with one part, and we had a useful discussion.
Round two was a role-play of a sourcing call. They gave me the profile of an invented candidate, a senior consultant at a competing firm, and asked me to make the first cold call. The interviewer played the candidate, and the candidate was not interested. I had thirty minutes to find an approach. I found one in about twenty. The candidate did not say yes, but the interviewer told me the approach was the right one.
Round three was with two senior consultants who would work closely with the recruiter. They wanted to know how I would talk to them about candidates, when I would say no if they wanted to make a search too wide, and what I would do if they wanted to hire a friend. I had a real answer to all three questions.
Round four was a final conversation with the managing partner. Mostly about culture. He asked what I did not like in previous firms, and if anything he had said sounded true to me.
The offer was €54,000 base plus a quarterly bonus. I asked how the bonus was calculated, and I worked out that realistic total pay would be about €60,000. Two other firms I was talking to in the same period had offered €45,000 to €48,000 for clearly the same work. I mentioned those numbers calmly and asked if the base salary could move. They came back at €56,000.
I said yes because the pay was clearly better, because this team had been the most direct with me, and because I liked the partner.
If I did this again, I would update my profile earlier. The platform did the matching. I only had to be easy to find.
8Applications
4Interviews
6 weeksSearch length
RecruiterSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.