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.
56Stories
8Verified offers
15Countries
16 / 44Median / Mean applications
Latest job wins
56 stories · page 1 of 6
Filtered by newest stories across all roles and locations.
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 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 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.
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 slow and 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.
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. 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. 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.
I'd been working as a backend engineer in India for a few years and felt like I'd hit a ceiling on the kind of exposure I was getting. I wanted to work in a different market, take on different engineering problems, and push myself past what I already knew. So I started targeting international roles specifically instead of just scrolling the usual local listings. I found a relocation-focused job platform that filtered for companies willing to sponsor and relocate candidates, and I spent a few evenings a week working through listings methodically. That's how Mercari in Tokyo showed up. I'd been following the company for a while. They were doing interesting things at scale, and the backend opening looked like a real fit. I applied through the platform and heard nothing for about ten days, which had me convinced it had gone nowhere.
When they did come back, the process ran in four structured rounds over roughly two months. The first was a live coding screen where I shared my screen and worked through problems in real time, the kind of session where your thought process counts as much as the final answer. The second was a deep technical interview with an engineer, focused on architecture decisions and how I reason about microservices: trade-offs, failure modes, how I'd 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, leaning toward how I'd work within a team and handle ambiguity. The last round was with a VP and was mostly behavioural, though it also dug into how quickly I could get productive in an unfamiliar tech stack. Fair concern, given I'd be joining from a different market entirely.
My first interview was in early December and the offer came through in February. I accepted the full-time, on-site role at 55,000 USD and started getting ready for the move to Japan.
I wasn't actively job-hunting when I came across Picnic. They turned up in a long-form article about startups going after food waste in Europe, and the mission grabbed me right away. The piece laid out how their model was cutting down on the surplus and spoilage that drag on traditional supermarkets. It was the specificity that got me: a concrete operational problem with measurable impact. I stopped scrolling and read the whole thing. No recruiter had ever sent me anything that made me feel that way, so I went straight to their careers page that same evening and applied for a senior software engineer role through the site.
The process was thorough and well-run. Five interview rounds sounds like a lot on paper, but Picnic had clearly thought about what each stage was meant to test. There was a technical screen early on focused on systems design, which I liked because it got straight to the substance instead of burning an hour on trivia. The later rounds brought in engineers I'd actually be working with, and the conversations felt honest rather than performative. People told me about real tradeoffs they'd made and real mistakes they'd learned from. What stuck with me most was their stated promise to move from application to offer within four weeks. They kept it.
The offer came in at 70,000 EUR for a full-time, on-site role in Amsterdam. Relocating to the Netherlands was a big call, but by the time the offer landed I'd already pictured myself there. I accepted.
I was a recent graduate looking for my first sales role. No commercial experience, a degree that had nothing to do with sales, and a private suspicion that I'd be bad at the job for at least the first six months. I'd tried the job-board route for two weeks and gotten exactly one rejection back.
The pivot was simple. I made a list of forty SaaS companies in Austin I'd seen hiring SDRs in the previous month. I wrote one cold email template, three sentences, asking for a fifteen-minute intro chat about the role, not asking for a job. The first sentence I rewrote for each company specifically. I sent the forty emails over four days.
The first reply came back that afternoon. Eight people replied in total. Three of those turned into real interview loops. One was a SaaS company in the healthcare niche.
Their process was the fastest. The intro chat was thirty minutes with the SDR manager. He'd read my email, my LinkedIn, and the one Notion page I'd linked, a writeup of an outreach experiment I'd run for a friend's startup as a favour. We mostly talked about that experiment. He asked what had worked, what hadn't, and what I'd do differently next time.
The second interview was a forty-five-minute role-play with the VP of sales. The scenario: thirty seconds to introduce myself on a cold call, ninety seconds to handle the first objection. We did three different versions. I bombed the first one. The second was OK. The third was actually good. He said he liked that I'd tried different openings rather than reusing the same one.
There was a third "interview" the same day with a senior SDR, less an interview than a conversation about the hours, the comp structure, and what the team was like at 7 PM on a Thursday. I asked direct questions and got direct answers.
The offer was US$58,000 base plus uncapped commission with a realistic OTE of US$80,000 in the first year. I asked specifically about the ramp and whether the OTE was based on a tenured rep or a first-year rep. They were honest: first-year reps usually hit about 80% of OTE, which would put me around US$64,000 all-in. I asked for a US$2,000 sign-on bonus and a slightly higher base. They came back with US$62,000 base and the sign-on. Realistic year-one comp: around US$78,000.
Forty cold emails took four hours to write and send. Most got no reply.
Eighteen applications into my search, Mews offered me a Senior PM role: €96k base, equity, fully remote out of Amsterdam. I nearly took it.
The interviews were polished. The hiring manager kept coming back to ownership, to giving PMs real authority over the roadmap, to moving fast without the usual enterprise drag. I left each round feeling energized. The equity conversation was straightforward, the base hit my number, and the remote setup meant I could stay put. I was close to signing without thinking much harder about it.
Before I did, though, I spent a couple of evenings on LinkedIn cross-referencing people who'd held PM roles at Mews in the last two years. I found two former PMs and sent short, direct messages saying I had an offer and asking for fifteen minutes. Both replied within a day, which probably told me something on its own. What they said lined up too closely to wave off. The roadmap got rewritten roughly every six weeks, not because the market had moved but because senior leadership kept reversing decisions they'd already handed down. Two PMs had quit in the single quarter before my offer, neither of them as part of any planned transition. One of them told me she'd spent her last month rebuilding a spec she'd already shipped once. That detail stuck with me more than the rest.
I declined the next day. I kept the message short and professional and gave no specific reason. Finding something else took longer than I'd hoped after that, and there were a few weeks where I questioned the call. I never regretted it, though.
I'd been looking for new opportunities for about a month when I showed up to a Kotlin meetup in Toronto one February evening, mostly just to get out of the apartment and talk shop with other Android developers. The turnout was decent, maybe thirty people, and I ended up next to an engineer from Wattpad during the break. We started comparing notes on Compose Multiplatform, specifically state management and some of the rougher edges with shared UI logic across platforms. What I thought would be a five-minute chat stretched to nearly an hour. We swapped contacts before we left, and I didn't think much of it beyond a good networking moment.
About a week later he messaged me out of nowhere. A senior Android Developer position had just opened up internally, and he asked if he could put my name in. I said yes immediately. I'd done some light research on Wattpad before: Toronto-based, product-focused, reasonably sized engineering team, and what I found was encouraging. Over the next five weeks or so I went through six applications total for other roles while this one moved forward, but the Wattpad process was by far the most structured and engaging. Three rounds. A hiring manager screen where we talked about my experience with production-scale Android apps and what I wanted next. A technical live-code session where they handed me a real recursive layout bug they'd actually hit in production, and that one kept me on my toes because the fix wasn't obvious until I traced the measurement pass carefully. Then a team panel with three engineers that felt more like a genuine conversation than an interrogation.
The offer landed about a week after the final panel, thirty-eight days after that initial meetup conversation. It came in at CA$125,000. I pushed back once, citing market rate for senior Android work in Toronto. They came back with CA$130,000. I accepted.
I came to Germany as an international worker with a self-taught frontend skill set and a portfolio built through online courses and personal projects. It felt like a long shot. The rejections piled up fast. We're talking hundreds. Some were automated no-replies, some were polite one-liners, and a few were detailed enough to sting. Every time a promising application went cold, I had to talk myself out of reading too much into it.
What kept things moving was persistence and casting a wide net through the right channels. I was active on LinkedIn, Xing, and Germany's Make-it-in-Germany program, which exists specifically to help international workers find their way through the local job market. LinkedIn was where I got the most traction. I tightened up my profile, started connecting with recruiters directly, and put my portfolio links front and center. I tried to treat each rejection as a data point, not a verdict. If my HTML and CSS projects weren't getting attention, I pushed harder on JavaScript. If a cover letter wasn't landing, I rewrote it. Slow, unglamorous work, but methodical.
Eventually I got through to a company willing to look past the unconventional background. The interview process had four rounds, covering everything from a technical skills screen to a cultural fit conversation, and each one felt like a real test of how far I'd actually come. When the offer arrived for a full-time junior frontend developer role in a hybrid setup at 45,000 EUR, I accepted.
—Applications
4Interviews
—Search length
LinkedInSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.