About

Hello, I'm Heo Jae Won, a frontend developer.
From planning to screens, I build it through with the team. As team lead 4 times, I led planning, role assignment and scheduling.
I actively use AI tools to work more productively, and keep verifying the code along the way.
Values
Not stopping at features,a developer who checks and fixes to the end
Leading a team to the end
Led planning through scheduling as team lead 4 times. On CapTeam I designed the student and admin screen structure as team lead and owned the frontend on my own; the team won the school capstone project grand prize.
Beyond the screen, into operations
Repeated API calls are not only a speed problem — they add load on the server. I checked in the Network tab where calls piled up and cut the number of calls. I keep a record of what the frontend can solve and what needs a backend change.
Verifying after using AI
I check what AI produces on the screen, Network, E2E and mobile viewports. Code being written and code working in the real service are two different things.
Tech Stack
I pick the tool the work calls for, and record where and why I used it
Each entry carries the context in which I actually used it.
01
ReactFrontendSplit screens into components and reused repeated UI behind a defined interface. Organised the states a screen can hold — inputs, modals, loading, errors — with useState, and moved flows outside the screen into custom hooks so components stay focused on rendering.
Used alongside
React RouterUsed the URL as the unit of a screen, splitting routes and separating detail views with dynamic parameters.
ZustandManaged auth state and the login session in a global store, shared across screens.
AxiosOwned communication with the backend API, and reduced the number of calls after checking in the Network tab where repeated calls piled up.
02
JavaScriptFrontendWrite on ES6+ syntax. Shape server responses to the screen's structure with map, filter, find and slice, and handle async flows with async/await and Promises. Design the failure path alongside the happy path with try/catch/finally, so a failed request never leaves the user with an empty screen.
03
CSS ModulesStylingIsolate styles per component so class names never collide. Colour, spacing and typography live as CSS variables in one place, and light and dark themes swap behind the same variable names.
Learning
04
Next.jsFrontendLearning the App Router and server component model — where to place the boundary between rendering and data fetching, and how far the code shipped in the client bundle can be reduced.
05
TypeScriptFrontendLearning to catch errors before runtime with types: defining a function's input and output first, and making the points where a value may be absent visible in the type.
06
Tailwind CSSStylingLearning utility-class styling, measured against the CSS Modules I use today: which approach stays easier to read and change as a project grows.
Experience
Awards
- Grand prize, school capstone project · CapTeam2026.03 — 2026.08
- School hackathon, 3rd place (Excellence Award) · Byeongi2026.07
- Grand prize, school portfolio contest2026.06
- 3rd place, Level Up program · JICHINI2026.01 — 2026.03
Education
2025 — 2028
Gyeongbuk Software Meister High School
Expected graduation
Activity & Record
2026
- Class president, Year 2 Class 32026.08 — Present
- Vice president, WINE web development club2026.08 — Present
- Head of sports, student council2026.08 — Present
2025
- Academic improvement scholarship2025.12
- Study trip to Singapore2025.08
Contact
Building services that are convenientand made for the people using them.
I'm looking forward to hearing from you.
