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.
Three weeks after finishing a six-month software engineering bootcamp, I had four offers on the table. The breakdown told the story. Cold messages got me zero interviews, warm leads got me one, and hot connections, people who'd actually watched me build things and debug code in real time, got me five interviews out of six. I applied to just six positions total, and every one that mattered came through a relationship I'd deliberately built.
During the bootcamp I made a choice early on to treat every guest speaker, every alumni panel, and every study group as a potential thread in a professional network. While some of my cohort spent evenings blasting resumes into job boards, I was having thirty-minute coffee chats over Zoom with engineers who'd graduated a year or two ahead of me. I asked specific questions about their stacks, their onboarding, and what they wished they'd known. I wasn't pitching myself, just being curious. By the time I finished the program, I had maybe fifteen people who actually knew my name and what I could do.
When I started the search, I reached out to that group directly. Five of them either referred me internally or made a direct introduction to a hiring manager. The difference in response rate was almost embarrassing. The handful of cold messages I sent into the void came back with silence. The warm introductions moved fast: first conversations scheduled within days, technical screens that felt more like collaborative problem-solving than interrogations. One of those led to a full-stack developer role, hybrid in the US, at $75,000 a year, and I accepted twenty-one days after I started looking.
If you're just starting out, your network isn't a nice-to-have sitting next to your resume game. For me it was the whole pipeline, and building it meant starting well before I ever needed it.
Two years ago I left the military with a bit of IT experience and basically no civilian tech resume to speak of. I started at the bottom doing tier-one IT support: password resets, ticket queues, the whole thing. It was humbling, but I kept my head down and paid attention to how the infrastructure around me actually worked. After about eight months I moved into a network operations role, which gave me real exposure to traffic analysis, firewall rules, and incident escalations. That was when I saw where I wanted to go. Security engineering.
From there I spent my evenings and weekends on training. I mean late nights after full shifts, working through courses on platforms I paid for out of pocket, grinding through labs, building a home setup so I could practice hands-on. I picked up certifications along the way and kept a running list of projects I could point to. Not because they were impressive, but because they were evidence I was moving in a clear direction. I found the job posting on a job board while I was still in the network operations role, and I almost talked myself out of applying. The requirements listed experience I didn't fully have yet. I applied anyway.
The interview process ran three rounds. The first was a general conversation about my background, the second got technical, and the third felt more like a culture and judgment assessment. In each one I was completely straight about where my hands-on security experience was thin. I didn't dress it up or dodge the questions. I told them exactly what I knew, what I was still learning, and what my plan was for closing those gaps. They offered me $95,000 for a hybrid, full-time security engineer position. I accepted without hesitation. I think the honesty landed as well as the certifications did. They could see the trajectory clearly, and apparently that was enough.
One twenty-minute conversation at a logistics meetup turned into an internal job posting that landed in my inbox before it was on the company's careers page.
I'd been an operations manager at a small ecommerce company in Mexico City for three years. The company grew fast for two years and then plateaued. I'd hit my own ceiling on what I could change there. I'd been quietly looking for a role at a logistics-focused company, but the search wasn't going anywhere. Partly because I wasn't actively applying. Partly because most logistics-focused companies in Mexico City didn't have the kind of public hiring process that made it easy to know what was open.
I went to a logistics meetup in late autumn, mostly because a friend was speaking. The COO of a Mexico City logistics company was in the audience and we ended up next to each other during the coffee break. We talked for about twenty minutes. It was specifically about a problem her team was working on at the time, how to scale warehouse operations from one site to four sites, and I described how we'd handled a similar problem at half the scale. We swapped WhatsApp numbers because she wanted to send me a paper she'd been reading on the topic.
Three weeks later she messaged me. The team had been about to post an operations manager role and she wanted to talk to me before they listed it publicly. Could I come in for a coffee?
The "coffee" was ninety minutes with her and one other senior operations person. We didn't really do an interview. We walked through three real problems they were working on, and most of the conversation was me asking clarifying questions and them answering them. By the end she said she'd put me through their formal process if I was interested.
The process was two interviews and a written exercise.
The first interview was the COO and the head of warehouse operations. Sixty minutes. They asked how I'd scale the warehouse network from one site to four. I'd thought about it. The answer was specific.
The second was a written ops-plan exercise. They gave me a one-page brief on a real problem, the rollout of a new warehouse in Monterrey, and asked for a six-page plan in a week. I sent back five pages with a one-page appendix. The discussion in the next round was specifically about the appendix.
The final round was a conversation with the founder, mostly about equity and what staying for three years would look like. He was direct. The equity grant on offer was meaningful relative to the comp.
The offer was US$45,000 base plus equity. I asked for US$48,000 plus a slightly larger equity grant, citing the equity arithmetic at a realistic exit. They came back with US$48,000 and a small equity bump. I accepted.
I'd sent one real application during the whole search, the one to that company, after the conversation. Everything else flowed from a twenty-minute hallway conversation I almost didn't have.
Looking for ML roles in Europe took longer and was more draining than I'd expected. I sent out 32 applications over roughly three months, and the pattern of rejections got predictable fast: most teams either wanted a PhD as a hard filter or were exclusively chasing LLM fine-tuning experience. My background is recommender systems and production ML tooling, the unglamorous plumbing that keeps models running at scale, and that combination landed awkwardly in a lot of job descriptions written with transformer research in mind. I got through to interviews at six places total, which felt like a low conversion rate for the volume I was pushing, and a couple of those early rounds ended with feedback that basically confirmed I was the wrong shape for what they were building.
The offer I eventually accepted came through a referral, and that was the only thing that broke the pattern. An ex-colleague from a previous startup had joined Zalando in Berlin and flagged my name internally when a Senior ML Engineer position opened up. That internal signal seemed to get my application read differently. The recruiter reached out within a week, which hadn't happened anywhere else in this search. The process itself was rigorous: three technical rounds covering system design, coding, and a deep dive into my recsys work in production, plus a separate interview that genuinely surprised me. They called it a paper-discussion round. The format was that I had to argue both sides of a recent ML paper, switching positions mid-conversation when the interviewer pushed back. It was uncomfortable in a way I respected. They wanted to see how I thought, not just what I'd memorized.
The offer came in at 95,000 EUR for a full-time, on-site role in Berlin. The base is below what comparable US roles pay, and I knew that going in, but the package included 30 days PTO and full visa support, which made the real-world math work for my situation. Ninety-one days after I started applying, I accepted.
The case study went up on a Tuesday afternoon. By Thursday morning I had three replies in my LinkedIn inbox.
I'd been thinking about job-hunting for a while without doing anything about it. The plan had always been polish the portfolio first, then start applying. After two months of polish that clearly wasn't converging on a finished portfolio, I tried the opposite: pick one project, write it up properly, post it publicly, and let people tell me whether it was good enough.
The project was an onboarding redesign for a fintech I had nothing to do with. I'd been a customer and noticed three friction points. Over a long weekend I prototyped a flow that fixed two of them, built a Figma file with annotated frames, and posted a 600-word writeup on LinkedIn explaining the trade-offs.
N26 replied within a day. Their head of design said the writing was the part that had stopped her. Most case studies she sees are visual evidence with no reasoning attached, and she wanted to talk to designers who could think about trade-offs out loud.
The first call was 45 minutes with the head of design. We didn't talk about N26 specifically until the last ten minutes. Most of it was her asking how I'd handled specific decisions in past projects: when I'd disagreed with a PM, when I'd shipped something I knew was a compromise, what I'd learned the hard way about onboarding metrics. A real interview, not a "tell me about yourself" one.
Round two was a portfolio walkthrough with two designers from the team. Sixty minutes, three case studies. They cared about the in-between decisions. Why this typeface and not the obvious one. Why I'd recommended killing a feature instead of fixing it. The questions kept circling back to constraints rather than craft.
Round three was a paid take-home: redesign their settings flow, document the trade-offs in a written summary, time-boxed at five hours. I treated it as a real project, didn't over-polish, and shipped exactly what fit in five hours. The summary was three paragraphs on what I'd cut, why, and what I'd do next with a full week.
The final round was a 30-minute conversation with the CTO. Not a values check disguised as a chat, but a real conversation about the role, the team, what they'd ship over the next quarter, and whether I'd stay for two years. He was the most direct interviewer of the loop.
The offer was €58,000. I asked once for a bump on the base, citing the scope they'd described in the final round. They came back the same day with the same number plus a sign-on that covered relocation. I accepted.
I sent 18 applications during this whole search. Three were the immediate replies to the case study post. The rest went to companies I'd targeted because their product overlapped with the case-study domain. Volume wasn't the lever. Specificity was.
The offer letter came through at £62k full-time hybrid, and my first reaction wasn't the excitement I expected after 41 days of searching and five rounds of interviews. It was more a quiet dread. I'd spent the last two years working four days a week at my previous company, and I genuinely wasn't sure I could go back to five without resenting it from day one.
The search itself had been grinding. I sent out 22 applications across Manchester and a handful of remote-friendly studios, heard back from a fraction, and most of the interviews I did land felt like they were going nowhere. The conversation with the design studio started differently, partly because I came in through a referral from a designer I'd worked with a few years back. That warm intro meant the first call felt less like an audition and more like a conversation about what the team actually needed. Over five interviews they walked me through their research process, their design system, and how product sat alongside engineering. Thorough, but it never felt adversarial.
When the written offer arrived I sat on it for a day before responding. I knew I wanted to ask for the four-day arrangement, but I'd seen that conversation go badly before, companies treating it as a red flag, suddenly unsure about your commitment. I kept the ask simple: I'd been working a four-day week, it suited how I do my best work, and I wanted to continue at 80% pay to reflect that. Their response surprised me. They came back and said they'd actually prefer to keep me at full salary, on the condition that I committed to a specific Wednesday rhythm, a standing research day the whole product team observed together. They wanted the consistency more than the cost saving, which I respected. I signed within an hour. No regrets.
I'd been job hunting for about seven weeks when I finally landed on Pearson's careers page and spotted their Junior Data Scientist listing. I'd already sent out 28 applications across London by then, cycling through job boards, LinkedIn, and direct company websites, and honestly the hit rate was demoralising. Pearson was one of those rare cases where applying through the company website felt worthwhile. The role description was specific enough that I could tell a real hiring manager had written it instead of copy-pasting from a template.
Six interviews over 49 days. That's a long stretch when you're mid-search and trying to keep your momentum up. There was an initial screen, a technical take-home, two panel rounds with the data team, a stakeholder interview with someone from the commercial side, and a final conversation with the hiring manager. Each stage felt substantive rather than performative, which at least made the wait easier to justify. By the end I was genuinely excited about the work. They had a messy, interesting data infrastructure problem and actual budget to fix it.
When the offer came through at £55k I wasn't surprised it sat on the lower end. The role was posted as Junior. But the work they were describing mapped much more closely to what I'd been doing for the past three years at two similar-stage companies. So instead of a flat counter-offer, I put together a short document, three or four pages, walking through specific projects, the scale of decisions I'd influenced, and the measurable outcomes. Revenue impact, model performance improvements, team scope. I framed it less as "pay me more" and more as "here's where I actually sit on your levelling rubric." I asked them to reconsider the level entirely, not just the number.
The hiring manager took it back to the panel. A few days later they came back with a revised offer: Senior Data Scientist at £78k. I started two weeks later. The document took me an afternoon to write and it was absolutely worth it.
The offer came in after a 48-day process that felt longer than it was. I'd applied to 16 roles in total and gone through 5 full interview loops, so by the time this verbal landed, I was far enough into other processes that I had real leverage. Not manufactured leverage. Actual competing timelines. The role was a hybrid Engineering Manager position at a New York startup, and a recruiter had connected me to the company after reaching out cold. I almost ignored the message. Glad I didn't.
The initial verbal was $165k base with a $30k sign-on. I appreciated the sign-on, but the base was the number I cared about. It's what compounds, it's what your next offer anchors off of, and it was sitting meaningfully below where I felt the market was for this scope. I had two other companies I was in final-round loops with, and I decided to name them outright rather than hint vaguely. I told the recruiter the exact stage I was at with each and that I expected decisions within two weeks. I wasn't bluffing, and I think the specificity mattered. Vague competing offers get dismissed. Concrete ones don't.
I countered at $195k base and $45k sign-on. The ask felt aggressive but not unreasonable given what I knew about the band. They came back within a few days at $195k base, $35k sign-on, and added an equity refresh at the 12-month mark, which I hadn't asked for. That addition told me they wanted to close and were willing to get creative instead of just splitting the sign-on difference. The whole negotiation ran about a week of back-and-forth through the recruiter.
I signed it. Getting to $195k from $165k on base alone was the priority going in, and that's exactly what happened. The equity refresh was a bonus.
I'd been applying to technical writing roles across Europe when I found a listing on the careers page of a Lisbon software company. Nine applications in, and this one felt different right away. Not because of the job description, but because of what they asked for upfront. Before any call, before any recruiter screen, they wanted a writing sample. Take a 600-word section of their live public documentation and rewrite it. Submit it before the first video call would even be scheduled.
I almost talked myself out of it. A 600-word rewrite sounds simple until you open their docs and see that the section they'd picked was dense API reference material with inconsistent terminology, passive constructions stacked three sentences deep, and a structure that assumed you already knew what you were trying to learn. I spent four hours on it, which was exactly what the brief told me to budget. I respected that they'd said so plainly instead of pretending it was quick. I restructured the whole thing, tightened the definitions, introduced consistent naming, and added a short summary table I thought would help skimmers. I had no idea if that last bit would land or just seem presumptuous.
It landed. They moved me to three video rounds over the next two and a half weeks. The first was a recruiter going through the basics. The second was the lead technical writer and an engineer who asked pointed questions about how I handle conflicting input from SMEs. The third was a short panel that felt more like a working conversation than a formal interview. Twenty-two days after I submitted that first application, I had an offer: a full-time hybrid role based in Lisbon at 28,000 EUR. I accepted without much back and forth.
They asked me to start within ten days of accepting because the team was down a writer and the gap was showing. I cleared my schedule and made it work. Worth it.
The whole thing moved faster than I expected. A recruiter reached out about the Sales Development Representative role at AlertMedia in Austin, and I almost passed because the posted comp felt low for the market. I went ahead anyway, sent in my application, and within about four weeks I had an offer in hand. Twenty-seven days total from first contact to close, across four interviews. But the number on that first offer sheet wasn't where I needed it, and I wasn't going to just sign and hope.
The standard SDR package was $52k base plus $20k in commission on their existing commission plan. I'd done enough research to know the OTE ceiling was the real problem. Not that $72k total was impossible to reach, but the structure made it nearly impossible to exceed, and the accelerators didn't kick in until 120%, a threshold most reps never hit during ramp. So instead of countering with a number out of thin air, I spent a weekend building a written analysis of their own funnel. I pulled what I could from public data and from what they'd shared in the interviews: average ramp timelines for SDRs in their segment, top-quartile MQL-to-meeting conversion rates, and the actual math on what a tiered accelerator above 110% would cost them versus what it would produce in pipeline. I framed it not as "pay me more" but as "here's how you get more output if you restructure the upside."
It worked. They came back and rebuilt the plan: $52k base with $30k in commission, and accelerators starting at 110% instead of 120%. That put my on-target earnings at $82k, exactly where I needed to land. The base didn't move, but the variable comp was redone from the ground up. Going in with a written analysis rather than a verbal counter is what made the difference. It gave them something concrete to take to finance.
9Applications
4Interviews
4 weeksSearch length
RecruiterSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.