

Hi, I'm Jun
I build from simple to complex web apps with strong Javascript skill, Next.js, and Nodejs.
I'm a friendly web developer.Over eight years of hands-on experience shipping web products, with deep expertise in JavaScript.
- Next.js
- React
- Vue
- Node.js
Collaborated works
Domains I've shipped product in.
A decade of building means a few industries become familiar. Here are the ones whose rhythms I know best.
My Skills
Familiar tools
and technicals
- JavaScript
- TypeScript
- Next.js
- Node.js
- React
- Vue
- Angular
- Tailwind
- Material UI
- Ant Design
- Three.js
- Figma
- Photoshop
- VS Code
- Cursor
- Claude
- ChatGPT
- Docker
- MySQL
- DynamoDB
- AWS
- JavaScript
- TypeScript
- Next.js
- Node.js
- React
- Vue
- Angular
- Tailwind
- Material UI
- Ant Design
- Three.js
- Figma
- Photoshop
- VS Code
- Cursor
- Claude
- ChatGPT
- Docker
- MySQL
- DynamoDB
- AWS
Responsibilities
My scope of work
Web apps
Full-stack builds in TypeScript and Next.js — from a fresh repo to something users sign into.
- Next.js
- tRPC
- Prisma
Discovery
Scoping, technical planning, and the early decisions that decide whether the rest goes smoothly.
- Scoping
- Estimates
- Architecture
APIs & integrations
REST, GraphQL, webhooks, and the third-party glue work that makes the product feel finished.
- Node
- GraphQL
- Webhooks
Performance
Profiling, caching, and the boring infra changes that move Core Web Vitals into the green.
- Profiling
- Caching
- CDN / edge
Maintenance
Long-running partnerships — upgrades, observability, on-call, and shipping new things without breaking the old ones.
- Upgrades
- Tests
- On-call
Review
Code reviews, audit passes, and second opinions on architecture or implementation choices.
- Code review
- Audits
- Second opinions
A few opinions I've formed after a decade of writing software for the web.
01
Ship small, ship often
A merged PR today beats a perfect branch next month. Small diffs are easier to review, revert, and reason about.
02
Read before you write
Most bugs are in code I haven't read yet. I spend the first week of a new codebase reading and asking questions.
03
Tests where they earn it
Test the hard logic and the public surface. Skip the trivial getters. Coverage is a side effect, not a goal.
04
Write the boring docs
A short README and a runbook save the next engineer — sometimes future-me — a bad afternoon.
A few honest numbers
Years writing code
Production projects
Commits this year
Companies and Groups
Collaborate
Ways we can work together.
For company or group
Full-time
Joining a team for the long run — on-site in Hanoi or fully remote.
- Offline at your Hanoi office
- Or fully remote with overlapping hours
- Open to discuss relocation for the right fit
Freelance
Runs in parallel with my current role — independent scopes, clean handoffs.
- Remote-first, async-friendly
- Limited in-office visits when needed
- Project- or hours-based pricing
Part-time
Continuous embed alongside your team for ongoing product work.
- Minimum 20 hrs / week, remote
- Reachable for urgent calls during office hours
- In-office sessions when the work calls for it
Personal
Got an idea of your own?
If you're thinking about a website of your own — from a simple landing page to something more ambitious — get in touch and I'll send back a rough reference on timeline and price. No commitment.



