When you’re hiring an AI Account Executive for a product that’s still being built, the job description needs to do two things at once: attract the right person and filter out the wrong one. The right AE for an evolving AI product isn’t someone who needs a polished pitch deck and a proven playbook. They’re someone who can build the playbook while selling from it. The questions below unpack exactly how to write that job description well.
What should an AE job description include when the product isn’t finished?
An AE job description for an unfinished product should include the current state of the product, the ideal customer profile you’re targeting, what success looks like in the first 90 days, and a clear picture of the sales motion you expect. Candidates need enough context to self-select honestly, and you need enough signal to filter out people who can’t operate in ambiguity.
Beyond the basics, focus on what the AE will actually own. Will they be building pipeline from scratch? Closing deals that the founders have been carrying? Feeding product insights back to the roadmap team? These specifics matter more than a generic list of responsibilities. When the product is still evolving, the role is partly sales and partly discovery, and the job description should reflect that honestly.
Also include what support the AE will have. Do they have a BDR? Marketing budget? A technical pre-sales resource? For an AI startup where the product is complex and still changing, the presence or absence of these resources will make or break whether a strong candidate says yes.
How do you describe a product that keeps changing in a job posting?
Describe your product by its core problem and the value it already delivers, not by its current feature set. If the product is changing, anchoring your job description to specific features will make it outdated within weeks. Instead, describe the category you’re competing in, the type of customer you serve, and the outcome your product helps them achieve.
Something like “We help mid-market finance teams reduce manual reporting time through AI-driven automation” is far more durable than listing specific integrations or modules that may shift. It also tells a candidate what they’ll be selling at a meaningful level without overpromising what the product can do today.
If there are known gaps or limitations, you don’t need to list them in the job description, but you should be prepared to address them honestly in the first conversation. Candidates who have sold early-stage AI products before will ask. The ones who don’t ask are sometimes the ones you should be more worried about.
What kind of AE thrives in an early-stage or evolving product environment?
The AE who thrives in an early-stage or evolving product environment is one who is genuinely comfortable with ambiguity, motivated by building rather than executing, and capable of selling on vision and value rather than feature depth. These are rare profiles, and they’re distinctly different from AEs who have only worked in mature SaaS businesses with established GTM playbooks.
Practically, you’re looking for someone who has done at least one early-stage or zero-to-one sales role before. They should be able to describe how they handled objections when the product wasn’t fully baked, how they worked with product teams to prioritize feedback from deals, and how they managed their own pipeline without a full support structure behind them.
When hiring an AE for an AI startup specifically, an understanding of how AI products are positioned and sold is increasingly valuable in 2026. Not because they need to be technical, but because buyers are more sophisticated now. They ask harder questions, and an AE who has navigated AI skepticism in the field will ramp faster than one who hasn’t.
Should you mention product maturity honestly in an AE job description?
Yes, you should be honest about product maturity in an AE job description, and doing so will actually improve the quality of applicants you attract. Candidates who have thrived in early-stage environments will recognize the signals and lean in. Candidates who need a mature product to succeed will self-select out, saving everyone time.
You don’t need to lead with your limitations. But phrases like “We’re in active product development,” “You’ll be selling alongside our roadmap,” or “You’ll help shape how we go to market” are honest, compelling, and accurate signals of what the role actually involves. They attract the profile you want without underselling the opportunity.
The risk of overselling product maturity in a job description is significant. If a strong AE joins expecting a polished product and a clear ICP, and finds neither, they’ll leave within six months. That’s an expensive mistake, and it’s one we see regularly in early-stage AI companies that are moving fast and hiring faster.
What mistakes do companies make when writing AE job descriptions for new products?
The most common mistake is writing a job description that was designed for a mature SaaS company and pasting it onto an early-stage AI role. This creates a mismatch between what the company needs and who applies. Asking for “5 years of enterprise SaaS closing experience” and “a proven track record of exceeding quota” sounds credible, but it often attracts people who need structure that doesn’t yet exist.
Other frequent mistakes include:
- Listing responsibilities that assume a full GTM team is already in place
- Being vague about the sales motion (is this inbound, outbound, or both?)
- Not mentioning the stage of the company at all
- Setting expectations around quota without acknowledging that the product is still being validated
- Writing the role as purely execution-focused when the company actually needs someone who can also do discovery and strategy
The job description is often the first impression a strong candidate has of your company. If it reads like a template, it signals that you haven’t thought carefully about what you actually need. For a game-changing hire, that first impression matters more than most hiring managers realize.
How do you set realistic quotas and targets in a job description for an unproven product?
For an unproven product, avoid publishing a hard quota in the job description unless you have real data to back it up. Instead, describe the sales motion, the average deal size you’re targeting, and the expected pipeline activity in the first 90 days. This gives candidates a realistic picture without locking you into a number you’ll have to revise in three months.
If investors or leadership are pushing for a quota in the posting, frame it as a ramp target rather than a year-one quota. Something like “We’re targeting our first five enterprise logos in the first two quarters” is honest, meaningful, and doesn’t require you to invent a number based on nothing.
The AEs you want to hire for an AI startup understand that quotas in early-stage environments are part art, part aspiration. What they’re really evaluating is whether the opportunity is real, whether the leadership team is credible, and whether the product has genuine traction with at least a handful of customers. If those things are true, a strong candidate will take the role even without a polished quota structure. If those things aren’t true, a quota won’t save you.
At Nobel Recruitment, we speak to hundreds of GTM candidates and hiring managers every week. Curious what we’re seeing in the market right now? Reach out, we’re happy to share, or take a look at how we approach GTM executive search.
Frequently Asked Questions
How do you screen AE candidates to make sure they can actually handle an unfinished product?
Ask candidates to walk you through a deal they closed where the product had a significant gap or limitation at the time. You’re listening for how they managed the customer’s expectations, how they worked with their internal team, and whether they saw the limitation as a blocker or a challenge to navigate. Candidates who have genuinely operated in ambiguity will have a specific, honest story. Candidates who haven’t will give you a polished but vague answer.
Should we include compensation details in the job description for an early-stage AI AE role?
Yes, and being transparent about OTE and equity is especially important at the early stage. Strong candidates evaluating an unfinished product are already taking on risk, and they’ll want to understand the upside clearly before investing time in your process. If your base-to-variable split or equity structure is competitive, make it visible — it’s one of your strongest selling points when the product itself is still maturing.
How many AEs should an AI startup hire when the product is still being built?
In most cases, start with one. Hiring multiple AEs before you’ve validated the sales motion means you’re scaling a process that doesn’t yet exist, which leads to inconsistent results and high churn. Hire one strong, adaptable AE who can help you build the playbook, run the experiments, and identify what actually works — then scale from that foundation once you have repeatable signals.
What's the best way to attract experienced AEs to a role where the product isn't proven yet?
Lead with the opportunity, not the product. Experienced early-stage AEs are motivated by ownership, upside, and the chance to build something meaningful — not by a polished deck. In your job description and outreach, be clear about the equity stake, the size of the market you’re going after, the credibility of the founding team, and the traction you do have, even if it’s small. A handful of real customers and a clear problem is often enough for the right candidate to get excited.
How do you write a job description that works now but won't be outdated in three months?
Anchor the description to the role’s core mission and the problem the AE is solving, rather than to specific product features, integrations, or team structures that are likely to change. Phrases tied to outcomes — like ‘own the full sales cycle for our first enterprise segment’ or ‘help us identify and close our first 10 customers’ — stay accurate far longer than feature-specific or headcount-specific language. Review and update the posting at each major product or GTM milestone.
What's a red flag to watch for when an AE candidate seems too eager to join despite the product being early-stage?
Be cautious of candidates who ask very few critical questions about the product, the ICP, or the current state of traction. A strong early-stage AE should be doing their own due diligence — asking about pipeline, existing customers, how objections have been handled so far, and what support they’ll have. Excessive enthusiasm without scrutiny can signal that the candidate is between jobs and treating your role as a fallback rather than a deliberate career move.
Should the founders still be involved in sales after the first AE is hired?
Yes, especially in the early months. The first AE hire works best as a collaborative handoff, not a full delegation. Founders carry critical context about why customers buy, what objections come up, and how the product vision maps to customer pain — and that knowledge needs to be transferred actively, not just documented. A clean handoff typically takes one to two quarters of working deals together before the AE can operate independently with confidence.
Related Articles
