Hi, I’m Woody. I’m a designer, builder and overthinker.
I’m a Design Engineer and Product Designer in New York City. I work across product strategy, interaction design, and implementation to make complex software easier to use.
Drag to spin · click a place7/7
New York City40.71° N 74.01° W
Boarding passLeg 7/7
HNLHawaii
NYCNew York City
- Passenger
- KIM / WOODY
- Carrier
- Midnight Health
- Dates
- 2026–Present
HNL-NYC-07
Experience & Education
Now
I’m building Midnight Health, bringing wearable, nutrition, and daily health context together. Get in touch about design engineering and product design opportunities.
What people say
“Woody is self-motivated and flexible. He has immense desire to grow. He's restless (in the good sense) and is always looking for his next adventure.”
Boris WolfsonSenior Product Manager, Microsoft 365 Dynamics & AI “What sets Woody apart is his rare combination of strategic thinking and genuine relationship building. He thinks deeply about the "why" behind his designs and brings people along in the process. He elevates not just the work, but everyone around him.”
Hunter NoldinSenior Product Designer, Lowe's “Woody is incredibly knowledgeable and proactive. I learned a lot watching him interact with users and stakeholders, and his candor made for more effective collaboration. I've been inspired to grow as a designer thanks to his influence.”
Peter NguyenUX Designer, Echo Global Logistics
Woody’s Tooling
For shaping ideas, building products, and keeping things running. 11 tools; open one for the notes.
A shared canvas makes interface decisions easier to discuss. Components, variants, and prototypes let me work through the details while keeping the broader system in view.
Useful for turning an idea into something I can react to. Bringing existing components and visual rules into a prototype makes it easier to explore a direction before investing in the full build.
Coding agents work directly in the repository, which keeps the conversation close to the code. Claude Code does most of the coding, Codex the implementation and review loop, and Antigravity shows how an agent approaches a task so I can check the work it produces. The useful part is the loop between intent, implementation, and verification.
Visit Claude Code (opens in a new tab)Visit Codex (opens in a new tab)Visit Antigravity (opens in a new tab)
Written rubrics become structured questions a model answers about a piece of text. Useful as a qualitative evaluator beside deterministic checks, never as ground truth, and storing its answers keeps each decision reproducible.
Pull requests give a change a clear boundary: what changed, why, and how it was checked. The history becomes a record I can return to when a design or engineering decision needs context.
A useful place to turn a broad idea into work small enough to finish. Issues and projects keep the next step, its context, and the remaining decisions in one place.
A preview URL makes the work tangible before it reaches production. Reviewing an actual page on different screens is more useful than trying to settle every detail from a static capture.
Managed Postgres keeps the data model familiar without database-server maintenance. Supabase puts authentication beside the data, with access rules expressed at the database layer, which makes it easier to reason about who can read or change a record. Neon fits smaller services that need real persistence.
Visit Supabase (opens in a new tab)Visit Neon (opens in a new tab)
Events and funnels help connect a design decision to what people actually do. Useful for finding where a flow loses people and deciding what deserves a closer look.
A repeatable set of cases gives prompt and model changes something concrete to answer to. I can compare outputs against explicit expectations instead of relying on a few convincing examples.
Email is part of the product experience, especially at sign-in. A focused API and delivery logs make it easier to connect the application flow to what was actually sent.