The resume tells you where a Founding AE has been; it does not tell you whether they can sell where there is no playbook yet. Listen for three things in the conversation — the ABCs. A: ability to handle ambiguity, meaning they create focus when no one hands them data. B: build trust through understanding, meaning they make a complex thing simpler so the buyer feels understood. C: curiosity about the operational world, meaning they know exactly what was happening in a customer's business when a deal closed. None of the three show up on a resume. You find them in how someone answers questions they can't prepare for.
Because at some point the resume stops helping. You're in the room with someone, and you have to decide whether this person can do it.
That's a different question than "have they sold before." The job you're hiring for doesn't have a playbook yet. No clean CRM. No list of accounts ranked by fit, because you don't have enough data to rank them. The systems are immature. That's the nature of the role.
Experience helps. Someone who's sold in an early-stage environment is starting from a better place than someone who only knows a mature one. But experience tells you where they've been. It doesn't tell you whether they can build momentum when nothing is built yet.
That's what I'm listening for in the conversation. Three things. A, B, C.
A — Ability to handle ambiguity
When there isn't enough data to tell you where to focus, what do you do?
That's the question I ask. And I'm not really listening for the answer. I'm listening for whether they created clarity in a place where there was none.
A weak founding AE waits for the data. They want the territory defined, the ICP locked, the list handed to them. When it's not there, they stall. They run activity and call it progress.
A strong one makes a call. They look at what little signal exists, pick a place to push, and commit. They might be wrong. But they made a bet instead of waiting for certainty that was never coming.
That's the skill. Not being right. Being willing to create a focus when no one hands you one.
B — Build trust through understanding
Can they explain something complex in a way that makes the buyer feel understood?
This is credibility. And credibility doesn't come from knowing your product. It comes from understanding the buyer's world well enough to say it back to them clearly.
Watch how they handle a complicated situation. Do they make it simpler, or do they make it sound complicated to prove they're smart?
The ones who build trust take something tangled and compress it. The buyer hears it and thinks, "this person gets it." That's the moment trust transfers.
Simplicity isn't the easy version. It's the hard version. It takes more understanding to be clear than to be thorough. The AE who can be clear has done the work.
C — Curiosity about the operational world
When someone made a decision to buy, did they know exactly what was going on in that customer's business?
Or were they generic?
This is the one that separates the real operators. Ask them about a deal they won. Then listen to how they describe the customer.
The generic answer sounds like this: "Their data was in different places. They were doing everything manually. They needed to be more efficient." That's not understanding. That's collecting. They heard some pain, wrote it down, and moved on.
The specific answer sounds different. They know exactly how the customer's day worked. They know which person was getting blamed for the problem. They know what changed that made it urgent. They were reading the signal, not collecting data points.
When a buyer tells you what matters, they're signaling. The generic AE collects it and moves to the next question. The curious one stays on it, goes deeper, and ends up understanding the operational world better than the buyer can articulate it themselves.
That's the AE who knows why a deal closed. Not "they bought." But exactly what shifted, for which person, and why now.
Weak signal vs. strong signal: what to listen for
The same three traits show up — or don't — in the way a candidate talks. Here's the contrast I'm listening for in each.
| Trait | Weak signal | Strong signal |
|---|---|---|
| A — Ambiguity | Waits for the territory, ICP, and list to be handed over. Stalls without data. Runs activity and calls it progress. | Reads what little signal exists, picks a place to push, and commits. Makes a bet instead of waiting for certainty. |
| B — Build trust | Makes a complicated thing sound complicated to prove they're smart. Leans on product knowledge. | Compresses something tangled into something clear. The buyer thinks, "this person gets it." |
| C — Curiosity | Describes a won deal in generic pain: data everywhere, manual work, "needed to be more efficient." | Knows how the customer's day worked, who was getting blamed, and what made it urgent now. |
What this adds up to
Ambiguity. Build trust. Curiosity.
None of the three show up on a resume. You find them in the conversation — in how someone answers a question they can't prepare for, how they explain something hard, how they describe a deal they've already won.
Your founding AE is going to walk into ambiguity, talk to buyers you haven't figured out yet, and make calls you can't make for them. The resume tells you whether they did well somewhere else.
The ABCs tell you whether they can do it here.