1 min lesson
Reading the JD like an interviewer
Explain the practical point behind "The interviewer isn't checking whether the words describe you."
Step 1 of 3
Every line of the job description is a question in disguise. The interviewer isn't checking whether the words describe you - they're checking whether you have a specific story that proves the trait. Walk in with one ready per line.
The trap is answering with adjectives. “I'm a relentless self-starter” is worth nothing; the time you built a target list from scratch and booked three meetings before anyone gave you leads is worth everything. Convert each requirement into evidence.
Learn more
Advanced table
Read right-to-left
- JD line
- Relentless self-starter who owns their pipeline
- What it's really testing
- Will you self-source without waiting for handed leads?
- Evidence to bring
- A story where you built the list and the outreach yourself and it converted
- JD line
- Simplify a complex product for a technical audience
- What it's really testing
- Can you explain Cursor without hype to engineers?
- Evidence to bring
- A 30-second plain-English Cursor explanation you can deliver on demand
- JD line
- Genuine curiosity about how software is built
- What it's really testing
- Do you actually care about engineering or job-shopping?
- Evidence to bring
- Specifics: a workflow you find interesting, what you've learned about how devs work
- JD line
- 1-2 years sales / customer-facing
- What it's really testing
- Do you have transferable selling reps?
- Evidence to bring
- Reframe non-SDR wins - any role where you persuaded, prospected or hit a target
- JD line
- Resilient, handles rejection
- What it's really testing
- Will you rebound from no without it being personal?
- Evidence to bring
- A real rejection-and-recovery example with what you changed next
| JD line | What it's really testing | Evidence to bring |
|---|---|---|
| Relentless self-starter who owns their pipeline | Will you self-source without waiting for handed leads? | A story where you built the list and the outreach yourself and it converted |
| Simplify a complex product for a technical audience | Can you explain Cursor without hype to engineers? | A 30-second plain-English Cursor explanation you can deliver on demand |
| Genuine curiosity about how software is built | Do you actually care about engineering or job-shopping? | Specifics: a workflow you find interesting, what you've learned about how devs work |
| 1-2 years sales / customer-facing | Do you have transferable selling reps? | Reframe non-SDR wins - any role where you persuaded, prospected or hit a target |
| Resilient, handles rejection | Will you rebound from no without it being personal? | A real rejection-and-recovery example with what you changed next |
Read right-to-left: the interviewer starts from the evidence column and works backward to score the trait.
- Curiosity about engineering
- Cursor screens hard for authentic interest in how software is built - generic 'I love tech' reads as a flag
- Ambition toward AE
- The AE path must sound like a real goal you've thought about, not a polite throwaway
The values round digs for a genuine passion for the problem of automating coding rather than someone treating this as just a job. The AE line gets extra pressure because the seat is a launchpad - they fund people who actually want the next rung.
Learn more
Optional practice