Skip to main content
강홍재/ James

QA Lead / Engineer · 14+ years · Product Builder

강홍재 / James

Fourteen-plus years as a QA engineer, up close with product failure modes, user problems, and release risk. I started by finding defects; today I catch what could go wrong at design time and build the product with that same eye. Open to QA Lead/Engineer roles, and the people and teams I can build alongside.

QA Lead / Engineer
14+ years across mobile, web, and embedded - managing release risk end to end.
Product Builder
Builds tools for release decisions, prioritization, and experiments.
Open to
QA Lead / Engineer roles · people and teams to build with · AI workflow integration.

Positioning

Up close with product risk for 14+ years.

Risk sense

The release-meeting seat where "is this safe to ship?" comes up most often. What could go wrong belongs in the feature design, not the post-mortem.

User problem

Tracker tickets are only a slice of user pain. The frustrations users never bother to file are the ones that should move the product backlog.

Release judgement

GO / HOLD starts with data and ends with a person. The score, the reasoning, and the dissent should live on one screen so the decision holds up later.

Validation loop

Testing isn't a pre-release ritual; it's a loop that narrows a hypothesis. The reproducible-experiment instinct a QA engineer has carries into product discovery.

QA Leadership

Built and led the QA org, 0→1.

0→1 QA team · release gates

Built QA teams 0→1 in Korea and the US, and set risk-based QA strategy and release gates as the organization's standard.

Regulated quality (QMR)

Ran the ISO 13485 quality management system and handled MFDS certification and innovative-medical-device designation as Quality Management Representative (QMR).

Quality metrics

Issue lead time down 20% · duplicate issues down 11.81% · E2E coverage 93%.

If we should build something - or think it through together.

Collaboration, hiring, product feedback - all welcome. Feel free to reach out.