CASE STUDY · 2020—2021

Tuning a streaming UI inside an English-first team.

UX engineering on a major Japanese streaming service inside an organization where English is the official language. Iterated player UI, layouts, and small-but-frequent UX touches, working across teams in English.

Period

2020 — 2021
8 months

Role

UX Engineer

Stack

JavaScript, Sass,
AWS, Smarty, Figma

Team

10—50
Streaming

Daily-feel improvements on a service many people watch.

A major Japanese streaming service operating inside an organization with English as the official internal language. I joined as a UX Engineer focused on iterative UI/UX improvements — not redesigns, but the daily-feel changes that compound across many viewers.

Small changes still compound across the viewing experience.

Carry UX intent across languages and cultures.

Iterated player and layout UX in small loops

Streaming services live by thousands of small UX decisions: tap targets, transition timings, where the hover state lands. Most of my contributions sat in this register — frequent, small, observed after shipping. Lots of micro-improvements, lots of "is this better or worse" conversations.

Worked the design ↔ engineering boundary in English

Daily standups, design reviews, and code reviews ran in English with engineers and designers from many backgrounds. The hard skill being built wasn't JavaScript — it was lossless communication of UX intent across languages and cultures.

Handling small points of friction.

This experience still shows up in how I design products today: looking for the small friction points people touch repeatedly, shipping a narrow improvement, then observing whether it feels better. Working in English also sharpened how I explain design intent in Figma, specs, and reviews.