Skip to lesson
Exit
The Role & Your Charter1 / 2

1 min lesson

What this means for your prep

Rebuild the sequence in "What this means for your prep" from memory, ending with the check that proves the outcome.

Step 1 of 2

What this means for your prepturn culture into preparation

  1. 1Prepare ambiguous-problem stories. A time you scoped and shipped infra with no spec - that's the lived proof of end-to-end ownership.
  2. 2Rehearse a defensible tradeoff out loud. Pick a cost-vs-reliability call you made and be ready to defend it under pushback.
  3. 3Practice changing your mind. Have one example where evidence flipped your position; truth-seeking is graded.
  4. 4Actually use Cursor, deeply. Genuine passion for the product over job-shopping is an explicit filter and infra owns the foundation under the thing you'd be using daily.
Say it like this

I do my best work where the team is small enough that I own a problem end-to-end. Give me an ambiguous cost or latency problem under the product, let me scope it down to something I can ship this week and let me defend the tradeoff - that's the environment I'm looking for and it's why a flat infra team at this scale appeals to me.

Watch out

Don't signal that you need a spec, a manager's sign-off or a quarter of ramp before you contribute. On a flat team that ships week one, "I'd spend my first three months learning before touching anything" reads as a mismatch. Show you can ship a contained, correct thing early while you learn the rest.