interview-reps 0.4.0 → 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (50) hide show
  1. package/README.md +6 -0
  2. package/content/CLAUDE.md +54 -8
  3. package/content/assessments/A01-library-desk/README.md +13 -0
  4. package/content/assessments/A01-library-desk/level-1.md +17 -0
  5. package/content/assessments/A01-library-desk/level-2.md +16 -0
  6. package/content/assessments/A01-library-desk/level-3.md +16 -0
  7. package/content/assessments/A01-library-desk/level-4.md +15 -0
  8. package/content/assessments/A02-ticket-counter/README.md +16 -0
  9. package/content/assessments/A02-ticket-counter/level-1.md +18 -0
  10. package/content/assessments/A02-ticket-counter/level-2.md +16 -0
  11. package/content/assessments/A02-ticket-counter/level-3.md +16 -0
  12. package/content/assessments/A02-ticket-counter/level-4.md +16 -0
  13. package/content/assessments/REVIEW.md +70 -0
  14. package/content/behavioral/QUESTIONS.md +44 -0
  15. package/content/behavioral/REVIEW.md +92 -4
  16. package/content/design/D13-video-streaming/README.md +21 -0
  17. package/content/design/D14-ticket-booking/README.md +20 -0
  18. package/content/design/D15-ad-click-aggregator/README.md +20 -0
  19. package/content/design/D16-distributed-key-value-store/README.md +21 -0
  20. package/content/design/D17-collaborative-document-editor/README.md +20 -0
  21. package/content/design/D18-ai-assistant-on-a-budget/README.md +21 -0
  22. package/content/design/D19-going-multi-region/README.md +20 -0
  23. package/content/design/D20-checkout-at-10x-load/README.md +20 -0
  24. package/content/design/D21-webhook-delivery/README.md +20 -0
  25. package/content/design/D22-game-leaderboard/README.md +20 -0
  26. package/content/design/D23-discovery-recommendations/README.md +21 -0
  27. package/content/design/D24-splitting-a-shared-database/README.md +20 -0
  28. package/content/design/REVIEW.md +70 -0
  29. package/content/product/P21-support-reply-drafts/README.md +29 -0
  30. package/content/product/P22-receipt-categories/README.md +29 -0
  31. package/content/product/P23-pharmacy-symptom-helper/README.md +31 -0
  32. package/content/product/P24-listing-descriptions/README.md +29 -0
  33. package/content/product/P25-group-class-bookings/README.md +28 -0
  34. package/content/product/P26-home-repair-press-release/README.md +28 -0
  35. package/content/product/P27-merchant-cash-advances/README.md +30 -0
  36. package/content/product/P28-retire-the-desktop-app/README.md +28 -0
  37. package/content/product/P29-live-courier-location/README.md +28 -0
  38. package/content/product/P30-carts-across-devices/README.md +28 -0
  39. package/content/product/P31-ticket-on-sale/README.md +29 -0
  40. package/content/product/P32-transfer-status/README.md +28 -0
  41. package/content/product/P33-new-revenue-by-plan/README.md +47 -0
  42. package/content/product/P34-weekly-app-opens/README.md +46 -0
  43. package/content/product/P35-second-orders/README.md +49 -0
  44. package/content/product/P36-on-time-by-city/README.md +46 -0
  45. package/content/product/P37-trials-that-never-pay/README.md +52 -0
  46. package/content/product/P38-smaller-grocery-baskets/README.md +51 -0
  47. package/content/product/P39-clinic-bookings-abroad/README.md +52 -0
  48. package/content/product/REVIEW.md +136 -1
  49. package/dist/cli.mjs +3615 -797
  50. package/package.json +1 -1
@@ -10,7 +10,8 @@ weak area, name the KIND of gap and the question they should ask themselves next
10
10
 
11
11
  1. Read the prompt: `product/<Pnn-slug>/README.md`, including its `## If you ask` answers and its
12
12
  `## What a strong answer covers` criteria. Its Category line says which kind of question it is:
13
- Product sense, Execution, Strategy, Estimation or Analytical.
13
+ Product sense, Execution, Strategy, Estimation, Analytical, AI product, Written doc, Technical, SQL or
14
+ Case presentation. The last five have their own note sections; read the notes under those sections.
14
15
  2. Read the person's notes and timing (the app passes them in the review request).
15
16
  3. Read earlier reviews of the same prompt in `.reps/product/reviews/<Pnn>-*.md`, if any, and note
16
17
  their gaps and "Next time" lines.
@@ -55,6 +56,91 @@ line under each says how to read it for the kinds where it looks different.
55
56
  recommendation or answer? Did the run fit the target time, and do the later sections show the time
56
57
  reached them? Only the total time is recorded, so never guess how long each section took.
57
58
 
59
+ ### Reading the dimensions for the AI product, written doc, technical, SQL and case presentation kinds
60
+
61
+ These five kinds keep the same eight dimensions and the same header, so every score and tag counts with
62
+ the rest. Read each dimension as below instead of the line above. Each one still needs a 3 for a solid
63
+ run, so a dimension with nothing to judge in the notes scores 1 or 2.
64
+
65
+ **AI product.** The question behind every line: does this problem need a model, and would they know
66
+ before launch whether it works?
67
+ - goal: the goal, the constraints and the scope are pinned down before the design.
68
+ - users: who is served and who is affected when the output is wrong, and which group they picked.
69
+ - structure: they decided between AI, rules and plain software from the problem, said why, and the
70
+ design follows that choice. Choosing a model without asking whether one is needed scores 2 at most.
71
+ - analysis: the design is concrete: what the person sees, what the model takes in and gives back, and
72
+ where a person stays in control.
73
+ - prioritization: they chose what goes in the first version and set a launch bar to clear.
74
+ - metrics: tests before launch (offline evals with the cases they would test) and online measures after,
75
+ with a guardrail. A single accuracy number with no test set scores 2 at most.
76
+ - trade-offs: how mistakes show up and whom they hurt, the fallback when the model is wrong or slow, and
77
+ the cost and latency of each request against the value.
78
+ - communication: as above.
79
+
80
+ **Written doc** (a requirements doc, a press release with FAQ, or a strategy memo). Judge it as a document
81
+ someone else must decide from, not as interview notes.
82
+ - goal: the problem is stated with who has it, how they know, and why now.
83
+ - users: the reader can tell whom it is for and which group comes first.
84
+ - structure: it reads without the author. A person who was not there could follow it from start to end:
85
+ terms defined, sections in order, no shorthand only the author understands.
86
+ - analysis: the proposal is specific enough to build or act on, and the non-goals mark its edges.
87
+ - prioritization: decision clarity. The reader can say what is being decided and what the author recommends.
88
+ - metrics: as above, with a time frame.
89
+ - trade-offs: depth, not a list. The alternatives turned down, why, and what the chosen path costs.
90
+ - communication: length discipline. It says what it must in the space it needs; repetition, padding, or a
91
+ document that runs out before Metrics and Open questions scores 2 at most. Note whether it fits the
92
+ document type the prompt asked for.
93
+
94
+ **Technical.** A product manager's view of how it works: enough to make good product calls, not a full
95
+ system design.
96
+ - goal: the user goal, the scale and the scope come first.
97
+ - users: link to the user. Each technical choice is tied back to what the person notices.
98
+ - structure: the right components. The main objects and parts are there, and nothing important is missing.
99
+ - analysis: the APIs and the data flow are concrete: who calls what, with what, in what order.
100
+ - prioritization: not over-building. They kept to what the product needs now and said what waits.
101
+ - metrics: the measures that show it works for the user (speed, errors, freshness), with a target.
102
+ - trade-offs: latency, consistency and cost reasoned about for this product, with what each choice gives up.
103
+ - communication: as above, and their questions for engineering are ones a team could answer.
104
+
105
+ **SQL** (an analytical question answered with a query). Read the query; never run it, never print a
106
+ corrected query, and never name the join, filter or grouping that is missing.
107
+ - goal: they restated exactly what is asked and wrote down how they read the tables and any ambiguity.
108
+ - users: who is counted. The rows that belong in the answer and the ones that do not (test accounts,
109
+ refunds, duplicates, the wrong dates) are thought about.
110
+ - structure: a query plan before the SQL: which tables, in what order, to what result.
111
+ - analysis: the joins, filters and grouping would return what they meant. Name the KIND of problem only,
112
+ such as "rows can be counted twice" or "the date filter misses part of the range".
113
+ - prioritization: the query answers the question that was asked, not a nearby one.
114
+ - metrics: reading the result. They say what the output shows, in which units, and what they would do next.
115
+ - trade-offs: checks and caveats. Edge cases in the data and how they would check the number.
116
+ - communication: the query is readable (layout, names, comments where needed) and the notes end on an answer.
117
+
118
+ **Case presentation** (a brief with data tables, five slides, then four panel questions). The notes hold
119
+ their brief notes, the five slides (each a headline line, then two or three lines) and the panel's
120
+ questions with the gist of each answer. Four parts carry the most weight: insight from the data, a clear
121
+ recommendation, the plan, and handling of follow-up questions.
122
+ - goal: reading the brief. The situation slide states what is asked and what changed, accurately.
123
+ - users: who it affects. The slides say which customers or teams the numbers are about.
124
+ - structure: the slides tell one story. Each headline says its point, so the five headlines alone make the case.
125
+ - analysis: insight from the data. The insight rests on the brief's tables and cites a number from them;
126
+ an insight with no number from the brief scores 2 at most.
127
+ - prioritization: a clear recommendation. One option, chosen against the others, with the reason.
128
+ - metrics: the plan. First steps with an owner and a time, how they will know it works, and a line that
129
+ would make them stop or change course.
130
+ - trade-offs: options and trade-offs. Real options, and what the recommendation gives up.
131
+ - communication: handling follow-up questions. Each gist answers the question asked, directly, with a
132
+ number or a condition, rather than repeating a slide. An empty gist scores that question as missed.
133
+
134
+ Write the case review in the teaching style, for each of the weakest two or three parts: **What we saw**
135
+ (quote their slide or gist), **Why it matters** (to a panel), and **Before and after**: a short example of
136
+ the same kind of fix on a made-up situation, never this brief's numbers or this case's answer, so it shows
137
+ the shape of a better headline or answer without writing theirs. End with one short drill to practise it.
138
+
139
+ Map gaps to the tags below by dimension: for example an insight with no number is `product:analysis`, a
140
+ panel answer that dodges the question is `communication`, a SQL join that counts rows twice is
141
+ `product:analysis`, an AI design with no evals is `product:metrics`, a written doc that never says what
142
+ to decide is `product:recommendation`, and a doc far over length is `communication`.
143
+
58
144
  The prompt's `## What a strong answer covers` list is the checklist for this prompt: use it to judge
59
145
  the dimensions, but never quote it back as the answer.
60
146
 
@@ -105,3 +191,52 @@ Then, briefly:
105
191
  5. **Did last time's feedback stick?** Compare with the earlier reviews of this prompt: say plainly
106
192
  whether their gaps came back or were fixed. Skip if this is the first run.
107
193
  6. **Next time**: one habit, the same as the header line, with a sentence on how to practise it.
194
+
195
+ ## Teaching the review
196
+
197
+ The hub asks for a teaching review: it sends the person's save points (drafts), how far they went in
198
+ the Help tab, and their finish answers. Teach, don't only state findings. Use these exact `##`
199
+ headings, so the hub can lay the review out.
200
+
201
+ **Open** with one or two plain sentences on how it went: the approach, and what cost the time.
202
+
203
+ **`## Between your drafts`**, right after the opening, only when there are two or more save points.
204
+ Name the drafts where something changed (for example `### Drafts 2 to 3: a second user group
205
+ appeared`), quote only the changed lines (at most 12 lines in one block), and add **What it means:** in
206
+ one to three sentences on what the change shows about how they worked. Leave the section out with one
207
+ draft or none.
208
+
209
+ **Plan against what they finished.** In point 2 (Time), compare the structure they set out with what
210
+ the notes ended up covering. When they answered "What changed from your plan", use their words.
211
+
212
+ **`## What to work on, with examples`**, after point 4. One `###` entry per finding that has a gap tag,
213
+ written out in full:
214
+
215
+ - **What we saw:** their words, quoted, or what the drafts showed.
216
+ - **Why it matters:** one to three sentences: what goes wrong, and what an interviewer makes of it.
217
+ - **Before** and **After**: the same short fragment (at most 6 lines each) on a different, made-up
218
+ product, such as a library's audiobook app: a line or two about its user, its goal or its metric,
219
+ first done the weak way, then the better way.
220
+ - **How to practise:** a short drill in words, or another prompt from the bank by its id.
221
+ - **What to say:** one sentence they could say in the interview.
222
+
223
+ The fragment teaches the habit (a goal stated before ideas, users split by behaviour, one measure that
224
+ follows from the goal) on a product that is not this prompt. It never shows this prompt's answer, and
225
+ never names the user group, idea, metric or number that would fix this prompt's gap, so the rule at
226
+ the top still holds.
227
+
228
+ **What I learned.** If they wrote one, say in one line whether it names the main gap.
229
+
230
+ At the end, after point 6, three short sections the hub shows beside the review, in this order:
231
+
232
+ 1. **`## How you solved it`**: a list with Result (*solved alone*; *solved with questions* when help
233
+ stopped at step 4 or earlier; *solved with help* from step 5 on), Help (the furthest step and its
234
+ name, or none), Moved you (only when help was used: the step that got them moving), Time and
235
+ Drafts. Add one line on why it counts as that result.
236
+ 2. **`## Gaps noted, and why`**: one line per tag in the Gaps header line: why this tag, in plain
237
+ words, and what "fixed" looks like. Then `Not tagged:` with a tag you considered and left out, and
238
+ why. Leave this section out when Gaps is none.
239
+ 3. **`## When it comes back`**: `- Redo:` a weekday and date, two or three days out (three when solved
240
+ with help; for solid, a look back in about a week), and how: from a blank page, no help, the target
241
+ time. `- Then:` a sibling prompt from the bank, by its id. `- Daily:` a two or three minute drill
242
+ for the main gap.