Hi, I'm Taewook
AVAILABLE FOR WORK

Frontend
Engineer

I build fast, readable, product-driven interfaces, with an auditor's eye for what breaks.

Taewook Yang, portrait

/ 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 - Present
Frontend Engineer → Lead (2026)

Took TetherMax's web + mobile frontend (100K+ users) in-house in 2024, then drove the rebrand and performance overhaul: JS down 85-90%, in-app screens 2-3s → 0.5s. Now leading the frontend team.

Next.jsTypeScriptReact NativePerformance Optimization

HAECHI LABS

2019 - 2021
Smart Contract Auditor

Contract from 2019, full-time from late 2020. 100+ DeFi & ERC-20 audits securing $5B+ in TVL; production Solidity shipped to client spec.

SolidityEthereumSecurity Audit

Selected Work

/ Technical Strengths

Performance & Bundle

Image pipelines, dynamic imports, bundle trimming: TetherMax JS down 85-90%. When React is the bottleneck, work moves out of the render loop (refs + rAF).

Data Fetching & Caching

App Router per-route caching + TanStack Query, aggressive where static, exempt where staleness costs users money.

Cross-Platform

React Native + WebView hybrid, ~90% code reuse. Native for interaction, WebView for weekly-changing screens, pre-warmed to <0.5s.

Reliability & Process

CI/CD and code-review standards adopted team-wide. Sentry + Mixpanel observability. Pure cores that unit-test.

Security Habits

Two years auditing Solidity. Untrusted input and "how does this break?" carried into every frontend.

AI-Native Engineering

Agent workflows instrumented, not just used: lifecycle hooks, token-derived identity, and dashboards that make agent state readable. The LLM parses intent; it never designs.

Stack

Frontend
Next.jsReact NativeTypeScriptReact
UI / Motion
Framer MotionThree.jsReact Three Fiber
State / Data
ZustandTanStack QueryNestJSSupabase
Quality / Ops
SentryMixpanelVercelCI/CD
Where I started
SolidityHardhatDeFi

Lab

Working 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?" Same for writing: 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, so I'd rather catch a failure in CI than in a support ticket.