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.
The library wasn't a job application. I keep having to remind myself of that, because it ended up being the most effective job application I've ever sent.
I'd been working as an iOS engineer in Lisbon for three years and was quietly looking for somewhere with a more interesting design system. On the side I'd been tinkering with a small open-source UI library: three custom controls I'd wanted to exist for years and had finally gotten around to building. About 800 lines of Swift, well documented, with a sample app.
I posted it in late autumn. Tweeted about it, put it on the iOS subreddit, emailed a few iOS newsletters, including a small one called Lisbon Mobile that maybe two hundred people in the city's mobile dev scene read. The editor wrote it up the following week.
The lead engineer at a Lisbon software company saw that newsletter post. He DMed me on Twitter the same day. They'd been hiring an iOS engineer for about six weeks and the search wasn't going well. Would I be open to a chat?
I was. The chat ran thirty minutes. He'd cloned the library, built it, and integrated one of the controls into a side project of his. His questions were specific to decisions I'd made: why I'd used a particular pattern for state management, why one control had the API surface it did. We disagreed on one thing. It was the kind of conversation I'd wanted to be having for two years.
The first formal round was a coding screen with two of their senior engineers. A small refactor of a real piece of their codebase, two hours. I shipped a clean implementation with one small extension they hadn't asked for but that I thought made sense. They said the extension was the part they liked.
Round two was a code review session. They sent me a piece of their code in advance and asked me to be ready to review it. I came with ten comments. About half were right, two were wrong, and three opened up a discussion that ate the rest of the hour. Good interview.
Round three was a culture round with the head of product and the lead designer. Less an interview, more a conversation about how the team worked and what success looked like.
The offer was €50,000 base. I asked for €54,000, citing my current comp and the relocation impact. They came back at €52,000 plus a small relocation help. I accepted. Seven weeks of searching, nine applications. Eight of those went out before the library got picked up. The ninth was the role at the company, which I applied to formally after the chat with the lead, more paperwork than application.
The library is still open-source. I should probably write more of them.
Five years without a single interview will leave you rusty, and I knew passive review wouldn't fix that. So before I applied anywhere, I built a structured plan. I enrolled in an interview prep course, scheduled dozens of mock interviews with engineers I found through various platforms, and put serious time into system design. Not just reading about it. I whiteboarded distributed systems from scratch and stress-tested my explanations out loud. It took about two months before I felt like I was operating at the level the top-tier companies expect. Even then I wasn't sure it'd be enough.
I sourced interviews every way I could. I leaned on former colleagues for referrals, woke up dormant LinkedIn connections, answered inbound recruiter messages, and used a few lesser-known platforms that connect engineers straight with hiring teams. The goal was volume, because volume gives you leverage and calibration both. The first few onsites were rough. Not failures, but I could feel the gap between my prep and how I actually performed under pressure. By the fifth or sixth loop I started to settle. By the tenth I knew exactly how to pace a coding round, when to talk through my reasoning versus just write code, and how to structure a system-design answer so the interviewer could follow without getting lost. The whole thing became almost clinical.
I ended up with 7 offers out of 16 onsites, which still surprises me when I say it out loud. The spread of companies, comp packages, and team cultures gave me a clear picture of what I wanted. I accepted Airtable: full-time, hybrid, at $185,000. The role, the team's technical depth, and the product direction all lined up in a way the others didn't quite match. If you're coming back to the market after a long gap, here's what I'd tell you. Preparation compounds harder than you'd think, and mock interviews under realistic pressure are worth far more than another week of grinding problems alone.
The recruiter call came out of nowhere. The reason it came out of nowhere was that I'd answered a customer's question on Highbeam's community forum eighteen months earlier and had completely forgotten about it.
I'd been a solutions engineer at a mid-sized software company in Toronto for four years. Happy enough, but I'd been keeping an eye on roles at companies whose products I actually used. Highbeam was on that list. I'd been a power user for two years and had spent enough time in their community forum to know who the active people were.
The forum answer was about how to integrate Highbeam with a specific data warehouse setup. There was no good answer in their docs. I'd built a workaround for my own team and posted a writeup with code samples. About twenty people upvoted it. One person emailed me afterwards to say thanks. Then I forgot about it.
A year and a half later, a recruiter at Highbeam reached out. She'd been searching the forum for active community members who might fit a solutions engineer opening, found my writeup, and looked up my LinkedIn. The opening message was specific. She named the writeup, the role, and the salary band. She didn't ask for a CV in the first message. That came in the second.
The first call was forty-five minutes with the recruiter. She'd read my LinkedIn and knew what I'd been doing at my current company. The salary band she'd quoted was meaningfully better than what I was on, and that's the part that got me to take the second call.
Round two was a technical chat with the SE manager. Sixty minutes. We talked through how I'd handle three real customer scenarios. It was a genuinely useful conversation, the kind where I learned something about their product I hadn't known.
Round three was a customer demo. I had a week to prepare. The brief: imagine the customer is a fintech evaluating Highbeam against two competitors, you've got thirty minutes, walk us through a demo that addresses their specific concerns, detailed in this brief. I built a real demo on their free tier with a synthetic dataset. It ran forty minutes including questions. Two of the four people on the panel said it was the best demo they'd seen in the role's interview process.
Round four was a "tell me about your worst customer" round with two senior SEs. I had a real story.
Round five was the head of customer success. Thirty minutes, mostly cultural.
The offer was CA$100,000 base plus a quarterly bonus tied to retention metrics. I asked for CA$108,000, citing the depth of the process and the demo round specifically. They came back at CA$105,000 plus an additional week of vacation. I accepted.
If there's a lesson, it's this. The writeup I posted eighteen months earlier was more useful than any CV I've ever written. It worked because it was specific, public, and answered a real question.
When the Microsoft offer came in for a software engineer role in Redmond, my instinct was to say yes on the spot. I'd wanted to work there for a long time, and seeing the number in my inbox gave me that rush of relief that makes people accept things they probably shouldn't. But I made myself slow down. Instead of replying that afternoon, I opened a fresh document and started logging everything: every email, every phone call, every number on the table. That habit alone changed how I handled the whole conversation.
The initial package was a 109k base, a 120k stock grant vesting over four years, and a signing bonus that looked generous but had room to move. I knew it had room because I had a second process running in parallel with another company. Not a bluff. A real, ongoing conversation. That concurrent interest drove everything that followed. When I told the Microsoft recruiter I needed time to think, it wasn't a line. I genuinely had something else to weigh. That credibility shifted the dynamic. The recruiter stopped treating the offer as a formality and started treating it like something that might fall through.
I went through five interviews total before reaching this stage, so by the time the offer landed I had a good sense of how badly the team wanted to fill the role. I used that quietly. I never named a number first. Never said anything like "I was hoping for at least X." I only shared that I had competing interest and that the current package made it a hard call. Over two or three rounds of back-and-forth the base moved from 109k to 117k, the stock grant climbed from 120k to 130k, and the combined signing and start bonuses reached 35k. None of those movements needed me to be combative or even particularly assertive. What they needed was patience, preparation, and a refusal to anchor myself low by speaking first.
—Applications
5Interviews
—Search length
OtherSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.