How to hire your first enterprise account executive
Most founders interview their first enterprise account executive the same way they'd interview any salesperson: tell me about a deal you closed, walk me through your process, why do you want this job. That interview style hires closers. It does not hire someone who can survive the first six months of an enterprise motion at a company nobody's heard of, with no SDR team feeding them pipeline and no brand recognition to open doors. The candidate who can talk beautifully about closing a $200k deal at a company with 40 inbound leads a month is often the worst fit for a startup where the AE has to find, qualify, and build every one of those deals from zero.
Why this hire is different from your first sales rep
Your first sales rep sells what you've already proven works. Your first enterprise AE has to prove a motion that doesn't exist yet, at a deal size and sales cycle length that punishes mistakes for months before you find out about them. An enterprise deal at an early-stage company runs 120 to 180 days, not the 60 to 90 you'll read in generic benchmarks, because your buyer has never heard of you and has to build internal trust before they'll build a business case. That means a bad hire doesn't fail fast. It fails slow, quietly, for two quarters, against a $250k to $300k OTE line, before the empty pipeline finally shows up in a board deck.
The mistake founders make in the interview
Founders test for closing skill because closing is the visible, tellable part of a sales career. Candidates have a polished story ready for it. What almost never gets tested is self-sourcing: can this person build a pipeline with no marketing team handing them leads and no SDR booking their meetings? At an established company, an enterprise AE closes what's handed to them. At a company with 12 employees, the AE is also the SDR, the sales engineer for the first few demos, and the person writing the security questionnaire response at 11pm. If they've only ever worked a fed pipeline, you won't find out they can't build one until the pipeline is empty in month four.
The interview framework that actually tests for it
Run these four in order. Each one is designed to surface the self-sourcing gap before you make the offer, not after.
- Ask for their last 10 deals, sourced how. Not their best 10. Their last 10. If every one came from an inbound lead, a partner referral, or an SDR-booked meeting, they have never built a pipeline from nothing. That's not disqualifying by itself, but it changes what you should expect from month one.
- Give them your actual ICP and ask them to name five target accounts and their first move on each. Don't accept generic answers like "I'd reach out on LinkedIn." Push for the specific trigger they'd use, the specific person they'd target first, and why. This is the closest thing to a live audition for self-sourcing you can run in an interview.
- Ask what they'd need from you in week one that you don't currently have. The honest answer is usually a list: case studies, a security questionnaire template, a reference customer, a demo environment. If they say "nothing, I'll figure it out," that's a founder-pleasing answer, not a true one. You want someone who can tell you exactly what's missing, because they'll be the one building it.
- Ask about a deal that died in procurement or legal, not one that died on price. Anyone can talk about losing on price. Losing in legal review tells you whether they understand the actual mechanics of an enterprise deal: security reviews, DPAs, multi-stakeholder sign-off. A candidate who's never had a deal die there hasn't really sold enterprise yet.
What this looked like in practice
We ran the five-target-account test on a candidate with an impressive resume from a company that sold to the same buyer persona. He named five accounts instantly, but every "first move" was the same generic LinkedIn connection request. When we pushed on what specific trigger event he'd look for, he had nothing. We passed. Three months later we hired someone with a thinner resume who, in that same exercise, named a specific security certification renewal date for one target account as her opening reason to reach out. She had clearly built pipeline from nothing before. That one exercise told us more than 45 minutes of "tell me about your biggest deal" ever could have.
The one move to make before you post the job
Before you write the job description, write down your own answer to question two: five target accounts and the specific first move on each. If you can't do it, you're not ready to hire someone to do it for you, because you won't be able to tell a good answer from a rehearsed one. Do this exercise yourself first. It takes an afternoon and it will change every interview you run after it.
Frequently asked questions
How long should it take to hire a first enterprise AE?
Budget six to eight weeks from job post to signed offer if you're running a real self-sourcing test, longer than a standard sales hire because you need multiple live exercises, not just a resume screen and two calls.
Should the first enterprise AE also handle SMB deals?
No. Enterprise deals require a different cadence and patience than SMB, and splitting focus trains the habit of chasing quick SMB wins instead of building the slower enterprise pipeline you actually need them for.
What OTE should I expect to pay for a first enterprise AE?
Early-stage enterprise AE OTE typically runs $200k to $300k total, split roughly 50/50 base to variable, though the split can skew more toward base for a true pipeline-building hire in the first year.
Is a candidate from a big company with SDR support a bad fit?
Not automatically, but you have to test for it directly using the exercises above. A great big-company AE with zero self-sourcing experience can become a great startup AE, but only if you know that's the gap going in and set expectations accordingly.
What's the biggest red flag in an enterprise AE interview?
An answer that sounds rehearsed and general instead of specific to your product and your target accounts. Real self-sourcing experience always produces specific answers about specific triggers, not talking points.
Can I skip this and just promote my best SDR instead?
Only if that SDR has already shown they can build relationships with economic buyers, not just book meetings. The skill gap between booking a meeting and running a multi-stakeholder enterprise deal is real and worth testing for even internally.
The interview questions that matter for this hire are not the ones that make a candidate sound impressive. They're the ones that reveal whether they've ever built something from nothing, because that is exactly what you're asking them to do.