| What actually makes a seat enterprise | Not the title, the account definition behind it. Vendors draw the line by employee count (commonly 1,000 or 5,000 and up), customer revenue (often $1B and up), or a named list (Fortune 500, Global 2000, or a carve of 20 to 50 named accounts). The working markers: average contract value in six figures, cycles of 6 to 18 months, a buying committee rather than a buyer, a formal security review, procurement, and legal redlines on your paper. A posting that says enterprise but describes 150 accounts and a 45-day cycle is mid-market with a flattering title. |
|---|---|
| License or credential required | None for enterprise software, SaaS, data, infrastructure or professional services sales. No license, no exam, no governing body. Real exceptions: selling securities or investment products requires FINRA registration through a sponsoring firm (the Securities Industry Essentials exam plus a top-off such as the Series 7 and a state exam such as the Series 63, or the Series 79 on the banking side); insurance and benefits sales require a state insurance producer license per line of authority; medical device and hospital capital sales require vendor credentialing (symplr, GHX Vendormate, Reptrax) plus immunization records and operating room protocol training before you can enter a facility; some public-sector seats require a security clearance, which only a sponsoring employer can initiate. |
| The de facto credential, and how long the move takes | A verifiable attainment history in the segment you are applying to. Moving from mid-market to enterprise usually takes 12 to 24 months of deliberate work: one or two enterprise-shaped deals inside your current patch (committee of six or more, a security review, a multi-year term, six-figure ACV), then either an internal carve-out to named accounts or a lateral to a company one tier smaller that will trade brand for scope. A jump straight from SMB or SDR into an enterprise seat is rare and usually fails, because the first full enterprise cycle outlasts most employers' ramp patience. |
| The hiring loop | Recruiter numbers screen (quota, attainment, ACV, cycle length, segment, self-sourced percentage), hiring manager deal forensics, a live exercise (a 30-minute mock discovery call, or an account plan or 30/60/90 presentation on one of their real target accounts), a cross-functional panel including a sales engineer and often someone from customer success, then a VP or CRO. Two to five weeks is typical. Assume backchannel references, including people you did not list. |
| What the resume is screened on | Six numbers per role, in the top third of page one: quota in dollars, attainment as a percentage with the dollar figure beside it, ranking with its denominator (#4 of 31), average ACV, average cycle length, and the share of pipeline you sourced yourself. Then customers you personally closed, at the account size the employer sells into. Everything else is read after the decision has provisionally been made. |
| The evidence mid-market resumes are missing | Multi-threading, counted per deal: how many stakeholders you engaged by function and level, how many levels above your entry point you reached, whether you met the economic buyer and how you got there, whether you had a second champion when the first one left. Plus the paper path you have navigated: security review, data processing agreement, procurement, legal redlines, and at regulated buyers an AI governance or model-risk review. |
| Pay, and where to check it rather than guess | The structure is more useful than any quoted band. Enterprise software comp is usually split close to 50/50 base and variable, with quota set by a rule of thumb of roughly four to six times on-target earnings, which is the arithmetic behind the familiar ten-percent-of-bookings commission rate at plan, plus accelerators above 100 percent. Check real numbers in three places: posted ranges in pay-transparency jurisdictions (Colorado, California, Washington, New York, Illinois, Minnesota, Maryland, Vermont, New Jersey, Massachusetts and Hawaii among them, and the list has grown every year, so check the current rule for the state in the posting), asking whether the posted range is base or OTE; the BLS Occupational Employment and Wage Statistics data for SOC 41-4011 (sales representatives, wholesale and manufacturing, technical and scientific products) and 41-3091 (sales representatives of services, all other), where most software sellers are classified; and RepVue for self-reported attainment rates by employer. BLS top-codes the highest wages, so read its upper percentiles as a floor, not a target. |
| The number that decides whether the job is any good | What percentage of the AE team hit quota last year, and how that was distributed. Ask in the first interview. A seat with a large OTE where a third of sellers make plan is a worse job than a smaller OTE where most do. Ask also whether the seat is a backfill, what the previous holder attained, and why they left. A refusal to answer is itself the answer. |
What counts as enterprise, and the logo history the search is pattern-matching on
Calibrate the market first, because it changes how you spend your effort. Enterprise seats in 2026-27 are fewer per company and harder to win than they were in the 2021 and 2022 boom. Through 2024 and 2025 territories were consolidated rather than expanded, patches got larger per head, prospecting support per seller thinned, and a large number of experienced enterprise sellers were laid off and are in the same applicant pool as you. The practical consequences: a cold application into a posting is a weak channel because the pile is deep in qualified people, hiring managers resolve that by hiring from their own network, and attainment distributions on many teams are worse than their headline OTEs imply. None of that changes what the job screens for. It raises how precisely you have to show it, and how much the channel you arrive through matters.
The word enterprise in a job title means almost nothing on its own. What means something is the account definition behind it, and it is usually stated in the posting if you read for it: employee count or revenue thresholds, a named-account list, a patch size, an ACV expectation, a cycle length. Three postings can all say Enterprise Account Executive and describe a 40-account named patch with $400k average deals, a 150-account territory with $60k deals, and a renewals book with an upsell quota. Those are three different jobs and they screen for three different people.
What genuinely changes when you move up is not the size of the number. It is that you have fewer shots, each one involves more people, and most of the work is not selling to a buyer but assembling internal and external consensus. Fewer accounts means forecast risk concentrates: one slipped deal is your quarter, and in a 12-month cycle you can be two quarters into a seat with nothing closed and still be on track, which takes both your manager's nerve and your own. More people means the paper matters: security review, data processing agreements, procurement, legal redlines, vendor onboarding portals. Hiring managers know all of this, which is why they screen on evidence that you have lived it rather than on enthusiasm.
An enterprise search is a pattern match on four axes, and the recruiter is literally scoring you against them. Segment: did you sell to organizations the size of theirs. ACV: did you close deals at their price point, because the behaviors at $40k and $400k are different and a $40k seller tends to try to close too early. Motion and complexity: did you run new-logo acquisition or manage an existing book, did you sell into an existing budget line or create a new one, did you displace an incumbent or land greenfield. Brand: did you sell when the buyer already knew who you were.
The brand axis is the one candidates underestimate, and it cuts both ways. If you closed seven-figure deals at a vendor every CIO has heard of, with inbound demand, a brand-name customer list and a dedicated sales engineer, a Series B startup will quietly worry that you have never had to create belief from nothing. If you closed enterprise deals at an unknown company through pure outbound, a large vendor will worry about whether you can operate inside a matrixed account team with partner rules, a deal desk and a discounting committee. Either way the move is the same: name the gap yourself in the first conversation and bring specific evidence against it. Hiring managers reject surprises, not gaps.
Vertical is a fifth axis that is sometimes a hard requirement rather than a preference. Selling into US health systems, federal and state government, defense, or tier-one banks is a relationship-and-process business where a seller with existing committee relationships and a working knowledge of the procurement vehicle genuinely outperforms a better generalist. If a posting is verticalized, the search is often for the network and the process knowledge rather than the methodology, and a generalist resume will not clear it no matter how good the numbers are. The inverse is also true: a verticalized seller moving horizontally has to show the methodology survives without the rolodex.
Finally, be honest with yourself about net-new versus expansion, because this is the most common quiet mismatch. A seller whose last three years were renewals, expansions and upsell inside installed accounts has a real skill set, and it is not the skill set a new-logo enterprise seat is hiring. If that is you and you want a hunting seat, your bridge evidence is the one or two genuinely net-new logos you did land, written up in forensic detail, plus your self-sourced pipeline percentage.
- Read the account definition, not the title: employee or revenue threshold, patch size, whether accounts are named and carved or built by you, inbound versus outbound split, stated ACV and cycle length. If those are absent, ask the recruiter in the first five minutes.
- Segment fit: name the largest organizations you closed by rough employee count or revenue, not just by logo. The hiring manager is mapping them against their own target list.
- ACV fit: your average contract value and your largest, with the term length. A $1.2m total contract value on a three-year deal is a $400k ACV deal; call it what it is, because they will do the division in front of you.
- Motion fit: new logo, expansion, displacement or renewal, given as a percentage split across your last full year.
- Brand fit: say whether demand was inbound or created, whether you had a dedicated sales engineer, and whether the buyer knew the company before your first call. Volunteering this reads as credibility, not weakness.
- Vertical fit: if the posting is verticalized, lead with the committee relationships and the procurement vehicle you know (a GSA Multiple Award Schedule, SEWP, a state master agreement, a healthcare GPO contract, a bank's third-party risk process), because that is what they are buying.
- Public sector: ask early whether the product has FedRAMP authorization or is in process, and whether the seat requires an active clearance. Both gate deals and neither is something you can fix from the seat.
Multi-threading: the evidence enterprise searches actually ask for
Enterprise deals do not usually die because the product lost. They die single-threaded: the champion changes jobs, the sponsoring VP is reorganized, the budget moves to a different cost center, a new CIO freezes spend. Every enterprise sales leader has had a forecast destroyed this way, so the question behind almost every interview question is narrow and practical: will this person's forecast be real, or will it be one relationship deep and collapse in week eleven. Multi-threading evidence is how you answer that before you are asked.
Make it countable, because that is the form it is believed in. For each of your last three closed deals and your two largest losses you should be able to say without hesitating: how many individuals you had a live conversation with, their functions (business owner, technical evaluator, security, procurement, legal, finance, executive sponsor), how many levels above your original entry point you reached, who the economic buyer was and the date you first spoke to them, how you got to them (champion introduction, executive sponsor pairing, partner, cold, board connection), and who your second champion was. Candidates who have genuinely worked enterprise deals produce this in under a minute. Candidates who have not go vague immediately, and the interview is effectively over.
On the resume, compress it into the achievement line rather than claiming it as a skill. Something of this shape: closed a $480k ACV three-year agreement with a 7,000-employee insurer, 11 stakeholders across underwriting, IT security, data governance, procurement and finance, economic buyer reached in week five via an executive sponsor introduction, nine-month cycle including a six-week security review and a data processing agreement negotiation. That single line does more work than a paragraph about consultative selling, and it hands the hiring manager the exact deal they will interrogate, which you want, because you have prepared it.
Prepare specifically for the champion-leaves question, because it is asked constantly and most answers are bad. The weak answer is a story about rebuilding the relationship with the replacement. The strong answer starts earlier: you had a second relationship in the same function before the departure, the business case was written in the customer's own numbers so it survived the person who commissioned it, the executive sponsor's commitment was on record rather than only verbal, and the mutual action plan was something the account itself knew about, so the process had momentum independent of one person. Then tell the story of the time it actually happened and what it cost you.
Executive alignment is the piece mid-market sellers most often have never done. It means pairing your own leadership with theirs on purpose: your CRO or CEO to their CFO or CIO, with a prepared agenda and a specific ask, rather than a relationship meeting. If you have done it, say who you paired with whom, what the ask was, and what it unblocked. If you have not, say so and describe the closest thing you have done, because the alternative is being caught claiming it. There is a related lie detector experienced interviewers use: who at that customer would take your call today. A seller who multi-threaded genuinely has four names. A seller who did not has an excuse.
Bring the artifact. A sanitized mutual action plan or close plan from a real deal, with customer names removed, is the single most effective object you can put on the table in an enterprise AE interview: the stakeholder map by role, the paper steps with owners and dates, the security and legal path, the compelling event and the date it forces, and the risks written down. Candidates who put paper on the table are remembered. Candidates who describe their paper are not.
- Per-deal numbers to know cold: stakeholder count, their functions, levels above entry point, economic buyer and the week you met them, second champion, cycle length, discount given, term, and what nearly killed it.
- Bring sanitized: one mutual action plan, one stakeholder or org map, one business case with the customer's own cost figures, and one post-mortem on a loss. Say out loud that names are removed and figures scaled if they are.
- Expect these three almost verbatim: walk me through your largest deal from first touch to signature; tell me about a deal where your champion left; how do you get to the economic buyer when your champion will not introduce you.
- Have an answer for the champion who blocks access upward, which is more common than one who leaves. The usable version gives the champion a reason to want the executive meeting (their own case, their own credit) rather than going around them and burning them.
- Count the losses too. Hiring managers trust a candidate who can say a deal died because they were two stakeholders deep in a seven-stakeholder decision, and distrust one whose losses were all price.
How enterprise AE hiring runs, stage by stage, and how to get into the process at all
Start with the channel, because in this market it decides more than your resume does. The highest-yield route into an enterprise seat by a wide margin is the hiring manager's own network: former managers who got promoted, sales engineers you ran deals with, customer success leads, and champions at your own customers who have since moved to other companies. Second are specialist contingency sales recruiters, who matter more in this function than in almost any other and are worth two or three durable relationships maintained when you do not need them. Third are internal recruiters at scale-ups and large vendors, who handle volume. A cold application with nothing attached is fourth and distant. The usable version of applying cold is to arrive with a reason: you already sell into their target accounts, you know the committee at three of them by name, and here is the one-page deal sheet. Say that in four sentences to the hiring manager directly rather than in a cover letter nobody opens.
The recruiter screen is not a conversation, it is a data-entry exercise against a scorecard the hiring manager wrote. Expect twenty to thirty minutes of being asked your quota, your attainment by year, your average and largest ACV, your average cycle, your segment definition, your self-sourced pipeline percentage, your tenure and your reason for leaving, and expect the recruiter to be typing. The implication is simple and most candidates get it wrong: lead with the numbers, in that order, unprompted. Rapport does not advance you at this stage and vagueness ends it.
The hiring manager stage is deal forensics. They will pick one deal off your resume, usually the largest, and go down into it until something gives: exact ACV and total contract value, term, start date, discount percentage and who approved it, who signed, who the economic buyer was and when you first met them, what the compelling event was, who you competed against and why you won, how long the security review took, what procurement extracted from you at the end, what nearly killed it, and what you would do differently. This is where inflated resumes fail, and they fail quietly: the manager does not challenge you, they just stop going deep and move on. The defense is not better storytelling, it is having only true numbers on the page.
Then the live exercise, which is the stage people prepare for least well. The most common form is a 30-minute mock first call: you are given a persona (a VP of Engineering, a CISO, a VP of Finance) and sometimes a one-page brief in advance, and the hiring manager plays the buyer. What is being scored, roughly in order: did you set an agenda and get agreement on it, did you ask business-level questions before product questions, did you quantify the cost of the problem in the buyer's own units, did you ask who else has to be involved and ask for them by role, did you handle one objection without immediately discounting or caving, and did you close on a specific next step with named people, a date, and what each side will do before it. The dominant failure mode is pitching: candidates start demonstrating features in minute four, and the panel's note is one word, pitched.
The second common form is an account plan or a 30/60/90 presentation, often on one of the employer's real target accounts. What wins here is visibly unglamorous: you read the last annual report or earnings call and quote something from it, you name a compelling event with a date attached, you lay out the likely buying committee by title, you have a point of view on the entry point and on which partner or systems integrator is already inside, and you write down what you do not know and how you would find out in week one. What loses is a polished generic plan, because everyone can generate one of those now in a minute.
The panel is cross-functional and every person in it is a decision maker, particularly the sales engineer. The SE is being asked whether they want to work deals with you, and they will notice if you talked over them, oversold the product's capability, or could not hold a technical conversation at the level their buyers operate at. Someone from customer success is often there to check whether you sell deals that can actually be delivered, and the honest answer to have you ever oversold is yes, once, and here is what it cost and what changed.
The VP or CRO stage is short and about one thing: are you a forecast they can put their own name on. Expect pipeline math (how you build coverage, your sourcing split, your conversion rates, how many first meetings you need a week to make the number), one judgment question, and a read on whether you are coachable. At companies below about 200 people the CEO may be in this stage and will mostly be testing whether you understood what they sell.
Backchannel references are the stage candidates forget exists, and in enterprise sales they are routine on finalists. The VP calls a former manager of yours who is not on your list, usually through one degree of separation, and asks the two real questions: did they hit their number, and would you hire them again. Attainment claims get verified this way, which is a separate matter from the salary-history bans now in force in many states; those restrict asking you what you earned, and they neither prevent nor cause a performance reference. Use the channel yourself in the other direction: before you sign, talk to a current AE on that team who was not put in front of you by the recruiter. Expect two to five weeks for a loop, and far longer where a clearance or a contract award is involved.
- Prepare the recruiter screen as six rehearsed sentences: quota, attainment by year with dollars, average and largest ACV, average cycle, segment definition, self-sourced percentage. Then one line on why you are leaving that criticizes nobody.
- Ask the recruiter in that first call: is this a new seat or a backfill, are accounts named and carved, what is the inbound versus outbound split, what was team attainment last year, and is the posted range base or OTE. The answers tell you whether to spend two weeks on this process.
- For the mock call, prepare the first four questions you will ask and the agenda sentence you will open with. Do not prepare a pitch. If they push you to demo, say what you would need to know first and why, then ask it.
- For the account plan exercise, use a real source and quote it. One line from their 10-K, earnings call or a regulatory filing beats a page of inferred strategy.
- Have one oversold deal, one lost deal you should have won, and one deal you walked away from. All three get asked at this level, and having no failures reads as junior or dishonest.
- Line up your own references before the final stage and tell them what the role is and which deal to talk about. Then assume a reference you did not name will also be called.
Credentials: nothing licenses this job, except where it does
For enterprise software, SaaS, platform, data and professional services sales there is no license, no qualifying exam, no registration and no governing body. Anyone can hold the title tomorrow. That is why the market substitutes something harder to fake: a quota attainment history that holds up under a reference call. Treat your attainment record the way a licensed professional treats their license number. Keep your own copies of quota letters, comp plans, attainment reports, ranking screenshots and President's Club confirmations as you earn them, because you will not be able to get them after you leave and you will be asked to substantiate claims years later.
There are enterprise-adjacent sales roles where a genuine credential does gate the seat, and confusing them with software sales wastes months. Selling securities, investment products or institutional financial services requires FINRA registration. The detail that matters, and that gets reported wrongly: you can sit the Securities Industry Essentials exam on your own, without a sponsor, and passing it is a credible way to show intent before you have an offer. What you cannot do alone is the rest. The top-off exams (the Series 7 for general securities, the Series 79 on the investment banking side) and the state exam (commonly the Series 63) require a sponsoring member firm to file your registration. Insurance and employee-benefits sales require a state insurance producer license: pre-licensing hours, a state exam, fingerprinting, and separate lines of authority for life, health and property and casualty, with reciprocity between states but no single national license. Medical device, implant and hospital capital sales require vendor credentialing before you may set foot in a facility: a profile with a credentialing system such as symplr, GHX Vendormate or Reptrax, immunization and TB records, a background check, HIPAA and bloodborne pathogen training, and operating room protocol training, typically renewed annually. Budget weeks, not days. Some public-sector seats require a security clearance, which again only a sponsoring employer can initiate and which can leave months between a verbal offer and a start date.
Sales methodology certificates are a different category and are widely misunderstood. The methodologies are real and worth knowing: MEDDIC and MEDDPICC as a qualification discipline, Force Management's Command of the Message for value framing, Challenger, Miller Heiman Strategic Selling for complex account mapping, ValueSelling, Sandler. What is worth little is a self-purchased certificate listed as a credential. These are overwhelmingly delivered by employers to their own teams, so hiring managers read them as a signal about where you worked rather than about what you can do. What moves the needle is applying the framework to a real deal out loud, from memory, including the parts candidates skip: the decision process and the paper process, the metrics in the customer's own units, and a pain the customer themselves articulated. If you know which methodology the employer runs, use its vocabulary naturally. Reciting the acronym is not the same thing and gets noticed.
Degrees are close to irrelevant here. Very few enterprise AE postings require one and nobody checks beyond a background screen. What substitutes, and in domain-heavy sales substitutes powerfully, is having been the buyer or the practitioner: a former hospital IT director selling into health systems, a former actuary selling into insurers, a former security engineer selling into CISOs. If that is your background, your interview challenge is the opposite of most candidates': you have to prove you can run a process and build pipeline, not that you understand the problem.
Vendor and platform certifications occupy a narrow but real slot. If you sell inside an ecosystem, a foundational certification (AWS or Azure cloud practitioner level, Salesforce, ServiceNow, Snowflake, Databricks fundamentals) is cheap, takes days to weeks, and does two useful things: it lets you hold a credible conversation with the technical evaluator, and it signals that you will do the homework. What it does not do is substitute for deals. Nobody has been hired into an enterprise seat on a certification, and listing four of them where your attainment numbers should be reads as compensating.
- Software, SaaS, data, infrastructure, professional services: no license. The gate is attainment history plus references.
- Securities and investment products: the SIE exam you can take unsponsored; the Series 7 or 79 top-off and the Series 63 state exam require a sponsoring member firm to register you.
- Insurance and benefits: state producer license per line of authority, pre-licensing hours plus a state exam, renewed with continuing education.
- Medical device, implants, hospital capital equipment: vendor credentialing (symplr, GHX Vendormate, Reptrax), immunizations, background check, HIPAA and operating room training, usually renewed annually. Weeks, not days.
- Public sector and defense: a clearance where required, sponsored only. Ask about the gap between offer and start date before you resign anything.
- Methodology training: valuable to know, weak as a resume line unless employer-delivered. Demonstrate it on a real deal instead.
- Keep your own evidence file: quota letters, comp plans, attainment and ranking reports, President's Club confirmations, saved as you earn them.
The resume: a numbers document, and how to stop reading mid-market
An enterprise AE resume is an attainment ledger with a short narrative wrapped around it. That is a genuinely different document from most professional resumes, and candidates coming from other functions write it wrong by instinct. The reader is a sales leader or a recruiter working from a scorecard, they spend well under a minute on the first pass, and they are looking for six specific numbers. If those numbers are not in the top third of page one, the rest of the document is not read.
The six, per role: quota in dollars, attainment as a percentage with the dollar figure beside it, ranking with its denominator, average ACV, average cycle length, and the share of pipeline you sourced yourself. A role block that works looks roughly like this. Enterprise Account Executive, named accounts, North America financial services, 2024 to 2026. Quota $1.8m new ACV. FY25 attainment 112 percent ($2.02m), ranked 4 of 31. FY24 attainment 94 percent ($1.69m) against a $1.8m quota. Average ACV $340k, average cycle nine months, 61 percent of closed pipeline self-sourced. Then two or three achievement lines, each one a specific deal with the stakeholder count, the committee, the competitor displaced and the term. Then stop.
Honesty about denominators is not a moral point, it is a tactical one, because every number on this page gets interrogated. Always show the quota the percentage is measured against, because 180 percent of a $400k quota is a weaker claim than 101 percent of a $2.4m quota and a leader reads it that way instantly. Say when a figure is pro-rated or a partial year, on the page rather than in the interview. If your quota was rebaselined mid-year, say which number you are measuring against. If you were on a ramp quota, label it. A candidate who volunteers these qualifications is read as rigorous. A candidate who is caught on one is read as having been caught, and in a function built on forecast credibility that is fatal.
On customer names, two rules. First, ownership: name accounts you personally closed or personally ran, not accounts your company has. A hiring manager will ask who the economic buyer was and who signed, and the answer I supported that deal, after listing it as yours, is a closed process. If you genuinely co-sold, write co-sold and say what you owned. Second, confidentiality: a customer your employer publicly announced or lists on its own site is safe to name. A customer who is not is not, and the professional convention is to describe rather than name, which carries almost the same weight: a top-five US health system, a European tier-one bank, a Fortune 100 industrial manufacturer, a federal civilian agency. Describing an account you cannot name reads as discretion. Naming one you should not have reads as a liability, and the person interviewing you may well know them.
What gets ignored or actively hurts: a summary paragraph of adjectives, a skills grid listing Salesforce and CRM, methodology acronyms with nothing attached to them, responsibilities phrasing (responsible for managing a territory), any use of we where the reader needs to know what you did, soft-skill claims, an objective statement, and more than two pages. Also every award whose criteria you cannot state. President's Club with the year and the criteria is useful; multiple sales awards is noise.
If your resume currently reads mid-market, the edit is narrow. Reorder so your three largest and longest deals are what a reader hits first, even if they were not your most recent. Add the committee: stakeholder counts, functions, and the economic buyer's level. Add the paper: security review, data processing agreement, procurement, legal, the term length and whether it was multi-year. State the cycle length explicitly, because an unlabeled nine-month deal reads as a three-month deal to someone scanning. Remove deal volume as a headline, because a high count of small deals is evidence against you in this search, and replace it with ACV. One more thing worth the effort: write the segment definition in your own words next to the role, in employees or revenue, rather than leaving the reader to guess what enterprise meant at your last company.
- Top-third template per role: segment and patch definition, quota in dollars, attainment percentage with dollars for each year, ranking with denominator, average and largest ACV, average cycle, self-sourced percentage.
- Achievement line template: $X ACV, N-year term, with a [size and type of organization]; N stakeholders across [functions]; economic buyer [title] reached in week N via [route]; displaced [competitor or status quo]; N-month cycle including [security review, DPA, procurement].
- Label everything that needs labeling: pro-rated, partial year, ramp quota, rebaselined, co-sold, team quota.
- Describe accounts you cannot name. A top-five US health system is a credible line; an unannounced customer's actual name is a risk you do not need to take.
- Cut: adjective summaries, CRM skills grids, bare methodology acronyms, we-phrasing, responsibilities language, unnamed awards, page three.
- Keep a separate one-page deal sheet for the interview: five deals with every number. It is not sent with the application; it is produced in the room, or attached when you reach the hiring manager directly.
Moving upmarket: the routes that work, and the bridge deal that makes the case
There are five routes into an enterprise seat that actually work, and they differ mostly in how much of the gap the employer is being asked to take on faith. In rough order of reliability: an internal carve-out at your current company, a lateral to a smaller company that trades brand for scope, a move from sales engineering into selling, a move from consulting or implementation into selling in the same domain, and a move from being a domain practitioner or buyer into selling to your former peers. A sixth, SDR or SMB straight into enterprise, is not a route. It is a thing that occasionally happens and usually ends in a termination before the first cycle completes.
The internal carve-out is the most reliable and the most underused. You already have the relationships, the product knowledge, the pipeline and a manager who can see your numbers, so the ask is small: a named-account carve of five to fifteen large accounts alongside or instead of part of your current patch, with a quota adjusted for cycle length. Make the ask with evidence rather than ambition: here are the three largest opportunities currently sitting in my territory that are not being worked properly because they need a nine-month cycle, here is the committee in each, here is what I need (sales engineer time, exec sponsorship, a ramp-adjusted quota) and here is what I will commit to in two quarters. Ask after a good quarter, in a planning window, not in a review.
The lateral is the common external move and it is a trade to make with your eyes open. A company one or two tiers smaller than your current employer will give you an enterprise title and bigger deals in exchange for taking on the brand problem: you will create demand rather than receive it, and you may be their first enterprise seller, which means you are also building the process. That can be the best career move available, and it can also be a seat where enterprise deals were never achievable at that product's maturity. Diligence the specific thing: how many deals above the ACV in my quota has this company ever closed, and who closed them. If the answer is none, your quota is a hypothesis.
The sales engineer route works well and is underrated. You already sit in the technical evaluation, you already know the committee, and you already have credibility with the exact people who block deals. The gap you have to close explicitly is commercial: pipeline generation, negotiation, and owning a forecast. Close it before you interview by having actually done some of it, which an SE can do inside their current role by sourcing a qualified opportunity, running a business-case conversation and co-owning a close plan. Consulting and implementation backgrounds work the same way in domain-heavy sales, with the same gap and the same fix. Domain practitioners and former buyers carry the strongest version of credibility and the largest version of the same gap, and the hiring managers who take that bet want to see that you are not squeamish about asking for money.
Whichever route you are on, the most persuasive thing you can bring is a bridge deal: one enterprise-shaped deal you actually ran, even if your title said mid-market. The shape matters more than the size. It needs a buying committee of six or more people, at least one level above your natural entry point, a formal security review, a negotiated contract rather than a click-through, a term longer than twelve months, and a compelling event you can name. One of those, told in forensic detail with the stakeholder map in your hand, changes the conversation from whether you can do enterprise to how you did it. You can engineer this deliberately: hunt the division of a large parent company in your existing patch, or the enterprise account that landed in mid-market because its first contract was small.
The adjacent move, which costs nothing, is getting yourself onto a real enterprise deal as a co-seller or overlay. Ask your manager and the enterprise AE whose patch it is. Most enterprise sellers working a fifteen-stakeholder deal will take free help, and you come out of it with a named deal you genuinely contributed to, a sales engineer relationship, and a reference inside the segment. Be scrupulous about how you describe it afterwards: co-sold, and here is the part I owned. Overclaiming it undoes the whole point.
Two things not to do. Do not take a title you cannot substantiate: an Enterprise Account Executive title on a patch of 200 mid-market accounts will be exposed in the first forensics interview and costs you more credibility than the title buys. And do not stack short tenures. Enterprise cycles run 6 to 18 months, so three jobs in three years tells a hiring manager you have never personally seen a full cycle through from sourcing to signature, which is the exact thing they are hiring for. If your history already looks like that, address it in your own words in the first conversation, with the reason and what you are optimizing for now.
- Ask for the carve-out with a written case: the three or four large opportunities in your current patch, the committee in each, the quota adjustment you need and the two-quarter commitment you will make.
- Before taking a lateral to a smaller company, ask how many deals above your quota's ACV they have ever closed and who closed them. Ask to speak to that person.
- If you are an SE, consultant or domain operator, close the commercial gap before interviewing: source one opportunity, run one business-case conversation, co-own one close plan, and be able to talk about pipeline math.
- Engineer one bridge deal: a division of a large parent, or an enterprise account sitting in a mid-market patch. Six-plus stakeholders, a security review, a negotiated contract, a multi-year term, a named compelling event.
- Get onto someone else's enterprise deal as an overlay, then describe your part precisely and no more than that.
- If your tenure history is short, say why first, before anyone has to ask, and say what you are optimizing for now. Unexplained short tenure is one of the few things that ends an enterprise process on its own.
The interview: the mock call, the forensics, and explaining a year you missed
Strip away the stages and an enterprise AE interview tests four things: can you run a conversation a senior executive would not end early, are your numbers real, do you have judgment under commercial pressure, and will you be honest in a pipeline review when the news is bad. Almost every question maps to one of those. Candidates who prepare answers rather than evidence tend to fail on the second and the fourth, because both are tested by depth rather than by content.
In the mock discovery call, the order of what is scored matters more than the content. Open with a reason for the meeting and an agenda, and get agreement on it. Ask business-level questions before product questions and do not stop at the first problem statement; get to what it costs in the buyer's own units, which means money, headcount hours, cycle time, risk exposure or a regulatory deadline. Ask who else is affected and ask for them by role rather than hinting. Handle one objection without discounting and without agreeing too fast. Then close on a next step with a date, named people, and an obligation on each side. If you do all of that and never describe the product, you will score well, which surprises people.
Deal forensics is survivable only with true numbers and a memory for them. Prepare five deals to the depth of a deposition: ACV and total contract value, term, discount and who approved it, who signed, the economic buyer and when you met them, the compelling event, the competition and why you won or lost, the security review length, what procurement extracted, what nearly killed it, and who at that account would take your call today. Interviewers are not trying to catch you with trick questions. They follow one deal until the detail runs out, and where it runs out tells them what you actually did.
Almost every seller has a year they missed, and after the layoffs of the last two years many have a gap as well. Both are survivable and lying about either is not. For a missed number, give the structure in this order: the number and the gap, the cause stated plainly, what was inside your control, what you changed, and what happened next. Territory rebaselined in Q2 and two deals slipped into the following year is a reason; so is I built on one champion and lost the quarter when he left, which cost me 18 points, and here is what I do differently now. Name the team-wide context if it is true and checkable (nobody on the team made plan that year, the segment's quota was reset the following quarter), because that is verifiable through the same backchannel that would otherwise sink you. For a layoff, say the function or segment that was cut, your attainment at the time, and a manager who will confirm both. Then stop. Self-justification past three sentences reads as a problem.
Treat your own questions as a graded exercise, because at this level they are. Asking about team attainment distribution, territory definition, ramp quota, win rates, average cycle, the discounting approval path, and how long the VP has been in the seat shows you are commercial and screens the job at the same time. Asking nothing, or asking only about culture and career path, reads as someone who has not run a business. One good closing question that is also genuinely useful: what does an AE who fails here usually get wrong in the first six months.
The loss post-mortem is where good candidates separate themselves. Tell the story of a deal you should have won, name the cause with no cushioning (single-threaded, wrong level, no compelling event, I believed a champion who had no budget authority, I let procurement meet the CFO before I did), and name the specific thing you changed in your process afterwards. Interviewers at this level have lost deals the same way, and a candidate with no losses reads as junior or evasive.
What gets people rejected, in roughly the order it happens: numbers that do not survive the second question; we-language that makes it impossible to isolate what the candidate did; pitching in the mock call; deal stories with no compelling event, which make you sound like an order-taker on deals that would have closed anyway; single-threaded deal stories, which is the specific thing enterprise managers listen for; claiming customers the company sold and you did not own; attainment with no denominator; unexplained short tenure; asking no commercial questions; and badmouthing a former manager, which is reliably checked and ends processes outright.
- Walk me through your largest deal, start to finish. Who was the economic buyer and when did you first speak to them.
- How did you source your pipeline, and what percentage of closed revenue came from your own sourcing.
- Tell me about a deal where your champion left or was reorganized out mid-cycle.
- What was your quota, what was attainment, what was the ranking and out of how many.
- Tell me about a year you missed your number. What was the gap and what changed afterwards.
- How do you build a business case, and whose numbers are in it.
- Run a first call with me. I am a CISO at a 12,000-person organization and I have 30 minutes.
- Build an account plan for one of our target accounts and present it.
- What is your pipeline coverage ratio, and how many first meetings a week do you need to make your number.
- Tell me about a deal you lost that you should have won.
- Tell me about a time you oversold, or sold something delivery could not deliver.
- How do you handle procurement when they hold the contract until the last day of the quarter.
- What would you do in your first 30, 60 and 90 days with a cold named-account patch.
- What questions do you have for me. Treat this as part of the test, not the end of it.
Pay, the comp plan, and the territory questions to ask before you sign
Enterprise software comp has a standard shape, and knowing the shape protects you from a bad offer that looks good. Base and variable are usually split close to 50/50 at on-target earnings. Quota is set by a rule of thumb of roughly four to six times OTE, and that arithmetic is where the familiar ten-percent-of-bookings commission rate at plan comes from; it is a heuristic, not a law, and plans vary. There are accelerators above 100 percent attainment, usually stepped, and often a decelerated or zero rate on the first portion of quota. There is frequently a ramp period of one or two quarters with a reduced quota, sometimes supported by a draw. And the plan is almost always a separate document from the offer letter, which is the document you must actually read.
Do not accept a quoted band from anyone, including a recruiter, as a fact about the market. Three checkable sources are better. First, posted ranges: pay-transparency laws require ranges in postings in a growing list of states, Colorado, California, Washington, New York, Illinois, Minnesota, Maryland, Vermont, New Jersey, Massachusetts and Hawaii among them, so check the current rule for the state in the posting. For sales roles the critical question is whether the posted range is base only or OTE, which is often ambiguous and always worth asking directly. Second, the BLS Occupational Employment and Wage Statistics data, which publishes wage distributions by metro area for the codes enterprise sellers are classified under, principally 41-4011 (sales representatives, wholesale and manufacturing, technical and scientific products) and 41-3091 (sales representatives of services, all other). It is authoritative, it includes commission earnings, and it top-codes the highest wages, so read the upper percentiles as a floor rather than a target. Third, RepVue, where sellers self-report quota attainment rates, OTE and quota by employer. That data is self-reported and directional, but attainment rate by employer is the single most decision-relevant number available to you and it is published nowhere official.
Read the comp plan document before you resign anything, and read for seven specific things. When commission is earned: on booking, on invoice, or on cash collected, which can be a difference of months. The clawback: if a customer does not pay, or churns inside a window, how much comes back and over what period. Whether a draw is recoverable, which turns a cushion into a debt. How multi-year deals are credited, full total contract value, year-one ACV only, or something in between, which changes your entire selling behavior. How expansion, renewal and partner-led deals are credited, and whether house accounts in your patch pay you anything. Whether there is a cap, anywhere. And the clause, present in nearly every plan, allowing the company to change the plan and the territory at its discretion, which is why you negotiate the first year concretely rather than relying on the structure holding.
Ramp is the thing to negotiate hardest, because it is where enterprise sellers get hurt by arithmetic rather than by performance. A twelve-month average cycle against a full annual quota in year one is a trap: nothing you source in month one can close inside the plan year, so you are dependent on inherited pipeline that may not exist. The reasonable asks are a ramped quota over two or three quarters, a non-recoverable draw or guarantee for the first two quarters, and credit for deals closing shortly after the plan year boundary. These are standard and routinely granted when asked for in writing. They are rarely offered.
Then diligence the territory, because the territory decides your income far more than the OTE does. Is the seat new or a backfill, and if a backfill, what did the previous holder attain and why did they leave. Are accounts named and carved, or do you build the list, and can you see the list before you sign. How many of your accounts are already customers, and does that pay you. What pipeline comes with the seat, in dollars and by stage. Is the sales engineer dedicated or shared, and shared how many ways. What is the inbound and outbound split in practice. What is the current win rate and average cycle in this segment. Who approves discounts and is there a floor. How long has the VP been in the seat, and how many VPs have there been in three years, because a comp plan survives roughly as long as the leader who wrote it.
Finally, ask for the attainment distribution, in the first interview rather than the last. What percentage of AEs on this team hit quota last year, and what did the spread look like. A team where most sellers make plan on a modest OTE will pay you more over three years than a team with a headline OTE where the top two sellers absorb the territory's only real accounts. If a hiring manager will not answer, or answers with the top performer's number, you have learned the thing you needed to know. Sales leaders running a healthy team are generally pleased to be asked, because the answer is a recruiting advantage and they know it.
- Ask whether a posted range is base or OTE. In pay-transparency states it is often base only, and the difference is roughly double.
- Read the comp plan, not the offer letter: earning trigger (booking, invoice, cash), clawback window, recoverable draw, multi-year crediting, expansion and renewal crediting, house accounts, caps, and the change-at-discretion clause.
- Negotiate ramp in writing: reduced quota for two to three quarters, a non-recoverable guarantee for the first two, and credit for deals that close just past the plan-year boundary.
- See the account list before you sign, or at least the count, the segment definition, and how many are existing customers.
- Ask what the previous holder of this seat attained and why they left. A backfill on a carved territory with no pipeline is a specific and common trap.
- Ask for team attainment distribution and the sales engineer coverage ratio. These two predict your first-year income better than OTE does.
- Check RepVue for the employer's self-reported attainment rate, and read BLS wage data for your metro as a floor. Treat neither as a quote.
- Count the VPs. Three sales leaders in three years means the plan, the territory and the ideal customer profile will all change under you.
What an enterprise account executive has to know about AI in 2026-27
Start with the honest version, because overclaiming here will cost you an interview. The core of this job has not been automated and is one of the harder things in go-to-market to automate: getting seven to fifteen people inside a large organization to agree on spending money, surviving a security review and a procurement department, and holding an executive relationship through a reorganization. No tool does that, and the enterprise sellers who were good in 2023 are still good. What changed is the week around the job, how much pipeline you are personally expected to create, how closely your deals are inspected, and a new stage inside the deal itself. If you walk into an interview and say AI transformed enterprise selling, an experienced sales leader will hear someone who has not recently carried a quota.
The largest real change is upstream of you: prospecting support per enterprise seller is thinner than it was. AI-assisted research and sequencing (Clay, Apollo, ZoomInfo, Outreach, Salesloft and the AI-SDR category) made outbound volume close to free, and at the same time the large mailbox providers tightened bulk-sending requirements, Google and Yahoo first and others after, so cold email got both more crowded and more filtered. Whatever the cause at any one company, the screening consequence is now standard: what percentage of your closed revenue did you source yourself. The answer marketing and my SDR gave me leads ends processes that your numbers would otherwise have won. Be careful in the other direction too. Employers' results with autonomous AI prospecting at enterprise deal sizes have been uneven, so do not arrive evangelizing a tool and do not assume the team has one. Ask what prospecting support the seat actually has, and whether that is a person, a tool, or nothing.
Every call you make is recorded, transcribed and scored. Conversation intelligence is default at enterprise vendors, Gong for call capture and deal inspection, Clari for forecasting, with equivalent capability now native in Salesforce and in the major meeting platforms. The consequence is that deal inspection runs on signals rather than on your word in the pipeline review: is there a next meeting on the calendar, has anyone from the economic buyer's level been on a call, has the mutual action plan moved this week, how many distinct stakeholders are in the thread. Three practical implications. Optimistic forecasting gets caught in your first quarter rather than your third. Your onboarding will largely be a call library, so ask for access to it. And some employers will ask about metrics now measured per rep, including next-step rate, talk ratio and stakeholder count per opportunity.
CRM admin and the qualification fields are partly auto-filled from transcripts now, by Salesforce Agentforce and Einstein, HubSpot Breeze, and the deal boards in Gong and Clari. The practical effect is that being good at Salesforce is no longer a thing to put on a resume. The differentiator is whether your deal record is true. An auto-populated MEDDPICC field is a draft, not qualification: a champion the transcript inferred is not a champion, a generated close plan the customer has never seen is not a close plan, and the characteristic 2026 forecast failure is a deal that looked fully qualified in the system because a model filled the fields in. Being able to describe how you verify the record, and one specific time the system was confidently wrong, is a strong answer to a question most candidates fumble.
Research parity has removed an old edge. Knowing an account, its filings, its tech stack, its org chart and its trigger events used to be hours of work that distinguished diligent sellers. It is now minutes, and your competitors on the deal have the same minutes. Generic personalization is worth nothing because buyers receive it constantly and recognize it instantly. The bar moved to a hypothesis that is specific, falsifiable, and sourced from something a model will not hand you: a conversation with someone who left that company, your own customer in the same vertical facing the same regulator, a systems integrator already inside the account, or something you saw in the buyer's actual environment. In the interview, this is exactly what the account-plan exercise is now testing, whether or not anyone says so.
The buyer changed more than you did. Enterprise buying committees now run their own assisted vendor comparisons, draft their own security questionnaires, and benchmark your pricing against public and crowdsourced data before the first call. They arrive later in their own process, better informed, and materially better armed in procurement. The consequences are fewer and shorter conversations, much less value in educating a buyer about a category, and a harder discounting endgame. And there is a new objection you must answer flatly and without defensiveness, now raised in deals that have nothing to do with AI products: why would we not build this ourselves with an LLM. The usable answer is not a feature list. It is total cost over three years, who maintains it, what happens when the person who built it leaves, the compliance and audit surface they inherit, and an honest statement of where building is in fact the right call.
Last, the new gate in the paper process, which is the cleanest differentiator available to you in a 2026-27 interview. If what you sell touches customer data or embeds a model, regulated buyers have added a review stage that did not exist in 2023: an AI governance or model-risk committee, asking about training data provenance, sub-processors, retention and deletion, human oversight, and model-change notification. European deployments bring EU AI Act commitments into the contract language, and because that regime's obligations and timetable have themselves been amended, buyers' legal teams tend to ask for commitments and notification rights rather than for certainty. It is a real, nameable stage, it adds weeks, it often sits in a function (model risk, data governance, a chief AI officer's office) that your champion does not control, and it is routinely discovered at the end of a quarter by sellers who did not map it. An AE who can describe that path concretely, say who owns each step, and explain how they run it in parallel from week three rather than serially at the end, is visibly a better hire than one who cannot.
Self-sourcing enterprise pipeline now that prospecting support is thinner
Employers have cut the ratio of human prospectors to enterprise sellers, and the tooling that was supposed to replace them has performed unevenly at large ACV. Pipeline creation came back to the AE, and self-sourced percentage is now asked in the first screening call. A seller whose number was built on inherited pipeline cannot be compared against a seller who built their own, and hiring managers resolve that uncertainty by not hiring.
Show it: Give the percentage with the method behind it: 61 percent of FY25 closed ACV was self-sourced; roughly half of that came from four customer champions who changed companies, the rest from partner introductions and an event-driven motion around a regulatory deadline. Name the tools you actually use and what you use them for, research, enrichment, sequencing, and be ready to state your reply and meeting rates. If you have not sourced, say so and say what you are doing about it now, because the number is easier to forgive than the evasion.
Operating where every call is recorded, scored and inspected
Conversation intelligence moved pipeline reviews from narrative to evidence. A deal with no next meeting booked and nobody above director level on a call is visibly not a deal, whatever the stage field says. Sales leaders have been burned by optimistic forecasters and now have tooling that catches them, so they screen for sellers whose forecast discipline is a habit rather than a quarterly performance.
Show it: Talk about your own forecast accuracy as a number if you have it, and describe your commit criteria concretely: what has to be true for you to call a deal committed, and what you do when it is not. Mention that you use call recordings deliberately, for example reviewing your own discovery calls before a second meeting or sending a recording to a sales engineer before a technical session. One sentence about a deal you pulled out of the forecast yourself, before your manager asked, does more than any claim about honesty.
Building an account hypothesis that survives the buyer and your competitors having the same research tools
Account research is no longer scarce, so it is no longer an edge, and buyers recognize machine-assembled personalization on sight. What remains scarce is a specific claim about that organization's business that could be wrong, grounded in something not publicly scrapeable. The account-plan exercise in the interview loop is testing exactly this, and the polished generic plan now reads as a tell rather than as diligence.
Show it: In the exercise, quote one real source (an earnings call line, a regulatory filing, a published incident, a named job posting) and build one falsifiable hypothesis on it, then say what you do not know and the three calls you would make in week one to find out. Name a human source you would actually use: a former employee, a systems integrator already in the account, an existing customer under the same regulator. Write the committee out by title and say which one you would enter through and why.
Mapping and sequencing the AI governance and model-risk review inside the paper process
This is a genuinely new stage in enterprise deals at regulated buyers, it sits outside your champion's authority, and it adds weeks that sellers discover too late. It is also the cleanest thing you can demonstrate that a mid-market seller cannot, because mid-market buyers do not have model-risk committees. Hiring managers selling anything with a model in it are actively looking for someone who has already been through it.
Show it: Describe the path as steps with owners: who raises it, which function owns it (model risk, data governance, privacy, a chief AI officer's office), what artifacts they demand (data-flow diagrams, training-data provenance, sub-processor lists, retention and deletion terms, human-oversight description, model-change notification commitments), where EU AI Act obligations come into the contract if any part of the deployment touches Europe, and which clauses get negotiated. Then say when you start it: in parallel from week three, not after verbal agreement. One real story of a deal where this nearly slipped a quarter is worth more than the whole framework.
Answering why not build this ourselves with an LLM, without flinching
This is now a standard objection in enterprise deals that have nothing to do with AI products, because buyers have in-house teams that can prototype something plausible in a fortnight. A seller who gets defensive, or who dismisses it, loses credibility with the technical evaluator in the room. A seller who takes it seriously and reframes it as a three-year total-cost and ownership question keeps the deal and often converts the person asking.
Show it: Have the answer rehearsed to four points: build and maintenance cost including the engineers' opportunity cost, who owns it when they leave, the compliance, audit and security surface they inherit, and the parts of the problem a prototype does not touch (integrations, edge cases, support obligations, change management). Then add the line that earns trust: name the cases where building genuinely is the right call, and say you have advised a prospect accordingly. Interviewers notice candidates who can concede a point without losing the room.
Selling and negotiating consumption and usage-based structures, not only seat-based multi-year
AI-era products pushed commercial models toward consumption, credits and committed spend, and procurement has learned to resist long commitments on fast-changing technology. That changes the deal you are negotiating: you are selling a commitment level and a ramp, not a seat count, and you forecast expansion from usage signals rather than from headcount growth. Many sellers with excellent seat-based records have never structured one of these.
Show it: If you have done it, say what you structured: committed spend with a ramp schedule, the overage rate, rollover terms, a usage floor, a true-up mechanism, the term, and what the customer traded for the discount. If you have not, do not pretend; say you have sold seat-based and subscription structures and show that you understand what changes, particularly that renewal risk moves from license utilization to actual consumption, and that you would want usage visibility from month one.
Using AI for your own deal preparation without outsourcing qualification to it
The tooling is genuinely useful for first-draft business cases, call prep, competitive briefs, security-questionnaire responses and executive summaries, and declining to use it looks obtuse. The failure mode is specific and expensive: a fluent, confident, slightly wrong artifact that reaches a customer with your name on it, or a qualification field filled in by a model and then relied on in a forecast. Accountability did not move to the tool.
Show it: Name a concrete before-and-after with your own measurement: first-draft business cases went from two hours to twenty minutes, and the discipline is that no number reaches the customer until the customer's own finance contact has confirmed it. Then name what you deliberately do not delegate: the discovery questions, the champion assessment, the forecast call, and anything a buyer will quote back to you. One story about a generated artifact you caught before it went out is the most credible version of this.
Holding a technical conversation about what you sell alongside the sales engineer, not instead of them
Technical evaluators and security reviewers ask harder and earlier questions now, especially about data handling and model behavior, and they discount a seller who cannot follow the answer. The opposite failure is worse: an AE who answers a technical question wrong, or oversells capability, creates a problem the sales engineer has to walk back, and the panel's sales engineer is specifically watching for it in your interview.
Show it: Be able to explain at a credible level what the product does with customer data, where it runs, what it is and is not trained on, and the two or three limitations you proactively disclose to buyers. Say plainly where your knowledge stops and that you bring the sales engineer in rather than guessing. If you are moving from a less technical segment, a foundational certification in the relevant ecosystem (cloud practitioner level, or the platform you will sell alongside) is a few days of work and signals that you will do the homework.
What a screen is looking for
These are the terms that a resume screen, human or automated, is matching against for this role. Use the ones that are true of you, in the words the posting uses.
- Enterprise sales
- Enterprise account executive
- Enterprise AE
- Account executive
- Strategic account executive
- Strategic accounts
- Named accounts
- Major accounts
- Global accounts
- New logo acquisition
- New business development
- Quota attainment
- Quota over-achievement
- Annual contract value (ACV)
- Annual recurring revenue (ARR)
- Net new ARR
- Total contract value (TCV)
- Bookings
- Pipeline generation
- Pipeline coverage
- Self-sourced pipeline
- Outbound prospecting
- Territory planning
- Account planning
- Account mapping
- Stakeholder mapping
- Multi-threading
- Executive engagement
- Executive sponsor
- C-suite selling
- Economic buyer
- Champion development
- Buying committee
- Consensus selling
- Discovery call
- Qualification
- MEDDIC
- MEDDPICC
- Command of the Message
- Challenger Sale
- SPIN Selling
- Sandler
- Miller Heiman Strategic Selling
- ValueSelling Framework
- Business case development
- Business value assessment
- ROI and value analysis
- Mutual action plan (MAP)
- Close plan
- Compelling event
- Competitive displacement
- RFP and RFI response
- Proof of concept (POC)
- Pilot to production
- Security review
- Third-party risk assessment
- SOC 2
- Data processing agreement (DPA)
- Master services agreement (MSA)
- Procurement negotiation
- Legal redlines
- Contract negotiation
- Deal desk
- Pricing and discounting
- Multi-year agreement
- Enterprise license agreement (ELA)
- Consumption and usage-based pricing
- Committed spend
- Expansion and upsell
- Cross-sell
- Land and expand
- Renewals
- Net revenue retention (NRR)
- Forecasting
- Forecast accuracy
- Deal inspection
- Sales cycle management
- CRM hygiene
- Salesforce
- HubSpot
- Gong
- Clari
- Outreach
- Salesloft
- Apollo
- ZoomInfo
- LinkedIn Sales Navigator
- Clay
- Highspot
- DocuSign
- Partner and channel co-selling
- Systems integrator (SI) partners
- AWS Marketplace
- Sales engineer collaboration
- Customer success handoff
- Onboarding and ramp
- President's Club
- Territory carve
- Verticalized selling
- Financial services sales
- Healthcare and health system sales
- Public sector sales
- FedRAMP
- GSA Multiple Award Schedule
- Regulated industry sales
- SaaS sales
- Platform sales
- Solution selling
- AI governance review
- Model risk review
- EU AI Act
- Vendor credentialing
- FINRA SIE
- FINRA Series 7
- Insurance producer license
Mistakes that cost people this job
Putting attainment percentages on the resume without the quota they were measured against.
Always give the denominator and the dollars: 112 percent of a $1.8m new-ACV quota ($2.02m), ranked 4 of 31. A sales leader reads 180 percent of an unnamed quota as a small quota, and asks a question you do not want asked. Label pro-rated years, partial years, ramp quotas and rebaselined numbers on the page rather than in the interview.
Listing customers the company sold rather than deals you personally owned.
List only accounts where you can name the economic buyer, who signed, and the term. Write co-sold where it was co-sold and say what you owned. The forensics interview finds this within two questions, and being caught on one logo contaminates every other line on the page.
Applying to enterprise postings with a resume that silently reads mid-market: high deal counts, no cycle lengths, no committee, no paper.
Reorder so your largest and longest deals are first, add stakeholder counts and functions, add the economic buyer's level, add the security review, DPA, procurement and legal path, state the term length, and state the cycle in months. Replace deal volume as a headline with ACV. A high count of small deals is evidence against you in this search.
Relying on cold applications into postings as your main channel.
Spend most of your time on the channels that convert: former managers who got promoted, sales engineers and customer success leads you worked deals with, and champions at your own customers who moved to new companies. Two or three durable relationships with specialist sales recruiters are worth maintaining when you do not need them. When you do apply cold, reach the hiring manager directly with four sentences and a one-page deal sheet, and lead with the fact that you already sell into their target accounts.
Pitching in the mock discovery call.
Open with an agenda, get agreement on it, ask business questions before product questions, quantify the problem in the buyer's own units, ask who else must be involved by role, handle one objection without discounting, and close on a next step with a date and named people. You can score well in a mock call without ever describing the product. Candidates who demo in minute four get a one-word note: pitched.
Telling deal stories with no compelling event.
For every deal you cite, name the thing that made the buyer act on a date: a contract expiry, an audit finding, a regulatory deadline, a migration, a new executive's mandate, a system end-of-life. Without one you sound like you took an order on a deal that was going to close anyway, which is exactly the doubt an enterprise hiring manager is testing for.
Single-threaded deal stories, where everything ran through one champion.
Count your stakeholders per deal, by function and level, and lead with the number. Say how you reached the economic buyer and by what route. Have a prepared, specific answer to the champion-leaves question that starts before the departure, not after it. This is the single thing enterprise managers listen hardest for.
Hiding or over-explaining a year you missed quota, or a layoff.
Give it in five parts and then stop: the number and the gap, the cause stated plainly, what was inside your control, what you changed, and what happened next. For a layoff, name the function or segment that was cut, your attainment at the time, and a manager who will confirm both. Both get verified through the backchannel anyway, and a straight account of a bad year costs far less than a discovered one.
Coming from a famous brand with inbound demand and not addressing it.
Volunteer it in the first conversation: say whether demand was inbound or created, whether the buyer knew the company before your call, and whether you had a dedicated sales engineer. Then bring the evidence against the doubt, which is the deals you created from nothing. Hiring managers reject surprises, not gaps.
Stacking short tenures in a job where one sales cycle can run eighteen months.
Address it before anyone asks. Three roles in three years reads as someone who has never personally carried a deal from sourcing to signature, which is the thing being hired for. Give the reason, name any deal you did close end to end, and say what you are optimizing for now. Unexplained short tenure ends enterprise processes on its own.
Asking no commercial questions, or asking only about culture and progression.
Ask what percentage of the team hit quota last year and how it was distributed, whether the seat is new or a backfill and what the previous holder attained, whether accounts are named and carved, what pipeline comes with the seat, the sales engineer coverage ratio, the win rate and average cycle, and how long the VP has been in post. These questions advance your candidacy and screen the job at the same time.
Accepting a full annual quota in year one against a nine to twelve month average cycle.
Negotiate ramp in writing before you resign: a reduced quota for two or three quarters, a non-recoverable guarantee for the first two, and credit for deals closing just past the plan-year boundary. Nothing you source in month one can close inside the plan year, so an unramped quota means betting on inherited pipeline you have not been shown.
Reading the offer letter and not the compensation plan.
Read the plan document for when commission is earned (booking, invoice or cash collected), the clawback window, whether any draw is recoverable, how multi-year deals are credited, how expansion and renewals are credited, whether house accounts pay, any cap, and the clause letting the company change plan and territory at will. That last clause is why you negotiate year one concretely.
Assuming the backchannel reference will not happen, and speaking freely about a former manager.
Assume a reference you did not list will be called, because in enterprise sales it routinely is, and that the two questions will be whether you hit your number and whether they would hire you again. Line up and brief your own references, keep your attainment evidence on file, and describe past employers neutrally even when they deserve worse. Badmouthing a former manager ends processes outright.
Questions people ask
What does an enterprise account executive actually do?
An enterprise account executive carries a revenue quota for selling into large organizations, typically with contract values in six figures, sales cycles of 6 to 18 months, and a buying committee of roughly five to fifteen people. The week divides into four things: creating pipeline in a small number of named accounts, running discovery and building a business case in the customer's own numbers, assembling consensus across the business owner, technical evaluators, security, procurement, legal and finance, and forecasting honestly to their own leadership. Most of the work is not persuading one buyer; it is engineering agreement among many, then surviving the paper process that follows. The clearest test of whether a role is genuinely enterprise is the account definition and the cycle length, not the title.
What is the difference between an account executive and an enterprise account executive?
Segment, contract value, cycle length and committee size. A mid-market account executive typically handles 50 to 200 accounts with contract values in the tens of thousands and cycles measured in weeks to a few months, often with meaningful inbound demand. An enterprise account executive typically holds 20 to 50 named accounts or fewer, with six-figure contract values, cycles of 6 to 18 months, a formal security review, procurement and legal negotiation, and a buying committee rather than a buyer. The behaviors differ more than the titles suggest: enterprise sellers must tolerate long stretches with nothing closing, multi-thread deliberately, and sell internally as much as externally. Hiring managers screen for that difference, which is why a strong mid-market record does not automatically clear an enterprise search.
Do you need a degree or a certification to be an enterprise account executive?
No. Enterprise software, SaaS and services sales has no license, no qualifying exam and no governing body, and very few postings require a degree. The de facto credential is a verifiable quota attainment history that holds up under a reference call. Sales methodology training (MEDDIC or MEDDPICC, Force Management's Command of the Message, Challenger, Miller Heiman, ValueSelling) is worth knowing and is nearly always employer-delivered; a self-purchased certificate carries little weight, while applying the framework to a real deal out loud carries a lot. The exceptions are adjacent roles where a real credential gates the seat: FINRA registration for securities, where you can sit the SIE exam unsponsored but need a sponsoring firm for the Series 7 or 79 and the state exam; a state insurance producer license for insurance and benefits; hospital vendor credentialing for medical device sales; and a security clearance for some public-sector work.
How do I move from mid-market to enterprise sales?
The most reliable route is an internal carve-out at your current company: ask for five to fifteen named large accounts alongside your patch, with a quota adjusted for cycle length, and make the ask with a written case showing the specific opportunities and the committee in each. The second route is a lateral to a company one or two tiers smaller that will trade brand recognition for deal scope. Either way, the thing that changes the conversation is one bridge deal you actually ran with enterprise shape: a committee of six or more, at least one level above your natural entry point, a formal security review, a negotiated contract, a term longer than twelve months, and a compelling event you can name. Expect the move to take 12 to 24 months of deliberate work, and expect a straight jump from SMB or SDR into enterprise to be rare and usually unsuccessful, because the first full cycle outlasts most employers' ramp patience.
What does multi-threading mean in enterprise sales, and how do I prove I have done it?
Multi-threading means having live, independent relationships across a buying committee rather than running the deal through one champion, so the deal survives a departure, a reorganization or a budget move. Prove it with counts, per deal: how many individuals you had real conversations with, their functions (business owner, technical evaluator, security, procurement, legal, finance, executive sponsor), how many levels above your entry point you reached, who the economic buyer was and the week you first spoke to them, how you got there, and who your second champion was. Write it into the achievement line on the resume rather than claiming it as a skill, bring a sanitized stakeholder map and mutual action plan to the interview, and prepare the specific story of a deal where your champion left. The lie detector interviewers use is simple: who at that account would take your call today.
What does an enterprise account executive interview process look like?
Usually five stages over two to five weeks. A recruiter numbers screen that collects quota, attainment by year, average and largest contract value, cycle length, segment definition and self-sourced pipeline percentage. Deal forensics with the hiring manager, who picks one deal off your resume and goes down into it until the detail runs out. A live exercise, most often a 30-minute mock first call with the manager playing a named persona, or an account plan or 30/60/90 presentation on one of their real target accounts. A cross-functional panel including a sales engineer and often someone from customer success. Then a VP or CRO conversation about pipeline math and judgment. Backchannel references are routine on finalists, including people you did not list, and the two questions asked are whether you hit your number and whether they would hire you again.
How much does an enterprise account executive earn?
The structure is more useful to know than any quoted band. Enterprise software compensation is usually split close to 50/50 between base salary and variable, quota is set by a rule of thumb of roughly four to six times on-target earnings, which is where the familiar ten-percent-of-bookings commission rate at plan comes from, and there are stepped accelerators above 100 percent attainment. For real numbers use three sources rather than a figure someone quoted you: posted ranges in pay-transparency states (Colorado, California, Washington, New York, Illinois, Minnesota, Maryland, Vermont, New Jersey, Massachusetts and Hawaii among them), always asking whether the posted range is base or on-target earnings; the BLS Occupational Employment and Wage Statistics data for SOC 41-4011 and 41-3091, the codes most enterprise sellers fall under, read as a floor because BLS top-codes the highest wages; and RepVue for self-reported attainment rates by employer. Attainment rate matters more to your actual income than the headline OTE does.
What should an enterprise account executive resume include?
Six numbers per role in the top third of page one: quota in dollars, attainment as a percentage with the dollar figure beside it, ranking with its denominator, average contract value, average cycle length, and the share of pipeline you sourced yourself. Then two or three achievement lines, each a specific deal with the contract value, term, stakeholder count and functions, the economic buyer's level, the competitor or status quo displaced, and the paper path (security review, data processing agreement, procurement, legal). Name only customers you personally owned, and describe rather than name accounts your employer has not publicly announced. Cut the adjective summary, the CRM skills grid, bare methodology acronyms, we-phrasing, responsibilities language and anything on a third page. Keep a separate one-page deal sheet with five deals and every number for the interview itself.
Has AI reduced the number of enterprise account executive jobs?
Not visibly at the enterprise AE level, and the honest shape of the change is upstream and downstream of the seat rather than in it. The prospecting layer thinned: AI-assisted research and sequencing made outbound volume close to free, mailbox providers tightened bulk-sending rules, and support per enterprise seller is leaner, which pushed pipeline creation back onto the AE and made self-sourced percentage a standard screening question. Deal inspection and CRM administration are substantially automated by conversation intelligence and transcript-driven field population, which means optimistic forecasting is caught faster and being good at Salesforce is no longer a differentiator. The core of the job, getting a committee of senior people inside a large organization to agree to spend money and surviving procurement, is intact. What is new inside the deal is an AI governance and model-risk review stage at regulated buyers, and a routine objection about building the thing in-house with an LLM.
How do I explain a year I missed quota, or being laid off?
Plainly, in five parts, and then stop: the number and the size of the gap, the cause stated without cushioning, what was inside your control, what you changed, and what happened next. Territory rebaselined in Q2 and two deals slipped into the following year is a legitimate reason; so is I built on one champion and lost the quarter when he left, and here is what I do differently now. If team-wide context is true and checkable, say it, because the same backchannel reference that would otherwise sink you will confirm it. For a layoff, name the function or segment that was cut, your attainment at the time, and a former manager who will confirm both. Nearly every seller with a long career has a bad year, and hiring managers discount it heavily when you volunteer it; what they do not forgive is finding it themselves.
Put this on a resume in about a minute
Paste your history once and point it at the Enterprise Account Executive posting you are looking at. No account, no card.
Build my resume free More roles