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.
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.
Five months of searching, more than 400 applications across Indeed and LinkedIn, and a single interview to show for it. I started out cautiously optimistic. I had customer service experience, I was applying to remote roles that looked like a good fit, and I assumed something would land within a few weeks. It didn't. I kept a spreadsheet to track everything, and watching the row count pass 100, then 200, then 300 with no callbacks wore me down. I started doubting my resume, my cover letters, the whole approach. I rewrote the resume twice. I even applied to roles a step below my experience just to get any response. Still nothing. Some weeks I'd send 30 or 40 applications and hear back from none of them. The silence got exhausting in its own way.
Around the four-and-a-half-month mark, a Customer Service Representative posting on Indeed finally went somewhere. A screening call, then a full interview, the only one in the entire search. I thought it went well, but after months without feedback I couldn't tell. When the offer came in, it was below what I needed for the role to actually work financially. So I countered. I was scared to, because this was my one shot and I didn't want to lose it over a number. I spelled out exactly what I needed: $42,000. I gave my reasoning and sent it. Then they went quiet for what felt like forever, and I was sure I'd overplayed it and blown the only opportunity I'd had in five months.
Then they came back and met my number exactly. I accepted on the spot.
Changing careers from software sales into product design was brutal by the numbers: 14 months, more than 200 applications, 205 rejections, 6 interviews, and one offer: a product design internship at Braze in New York.
I spent the first few months convinced I just needed a better portfolio. So I enrolled in a bootcamp, rebuilt my case studies from scratch, and watched endless teardowns of apps I'd never used. I was still working a software sales job through all of it, which meant most of my design work happened after 9 PM or on weekends. I applied through job boards obsessively: LinkedIn, Wellfound, Handshake, company career pages, refreshing confirmation emails like they meant something. Most of the time they meant an automated rejection two weeks later, or nothing at all. I kept a spreadsheet. Watching it climb past 100 applications and then past 150 without a single interview response made me question everything about the pivot. My portfolio, my bootcamp, my timing, whether product design was even the right move.
The six interviews I did get felt enormous, partly because they were so rare. I over-prepared for every one. Researching the company's product in detail, practicing design critiques out loud, writing down questions I actually wanted answered. The Braze process was thorough. Hybrid, New York-based, and the internship paid 60,000 USD annualized. None of that was guaranteed to go my way, and I knew it. I treated each round like it was my only shot, because the odds said it nearly was.
I had been working as a backend engineer in India for a few years, and I felt I had reached a limit in the kind of work I was seeing. I wanted to work in a different market, with different engineering problems, and to learn more than I already knew. So I looked for international roles instead of only reading the usual local listings. I found a job platform focused on relocation, which filters for companies that sponsor visas and pay for the move, and I spent a few evenings each week going through the listings methodically. That is how I found Mercari in Tokyo. I had been following the company for some time. They were doing interesting things at scale, and the backend opening looked like a good fit. I applied through the platform and heard nothing for about ten days, and I was sure the application was dead.
When they answered, the process had four structured rounds over about two months. The first was a live coding session where I shared my screen and solved problems in real time, the kind of session where your reasoning matters as much as the final answer. The second was a deep technical interview with an engineer, about architecture decisions and about how I think through microservices: trade-offs, failure modes, how I would scale a specific system under load. That one I enjoyed most. It felt like a real conversation between engineers. The third was a mixed technical and behavioural round with a hiring manager, mostly about how I work inside a team and how I handle uncertainty. The last round was with a VP and was mostly behavioural, but it also covered how quickly I could become productive in an unfamiliar tech stack. That was a fair question, because I was joining from a different market.
My first interview was at the beginning of December and the offer arrived in February. I accepted the full-time, on-site role at 55,000 USD and started to prepare for the move to Japan.
After two years of teaching myself, freelancing, and blogging while raising my family, I felt ready to apply for a full-time role. There were months where I wondered if I was cut out for this, weeks where the kids were sick and I barely opened my laptop, and more than a few projects I dropped halfway through once I realised I'd gone about them the wrong way. But every misstep taught me something, and my portfolio started to look like the work of someone who knew what they were doing.
When I finally started applying, I was selective about it. I sent four applications in total: one straight to a company whose product I used and admired, and three through a job board via a recruitment agency. I put real time into each one: tailoring the cover letter, making sure the portfolio was clean and loaded quickly, and double-checking that the code I linked to was something I was proud of. Two of those four came back with interview invitations. The first one moved fast, and within a couple of weeks I had an offer: a fully remote frontend developer role based in the UK, paying £30,000 a year. I accepted without much hesitation.
The interview felt manageable because I'd been preparing for two years. I'd talked about my work at meetups and conferences, written up my thinking on my blog, and taken on freelance clients who asked hard questions. So by the time I sat down with the hiring team, explaining my decisions and walking through my code felt natural.
I'd been working in QA for three years, splitting my time between manual testing and building out automation suites, mostly in Selenium and then Playwright once that became our team's preferred tool. When I decided to move, I wanted something fully remote and ideally a step up in responsibility. I set a rough target of around 25 roles and spent about two weeks working through listings on Indeed and LinkedIn Jobs, filtering hard for remote positions in the UK. Some ads were clearly outdated or vague about the actual stack, so I skipped those and focused on companies where the listing gave me enough detail to write a tailored cover letter. By the end I'd sent out 24 applications and was bracing for the usual silence.
The Manchester software company that hired me was different from the start. They replied within 48 hours, which caught me off guard. I'd already half-forgotten applying. There was no recruiter call. Their first reply came with a take-home task attached. They sent over a Figma file of a checkout flow and a staging URL, and asked me to write structured test cases covering the key scenarios, then build a small Playwright suite to automate the critical path. It was a realistic, well-scoped brief, not one of those tasks that expands into eight hours of work. I spent an evening on the test cases, thinking through edge cases like empty cart states and failed payment responses, then wrote the Playwright scripts the next morning. I kept the structure clean and added a short README explaining my decisions.
Two video calls followed. The first was technical. A senior engineer walked through my submission with me, asked why I'd prioritised certain scenarios, and we talked through how I'd scale the suite as the product grew. The second was a team-fit conversation with the engineering lead, much more relaxed, focused on how I collaborate with developers and product when bugs surface late in a sprint. At the end of that second call they offered me the role: QA Engineer, fully remote, £34,000. I took it. Start to offer was nineteen days, which felt fast after some of the drawn-out processes I'd heard about from friends.
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 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 applied to about 80 roles over two months, and League was the only company that responded with a take-home before any call.
Most of the applications went through job boards. I'd built a small spreadsheet to track them, partly because I knew I'd lose count otherwise, and partly because I wanted to look back later and see whether any of it was working. The honest answer was: not really. About 12% of applications got an automated rejection within 48 hours. About 6% got a recruiter screen. Most of the rest just disappeared.
League's take-home arrived in week six of the search. It was a pleasant surprise. Most companies don't reply for two weeks, then ask for forty-five minutes of pleasantries before they'll talk about the actual role. League sent a real anonymized dataset, asked four questions, and gave me a week to send back the answers in whatever format made sense.
The dataset was patient appointment data. A few hundred thousand rows, a handful of dimensions. The questions weren't trick questions. They wanted to know whether I could find the obvious thing first, whether I'd notice the less obvious thing after that, and whether I'd write up my findings so a non-analyst could read them.
I spent two evenings on it. About four hours in total. Most of that was writing. The analysis itself was straightforward, but the writeup needed to be tight. I sent back a six-page PDF with the four answers, a few caveats about the data quality, and a one-paragraph summary up top.
They moved me to a video interview the next week. Two analysts on the call, both of whom had read the writeup carefully. The questions were about what I'd left out and why. One of them asked, gently, whether I'd noticed an outlier I hadn't mentioned. I had, and I explained why I'd left it out. He said that was the answer he was looking for.
Round two was with the head of analytics. Less technical, more about how I worked with PMs and how I'd push back if asked to produce a number that didn't tell the whole story. We had a real, slightly uncomfortable conversation about a project where I'd been asked to do exactly that, and what I'd done about it.
The offer arrived three days later. CA$66,000 base, at the lower end of the band they'd quoted in the recruiter screen. I asked for the higher end, citing the depth of the take-home process and a competing offer that was close in cash but worse on scope. They came back at CA$70,000. I took it.
The thing I think mattered most: the take-home was a filter for how you communicate. The technical work was easy. The writeup was the test. Every analyst I've worked with since has said something similar about hiring. They want someone who can explain the answer to a stakeholder who doesn't care about the query.
80Applications
2Interviews
2 monthsSearch length
Job boardSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.