Technical PM

How the path is built

You can only challenge what you can read. The path starts from how a web product works to read its architecture, then covers the three contracts a feature almost always touches (APIs, data, who can do what), and ends with shipping as a team.

1. Stage 1

   Read and challenge the architecture

   Follow a request from the browser to the database, then read an architecture diagram and turn "it has to be fast" into measurable requirements. The diagram from the first course is enough to start the second. You leave with an architecture review of your product, down to a decision recorded in an ADR.

   Explain how a web product works, from browser to server · Read and challenge a technical architecture

2. Stage 2

   Specify APIs, data and permissions

   Test an API yourself and write an integration spec engineers can estimate, model the data of a feature and query it in SQL, then specify authentication and roles. You leave with an integration spec, a data model and ten queries, and the roles × actions matrix of your product.

   Design and test an API integration as a PM · Model your product’s data and query it with SQL · Design authentication and permissions for a product

3. Stage 3

   Ship as a team

   Work on a branch, open a pull request, pass the checks, resolve a conflict and roll back a change cleanly. You finish by shipping a small improvement end to end in a practice repository.

   Git for PMs: ship as a team without putting production at risk

The 6 courses, in order

Each course has its own page: detailed syllabus, prerequisites and deliverable.

1. 1

   Explain how a web product works, from browser to server

   All levels2 hr 30 min

   Follow a request from URL to database, read the Network tab, place an incident in the right layer, and map your own product.

2. 2

   Read and challenge a technical architecture

   Junior3 hr

   Read an architecture diagram, quantify requirements, understand the big choices and ask the questions that surface risks and trade-offs.

3. 3

   Design and test an API integration as a PM

   Junior3 hr

   Read an API’s docs, test it yourself in Bruno or Postman, and write an integration spec developers can estimate.

4. 4

   Model your product’s data and query it with SQL

   Junior3 hr 30 min

   Read and design a feature’s data model, then answer your own product questions in SQL, read-only, with AI-drafted SQL you know how to check.

5. 5

   Design authentication and permissions for a product

   Junior2 hr 30 min

   Specify sign-in, SSO, MFA and passkeys, and a safe roles × actions matrix for a multi-tenant product.

6. 6

   Git for PMs: ship as a team without putting production at risk

   Advanced3 hr 30 min

   Contribute safely to an existing repo with CI/CD: short branches, reviewed pull requests, checks and previews, conflicts, safety nets, clean undo and an AI agent kept in check.

What buying the path gives you

• Access to the courses the path holds on the purchase date; courses added to the path later are not included.
• Lifetime access: for as long as Module operates, with updates to the content of these courses.
• A certificate for every course you finish.
• One payment via Stripe, no subscription, with an invoice.

Details in the terms of sale (sections 5 and 6)

Other learning paths