Project Template

Use this format for every main project in the playbook.

Project card

• Project name
• Difficulty
• Primary stack
• Estimated duration
• Primary hiring signal
• Primary monetization signal

Required sections

1. Problem statement
   What business problem does the system solve?
2. User roles
   Who uses it, approves it, and supports it?
3. Core workflows
   What must happen from user request to final output?
4. Architecture
   UI, API, model layer, tool layer, retrieval layer, storage, and observability.
5. Milestones
   Split into at least four shippable checkpoints.
6. Acceptance criteria
   Define what "done" looks like.
7. Stretch goals
   Add evals, tracing, role-based access, multi-tenant concerns, or deployment.
8. Portfolio packaging
   What screenshots, diagrams, demo flows, and metrics should be published?
9. Interview story
   What engineering decisions should the learner be ready to explain?
10. Monetization path
    Can this become a template, service offer, SaaS, or internal platform?

Deliverable rule

The learner should finish with:

• a working repository
• an architecture diagram
• a recorded demo
• a deployment plan
• a public write-up