JACK H. PARK · PRINCIPAL PRODUCT LEADER

Structure before execution.

Philosophy before frameworks, durable concepts before feature lists, and the discipline of choosing what not to build.

I build enterprise security platforms from 0 to 1 — and the discipline to refuse what doesn’t belong.

The Chain

Four layers, run in order. Skip one and the next still exists — but without the grounding that makes it reliable.

  1. 01

    Philosophy

    Why the product exists — the highest-order decision criterion.

  2. 02

    Principles

    Repeatable decision logic derived from philosophy.

  3. 03

    Conceptual Models

    Durable abstractions that make individual feature decisions predictable.

  4. 04

    Execution

    Stage-based workflow that operationalizes the layers above.

Each layer is load-bearing.


Operating Philosophy

Enterprise AI security is a negotiation among trust, speed, and scale. Four pillars keep the negotiation honest.

Trust & Human-Centric Design

Explainability before accuracy.

Enterprises adopt AI security tools in proportion to how much they trust them — not how accurate they are. Ship the explanation before the accuracy improvement.

Enterprise Rigor & Scale

Day 2 is the real launch.

The critical product phase begins after the contract is signed. Drift detection and silent operator reliability decide the renewal — not the demo.

Security & Risk Management

Adversarial thinking by default.

Before shipping a feature, ask: how would I exploit my own AI to leak data? Guardrails are what let the enterprise accelerate without risk exposure.

Strategic PM Mindset

Translate risk into value.

Speak the language of the CISO, the CFO, and the developer at once. Roadmaps that speak in outcomes earn executive trust faster than roadmaps that speak in features.

The Discipline of No

The hardest part of enterprise product management is not deciding what to build — it is the discipline to refuse what does not belong.

The four costs of scope creep
  • Identity dilution

    The product stops being the best at one thing and becomes average at many.

  • Wrong competitive set

    New features drag you into markets where you have no advantage.

  • Execution fragmentation

    Team focus splits; quality degrades across both domains.

  • Workflow mismatch

    Features built for one persona create confusion for another.

Saying no does not mean the need is invalid. It means this product is not the right solution for it — and pointing to the one that is.

Selected Work

Three chapters of enterprise product leadership — zero-to-one, portfolio scale, and personal craft.

Trajectory

Architect first, product leader second — in that order, on purpose.

  1. 2008–2011POSCO DXSoftware Architect, Platform R&D Center
  2. 2011–2014Samsung Mobile eXperience (MX)Software Architect & Technical Partnership, Samsung Smart School
  3. 2014–2018Samsung Mobile eXperience (MX)Product Strategy & Technical GTM Manager, Device Software Customization
  4. 2018–2024Samsung Mobile eXperience (MX)Global Lead Product Manager, Enterprise Mobility Platform & SaaS
  5. 2024–presentSamsung Research AmericaDirector, Strategic Product Management, Enterprise Mobile & AI Security
  • Carnegie Mellon University · MSIT, Software Engineering
  • Korea Advanced Institute of Science and Technology (KAIST) · MS, Software Technology

Let’s build something with structure.

Enter the studio