Mikiya’s working-holiday year: layoff, volleyball, then OTONOMOS

Mikiya’s Canadian year is dense because the plan was never “school first.” Strong at English since secondary school and vaguely drawn to looking cool working abroad, he spent about two years at teamLab enjoying people, new tech, and end-to-end project phases—even if mandatory office days look odd in hindsight. Family was unenthusiastic; he still left after aligning with his lead. Germany came first via Twitter-visible Japanese engineers and Berlin’s startup myth, until security worries and a preference for a thicker Japanese community flipped him to Vancouver—helped by knowing Frog’s track record.

From Japan he had already sprayed roughly 150 overseas applications over five months, with about ten document passes and one process that reached a third interview. After arriving in late August, the first Vancouver role landed in about one and a half to two months through an X post seeking someone with two to three years’ experience, plus a React/Node take-home that doubled as study. The company was small; when a main client contract died, several people including Mikiya were laid off. He had been full-stack with a backend lean among front-end-heavy teammates, learning React and TypeScript on the job after tutorial prep.

Round two took about four months, patched with Japan freelance via an agent and a car-wash job. He widened meetups beyond pure tech—volleyball contacts offered referrals even when they did not convert—and absorbed Frog advice to “own the interview room.” At OTONOMOS, found on LinkedIn, he presented a past project with code and friction stories instead of feature laundry lists, leading a one-to-ninety-minute engineering deep dive before a founder offer chat. Visa support surfaced only when he asked at the end—and was cheerfully approved through the company’s immigration consultants.

Now he works roughly nine-to-five, remote except one office day, on customer admin surfaces for a niche legal-tech product that helps incorporate in tax-advantaged jurisdictions. The Vancouver-heavy team of about twenty (with a UK pocket) keeps a flat four-person eng group reviewing each other’s PRs on React/TypeScript/Next, PHP/Laravel, and AWS. Early days meant inventing his own tickets. The hard part was not algorithms but understanding the business domain over three or four months of talking with the business team—exactly the unglamorous work that makes the “good guy who takes initiative” strategy stick.

Culture at OTONOMOS is flat enough that performance reviews are anonymous peer write-ups the founder summarizes, with raises tied partly to fundraising timing. Task hygiene can be soft because the PM also ships front-end most of the week, so engineers carve work with the business team themselves. He does not romanticize the niche: technical difficulty is moderate, domain learning took months. Still, the combination he keeps naming—being prepared, taking initiative, projecting “someone good to work with”—is what survived layoff, car-wash months, and a working-holiday clock that eventually flipped to an employer-supported work permit.