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. 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.
One twenty-minute conversation at a logistics meetup became an internal job posting that arrived in my inbox before it was on the company's careers page.
I had been an operations manager at a small ecommerce company in Mexico City for three years. The company grew fast for two years and then stopped growing. There was nothing more I could change there. I wanted a job at a logistics company, but nothing was happening. Part of the reason was that I was not really applying. The other part was that most logistics companies in CDMX do not post their jobs publicly, so it was hard to know what was open.
I went to a logistics meetup in late autumn, mostly because a friend was speaking. The COO of a logistics company in the city was in the audience, and we stood next to each other in the coffee break. We talked for about twenty minutes. She told me about a problem her team had at that moment: how to grow warehouse operations from one site to four. I told her how we solved a similar problem at my company, but at half the size. We exchanged WhatsApp numbers because she wanted to send me a paper she had been reading about it.
Three weeks later she wrote to me. Her team was going to post an operations manager job, and she wanted to talk to me before they published it. Could I come for a coffee?
The "coffee" was ninety minutes with her and one more senior person from operations. It was not really an interview. We went through three real problems they had, and most of the time I asked questions and they answered. At the end she said she would put me into their official process if I was interested.
The process was two interviews and a written exercise.
The first interview was with the COO and the head of warehouse operations. Sixty minutes. They asked how I would grow the warehouse network from one site to four. I had already thought about this, so my answer was specific.
The second part was a written exercise. They gave me a one-page brief about a real problem, opening a new warehouse in Monterrey, and asked for a six-page plan in one week. I sent five pages and a one-page appendix. In the next round we talked mostly about the appendix.
The last round was a conversation with the founder, mostly about equity and about what staying for three years would look like. He was direct. The equity they offered was large compared to the salary.
The offer was US$45,000 base plus equity. I asked for US$48,000 and a little more equity, and I showed them my own numbers for what the equity would be worth in a realistic exit. They came back with US$48,000 and a small increase in equity. I took the job.
I sent only one real application in the whole search.
Finding an Engineering Manager role in Singapore took me about 14 weeks from the first application to a signed offer, and it was harder than I expected. I sent 38 applications in total, mostly through job boards and company career pages in the early weeks, but the replies were irregular and the timelines were long. The Singapore market for EM roles was tighter than I expected. Most jobs attracted strong local and regional candidates, and because I was applying from abroad, I had to work harder to stand out. After a few slow weeks I moved my effort to meeting people in person.
The change came at a regional leadership offsite, where the CTO of a Singapore engineering scale-up was a keynote speaker. His talk was about scaling engineering organisations across Southeast Asia, exactly the problem I had been thinking about, so the conversation afterwards was easy. I did not pitch myself that day. I waited two weeks and then sent him a short document, setting out what I wanted to learn about their organisation structure, their current team problems, and how they thought about the scope of an EM role at their stage of growth. That document got me into the process. Nine rounds followed over several weeks: technical conversations, a take-home exercise on organisation design, a values interview with the founder that went deeper than I expected, and a few calls with senior engineers I would possibly manage.
The final package was US$165,000. The base is a little below what comparable EM roles in the US were paying at that time, but the company added expat health insurance and paid my relocation to Singapore, which made the whole picture work. After 102 days and 9 rounds of interviews, I said yes.
A manager who'd seen what I was building got in touch directly and invited me to explore an SDE II transfer to Amazon's London office. I hadn't been looking.
Once I committed, I spent a couple of weeks preparing before the three interview rounds began. I knew Amazon's interview process would lean on behavioural questions tied to the leadership principles, so I picked a small set of 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 we actually delivered 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. 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.
Breaking into product management took me about five months, and focus was the choice that mattered most. I stopped applying to every PM opening I could find and narrowed my search to the education sector, where I already had real experience. That context paid off more than I had guessed. When interviewers asked why a feature should exist, or how to prioritise a roadmap, I could answer from experience instead of inventing examples on the spot.
The portfolio came together at the same time as the applications. I started publishing product case studies online, working through real problems in edtech products I used or admired, and writing out my thinking on user research, prioritisation frameworks and trade-offs. It was slow work, 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 got me into serious conversations faster. I also used LinkedIn a lot, for networking as much as for applying. I got in touch with PMs already working in education and asked them for feedback on my case studies, and for honest opinions on what they wanted from junior candidates. Those conversations shaped how I interviewed more than any preparation course did, and a few of those connections became the referrals that opened the right doors. Almost every real opportunity I got came through people rather than through cold applications.
The 150 days felt long while I was living them. Twenty interviews across several companies in Bangalore meant a lot of repetition, a lot of rejection, and a few weeks when I asked myself whether the move was realistic. But by the end I had more than three offers to weigh, and I took the one that felt right on both the scope of the role and the hybrid arrangement. The CTC came to around US$18,000 a year, which for an Associate PM position felt like a fair starting point.
I'd been looking for new opportunities for about a month when I showed up to a Kotlin meetup in Toronto one February evening, cold enough that half the room still had their toques on, mostly 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, on state management and some of the rougher edges with shared UI logic across platforms. 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. It looked encouraging. Over the next five weeks or so I went through six applications in 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 the GTA. They came back with CA$130,000. I said yes.
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 fall, 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 afterward 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 behavior 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 behavioral. 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. $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 $118,000. I accepted.
I didn't apply through a job board. I never sent a resume 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.
I was at a marketing meetup in late autumn. 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 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, bluntly. 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 last fifteen minutes were the interesting part, 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 job ad 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. A thirty-minute conversation did it, at an event I almost didn't go to, with someone I didn't know, about a project I'd run a year earlier.
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.