Soomin Hwang
ENKO

Work with me

Frontend and delivery for browser apps that handle 3D visualization and large datasets — remote.

I work on the part that is harder than the layout — rendering large datasets without stalling the browser, keeping multi-megabyte visualization libraries off the critical path, and shipping it all through a release pipeline the team can actually trust. I have built 3D structure viewers, multi-megabyte visualization library integrations, and chart dashboards over large datasets, all in production products.

What I take on

Heavy viewer & rendering integration

Integrating 3D/WebGL viewers and node-heavy interactive workspaces into an existing app — including isolating multi-megabyte libraries route by route so initial load does not suffer.

Molstar + RDKit viewer integration →See all 3D & data visualization case studies (5)

Performance & bundle audit

Finding what actually makes a React app slow, then fixing it structurally: route-scoped loading, code splitting, and render-path profiling — reported with before/after numbers you can reproduce.

32MB → 6.5MB bundle cut →See all Performance case studies (1)

CI/CD & test automation

Standing up or tightening the release path — containerized E2E, full-suite regression runs, dependency and quality scanning, and build/image optimization.

One pipeline, three products →See all CI/CD & deployment case studies (4)

Results at a glance

Main bundle
32MB→6.5MB
Lighthouse Performance
29→78
Manual regression
~5 hours→~1 hour
Docker image size
1.3GB→500MB
Browse all case studies →

How a project runs

  1. 1

    Inquiry review

    · 1-2 business days

    You send the product and the problem; I assess whether it is something I can help with and reply. If it is not, I will say so.

  2. 2

    Scoping

    · 2-3 days

    A 30-minute call, then I write the scope document — deliverables, duration, what is included and what is not, and the access I will need.

  3. 3

    Agreement

    · 1-2 days

    We adjust the scope document together and confirm it.

  4. 4

    Delivery

    · Set during scoping

    A written progress update once a week. Live questions during the CET-morning window.

  5. 5

    Review & handover

    · Set during scoping

    A review round, fixes, then documentation of what changed and how it was measured.

From first inquiry to starting work is typically under a week. The delivery timeline is set together during scoping.

How I work

Korea-based, overlapping with European mornings

Late afternoon in Korea overlaps with the Central European morning, giving a dependable 3-4 hour window for live collaboration each day (17:00 KST is 09:00 CET). I worked across exactly that gap for a year and eight months with a production plant team in Serbia, coordinating process definitions and feedback — and worked remotely for a Korean startup.

English as the working language

Including direct coordination with overseas teams on technical requirements and process definitions.

Documentation outlives the contract

I document what changed, why, and how it was measured, so the team can carry the work forward once the engagement ends. On a short contract, that documentation is effectively the entire handover.

Discuss a project

Send a brief overview of the product and the technical challenge you're addressing. I'll follow up with an assessment of scope and fit.

Get in touch