TetherMax
Crypto trading-fee cashback platform with 100K+ users. Took over the web + mobile frontend, rebuilt it in-house, and own it end to end.
Next.jsTypeScriptReact Native
100K+ users · bundle ~2MB → ~250KB
Hi, I'm Taewook
NEXT.JS · REACT NATIVE · TYPESCRIPT · REACT
AVAILABLE FOR WORK
SINGAPORE · 2026Frontend
Engineer
I build fast, readable, product-driven interfaces — with an auditor's eye for what breaks.
/ About
Five years in engineering — two of them auditing Solidity, now focused on frontend. I care about interaction, reliability, and ownership, and I ship products that are easy to use, easy to read, and easy to maintain.
BASED IN SINGAPORE · EMPLOYMENT PASS HOLDER
/ Experience
Neovate
2024 — PresentFrontend Engineer → Lead (2026)
Rebuilt the web + mobile frontend of TetherMax, a crypto cashback platform with 100K+ users, in-house —cutting the JS bundle 85–90% (~2MB → 200–300KB). Now leading the frontend team.
Next.jsTypeScriptReact NativePerformance Optimization
HAECHI LABS
2019 — 2021Smart Contract Auditor
Contract from 2019, full-time from late 2020. Delivered 100+ DeFi & ERC-20 audits securing $5B+ in TVL, and shipped production Solidity to client spec.
SolidityEthereumSecurity Audit
01
FOUR PROJECTS · REAL SHIPSSelected Work
TongTong
Couples track shared expenses and assets in one place. Web, app, server, DB — built solo, live on Google Play.
Next.jsReact NativeNestJSSupabase
Solo (Web · App · Server · DB) Timeline 2026 · ~2 months Platform Web + Android
Discover Singapore
A fog-of-war map over real GPS. Offline tiles, one-polygon fog, noise-hardened dwell detection.
React NativeExpoMapLibreH3
120k features → 1 polygon
Contract Audit
100+ DeFi & ERC-20 smart contract audits at HAECHI LABS — where I learned to read code by asking how it breaks.
SolidityHardhatDeFi
100+ audits · $5B+ TVL
/ Technical Strengths
WHAT THE CASE STUDIES ADD UP TOPerformance & Bundle
Image pipelines, dynamic imports, bundle trimming — cut TetherMax's JS ~85–90%. When React itself is the bottleneck, I move work out of the render loop (refs + rAF, zero per-frame re-renders).
Data Fetching & Caching
Next.js App Router per-route caching, TanStack Query for server state — aggressive where content is static, exempt where staleness costs users money.
Cross-Platform
React Native alongside web from a ~90% shared codebase — one team, both platforms, releases in lockstep.
Reliability & Process
CI/CD and code-review standards set up and adopted team-wide. Sentry + Mixpanel observability. Pure-core architecture that makes logic unit-testable.
Security Habits
Two years auditing Solidity — untrusted input, exploit scenarios, and "how does this break?" carried into every frontend.
02
Side experiments where I go one layer down: render loops without React, layout from the camera frustum, an agent that needed a face.Lab
Personal — runs 24/7 on a Mac mini↗
Charlos
A personal AI agent with a face — and the face grows itself: new skills declare their own dashboard tabs.
WEB · PUBLISHING↗
MD Press
Upload markdown, pick a theme, get a URL. The gap between writing and publishing, closed.
3D · R3F↗
Beer Can
Grab a can, it spins with your drag — then coasts before settling back to idle.
3D · R3F↗
Arc Gallery
Photo cards wrap onto a 3D ring around the camera. Scroll to zoom, move to rotate, click to fan out an album.
WEB · PERSONAL↗
Wedding Invite
03
TOOLS I REACH FORStack
Frontend
Next.jsReact NativeTypeScriptReact
UI / Motion
Framer MotionThree.jsReact Three Fiber
State / Data
ZustandTanStack QueryNestJSSupabase
Quality / Ops
SentryMixpanelVercelCI/CD
Where I started
SolidityHardhatDeFi
04
HOW I BUILD — THREE PRINCIPLESWorking Style
01
Treat it like it's mine
Ownership doesn't stop at the merged PR. When something breaks at 3am, I want to be the one who knows why.
02
Read it like an auditor, build it like a teammate
Auditing Solidity taught me to ask "how does this break?" before "does this work?" The same habit shapes how I write for others: if a teammate can't follow it in one read, it's not done.
03
Reliability is the baseline, not a feature
Users never notice when it works — they leave when it doesn't. I'd rather catch a failure in CI than in a support ticket.
/ LET'S BUILD