Most Founding AE job descriptions fail because they are written as filters — requirement lists designed to screen people out. A strong Founding AE has options and is evaluating you, so the description has to work as a pitch instead: what has actually been sold and to whom, what the founder will hand over, and what happens if the motion does not transfer. Lead with the business and the honest flaw, and put the requirements list last.
You wrote the posting. It says the role is high-ownership and high-impact, that you are early and moving fast, that the right person will help build the playbook. Every word is true. It is also, almost verbatim, what the other forty companies hiring a Founding AE this quarter wrote.
Why do most Founding Account Executive job descriptions fail?
They fail because they are written as filters when the market requires a pitch. A job description written as a filter assumes a queue of applicants and a need to narrow it — so it leads with requirements, lists responsibilities, and treats the candidate as the thing being evaluated. That assumption holds for a mid-market AE role at a Series C company. It does not hold for a Founding AE.
The person you want is currently employed, hitting quota, and being contacted regularly. They are not applying to you. They are deciding whether to take a call. And when every posting makes identical promises, the reader cannot distinguish between them, so the decision defaults to the safest option — which is staying put. This is the same dynamic that stalls your sales pipeline when every vendor in your category sounds the same, and it has the same cause: undifferentiated messaging produces no decision, not a slow decision.
What is a Founding AE candidate actually screening for?
They are screening for whether the motion is real and whether the founder will let go of it. Those two questions sit underneath almost everything a good candidate asks in a first conversation, and neither one appears in a standard job description.
I have written the demand-side version of this from the seat — the seven signals that separate a good Founding AE role from a bad one. It is worth reading as the answer key. The posting you write is being graded against that list whether or not you know the list exists.
| Element | Job description written as a filter | Role pitch written to a candidate with options |
|---|---|---|
| Opening | Company boilerplate and mission statement | What the business actually sells, to whom, and at what volume |
| Traction | Vague growth language, or omitted | A specific revenue number and who closed it |
| Problems | Hidden until the third interview | Volunteered up front, with the reason it is an opportunity |
| Requirements | Leads the document, eight to twelve bullets | Last section, short, with selling ability separated from domain experience |
| Compensation | Competitive, commensurate with experience | Base, OTE, split, and equity range stated plainly |
| Who it is not for | Absent | Named explicitly, with the reason |
Most founders are wrong about their own constraint.
The thing you're trying to fix is usually a symptom of something upstream. Twelve questions, under five minutes, and you get your primary GTM constraint named — plus where you stand on all six dimensions. No email needed to see the result.
Free. Built from 300+ founder conversations since May 2025.
Rather read than click? 100 Founders is my weekly note — one pattern from those conversations, every Saturday.
What should a Founding Account Executive job description actually contain?
Six parts, in an order that inverts the standard template. Sell the business, then volunteer the flaw, then name why previous attempts failed, then answer the ceiling question, then disqualify explicitly, and only then list the facts.
The business first. Revenue, growth, what makes the product hard to copy. A candidate cannot evaluate the seat without evaluating the company, and every JD skips straight to duties.
The volunteered flaw. This is the load-bearing part. Naming the thing that is genuinely broken — the pipeline that arrived by inbound rather than motion, the pricing that has never been tested, the churn nobody has diagnosed — is what makes the rest of the document believable. It also doubles as the pitch, because the flaw is the opportunity: an untested ceiling is worth more to a strong closer than a mature territory.
Why previous hires did not work. If you have hired a seller before and it did not land, say what the pattern was. This tells the right candidate exactly what is being screened for and why they would win it, which is far more motivating than a requirements list. If you have not hired before, say that too.
The ceiling. Answer it unprompted. Is the good territory already claimed? Is the number defensible or expandable? This is the top private question of any senior closer.
Who it is not for. Repelling the wrong person authenticates everything else. A posting that could not possibly disqualify anyone reads as marketing.
The facts, last. Location, reporting line, buyer, deal size, cycle length, and compensation. State the numbers — see what to actually pay a first sales hire if you have not set the range yet.
How do you write the honest version when the motion is not proven?
You state the real number and let it be small. A founder with 400,000 in ARR across eleven customers has something specific and verifiable to say; a founder who writes about strong early traction has said nothing, and the candidate knows it.
This is the same discipline that separates a real positioning claim from a hollow one. Being better in the abstract is not a differentiator, and it is not product-market fit either. Small and checkable outperforms large and vague, in both directions — to buyers and to candidates.
The related question is whether the motion is transferable yet at all. If the answer is no, the posting is not your problem. A candidate who joins a role where the founder cannot articulate why deals close will fail regardless of how well the job was described, and you will spend six months learning that.
Where should the job description actually live?
In two places, at two lengths. Job boards reward brevity and serious candidates reward substance, so a single document tuned for both ends up serving neither.
The short version goes on the board and in the LinkedIn post: the business in three sentences, the number, the flaw, the comp, and a link. The long version is a page on your own site that makes the full case. That page is also the thing you send directly when you are reaching out to someone who was not looking.
I run this structure myself on the roles I am filling right now. Worth reading as a worked example rather than a template — the specific role rotates as searches change, but the shape holds: business and moat first, the honest flaw second, the ceiling third, disqualification fourth, and the factual block at the bottom.