1 min lesson
Probe intensity honestly: it protects both sides
Describe what "The JD hints at a demanding growth phase, possibly six-day weeks" changes in practice.
Step 1 of 3
Probe intensity honestly: it protects both sides
The JD hints at a demanding growth phase, possibly six-day weeks. Asking what that means concretely, such as close load, on-call for billing breaks and typical project timelines, isn't a red flag; it's how a senior person assesses fit and shows they intend to stay. The red flag is needing the answer to be "nice and calm."
Learn more
Advanced table
Red flags to avoid
Red flags to avoidAnti-signals
- Red flag
- Badmouthing a past employer
- Why it sinks you
- Reads as someone who'll badmouth Cursor next; signals low ownership
- Do instead
- Frame past pain as a system you tried to fix, not people who failed you
- Red flag
- Vague impact claims
- Why it sinks you
- "Improved the close" with no number reads as someone who didn't really own it
- Do instead
- Carry the metric: close days, break rate, $, multiple, audit hours saved
- Red flag
- Leaning on certifications
- Why it sinks you
- The JD values shipped outcomes over formality and credentials
- Do instead
- Lead with a system you put in production, not a CPA or a cert you hold
- Red flag
- Wanting a long, structured ramp
- Why it sinks you
- Telegraphs you'd struggle as the first and only finance-systems person
- Do instead
- Signal you can ship in weeks; cite a time you joined hot and were productive fast
- Red flag
- No questions at all
- Why it sinks you
- "You covered everything" reads as disengagement on a founding hire
- Do instead
- Keep two live questions in reserve aimed at the stack's seams and audit bar
| Red flag | Why it sinks you | Do instead |
|---|---|---|
| Badmouthing a past employer | Reads as someone who'll badmouth Cursor next; signals low ownership | Frame past pain as a system you tried to fix, not people who failed you |
| Vague impact claims | "Improved the close" with no number reads as someone who didn't really own it | Carry the metric: close days, break rate, $, multiple, audit hours saved |
| Leaning on certifications | The JD values shipped outcomes over formality and credentials | Lead with a system you put in production, not a CPA or a cert you hold |
| Wanting a long, structured ramp | Telegraphs you'd struggle as the first and only finance-systems person | Signal you can ship in weeks; cite a time you joined hot and were productive fast |
| No questions at all | "You covered everything" reads as disengagement on a founding hire | Keep two live questions in reserve aimed at the stack's seams and audit bar |
Watch out
Don't ask anything the JD or a quick search answers, such as "what does RevOps do?", "is Cursor growing?" or "do I get to use AI tools?". Those waste the slot and read as under-prepared. Spend it on the stack's unbuilt edges, the close and audit bar and where they want agents next.