Rhea (Jeong) Yoon

Rhea (Jeong) Yoon

Product Manager

Started building products at a startup while still in university, before I even knew what product management was. That was probably when I fell in love with startups.

Since then, I've worked as an intern at a startup VC, a Growth PM at a 4.5M MAU grocery commerce platform, and a Product Manager at a 10M+ MAU fashion commerce platform.

I've worked on recommendation systems, reviews, creator ecosystems, retention, customer journeys, and advertising products. Along the way, I ran 20+ A/B tests, improved recommendation ARPU by 77%, and learned that most product problems are ultimately about human behavior, trust, and incentives.

Based in London from May 2026 · Full UK working rights · No visa sponsorship required

Releases

v0.1.0

Born

Seoul. No roadmap attached.

The bug that started asking too many questions...

Read full release →
v1.0.0

University Years

3 releases →

Business and Global Media.

AI startup, hackathon grand prize, three side quests...

View all commits →
  • v1.1.0DevHighCampus AI startup. Trust before recommendations...
  • v1.2.0Kakao Hackathon48 hours. Grand prize. The idea lived on...
  • v1.3.0Virus NetworkStartup community. Persuasion outside the classroom...
v1.4.0

D.CAMP

Forty startups. Investment lens.

40 startups reviewed. Romantic view of startups: deprecated...

Read the patch notes →
v2.0.0

Kurly

Grocery growth. Recommendation PM.

4.5M MAU · Korea

20 tests. One number up 77%...

See the diff →
v3.0.0

Musinsa

4 modules →

Fashion platform. Four surfaces.

7.5M MAU · Korea

Reviews, content, CX, ads — one thread the whole time...

Full changelog →
  • v3.1.0ReviewsWhen trust disappeared, users left the app to look for answers elsewhere...
  • v3.2.0SnapCreators wanted reach. Brands wanted engagement. Users wanted relevance. The system wanted balance...
  • v3.3.0CX TFEvery team owned a surface. Nobody owned the full journey...
  • v3.4.0DiscoveryLuxury brands wanted storytelling. The business wanted new revenue streams...

How I Think

Why people choose what they choose

I'm less interested in features themselves and more interested in the decisions behind them. Why do people trust certain things? What makes them feel confident about a choice? How do identity, aspiration, incentives, and context shape behavior? Most of the products I've worked on eventually traced back to those questions.

What data is actually useful for

I care deeply about experimentation, metrics, and behavioral data. But I don't believe growth metrics alone define whether a product is genuinely valuable. Data is most useful when it helps verify whether a product is actually improving the user's experience, decision-making, or long-term satisfaction.

Why I enjoy ecosystem products

The problems I enjoy most involve multiple participants influencing each other: users, creators, brands, platforms, and businesses. I'm particularly drawn to products where different motivations need to coexist inside the same system. That's why I gravitate toward marketplaces, creator ecosystems, recommendation systems, and community-driven commerce.

Growth that actually means something

I care about growth. But I'm more interested in sustainable growth created by genuine user value than growth created by exploiting behavioral weaknesses. The most satisfying products to work on are the ones where business success and user benefit reinforce each other naturally.

How I Work

Problem framing before execution

I naturally spend a lot of time understanding why a problem matters before discussing solutions. I'm most energized when I can participate in the full process: problem definition, hypothesis building, experimentation, and iteration.

Comfortable with ambiguity

Some of the projects I enjoyed most involved unclear ownership, incomplete information, changing priorities, or cross-functional complexity. I feel comfortable operating in environments where the answer is not obvious yet.

Cross-functional by default

Throughout my career, I've worked closely with engineers, designers, marketers, business teams, creators, and leadership. I enjoy connecting perspectives across domains and translating between different ways of thinking. A surprising amount of product work is really communication work.

Thinking beyond individual features

I tend to think beyond individual features and focus on how products interact across the broader user journey. Some of the most important product problems exist between surfaces, teams, incentives, and behaviors rather than inside a single screen.

Working With Me

If you think we should ship something together

Or if you know a team that might be a good fit