ProductEngineer.pro
The Skill Atlas · v1.0

Everything a product engineer does, on one map.

A product engineer finds a problem worth solving, builds the solution, ships it, checks whether it worked and keeps it useful. Each tile below is one skill that takes. Each has a short description, checked resources and the tools people use.

Open the atlasMark what you know
10Territories
72Capabilities
347Skills
Map1 tile = 1 skill
01 Discovery02 Strategy03 Experience04 Engineering05 Shipping06 Measurement07 Activation08 Retention09 Distribution10 OperationsX Cross-cuttingExplore ↗
Not startedLearningComfortable
Index11 groups
  • 01DiscoveryAre we solving a real problem for the right people?32 skills
  • 02StrategyWhere should we invest our limited time and resources?32 skills
  • 03ExperienceCan users understand, use and benefit from the solution?40 skills
  • 04EngineeringCan we implement this effectively, correctly, securely and sustainably?52 skills
  • 05ShippingHow do we shorten the time from decision to real feedback?20 skills
  • 06MeasurementWhat evidence supports our next decision?37 skills
  • 07ActivationHow do we turn someone who tries the product into someone who experiences its value?19 skills
  • 08RetentionWhy should users continue using the product?18 skills
  • 09DistributionHow does the product reach users who genuinely benefit from it?27 skills
  • 10OperationsCan we sustain the value we have created?32 skills
  • XCross-cuttingHow do you think, decide and work with others across every territory?38 skills

How to use it

4 steps
  1. 01

    Find your way

    Open a territory, then a capability. Every level is a page, a map and a list.

  2. 02

    Read a skill

    What it is, why a product engineer needs it, and a few resources and tools worth the time.

  3. 03

    Mark it

    Click a hexagon to set learning or comfortable, or a whole capability at once. Your map fills in.

  4. 04

    Light a map

    A link can light any set of skills and join them in order, like this.

What a product engineer is

Definition

A software engineer who also owns the product side of the work: talking to users, deciding what is worth building, shipping it in small steps and checking whether it helped.

The job is not to be an expert in every discipline on this map. It is deep technical skill, good product judgment, and enough range to own the whole cycle and work well with specialists.

For an experienced engineer the biggest gains are rarely another framework. They are discovery, prioritization, experimentation, user behavior and business judgment. The map makes those gaps visible.

  1. 01Discover
    Find a real user problem.
  2. 02Decide
    Choose a valuable opportunity and a proportionate investment.
  3. 03Design
    Make the value understandable and usable.
  4. 04Build and ship
    Turn the hypothesis into working software in users’ hands.
  5. 05Measure and learn
    Find out what actually happened, and why.
  6. 06Own the outcome
    Improve, maintain, grow or remove what was built.