2 min lesson
Your why, in three layers
Name the parts in "Your why, in three layers" and give the practical job of each one.
Step 1 of 2
Your why, in three layersNarrative
- Why Cursor
- Real daily usage plus one honest critique, tied to the inference experience you'd own
- Why inference
- The hot path is the most impactful place to improve the product - latency, failover and routing decide how it feels
- Why now / why you
- Your track record on high-throughput low-latency systems maps onto the gateway, failover and admission-control projects in the JD
Tie your background to the JD's three projects, not to a generic mission statement.
Match the pace in how you close. Signal that you can ship from week one and don't need a long ramp - point at the moment in your career when you joined something hot and were productive fast, then say plainly that the gateway, failover and backpressure work is the kind of problem you want next.
“I use Cursor daily and the thing I'd want to own is exactly the path that frustrates me when it's slow. I've spent the last few years on low-latency serving systems where reliability, cost and tail latency fought each other, so the gateway, cross-provider failover and admission-control work in the JD reads like the problem I've been preparing for. I'd expect to be shipping inside that path in the first couple of weeks, not ramping for a quarter.”
Let your questions double as evidence of your read on the system. “Where does onboarding a new provider still need code?” quietly tells them you already understand the gateway's whole reason to exist - a config-not-code abstraction over provider APIs - without you having to claim it.