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.
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 quietly 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, the one to that company, after the conversation. Everything else flowed from a twenty-minute hallway conversation I almost didn't have.
Finding a Singapore-based Engineering Manager role took me about 14 weeks from first application to signed offer, and it was more of a grind than I'd anticipated. I sent out 38 applications in total, leaning heavily on job boards and company career pages in the early weeks, but the responses were inconsistent and the timelines stretched long. Singapore's market for EM roles felt tighter than I'd expected. Most postings drew strong local and regional candidates, and as someone considering relocation, I had to work harder to stand out. After a few weeks of slow traction, I shifted my energy toward in-person networking. That was the move that actually mattered.
The break came when I attended a regional leadership offsite where the CTO of a Singapore engineering scale-up was a keynote speaker. His talk was about scaling engineering organizations across Southeast Asia, exactly the problem space I'd been thinking about, so the conversation afterward felt natural rather than forced. I didn't pitch myself that day. Instead I waited two weeks, then followed up with a short document outlining what I'd genuinely want to learn about their org structure, their current team challenges, and how they thought about EM scope at their stage of growth. That document seemed to signal intent without being pushy, and it got me into the process. Nine rounds followed over several weeks: technical conversations, a take-home exercise focused on org design, a values interview with the founder that went deeper than I'd expected, and a few stakeholder calls with senior engineers I'd potentially be managing.
The final package came in at $165,000 USD. The base was honestly a bit below what comparable US-market EM roles were offering at the time, but the company included expat health insurance and covered SG relocation costs, which made the overall picture work. After 102 days and 9 interview rounds, I accepted. The process was long, but the networking-first pivot was what got me in the door.
My move to Amazon's London office didn't start with a job application. It started with someone noticing my work. I hadn't been searching or refreshing job boards. I was heads-down, shipping features and trying to do the work well. Then a manager who'd seen what I built reached out directly and invited me to explore an SDE II transfer to London. That was when it hit me that the opportunity was real and I needed to take it seriously.
Once I committed, I spent a couple of weeks preparing before the three interview rounds began. I knew Amazon's loop would lean heavily on behavioural questions tied to the leadership principles, so I didn't build a wide, shallow bank of stories. Instead I picked a small set of genuinely strong examples from my recent work and mapped each one carefully to the principles I expected most: Bias for Action, Ownership, Deliver Results. My thinking was that a few deeply rehearsed stories, told with real specificity and confidence, would land better than improvising something new under pressure every time. I made sure I could walk through each example with a tight structure: the situation, what I decided, why I decided it, and what actually shipped or changed as a result.
Across the three rounds I reused those same core stories on purpose, tweaking the framing depending on what the interviewer was probing for. It felt almost too simple. But it worked. All three interviewers voted to hire, and I got the SDE II offer for the London role at £78,000. The on-site requirement was something I'd already factored in and was fine with.
The lesson I keep coming back to is that visible, high-quality work is its own kind of networking. I didn't send a single cold message or touch my profile. The opportunity came to me because of what I'd already shipped. That's worth more than most job-search tactics I've read about.
Breaking into product management took me about five months, and the choice that mattered most was picking focus over a scattergun approach. Instead of applying to every PM opening I could find, I narrowed my search to the education sector, an industry I already had real experience in. That context paid off more than I'd guessed. When interviewers asked why a feature should exist or how to prioritize a roadmap, I could answer with actual conviction instead of inventing hypotheticals on the spot.
The portfolio came together almost in parallel with the applications. I started publishing product case studies online, working through real problems in edtech products I used or admired, writing out my thinking on user research, prioritization frameworks, and trade-offs. It was painstaking to put together, but it gave me something concrete to point to in conversations. Recruiters and hiring managers could read my reasoning before we even got on a call, which filtered me into serious conversations faster. Beyond the case studies, I leaned hard on LinkedIn, not just to apply but to genuinely network. I reached out to PMs already working in education and asked for feedback on my case studies and honest takes on what they looked for in junior candidates. Those conversations shaped how I interviewed more than any prep course did, and a few of those connections eventually became the direct referrals that opened the right doors. Nearly all of my meaningful opportunities came through networking rather than cold applications.
The 150 days felt long while I was living them. Twenty interviews across multiple companies in Bangalore meant a lot of repetition, a lot of rejection, and a few weeks where I genuinely questioned whether the transition was realistic. But by the end I had more than three offers to weigh, and I accepted one that felt right both on role scope and the hybrid setup. The salary came in around 18,000 USD a year, which for an Associate PM position felt like a fair starting point. Staying in an industry I already understood, and making my thinking visible in public, turned out to be a faster way in than starting from zero.
I'd been quietly exploring 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 honestly 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, calmly, citing market rate for senior Android work in Toronto. They came back with CA$130,000. I accepted without hesitation.
The talk was five minutes long. Two people from a Boston edtech company found me afterwards. Three months later I was a UX researcher there.
I'd been a UX researcher for six years and had a small but specific reputation in the diary-studies sub-niche of the field. I gave maybe one or two talks a year at conferences. This one was at a UX research conference in Boston in late autumn, a five-minute lightning slot I almost didn't apply to because it felt too short to do the topic justice.
The talk went well. The audience was about a hundred and twenty people, most of them researchers, and the questions afterwards continued in the hallway for a good half-hour. Two of the people who stopped me were from the company's UX research team. They told me they'd been looking for a researcher with diary-studies experience for several months and hadn't found anyone they wanted to talk to. Could we talk later that week?
We talked the following Tuesday. It was an informal conversation with the head of research, no formal interview structure. We talked about their work, my work, the methods they were trying to use, and where the team was struggling. By the end she said she'd like to put me through a real interview process if I was open to it.
I was. The process was three interviews.
The first was a portfolio review with the head of research and one senior researcher. I walked through three studies. They cared most about how I'd handled the messy parts: what I'd done when participants dropped out of a longitudinal study, how I'd reframed a research question after the first round of data told us something unexpected.
The second was a whiteboard exercise with two product managers. They gave me a real research question their team was struggling with, how to measure whether a particular education product was actually changing student behaviour over a semester, and asked me to design a study on the spot. I asked twenty clarifying questions for the first ten minutes and then sketched a design. They pushed back on one method choice. We argued for a few minutes and ended up with a hybrid approach I think was better than my first version.
The third was a final interview with the head of product. Mostly behavioural. The question I remember was "tell me about a time you were the only person on the team who thought a study was a bad idea." I had an example. We talked about it for a while.
The offer arrived a week later. US$112,000 base. I asked for a few thousand more, citing the seniority of the work and the conversations I'd been having elsewhere. They came back at US$118,000. I accepted.
I didn't apply through a job board. I never sent a CV through a careers page. The conference talk was the application. The interview process was a formality on top of conversations that had already established I was the right person for the role. If I hadn't given that talk, I wouldn't have the job.
The role didn't exist when we first met. It existed three months later because a conversation over a beer turned into something.
I was at a marketing meetup in late autumn. The kind of event where most people network in a way that's obvious and forced, and I'd mostly given up on those events being useful. I'd ended up in a corner of the room with two people I didn't know, one of them the head of marketing at Koala. We talked for about thirty minutes. Not about jobs, not about hiring. Just about a campaign I'd run earlier that year and what I'd learned positioning a B2C ecommerce brand against a much larger competitor.
We swapped numbers because she said she might want to follow up on something specific from that campaign. I didn't expect anything to come of it.
Three months later she emailed. The team had been thinking about hiring a marketing manager focused on exactly the kind of brand work I'd described. The role hadn't been advertised yet, and she wanted to talk to me before they posted it.
The first interview was her, ninety minutes, in their office. We didn't really do a formal interview. We walked through three of her current campaigns and she asked what I'd do differently. I disagreed with one of them quite directly. We argued for about ten minutes and she ended it by saying the disagreement was the most useful part.
The second interview was with the head of growth and the head of product. Sixty minutes. They asked the standard "tell me about a time" questions. I gave the standard answers. The interesting part was the last fifteen minutes, when they asked what I'd prioritise in the first ninety days. I'd thought about it on the train.
Round three was a short campaign-pitch exercise. They sent a one-paragraph brief: the company was launching a new product line and wanted a five-slide pitch on how to position it. I had three days. I sent back four slides. The head of marketing later said the cut from five to four was the part she liked most.
The offer was AU$84,000. I asked for the option to work from home three days a week, since the JD had said hybrid two days, and they agreed without negotiation. I asked for AU$86,000. They said yes within an hour.
Total applications I sent during the search: four. None got past the recruiter screen. What worked was a thirty-minute conversation at an event I almost didn't go to, with someone I didn't know, about a project I'd run a year earlier.
The lesson, if there is one: I had no plan walking into that event. But I had a clear answer to "what's the best campaign you've ever worked on," because I'd been chewing on it for months. That was enough.
4Applications
3Interviews
3 monthsSearch length
NetworkingSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.