Domain Bundle · Mid
Startup Generalist Bundle
Range over depth: shipping fast, wearing many hats, and pragmatic tradeoffs.
For startup loops that test breadth, ownership and comfort with ambiguity.
- Questions
- 360
- Topics
- 20
- Pages
- 289pages
- 360 questions, every one with a model answer
- Multi-role pack
- Pragmatism & tradeoff questions
- Ownership scenarios
- Rapid-shipping patterns
Get the Startup Generalist Bundle — $29
One-off. Delivered as a PDF by email the moment payment clears.
Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
- Narrowing a vague idea into a shippable slice
- Prioritisation, trade-offs and saying no
- Designing for the company you actually have
- Prototypes, spikes and throwaway code discipline
- Modularity, monoliths and extracting services
- Technical debt triage and paying it down
- Release cadence, pull requests and deployment
- Test strategy for a small team
- Incident response and blameless postmortems
- Observability on a budget
- Unit economics and infrastructure cost control
- Choosing metrics that change decisions
- Hiring, interviewing and levelling in a small team
- Onboarding an engineer without a large org
- Code review, pairing and team communication
- Working with product through changing requirements
- Schema evolution and migrations early on
- Security fundamentals every generalist owns
- API design and the frontend backend contract
- Experiments, staged rollout and learning fast
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
- A narrow slice that solves one painful job beats a broad product that satisfies nobody in month one.
- A framework is a forcing function for a conversation, not a way to compute the right answer.
- Design for the load and the team you have, and write down the number that would change your mind.
- A spike answers one question in a fixed time box, and its output is a written decision, not the code.
- Most startups should ship one deployable with clear internal module boundaries rather than a service mesh.
- Categorise debt as deliberate or accidental, and only deliberate debt is ever a real loan with a rate.
Questions this pack covers
- How do you decide which of three candidate problems to start with?
- What makes a first slice narrow enough to actually ship?
- Which prioritisation framework has actually changed a decision you made?
- How do you sequence work whose value depends on other work finishing first?
- How do you stop yourself designing for scale the business does not have?
- How many real cases does an abstraction need before it is justified?
- When is a spike the right tool instead of a task with an estimate?
- What should a time boxed spike actually produce at the end of it?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
About this pack
- How many questions?
- 360, spread across 20 topics, written out in full across 289 pages.
- Do the answers just list keywords?
- No. Each answer is written as prose, because that is what you have to reproduce when someone asks you the question.
- How do I get it?
- Pay once and the PDF arrives by email immediately, with a signed download link.
- Can I get it refunded?
- Yes, if it is not what you expected. See the refund policy.
