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.
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.
Over about five months I applied to roughly 50 positions, almost all through LinkedIn, with a handful via Glassdoor. No networking events, no warm introductions, no carefully crafted cover letters. Just a well-put-together profile, a clean CV, and a lot of scrolling through job alerts on Sunday evenings. I'd always assumed that breaking into a better-paid in-house Legal Counsel role would mean knowing someone on the inside, or at least having a former colleague put in a word. That assumption was costing me confidence I didn't need to lose.
The process took around 150 days from first application to accepted offer, which felt agonisingly slow at the time. There were weeks where nothing moved at all, and I genuinely wondered whether I was pitching myself at the right level or aiming at the right sectors. Out of 50 applications I got three interviews, which sounds like a low conversion rate, but each one was for a role I'd read carefully and felt I could do well. I didn't spray applications around. I made sure my experience matched the specifics in the listing before I applied. The third interview process was where everything clicked. The role was hybrid, based in the UK, and came with a salary of £60,000, a meaningful step up from where I'd been. There were also travel perks built into the position that I hadn't even thought to look for when I started. I accepted without hesitation.
A few things stand out as genuinely useful. Reading the job listing properly, not just skimming it, meant I could speak directly to what they wanted once I was in the room. Not having a referral clearly didn't disqualify me, so I'd push back on anyone who thinks LinkedIn applications are a black hole. And when the salary conversation started, I didn't undersell myself. I knew what the role was worth, and I held that line. It paid off.
The recruiter ping came on a Thursday afternoon. By Tuesday I was on a call with the founders.
I'd been at my previous company for four years. I wasn't actively looking. My LinkedIn was up to date because that's just hygiene. About a hundred recruiter messages a year hit my inbox. Ninety-five I ignored, four got a polite "not right now", one sometimes turned into a real conversation.
This one was different. The opening message was four sentences. It named the company, the team, the specific PM problem they were trying to solve, and a line about why my background looked like a fit. No platitudes, no asking for a phone number, no asking me to update my résumé. The link went to a brief written description of the role and a salary band wide enough to include where I actually was.
I replied that day, asking for fifteen minutes to talk about scope. The recruiter was prompt and direct. The job was Senior PM on a payments-adjacent product at a Series B scale-up. Reporting to the head of product. Real ownership of a roadmap. The company had funding through 2027 in the bank.
The first interview was with the founder, on a Friday. He was the most prepared interviewer I've ever spoken to. He'd read my CV, looked up two of the projects on my profile, and read a blog post I'd written four years earlier. The questions were specific. By the end of the call I had a clear sense of what the role was, what the next quarter looked like, what the next year looked like, and what success at the six-month mark would look like.
The next round was a portfolio review with the head of product and one of the senior engineers. I walked through three projects. They cared less about the outcome and more about how I'd made the calls along the way: which trade-offs I'd flagged early, which I'd missed, what I'd done when a forecast was wrong.
The big round was the strategy doc. They handed me a three-page brief on a real product area and asked for a six-page response in a week: what I'd prioritise in the first 90 days, what I'd cut, what I'd defer, what I'd want to see in two metrics dashboards on day one. I spent two evenings on it. The six pages became eight, and then I cut it back to six.
The presentation was forty-five minutes with the two founders, the head of product, and a board member. They pushed hard on the first three priorities. The last twenty minutes was them walking through their own version of the brief and asking where mine differed and why.
The offer was $US 118,000 base plus refresh. I asked for the equity refresh up-front and another $10,000 on the base, citing the scope the founder had described. They came back with $128,000 and the refresh I'd asked for. The verbal offer was Friday. The signed papers were Tuesday. I was on the team three weeks later.
I'd been applying selectively, only four applications over those two months, because I didn't want to waste time on roles that weren't actually interesting. Most of my search was quiet and slow, and honestly a little discouraging. Then I came across a Substack post by the CTO of a New York data company about their decision to refactor their entire data pipeline around dbt and Snowflake. The post was technical, specific, and honest about the tradeoffs they'd made. It wasn't marketing. It read like someone who actually lived inside the problem, and I recognized a lot of the same pain points from my previous role.
I spent a couple of evenings on a cold email. I didn't pitch myself generically. I referenced specific paragraphs from the post and linked a public GitHub repo I'd built for stream-to-batch reconciliation. The repo wasn't perfect, but it was real work: documented, tested, and directly relevant to what he'd described. I figured if he was the kind of engineer who wrote that post, he'd at least look at the code. Three days later he replied. No recruiter, no application portal, no automated acknowledgment. Just a direct response asking if I wanted to jump on a call that week.
The process ended up being four rounds over about nine weeks. The first call was conversational, more mutual vetting than a formal screen. The third and fourth rounds brought in the broader data team and covered system design and past-project deep-dives. But the second round was the one that stuck with me. It was framed as a live SQL pairing session, and it started that way, but somewhere around the thirty-minute mark we were both heads-down on an actual production query they were struggling with. We went ninety minutes. I didn't solve it completely, but how I reasoned through it mattered more than any clean answer would have.
The offer came in at $145,000, hybrid in New York. I accepted without hesitation.
The offer from an Austin startup came in on day 51. By then I'd been through five rounds of interviews and 22 applications I was working through at the same time. The process had been thorough: a technical screen, a take-home infrastructure scenario, two panel interviews with the platform engineering team, and a final conversation with the VP of Engineering. I was interested in the hybrid DevOps role. Austin made sense geographically, the team seemed sharp, and $132k base was competitive for where I was in my career.
Then I got to the equity portion of the offer letter. The package included 0.15% over four years with a one-year cliff. Not unusual on its face. But equity is only worth something if you can actually evaluate it. Any time stock is part of a comp conversation, I ask for the most recent 409A valuation and some visibility into dilution history. Not to be difficult. Those two documents tell you almost everything about whether the equity is real or just a number on paper. I sent a professional note to their CFO asking for exactly that before I'd sign anything.
What I got back was a runaround. The first response was vague and pointed me back to the offer letter itself, as if the strike price listed there was enough context. I followed up and asked again, specifically for the 409A and any cap table information they were willing to share. I got a flat refusal. No explanation, just a no. That was it for me. A company that won't share basic financial documentation with someone they're asking to take a four-year equity vesting commitment either has something to hide or a culture of opacity I don't want to be inside of.
I walked away from the offer. When I mentioned it to three engineering friends here in Austin over the following week, none of them were surprised. All three had heard nearly identical stories about the company within the past year. That told me everything about my decision.
22Applications
5Interviews
7 weeksSearch length
RecruiterSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.