Hawoon Joh 조하운 · 누와
Product Engineer — frontend, platform, and everything between
I build products end to end. That started as frontend work — Next.js and TypeScript — and kept expanding, because the interesting problems never stayed in one layer. Today that means leading a small engineering team, planning a product line, and owning the pipeline that ships it.
There was no straight line here. I studied spatial design, worked a non-dev job, went through a backend bootcamp, then taught myself frontend. Every step was the same move: learn whatever the work needed next.
Spatial design to production infrastructure, one self-taught step at a time.
Kookmin University
Four years spent thinking about how people move through a space and what makes a layout legible. It turns out to be the same question a UI asks, which is why the switch felt less like a career change than a change of material.
Design work
Working alongside software without being able to build it got old fast. I wanted to be the one shipping the thing, not handing off a file and hoping.
Bootcamp
I learned the server side before the client side. Backwards, by portfolio standards — but knowing what a query costs and how a schema is shaped has been quietly useful in every frontend decision since.
Self-taught
React, then Next.js and TypeScript, built by making things that had to actually work. No course completion certificate — just a pile of projects, each one harder than the last.
CloudHospital
Joined to build the frontend and ended up responsible for the platform around it — the marketing site and CMS, SEO, performance, and eventually the deployment pipeline. Now leading a team of four to eight.
Synolink
Leading synolink.ai end to end — three products, one modular suite. The largest thing I have been responsible for, and the first where the architecture decisions are mine to make.
Every step, I taught myself the next thing the work needed.
P / 01Performance and SEO are product features, not cleanup tasks.
P / 02Build the tool that builds the thing.
P / 03Never leave anything at POC level — dig deeper into the details.
At CloudHospital I own the frontend of icloudhospital.com and its backoffice, plus the marketing site and the CMS behind it. Building it was the first half of the job.
The second half is everything that decides whether the work reaches anyone: search and GEO visibility, page performance, and reading traffic closely enough to turn it into conversion. Same principle as P/01 — that is product work, not maintenance.
Boxout — 01
Every client hospital gets its own deployment. Doing that by hand does not scale past a handful, so I built the pipeline that provisions and ships them automatically — cluster workloads, GitOps-driven releases, and DNS wired up per tenant without anyone touching a console.
New product line — synolink.ai
A modular SaaS suite for running an online business. Each product stands alone — or plugs into the others as an extension.
Planned and led end to end (총괄).
Visual web builderIn development
A builder in the Webflow and Squarespace class, with AI-generated content, SEO- and GEO-optimized output, and i18n built in for global leads and marketing.
Omnichannel messagingLive
Customer conversations from every channel in one inbox.
Medical EHRIn development
An electronic health record platform, built to slot into the same suite rather than sit off to the side as a silo.
Next.js, TypeScript, React, Tailwind CSS, Motion
Kubernetes, ArgoCD, Azure, GitHub Actions, CI/CD, Vercel
SEO / GEO, Web performance, Analytics and conversion, i18n, Design systems, Team leadership
Already shipping inside the Synolink CMS as generated content; the interesting part is what else it can own.
Kubernetes and ArgoCD I use daily. Observability is the gap I am closing now.
Motion, 3D, and visual editors — the places where the design degree still pays rent.
Modding and watchmaking. A movement is a system you can hold: hundreds of parts, no abstraction layer, and it either keeps time or it does not. Nothing has taught me more about finishing a job properly.
On for most of the working day, and most of the non-working day.
The one part of the week with no backlog and no code review.
Fig. 2 — inputs. Watchmaking is where P/03 came from: nothing stays at POC level once it is open on the bench.
P/02 — build the tool that builds the thing. Three receipts.
A form builder powered by react-jsonschema-form with shadcn/ui components. Generates dynamic forms from JSON Schema through a visual builder interface.
A visual UI editor and content builder with a component-driven architecture. Drag and drop to assemble rich content layouts.
A GitHub Action that automates Node.js package versioning via PR labels. Supports major/minor/patch bumps, monorepo paths, custom commit messages, tag generation, and dry-run mode.
Set in Syne and Outfit. Built with Next.js, Tailwind CSS, and Motion.
About — Issue 01 · Seoul · 2026
— END —