Sales
Enterprise Account Executive
Six- and seven-figure deals, twelve-month cycles, and a committee of eight people who each have a reason to say no.
Six- and seven-figure deals, twelve-month cycles, and a committee of eight people who each have a reason to say no.
A day that is actually representative
| Time | What you are actually doing |
|---|---|
| 08:30 | Pipeline review. The honest question is which deals are real, and the honest answer is fewer than the forecast says. |
| 10:00 | A multi-threading call — meeting the person below your champion, because champions leave. |
| 12:30 | Procurement. Not selling, negotiating: legal redlines, security questionnaire, MSA. |
| 14:30 | An internal fight for engineering time on a commitment you should not have made. |
| 16:30 | Building the business case your champion will present without you in the room. |
The decisive round
“Walk me through a deal you lost.”
Interviewer: “A big one. What happened?”
A weak answer. “We lost to a competitor on price. The customer went with a cheaper option even though our product was stronger. Budget pressure was the deciding factor.” Every loss attributed to price is a diagnosis that prevents learning. Price is what a buyer says when the value case did not land, because it is the polite answer.
A strong answer. “A $600k deal at a manufacturer. I lost it and I lost it in month two, though I didn't find out until month nine.
What went wrong: I had one champion, the VP of Operations, and he was genuinely enthusiastic. So I ran the whole cycle through him. He told me finance was fine, security was fine, and his CIO was supportive. I believed him because believing him was comfortable.
What was actually true: the CIO had a standing preference for their incumbent vendor, and my champion had never tested that — he'd inferred it. When it reached the steering committee, the CIO asked one question I had no answer to, about how we handled their existing integration, and the deal moved to 'next year', which means never.
The mistake wasn't the answer. It was that I had never met the CIO. I had a single-threaded deal on a purchase that needed four people to agree, and I mistook enthusiasm for authority.
What I changed: I now won't forecast above 50% on any deal where I haven't personally spoken to someone who can say no. And I ask champions a specific question — 'who could stop this, and what would their objection be?' — because a champion who can't answer that isn't a champion yet, they're a fan.
And I'd push back gently on 'we lost on price'. We lost on value. Price is what they say when the business case wasn't strong enough to be worth the disruption.”
A real loss, self-diagnosed to a process failure rather than an external one, with a specific rule that came out of it. The reframe on price at the end is what enterprise sales leaders listen for.
What to build or bring
- A deal you lost, honestly diagnosed. This is asked in almost every enterprise loop.
- Your multi-threading discipline — how many people you meet per deal, and how you get to them.
- Your forecast accuracy, which is the number a sales leader actually trusts you on.
- A business case you built that your champion presented without you.
Compensation
| Market | Band | Notes |
|---|---|---|
| United States | $140k – $180k base | OTE typically 2×; $300k+ at strong quarters |
| India | ₹30L – ₹80L OTE | Deep enterprise AE market at SaaS and infrastructure vendors |
The book for this field
Sales
What sales postings actually ask for, the roles and how they differ, pipeline and forecasting, selling technical and AI products, the loop, and the honest version of crossing over from a technical role.
Cross-cutting
Skills every archetype tests
These are shared across every field on this site — the same question asked in different vocabulary — so preparation here compounds rather than being spent once. The book above is specific to your field.