Technical Product Manager

Product-Oriented
Tech Lead

I enjoy building better structures.

Hyunmook Roh · 노현묵 HYUNMOOK ROH.

Now

Content & marketing group

Tech Lead · since 2021 · Seoul

Since

2012

The year I started building

Concurrent

100,000

Peak across 2 platforms, team of 4–5

Team

9

Engineers I led as team lead

About

Building and running services since 2012, most drawn to reducing inefficiency and improving structure.

Engineering

Structure as services grow

100K concurrent, staged infra moves

Product

What makes a product viable

User interviews, early apps, founding

Team

How a team works together

Team lead, building and running

Startups

Many stages of building

Founder · founding member · dev lead

Education

MBA · Computer Science

Entered 2026 · Bachelor's

Principles

Structures that need less work

Three ways I work

Stack

TypeScript · Next.js · AWS

+ Redis · SQS · Auto Scaling · CI/CD

AI / Agents

Structures where AI works safely

Claude Code · Codex harness · cross-review

Contact

Send a message

About

I studied computer science and started out as a developer. Building products as an early startup member and a founder, then leading an engineering team, widened my interest in structure from how a service is built to how products are made and how teams run. I am now adding the study of organizations and management to that experience.

Now · Career

Hold the spike. Make building light.

Current

Digital content & marketing group

~600 people · Tech Lead · Senior Manager

Apr 2021 – Present

I turn business needs into technical work, priorities, and schedules, and lead product development end to end. With an engineering team of up to nine, I build and run the whole service: web platform, APIs, payments, integrations, and AWS infrastructure.

  • Peak traffic100KGA users in the last 30 minutes, at peak
  • Views10MContent from each of 2 flagship templates
  • App Store#1 ×2Helped reach #1 twice
  • Build speed2–3 daysCore flow built; follow-ups by one junior
  • Team9Largest engineering team I led

Spike-proof traffic and standardized production

B2C interactive content platform

Apr 2021 – Present · Tech Lead · Full-stack

  • Fixed bottlenecks and slow queries at peak traffic and spread database load with queue-based processing.
  • Added a Redis and SQS based async waiting layer to absorb spikes that auto scaling alone could not.
  • Standardized recurring content into templates and modules, moving production from seniors to a single junior.
  • Moved from Cafe24 and NHN Cloud to AWS with Auto Scaling, CDN, and Aurora for stability and cost.

PHP · MySQL/Aurora · Redis · SQS · AWS · New Relic · Sentry

Designing a no-code platform and consolidating services

No-code SaaS platform

Sep 2021 – Apr 2026 · Tech Lead · Full-stack

  • When asked to build a platform that accepts directly uploaded external code, I flagged the security and operating risks, then designed the alternative: a no-code creation and publishing platform for non-developers.
  • Connected template creation, an editing tool, and publishing into one flow, reducing reliance on engineering.
  • In a consolidation that moved a legacy PHP content platform onto the no-code platform, scoped what to keep, remove, or split and designed a gradual migration.

TypeScript · Next.js · NestJS · MongoDB · Prisma · Redis · GitHub Actions

Journey

I have worked on the same interest in structure and efficiency from three seats: the service, the product, and the team.

01

Engineering

Structure as services grow

I have built and run content platforms, campaign services, and SaaS products. With a team of four to five, I ran two platforms at once, including a mobile app, handled up to 100,000 concurrent users, and moved infrastructure as they grew, thinking through the structure needed to keep them running and scaling.

02

Product & Business

What makes a product viable

In startups, building went hand in hand with asking whether users needed the product and what would let the business keep going. I took on that question from different seats: as a founder, a founding member, and a development lead.

03

Team & Management

How a team works together

As an engineering lead, I led a team of nine while still building myself. That is where I saw that how work is divided and who makes the calls shapes the outcome as much as the structure of the service does.

Startups

A few experiences along the way

From meeting users in person to designing reward structures,
I have worked across many stages of building a product.

Venture attempt

Senior service (2019–20)

Ran a YouTube channel

While shaping a service for older adults, I ran a YouTube channel myself. It was the stage of checking whether the service was something people actually needed in daily life.

Founding member

English learning app (2018–19)

Founding Team Member / React Native

I joined as a founding member and built an English learning app, turning a product that had no form yet into an app people could actually use.

Founder

Content curation service (2018)

Founder · Token economy

I founded a service that rewards content curation through a token economy. I designed the reward structure that keeps curators contributing and laid it out in a white paper, signed an MOU with an original content partner and a technical partnership with a token developer, and built the MVP while meeting investors.

Timeline

From code to teams

01

2008 – 2011

Starting with code

I studied computer science, led student councils and an academic club, and competed.

  • 08Freshman · department student council
  • 09Sophomore · university student council
  • 10Junior · lead of an academic club
  • 11Senior · ACM-ICPC award, top 100 of 3,000 in a startup competition

Straight into my first startup after graduating

02

2012 – 2014

First startup

At my first startup I built a lowest-price smart cart, working around 100 hours a week to sharpen my engineering and get the service off the ground.

I wanted to know how what I built actually sells

03

2014 – 2017

Seeing products from outside engineering

At a software distributor, I handled technical sales and cloud consulting. Sitting with customers and partners showed me what makes a product sell.

I gained skills beyond engineering and took a step toward seeing the whole picture

04

2017 – 2019

Building again, testing through startups

I came back to building as a development lead, then tried founding a startup myself and joining one as a founding member. I learned firsthand which products hold up and which do not.

Chasing a long-held dream of founding gave me a view of the whole, and showed me what I still lacked

05

2020 –

Back to engineering, this time as a team

Back to building, this time leading a team to build and keep services running.

  • 20–21Front-end developer and project lead for education and IoT services
  • 21Joined a content platform division as Tech Lead and began designing a no-code SaaS
  • 22–24Led a team of up to nine, built a structure that holds 100K-user peaks, standardized content production
  • 25Moved to an AI division through a group merger, continuing as Tech Lead and Senior Manager

I wanted to lead teams better and set direction that fits the business

06

2026

Entering an MBA

While continuing my current role, I entered an MBA program to understand, more systematically, the organizational and management problems I met while leading an engineering team.

To be continued

How I work

Instead of working longer, I build structures that need less work.
01

Tighter deadlines mean fixing structure first

When a schedule gets tight, adding hours is not my first move. I optimize the structure, split the work, and agree to move what is not urgent into a later refinement phase, because structure built now pays back as efficiency later.

02

Build everything, and what matters gets sloppy

Requests always arrive as "we need all of it." Building all of it blurs the core of the service and its audience, and leaves plenty of output but key features full of bugs. So I decide first what to leave out.

03

Sharing judgment makes a team faster

Rather than handing out tasks, I set a review period before development so the people doing the work size the scope and effort themselves. The more judgment they own, the more they grow, and over time the whole team gets more efficient.

All three are about changing how the work is structured instead of spending more time. I now apply the same principle to how AI agents work.

Stack

Tools I work with

Frontend

  • TypeScript
  • React
  • Next.js
  • SCSS
  • Tailwind CSS
  • Bootstrap

Backend

  • Node.js
  • Nest.js
  • PHP
  • Python

Data & Cache

  • MySQL
  • PostgreSQL
  • MongoDB
  • Redis
  • Memcached

Cloud & Infra

  • AWS
  • GCP
  • Azure
  • Cafe24
  • ECS
  • Lambda
  • Auto Scaling
  • SQS
  • CloudFront
  • Cloudflare Workers
  • Docker

CI/CD & Monitoring

  • GitHub Actions
  • CodePipeline
  • CodeDeploy
  • Vercel
  • CloudWatch
  • Sentry
  • New Relic

Collaboration

  • GitHub
  • Jira
  • Trello
  • Figma
  • Slack

AI / Agents

More than using AI, I build the structure it can work in safely.

  • Claude Code
  • Codex

+ Gemini · Copilot · Antigravity

  • Harness engineeringHooks · guardrails · command audit logs
  • Cross-model reviewCodex reviews Claude's changes before merge
  • Role-based sub-agentsPlanning · code review · TDD · security
  • Automated work logsPer-task records · Slack alerts

Contact

If you want to talk more about an experience or have a problem to solve together, please reach out.

A detailed career description is shared individually in hiring or collaboration discussions.