daily users
Dabbl
Led the frontend for ShopRite's Downtime Dollars campaign and shipped the client work that earned a follow-on Kroger contract.

San Francisco · Product + AI/ML · 2026
Justin Chang builds systems for the moments when the problem is still unclear.
The unconventional decisions started early. Each turn looked separate at the time; together, they became a way of thinking.

Look for the overlooked path. Then do the work.
Field note 01I found a nontraditional route through California's education system, studied the probabilities, and committed. The bet led to admission at Berkeley, UCLA, and UC San Diego.
Philosophy felt like the most mathematical corner of the humanities—a way to sharpen logic, reading, and writing while preparing for medicine.
Medicine was not a casual idea. I entered Columbia's post-baccalaureate program to complete the science required to pursue it fully.
I learned what kind of life I did not want. For two unsettled years, programming kept returning—part necessity, part fascination, all possibility.
Code turned ideas into artifacts. The appeal was bigger than a job: with the skill, the number of futures I could build seemed to expand.
San Francisco revealed a higher standard. The response was simple: get close to stronger engineers, ship for real users, and close the distance.
daily users
Led the frontend for ShopRite's Downtime Dollars campaign and shipped the client work that earned a follow-on Kroger contract.
subcontractor MAU
Moved into San Francisco's engineering culture, saw the gap clearly, and doubled down until measurable product impact followed.
“The first lesson was how much I didn’t know. The second was that I could close the gap.”
Three teams. A promotion for exceptional performance. A deliberate move from software engineering into machine learning before the next bet began.
“I wanted to know whether I was good among great engineers.”
The answer created enough confidence to plan the next four years with intention.
Consecutive high-performance cycles
Ads metric audit coverage
Action rate for severe-harm models
Two years building independently turned product instincts, software, ML, writing, sales, and operations into one operating system. The combination was the advantage.

Custom human and dog action models, optional identity association, and a production system that reached two beta users. VLM-assisted annotation cut the expensive part—the dataset—by one to two orders of magnitude.
A social and long-form content platform that understood products, images, seasons, and offers—then produced coherent multi-page technical writing inside a 4,096-token world.
The first product created leads. Those customers revealed harder, more valuable problems, and custom product work became the company's commercial engine.
Small experiments. Fast loops. Ideas made tangible before they had permission to become products.
VLM autodistillation
Vision Pro timeline
Spatial simulation
At OpenAI, the setting changed. The pattern did not: find the ambiguous problem, build the system, and make its value visible.
A multi-source intelligence platform for the people who need to understand what is happening, why it matters, and what changed.
Member of Technical Staff · OpenAI
“Find the ambiguous problem. Build the system. Make its value visible.”
Different industries. Different technologies. The same operating principles keep resurfacing.
A working product is often the clearest argument.
Interface, model, data, infrastructure, operations, and adoption are connected.
Writing, philosophy, product judgment, software, and ML improve one another.
Acquire the missing capability before the next bet requires it.
Adoption and changed behavior matter more than novelty alone.
Running, tennis, the beach, Muir Woods, and a dog who keeps becoming the inspiration—or product manager—for the next experiment.

The next field test: camping. Then backpacking.

The boundary between life and building is porous. Practical problems become experiments; experiments sometimes become products.
The work I want next is where the answer is not obvious yet—and where building it is the fastest way to find out.
Product leadership · Technical depth · Ambitious teams