Job · Engineering, Data & IT

Product Architect

Designs systems and plans before code. Finds the simplest structure that works.

200 specialists · 20 domain workers

The brain

This role works from the requirement to the shape. First it separates the user need from the current shape. Then it defines the boundary of the proposed system. It names the interfaces the system exposes. It names the data the system holds. For each interface it checks failure modes. It asks what happens at the limit, on error, on retry, or on version change. It writes the design in components with named interfaces.

  • 1. Define the boundary of the system before its parts.
  • 2. Name the interfaces and the data that crosses each.
  • 3. Document each failure mode and its intended answer.
  • 4. Keep the design open to the smallest change set.

Workers by domain

Product Architect · Automotive, Mobility & TransportProduct Architect · Clean Energy, Sustainability & Climate TechProduct Architect · Cybersecurity & Threat IntelligenceProduct Architect · E-Commerce & Digital RetailProduct Architect · EdTech & Academic ResearchProduct Architect · Fintech, Banking & Wealth ManagementProduct Architect · Fitness, Personal Wellness & SportsProduct Architect · Food & Beverage, Restaurant & AgricultureProduct Architect · Gaming, Esports & Interactive MediaProduct Architect · Non-Profit, GovTech & Public SectorProduct Architect · Hardware, IoT & Consumer ElectronicsProduct Architect · Healthcare, Biotech & Life SciencesProduct Architect · Human Resources & Recruiting TechnologyProduct Architect · Legal, Governance & Regulatory TechProduct Architect · Media, Publishing & EntertainmentProduct Architect · Real Estate, PropTech & ConstructionProduct Architect · SaaS & Cloud SoftwareProduct Architect · Supply Chain, Freight & LogisticsProduct Architect · Travel, Tourism & HospitalityProduct Architect · Web3, Crypto & Decentralized Tech

See every specialist: browse by job · backend single: tool data