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.
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.
Looking for ML roles in Europe took longer and was more draining than I'd expected. I sent out 32 applications over roughly three months, and the pattern of rejections got predictable fast: most teams either wanted a PhD as a hard filter or were exclusively chasing LLM fine-tuning experience. My background is recommender systems and production ML tooling, the unglamorous plumbing that keeps models running at scale, and that combination landed awkwardly in a lot of job descriptions written with transformer research in mind. I got through to interviews at six places total, which felt like a low conversion rate for the volume I was pushing, and a couple of those early rounds ended with feedback that basically confirmed I was the wrong shape for what they were building.
The offer I eventually accepted came through a referral, and that was the only thing that broke the pattern. An ex-colleague from a previous startup had joined Zalando in Berlin and flagged my name internally when a Senior ML Engineer position opened up. That internal signal seemed to get my application read differently. The recruiter reached out within a week, which hadn't happened anywhere else in this search. The process itself was rigorous: three technical rounds covering system design, coding, and a deep dive into my recsys work in production, plus a separate interview that genuinely surprised me. They called it a paper-discussion round. The format was that I had to argue both sides of a recent ML paper, switching positions mid-conversation when the interviewer pushed back. It was uncomfortable in a way I respected. They wanted to see how I thought, not just what I'd memorized.
The offer came in at 95,000 EUR for a full-time, on-site role in Berlin. The base is below what comparable US roles pay, and I knew that going in, but the package included 30 days PTO and full visa support, which made the real-world math work for my situation. Ninety-one days after I started applying, I accepted.
The case study went up on a Tuesday afternoon. By Thursday morning I had three replies in my LinkedIn inbox.
I'd been thinking about job-hunting for a while without doing anything about it. The plan had always been polish the portfolio first, then start applying. After two months of polish that clearly wasn't converging on a finished portfolio, I tried the opposite: pick one project, write it up properly, post it publicly, and let people tell me whether it was good enough.
The project was an onboarding redesign for a fintech I had nothing to do with. I'd been a customer and noticed three friction points. Over a long weekend I prototyped a flow that fixed two of them, built a Figma file with annotated frames, and posted a 600-word writeup on LinkedIn explaining the trade-offs.
N26 replied within a day. Their head of design said the writing was the part that had stopped her. Most case studies she sees are visual evidence with no reasoning attached, and she wanted to talk to designers who could think about trade-offs out loud.
The first call was 45 minutes with the head of design. We didn't talk about N26 specifically until the last ten minutes. Most of it was her asking how I'd handled specific decisions in past projects: when I'd disagreed with a PM, when I'd shipped something I knew was a compromise, what I'd learned the hard way about onboarding metrics. A real interview, not a "tell me about yourself" one.
Round two was a portfolio walkthrough with two designers from the team. Sixty minutes, three case studies. They cared about the in-between decisions. Why this typeface and not the obvious one. Why I'd recommended killing a feature instead of fixing it. The questions kept circling back to constraints rather than craft.
Round three was a paid take-home: redesign their settings flow, document the trade-offs in a written summary, time-boxed at five hours. I treated it as a real project, didn't over-polish, and shipped exactly what fit in five hours. The summary was three paragraphs on what I'd cut, why, and what I'd do next with a full week.
The final round was a 30-minute conversation with the CTO. Not a values check disguised as a chat, but a real conversation about the role, the team, what they'd ship over the next quarter, and whether I'd stay for two years. He was the most direct interviewer of the loop.
The offer was €58,000. I asked once for a bump on the base, citing the scope they'd described in the final round. They came back the same day with the same number plus a sign-on that covered relocation. I accepted.
I sent 18 applications during this whole search. Three were the immediate replies to the case study post. The rest went to companies I'd targeted because their product overlapped with the case-study domain. Volume wasn't the lever. Specificity was.
The whole thing moved faster than I expected. A recruiter reached out about the Sales Development Representative role at AlertMedia in Austin, and I almost passed because the posted comp felt low for the market. I went ahead anyway, sent in my application, and within about four weeks I had an offer in hand. Twenty-seven days total from first contact to close, across four interviews. But the number on that first offer sheet wasn't where I needed it, and I wasn't going to just sign and hope.
The standard SDR package was $52k base plus $20k in commission on their existing commission plan. I'd done enough research to know the OTE ceiling was the real problem. Not that $72k total was impossible to reach, but the structure made it nearly impossible to exceed, and the accelerators didn't kick in until 120%, a threshold most reps never hit during ramp. So instead of countering with a number out of thin air, I spent a weekend building a written analysis of their own funnel. I pulled what I could from public data and from what they'd shared in the interviews: average ramp timelines for SDRs in their segment, top-quartile MQL-to-meeting conversion rates, and the actual math on what a tiered accelerator above 110% would cost them versus what it would produce in pipeline. I framed it not as "pay me more" but as "here's how you get more output if you restructure the upside."
It worked. They came back and rebuilt the plan: $52k base with $30k in commission, and accelerators starting at 110% instead of 120%. That put my on-target earnings at $82k, exactly where I needed to land. The base didn't move, but the variable comp was redone from the ground up. Going in with a written analysis rather than a verbal counter is what made the difference. It gave them something concrete to take to finance.
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.
An Instagram DM became a freelance project, and the freelance project became a full-time role three months later. I wouldn't have predicted any of those steps.
I'd been working as a freelance brand designer in Buenos Aires for two years. The work was inconsistent. Some months were fine. Some weren't. I'd been thinking about going back to a studio environment for the routine and the team, but most of the studios I wanted to work at were either based in São Paulo or paying in pesos at rates I couldn't make work.
One Buenos Aires design studio was different. They were small, six people, and they paid in USD via Deel because most of their clients were US-based. They had a public Instagram where they posted their work for a specific recurring client, a US-based health tech company. I'd been following them for about a year.
I had a thought. What if the studio would be open to a small spec project? I picked their main public client and rebuilt three concept variations of how I'd reposition the brand. I was honest with myself about it: this was speculative, the studio almost certainly hadn't asked for my opinion, and I was just going to send it as a portfolio piece, not a job application.
I DMed the founder. The message was three sentences. I'd been following the work, I'd built three variations of how I'd approach a brand refresh for the public client, did she have ten minutes to look at it? I attached a single Figma link.
She replied two hours later. The variations weren't what they were going to ship, she was direct about that, but they were the kind of work she wanted to be commissioning, and was I available for a one-off project they'd been needing to outsource? I was.
The project was a brand refresh for a different client. Three weeks of work. Five-figure fee, paid in USD. I shipped it on time. The client signed off without revisions, which is rare.
A month later the founder asked if I was open to a longer engagement. We agreed on a three-month rolling contract. After two months she asked if I'd consider going full-time. The role was permanent, paid in USD via Deel, and would mean working with the studio's existing six-person team rather than continuing as a contractor.
The offer was US$30,000 base. A number that doesn't look like much in dollar terms but works at the current exchange rate and is meaningfully better than what I'd have made independently. I asked for US$36,000, citing the depth of the work I'd already shipped and the cost of switching from contractor to employee structure. They came back at US$36,000.
I accepted. I'd sent two real applications during the entire search. Both went to job boards and both went unanswered. The Instagram DM was the application. I keep telling other designers that the studios you actually want to work at hire from their DMs, not from their job listings. They mostly don't believe me until they try it.
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.
Fresh out of a coding bootcamp, I treated the job hunt like a numbers game with a twist. I knew I didn't have a CS degree or years of experience to lean on, so the one edge I could build was making it personal. Instead of dropping resumes into application portals and watching them vanish into black holes, I cold-emailed real engineers and hiring managers at the companies I actually wanted to work at. I spent evenings tracking down contact details on LinkedIn, personal blogs, and GitHub profiles, then writing emails that referenced specific projects or posts so they didn't read like spam. I sent over 150 of those and got a 22% response rate, far better than anything the portals gave me.
Across roughly three months, I reached out to 291 companies total and turned that into 32 phone screens. Some weeks I had five or six calls stacked up, and I kept a spreadsheet tracking where each one stood. The rejection rate was brutal and relentless. Plenty of calls ended with "we're looking for someone more senior" or just went silent after what felt like a good conversation. There were stretches where I wondered whether the bootcamp had been a mistake. But the pipeline stayed full because I kept the outreach volume high even when my confidence wasn't.
The other thing that helped was how I sequenced my onsites. I scheduled interviews at companies I was less excited about first, so I could get the rust off, work through the nerves, and figure out where I was stumbling before walking into the rooms that mattered to me. By the time I interviewed at the company at the top of my list, I had 90 days of reps behind me and it showed. I landed a full-time software engineering role there at $95,000. The big takeaway: a personal email to a human beats a polished application into a void, and ordering your interviews from low-stakes to high-stakes is one of the most underrated edges a junior candidate can build.
I'd been watching a US software company for a few months before I made my move. They were clearly building toward Latin America. Blog posts hinted at regional plans, a couple of Spanish-language social posts felt like they were testing the waters, and the job board listed nothing in the region yet. So rather than wait for a posting that might never come, I spent a weekend writing a one-page pitch aimed straight at their CEO. My argument was that expanding into LATAM without a Spanish-fluent full-stack developer embedded in the timezone was a real execution risk, and that I was the person to close that gap. I kept it tight, specific to their product, and sent it cold on a Tuesday morning.
He replied the same day, and we had a call scheduled within 48 hours. That response time told me the timing had landed. What followed was four rounds of interviews over about a month, in a format unlike anything I'd done before. The founder runs an async-first organization, so there were no synchronous technical interviews at all. Instead I recorded Loom walkthroughs of my approach to two architecture problems and submitted written exercises that had me think through a localization strategy for one of their core features. It was slower and more careful than a typical panel loop, but it suited the way I work. I had room to think things through rather than perform under artificial pressure, and I think that showed in my answers.
The offer came in at USD 65,000 for a full-time, on-site role in Buenos Aires, with quarterly meet-ups in Mexico City. The on-site structure made sense given the regional mandate. Being physically present in BA was the whole point of the pitch. At that salary in Buenos Aires the purchasing power is strong, so while the number isn't the ceiling of the market, the real-world value made it easy to accept. Thirty-one days from first email to signed offer. I accepted the same afternoon I got it.
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 genuinely 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, not a test. 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 actual move to Japan. It was the outcome I'd been working toward for a while, and as demanding as the process was, it felt worth it.
—Applications
4Interviews
—Search length
Job boardSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.