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.
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.
I graduated in the spring and walked straight into one of the roughest hiring markets I'd seen described in any of the forums I was reading to prep. It didn't dent my optimism at first. I built a spreadsheet, set up job alerts across a few major boards, and started firing off applications. Over about three months I sent close to 200: tailored cover letters for some, quick-apply submissions for others when the listing was clearly a long shot. The rejections came in waves, sometimes five or six in a single afternoon, and a few roles just went silent after a first-round screen.
I made it to the interview stage at five companies. Four ran the standard process: a recruiter call, then one or two rounds of timed algorithmic problems. I'd been grinding practice problems for weeks, but there's a specific kind of pressure that hits when you're solving a graph traversal question while a stranger watches a timer count down, and I didn't always perform the way I knew I could. Those four ended without an offer. By month two the weight of it was getting to me. I was refreshing my inbox more than I should have, second-guessing whether I'd picked the right field at all.
The fifth company was different from the first message. The listing mentioned a project-based interview format, which I almost scrolled past because I assumed it was marketing language. It wasn't. The interviews were genuinely conversational. We walked through real engineering decisions, talked about tradeoffs I'd navigated in my capstone project, and got into how I approached debugging something I'd never seen before. It felt less like a performance and more like a preview of the actual job. The offer came in on-site, full-time, at 72k, with relocation assistance, profit sharing, and unlimited vacation. After months of quiet rejections, the relief was physical. My honest takeaway: keep applying through the noise, but pay close attention to the companies whose process actually gives you room to show what you can do.
I applied to about 80 roles over two months, and League was the only company that responded with a take-home before any call.
Most of the applications went through job boards. I'd built a small spreadsheet to track them, partly because I knew I'd lose count otherwise, and partly because I wanted to look back later and see whether any of it was working. The honest answer was: not really. About 12% of applications got an automated rejection within 48 hours. About 6% got a recruiter screen. Most of the rest just disappeared.
League's take-home arrived in week six of the search. It was a pleasant surprise. Most companies that don't reply for two weeks then ask for forty-five minutes of pleasantries before they'll talk about the actual role. League just sent a real anonymised dataset, asked four questions, and gave me a week to send back the answers in whatever format made sense.
The dataset was patient appointment data. A few hundred thousand rows, a handful of dimensions. The questions weren't trick questions. They wanted to know whether I could find the obvious thing first, whether I'd notice the less obvious thing after that, and whether I'd write up my findings so a non-analyst could read them.
I spent two evenings on it. About four hours total. Most of that was writing. The analysis itself was straightforward, but the writeup needed to be tight. I sent back a six-page PDF with the four answers, a few caveats about the data quality, and a one-paragraph summary up top.
They moved me to a video interview the next week. Two analysts on the call, both of whom had read the writeup carefully. The questions were about what I'd left out and why. One of them asked, gently, whether I'd noticed an outlier I hadn't mentioned. I had, and I explained why I'd left it out. He said that was the answer he was looking for.
Round two was with the head of analytics. Less technical, more about how I worked with PMs and how I'd push back if asked to produce a number that didn't tell the whole story. We had a real, slightly uncomfortable conversation about a project where I'd been asked to do exactly that, and what I'd done about it.
The offer arrived three days later. CA$66,000 base, at the lower end of the band they'd quoted in the recruiter screen. I asked for the higher end, citing the depth of the take-home process and a competing offer that was close in cash but worse on scope. They came back at CA$70,000. Accepted.
The thing I think mattered most: the take-home wasn't a filter for technical skill. It was a filter for how you communicate. The technical work was easy. The writeup was the test. Every analyst I've worked with since has said something similar about hiring. They're not looking for someone who can run the query, they're looking for someone who can explain the answer to a stakeholder who doesn't care about the query.
80Applications
2Interviews
2 monthsSearch length
Job boardSource
Move closer to your next job offer
Get expert help with your CV, interviews, salary negotiation and job search.