I connect software platforms to the people who have to live inside them.
Find what needs to happen, then go build it. That has looked like hardware code, field testing, aviation research, project management, partnerships, and shipping embedded product. It reads like several different jobs until you notice it is the same one.
Born in the Korean countryside. Grew up in Seoul. Virginia and DC after that. Learned myself in New York, and I am still here, in Brooklyn.
Everything else on this desk is optional reading.
darpa project · mitre lab
I started as a hardware and software real world testing intern on a DARPA project, hired in through its contractor.
Then a summer at the MITRE lab in Charlottesville, on centrifuge work and quadcopters.
The centrifuge code held consistent RPM regardless of load. Those parts were printed in metal, in a federal lab. A few weeks of light work, on and off, until it ran clean.
booz allen hamilton
I studied multi-disciplinary engineering at the University of Virginia, focused on climate resiliency and unmanned aerial systems.
UAS and drone work, then aviation, at Booz Allen Hamilton. A summer first, then part time through my senior year, then full time once I graduated.
Defense projects alongside it: 3D printing, aerial analysis, and mobile apps built to encourage peer communication in Afghanistan.
I formed the approach for how we would answer the analysis, ran it with the team, and wrote the report that went out. If it did not hold up, that was mine.
new york
Moved to New York for startup life. Several years as an implementation consultant and project manager at a tech platform, first running the projects, then the partnerships and integrations behind them.
Back office work for LVMH, other high fashion houses, and a run of cool New York brands.
Then I went back to writing code on purpose. I embedded a widget across major OEM, retailer and marketplace storefronts, writing the SDK code and releasing it alongside each client's engineering team.
The clients were global appliance, audio and consumer electronics brands. Every triage and every solution came out of docs, logs and stack traces. No autocomplete, no assistant.
embedded warranty on world's #1 app
I picked up a warranty partnership that had not been decided on yet, and spent the next couple of seasons getting both halves right: the commercial terms and the technical shape. Neither was settled when it landed on me.
I was our lead on it, and on the client's campus often. Internally I worked compliance, design, and how we would communicate AI claims through every team that had a stake. Then I led the client's dev teams through end-to-end testing against our endpoints. That is the rigor you want when it is going into the most popular app in the world.
Directors in the afternoon. Developers in the evening. Same project either way.
“This partnership doesn't go live without you.”
drop a file at /media/warranty.png
- Ship 01 warranty embedded inside that app's shop, via SDK and API endpoints
- Ship 02 warranty at checkout across major OEM brand sites
- Ship 03 in-store program, for full omnichannel coverage
Did you buy a warranty on headphones, an appliance, or a mattress online? There's a good chance an SDK or an endpoint I helped ship is what put it there.
i · solution firstI don't hand back a ticket. I hand back a path, and often a branch.
ii · both roomsBusiness directors and client developers, in the same conversation. I've spent a long time interpreting between them.
iii · end to endScoping, compliance, build, launch. I stay on it until it's live.
Open to the right thing.
Also: occasional consultations on capturing a special moment inside a physical keepsake.
Two dogs, and the person I share them with.
You found the one I didn't label.