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 1 of 6
Filtered by newest stories across all roles and locations.
Three weeks after finishing a six-month software engineering bootcamp, I had four offers. 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.
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 late nights after full shifts on training: courses on platforms I paid for out of pocket, labs, and a home setup for hands-on practice. 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.
One twenty-minute conversation at a logistics meetup became an internal job posting that arrived in my inbox before it was on the company's careers page.
I had been an operations manager at a small ecommerce company in Mexico City for three years. The company grew fast for two years and then stopped growing. There was nothing more I could change there. I wanted a job at a logistics company, but nothing was happening. Part of the reason was that I was not really applying. The other part was that most logistics companies in CDMX do not post their jobs publicly, so it was hard to know what was open.
I went to a logistics meetup in late autumn, mostly because a friend was speaking. The COO of a logistics company in the city was in the audience, and we stood next to each other in the coffee break. We talked for about twenty minutes. She told me about a problem her team had at that moment: how to grow warehouse operations from one site to four. I told her how we solved a similar problem at my company, but at half the size. We exchanged WhatsApp numbers because she wanted to send me a paper she had been reading about it.
Three weeks later she wrote to me. Her team was going to post an operations manager job, and she wanted to talk to me before they published it. Could I come for a coffee?
The "coffee" was ninety minutes with her and one more senior person from operations. It was not really an interview. We went through three real problems they had, and most of the time I asked questions and they answered. At the end she said she would put me into their official process if I was interested.
The process was two interviews and a written exercise.
The first interview was with the COO and the head of warehouse operations. Sixty minutes. They asked how I would grow the warehouse network from one site to four. I had already thought about this, so my answer was specific.
The second part was a written exercise. They gave me a one-page brief about a real problem, opening a new warehouse in Monterrey, and asked for a six-page plan in one week. I sent five pages and a one-page appendix. In the next round we talked mostly about the appendix.
The last round was a conversation with the founder, mostly about equity and about what staying for three years would look like. He was direct. The equity they offered was large compared to the salary.
The offer was US$45,000 base plus equity. I asked for US$48,000 and a little more equity, and I showed them my own numbers for what the equity would be worth in a realistic exit. They came back with US$48,000 and a small increase in equity. I took the job.
I sent only one real application in the whole search.
Looking for ML roles in Europe took longer and was more tiring than I expected. I sent 32 applications over about three months, and the rejections followed a clear pattern: most teams either required a PhD or wanted only experience with LLM fine-tuning. My background is recommender systems and production ML tooling, the unglamorous work that keeps models running at scale, and that combination fitted badly with job descriptions written with transformer research in mind. I reached interviews at six places, which felt low for the number of applications I sent, and some of those early rounds ended with feedback that confirmed I was not what they were looking for.
The offer came through a referral. A former colleague from a previous startup had joined Zalando in Berlin and gave my name internally when a Senior ML Engineer position opened. That seemed to make people read my application differently. The recruiter wrote to me within a week, which had not happened anywhere else in this search. The process was rigorous: three technical rounds about system design, coding, and my recommender work in production, plus one more interview that surprised me. They called it a paper-discussion round. I had to argue both sides of a recent ML paper and change position in the middle of the conversation when the interviewer disagreed with me.
The offer was 95,000 EUR for a full-time job in Berlin, on site. The base is lower than comparable roles in the US, and I knew that before, but the package included 30 days of holiday and full visa support, which made the real numbers work for my situation. Ninety-one days after I started applying, I said yes.
I published the case study on a Tuesday afternoon. By Thursday morning I had three replies in my LinkedIn inbox.
I had been thinking about looking for a job for a long time without doing anything. My plan was always the same: finish the portfolio first, then start applying. After two months of polishing, the portfolio was still not finished, so I tried the opposite. Take one project, write about it completely, publish it, and let people tell me if it was good enough.
The project was a redesign of the onboarding of a fintech company where I did not work. I was a customer and I had noticed three problems. During one long weekend I made a prototype of a flow that solved two of them, built a Figma file with notes on the frames, and published a text of 600 words on LinkedIn explaining what I changed and what I did not touch.
N26 answered within one day. Their head of design said the writing was the part that made her stop. Most case studies she sees are only images, with no explanation of the thinking behind them, and she wanted to talk to designers who can explain their trade-offs out loud.
The first call was 45 minutes with the head of design. We did not talk about N26 until the last ten minutes. Most of the time she asked how I made specific decisions in past projects: when I disagreed with a PM, when I delivered something that I knew was a compromise, what I learned about onboarding metrics from my own mistakes.
I presented three case studies to two designers from the team, one hour in total. They were interested in the decisions in between: why this typeface and not the obvious one, why I recommended removing a feature instead of repairing it. The questions always returned to constraints, not to craft.
Round three was a paid exercise at home: redesign their settings flow and document the trade-offs in a written summary, with a limit of five hours. I treated it as a real project, I did not polish it too much, and I delivered exactly what fitted in five hours. The summary was three paragraphs about what I cut, why, and what I would do next if I had a full week.
The last round was a conversation of 30 minutes with the CTO. We talked about the role, the team, what they would release in the next quarter, and if I would stay for two years. He was the most direct interviewer in the whole process.
The offer was €58,000. I asked once for a higher base salary, and I explained the scope they had described in the final round. They answered the same day with the same number plus a sign-on bonus that covered my relocation. I signed the contract.
I sent 18 applications in this whole search. Three of them were the answers to the case study post. The rest went to companies I chose because their product was close to the subject of my case study.
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.
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.
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 wasn't sure I could go back to five without resenting it from day one.
The search itself had been a slog. 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 introduction 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.
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 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. I signed within an hour.
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 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. By the end I was 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. I answered with 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 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 a fortnight later. The document took me an afternoon to write.
I had been applying for technical writing roles across Europe when I found a job on the careers page of a Lisbon software company. Before any recruiter call they wanted a writing sample. Take a 600-word section of their public documentation and rewrite it. Send it before they even schedule the first video call.
I almost decided not to do it. A 600-word rewrite sounds simple until you open their documentation and see that the section they chose was dense API reference material, with inconsistent terminology, three passive sentences one after another, and a structure that assumed you already knew what you wanted to learn. I spent four hours on it, exactly the time the brief suggested. I respected that they said this clearly instead of pretending it was quick. I restructured everything, made the definitions tighter, used consistent names, and added a short summary table that I thought would help people who read fast. I did not know if that last part would be appreciated or look arrogant.
They liked it. They moved me to three video rounds over the next two and a half weeks. The first was a recruiter asking the basic questions. The second was with the lead technical writer and an engineer, who asked precise questions about how I handle conflicting input from subject-matter experts. The third was a short panel that felt more like a working conversation than a formal interview. Twenty-two days after I sent that first application, I had an offer: a full-time hybrid role in Lisbon at 28,000 EUR. I accepted quickly, with almost no negotiation.
They asked me to start within ten days because the team was missing a writer and the problem was visible. I changed my plans and made it possible.
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: the structure made $72k nearly impossible to reach, and accelerators didn't kick in until 120%, a threshold most reps never hit during ramp. So 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. The whole document argued their side: restructure the upside and the same rep produces more pipeline than the accelerator costs.
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. 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.