Norio’s Vancouver win—and the startup that went under beneath him

Norio planned the leap years out. A first Japan SE job meant Excel-heavy upstream work with development outsourced—so unsatisfying he left after two years despite thin skills. Tokyo refilled the gap with roughly three years of Java and Android client work. At twenty-seven he decided that at twenty-nine he would go abroad for stimulation working-holiday age limits still allowed, consulting Frog about a multi-year school-plus-holiday shape instead of a naked one-year gamble.

Speaking English was weak; daily Skype lessons built the courage to open his mouth. At ITD’s game-developer track he cared less about curriculum prestige than staying longer and practicing—especially explaining Java and C to greener classmates in English. Game math revisited in English was a bonus; Windows game projects did not convert to jobs. When co-op neared, game applications failed, so he pivoted to Android about a month out and found work in roughly a month more. Portfolio was thin because production history could be narrated; he still urges beginners to ship proof.

The company was a pre-revenue, investor-fueled startup. The Android lead who interviewed him lacked currency and soon quit after clashing with the CEO; Norio pushed peer review habits into a messy GitHub. A first paycheck deposited by cheque vanished when the bank could not collect—his account went negative over a holiday. Some colleagues went unpaid for months; headcount cratered; fired staff sued; accounts were frozen; a backend key person left; the company died. Norio was paid to the end and had a next gig lined up as the lights went out.

Recruiters who found his LinkedIn brought contract leads; technical interviews still applied. A six-month residency-style contract extended, then the extension evaporated a month before end with working-holiday time nearly gone—until a shorter Monster-sourced project appeared. He returned to Japan for personal and freelance-status reasons, joining a major IT firm as an Android developer who could point to English delivery. His distilled advice: prepare English before landing, earn Japan junior experience if you can, choose a T-shaped focus (his accidental Node API work later unlocked React Native trust), and remember that skill is what remains when a logo disappears.

He still loves Vancouver summers and workable offices, yet found the outdoor-weekend geography less magnetic than visitors promise—long drives to somewhere new, beautiful nature that did not quite hook him. The United States as a short trip (Las Vegas, New York) felt closer to delight. His closing creed is portable: if you can ship as a developer in English, meals follow wherever visas allow. Tokyo’s denser speaking circuit for Android, and maybe building an English-speaking Android community himself, became the constructive sequel to a company that literally disappeared.

For Android newcomers he still sequences learning ruthlessly: skim Java to Kotlin to Android via video courses so the map exists before the deep wells of object orientation and version-specific widgets swallow motivation. Accidental Node experience later pulled him into APIs and then React Native—not because everyone must go full-stack, but because a T-shape invites adjacent asks. The bankrupt startup remains the cautionary postcard from a city that loves new companies as much as it loves mountains.