Full-stack developer · Seoul

I ship the whole stack

I design the data model, build the API, and craft the interface on top of it — so features arrive whole, not half-finished. Here is a selection of what I have shipped.

How I work

One engineer, the whole feature

Most work needs a schema change, an API endpoint, and a screen to drive it. I do all three, which means fewer handoffs, tighter feedback loops, and features that actually ship.

Backend that holds up

Normalized schemas, idempotent workers, and row-level security — the parts that quietly keep data correct under load.

APIs you can trust

Typed contracts, thoughtful caching, and honest error states, so the front end never has to guess what the server meant.

Interfaces that feel fast

Optimistic updates, accessible components, and layouts that stay responsive from a warehouse phone to a 4K monitor.

How a feature travels through the stack

day 1

Schema

Model the data first — migrations, constraints, and RLS from the start.

day 2

API

Typed endpoints with tests, honest errors, and pagination that scales.

day 3-4

Interface

Screens wired to the real API — loading, empty, and error states included.

day 5

Ship & observe

Feature-flagged rollout with logs and metrics watching the seams.

Have a product that needs the full stack?

I'm open to full-time roles and focused contract work — especially gnarly data problems and greenfield builds. Tell me what you're building.