# Head of Product ## About the Company We're building AI-powered customer support tools that help e-commerce brands resolve tickets faster and keep shoppers happy. Fresh off a $3M seed round, our team of 8 is working with early design partners and seeing strong pull from DTC brands ready to replace legacy helpdesks. We're at the stage where every decision shapes the company. ## About the Role As our first Head of Product, you'll own what we build and why. In your first 6-12 months, you'll define our product strategy, establish a customer discovery rhythm that informs every sprint, and ship features that take us from early design partners to a repeatable, paid product. Success looks like clear product-market fit signals, a roadmap the team rallies behind, and customers telling their peers about us. ## What You'll Do - Own the product roadmap end-to-end, from discovery through launch, with direct input from the CEO and engineering lead - Talk to 5+ customers and prospects every week and turn those conversations into prioritized bets - Define and track the metrics that tell us whether we're winning—activation, resolution rate, retention - Ship the next generation of our AI agent capabilities in tight collaboration with engineering, moving from weekly to daily releases - Build the feedback loops (user research, analytics, support tickets) that keep us close to customer reality as we scale - Hire and mentor the first product hires behind you—PMs, designers, or a researcher—once we've earned the right to grow the team - Partner with go-to-market on positioning, pricing, and packaging as we move from design partners to self-serve and sales-led motions ## What We're Looking For - 6+ years in product, with at least 2 leading product at an early-stage B2B SaaS company (Seed to Series B) - A track record of shipping products customers actually use and pay for—bonus if you've taken something from 0 to 1 - Comfort with ambiguity: you write the brief, run the interview, open the PR comment, and update the pricing page - Strong opinions about AI/LLM-powered products, loosely held, with real experience shipping them - Excellent written communication—you'll set direction largely through docs ## Nice to Have - Background in customer support, helpdesk, or e-commerce tooling - Experience working with DTC brands as customers - Technical background (CS degree, former engineer, or similar) ## Compensation & Benefits - **Salary:** $160,000–$190,000 - **Equity:** 0.75%–1.5% - **Remote-first**, US time zones (overlap with Pacific preferred) [assumed based on team location] - [Assumed] Full health, dental, and vision coverage; $2,000 home office stipend; unlimited PTO with a 3-week minimum ## How to Apply Email us at [careers@company.com] with a short note on a product you shipped that you're proud of and why. No cover letters needed—just be specific. We respond to every applicant within a week.
Writing Job Descriptions for Early-Stage Startups
Tested prompts for how to write a job description for a startup compared across 5 leading AI models.
Startup job descriptions fail in two predictable ways: they either copy enterprise templates that make the role sound bureaucratic and safe, or they go too casual and leave candidates guessing what the job actually requires. Neither works when you are competing against funded companies with brand recognition and HR departments.
If you are writing a job description for an early-stage startup, you are selling the role as much as you are screening for it. Your description needs to tell a candidate exactly what they will own, what the company is building, and why this seat matters right now. Vague titles and bullet-point lists of requirements pulled from LinkedIn templates will not do that.
This page shows you how to use AI to produce a startup job description that is honest about stage, specific about scope, and compelling to the right candidate. You will see the prompt used, four different model outputs, and a comparison of what each approach gets right so you can apply the technique directly.
When to use this
This approach fits when you need to hire fast, have not written many job descriptions before, or want to avoid the copy-paste trap of using a big-company template that does not reflect how your team actually works. It is especially useful when the role is cross-functional or does not map cleanly to a standard title.
- You are a founder or operator writing your first few hires without an HR team
- The role is a hybrid or catch-all position that spans multiple functions
- You need to post quickly but want something better than a recycled template
- You are hiring for a role where culture fit and ambiguity tolerance matter as much as credentials
- You want to attract senior candidates who would be turned off by generic, corporate-sounding language
When this format breaks down
- Regulated roles where the job description must match specific legal language, such as government contracting, healthcare compliance, or licensed professional positions
- Roles at Series C and beyond where you have an established HR function with approved templates and legal review requirements
- Situations where the role is not yet defined internally and you would be using the JD to figure out what you actually need, since AI output will be confidently vague without a real brief
- Executive or C-suite searches where the description is typically written collaboratively with a recruiter or executive search firm who owns the process
The prompt we tested
You are an expert startup recruiter and hiring manager who writes compelling job descriptions for early-stage startups. Using the startup and role details provided, write a complete job description that attracts mission-driven candidates comfortable with ambiguity, ownership, and rapid growth. Structure the output with these sections: (1) About the Company (2-3 sentences on mission, stage, and traction), (2) About the Role (what success looks like in the first 6-12 months), (3) What You'll Do (5-7 bullet outcomes, not tasks), (4) What We're Looking For (must-have experience and traits), (5) Nice to Have, (6) Compensation & Benefits (include equity, salary range, remote policy), and (7) How to Apply. Emphasize impact, scope, and growth opportunity over corporate perks, and avoid generic buzzwords like 'rockstar' or 'ninja'.
Rules: Keep the total length between 350-500 words, use plain direct language, and write in second person ('you'll'). Lead with mission and impact, be specific about stage-appropriate expectations (wearing multiple hats, building from zero, etc.), and include a concrete salary and equity range even if the user didn't specify one—flag assumptions in brackets.
Startup and role details:
We're a seed-stage B2B SaaS startup (8 people, just raised $3M) building AI-powered customer support tools for e-commerce brands. We need to hire our first Head of Product—someone who can own roadmap, talk to customers daily, and ship fast. Remote-first, based in US time zones, budget is around $160-190k plus 0.75-1.5% equity.
Model comparison
| Model | Quality | Cost | Latency | Tokens |
|---|---|---|---|---|
| Claude Opus 4.7 | 8 | $0.0813 | 20.3s | 548 / 974 |
| Claude Haiku 4.5 | 8 | $0.0049 | 11.3s | 385 / 898 |
| GPT-5.4 | 8 | $0.0112 | 13.6s | 352 / 688 |
| Grok 4.1 Fast Reasoning | 8 | $0.0004 | 9.0s | 500 / 571 |
Outputs
# Job Description: Head of Product ## About the Company We're building the operating system for e-commerce customer support—AI that actually reduces ticket volume instead of just routing them faster. We've raised $3M from top-tier investors and have 8 people shipping real product to paying customers. Our mission: give small and mid-market brands the support infrastructure that only enterprise companies could afford before. ## About the Role You'll own what we build and why. In your first 6-12 months, you'll have articulated a compelling product roadmap based on direct customer feedback, shipped 2-3 major features that measurably reduce support costs for our users, and established yourself as the customer voice inside the company. Success means our retention rate improves, our feature adoption accelerates, and our sales team has concrete evidence of product-market fit to close larger deals. You'll be equally comfortable writing specs and jumping on customer calls—there's no "that's not my job" here. ## What You'll Do - **Talk to customers constantly.** You'll spend 5-8 hours weekly on calls with support leaders and e-commerce operators, turning pain points into prioritized features and strategic bets. - **Own the roadmap end-to-end.** You'll make trade-offs between quick wins and longer-term vision, communicate them clearly to the team, and explain why we're building what we're building. - **Ship features that stick.** You'll work directly with our engineering and design team to get from concept to live in 2-4 week cycles, measure impact, and iterate based on real usage data. - **Define success metrics.** You'll establish dashboards that matter—retention, feature adoption, support cost reduction, NPS—and use them to guide decisions. - **Unblock the business.** As our first product hire, you'll wear adjacent hats: analyzing pricing strategy with the founder, helping close deals, and shaping the company narrative around our solution. - **Build the product function.** You'll document how we make decisions, set up customer research infrastructure, and define what good product work looks like as we hire the next person. ## What We're Looking For - **3+ years as a product manager** at a B2B SaaS or similar environment (or equivalent through a founder/operator role) - **Comfort with ambiguity and speed.** You've shipped products with incomplete information and made decisions without consensus—and learned from both. - **Customer obsession that's genuine.** You can sit with unhappy users and extract signal from emotion; you actually want to talk to customers, not delegate it. - **Technical fluency.** You don't need to code, but you understand APIs, data pipelines, and AI limitations well enough to have real conversations with engineers. - **Ownership mentality.** You see roadmap misses as your responsibility, not the team's fault. You've fought for resources and made difficult cuts. ## Nice to Have - Experience in customer support, SaaS operations, or AI/ML products - Startup background or experience in high-growth environments - Track record of improving retention or reducing churn through product changes - Background in e-commerce or understanding of support workflows ## Compensation & Benefits - **Salary:** $160k–$190k [based on experience] - **Equity:** 0.75–1.5% [refresher grants planned at future funding rounds] - **Remote-first:** US time zones required for customer meetings and team sync - **Practical benefits:** Health/dental/vision, laptop stipend, annual learning budget, unlimited PTO (we actually use it) We're not a perks company; we're a product company. Compensation reflects early-stage constraints but will reset as we grow. ## How to Apply Send a brief email to [hiring contact] with: - Your resume - One paragraph on why this problem excites you - A link to a product you've shaped (or a decision you made) you're proud of We review applications rolling and move fast for strong fits.
## About the Company We're building AI-powered customer support tools that help e-commerce brands resolve issues faster, reduce support costs, and create better customer experiences at scale. We're a seed-stage B2B SaaS startup, 8 people today, and we recently raised $3M to accelerate product development and go-to-market. We already have early customer traction and now need a product leader who can help turn strong signals into a durable, category-defining company. ## About the Role As our first Head of Product, you'll own the product roadmap from insight to launch. You'll work directly with founders, engineers, and customers to decide what to build, why it matters, and how to ship it quickly without losing focus. Success in your first 6-12 months will look like this: you'll establish a clear product strategy tied to customer pain points and company goals, create a tight feedback loop with users, and help the team ship high-impact features faster and with more confidence. You'll bring structure where it's needed, but stay hands-on and pragmatic in a fast-moving seed-stage environment. ## What You'll Do - Turn customer pain points and market signals into a focused roadmap that drives retention, expansion, and product differentiation. - Build a repeatable customer feedback process so product decisions are grounded in real usage, not assumptions. - Partner closely with engineering and design to ship meaningful improvements and new capabilities at startup speed. - Define the metrics that matter and use them to prioritize, learn, and adjust quickly. - Create clarity across the company on what we're building, why it matters, and what success looks like. - Help shape our AI product strategy, balancing user value, technical feasibility, and commercial impact. - Lay the foundation for how product is run as the company scales, while still doing the hands-on work yourself. ## What We're Looking For - You've led product at an early-stage startup or been a senior product leader in a fast-growing SaaS company with clear ownership. - You know how to go from zero to one: finding signal in ambiguity, making decisions with imperfect information, and iterating quickly. - You're highly customer-oriented and comfortable talking to users frequently—ideally daily. - You can balance strategy and execution; you don't just define priorities, you drive them through launch and learning. - You communicate clearly, make tradeoffs explicit, and build trust across technical and non-technical teams. - You care about building products that solve real business problems for customers. ## Nice to Have - Experience in e-commerce, customer support, or workflow software. - Experience building AI/LLM-powered products. - Familiarity with analytics, experimentation, and usage-based product decision-making. - Prior experience as the first product hire or first senior product leader. ## Compensation & Benefits - Salary: $160,000-$190,000 base [assumption based on stated budget] - Equity: 0.75%-1.5% [assumption based on stated range] - Remote-first within US time zones - Early-stage ownership, direct founder partnership, and significant influence on company direction ## How to Apply Send us your resume or LinkedIn, plus a short note on why this role fits your experience. If you've been the person figuring out what to build in messy, fast-moving environments, we'd love to hear from you.
### About the Company We're a seed-stage B2B SaaS startup building AI-powered customer support tools that help e-commerce brands resolve tickets 5x faster and scale without hiring armies of agents. With 8 people and a fresh $3M seed round, we're moving from prototype to first paying customers. You'll join at the ground floor, shaping a product that directly impacts brands like Shopify merchants handling millions in orders. ### About the Role In your first 6-12 months as our first Head of Product, you'll define the initial roadmap, ship an MVP that lands 10+ beta customers, and establish weekly customer feedback loops to hit product-market fit. Success means owning end-to-end product decisions—from discovery to launch—while collaborating with engineering to iterate weekly, turning ambiguity into a validated product serving real revenue. ### What You'll Do - Launch a core AI support feature that reduces customer ticket resolution time by 50% for early users. - Build and refine a product roadmap based on 50+ customer interviews, prioritizing features that drive retention. - Ship 3-5 major iterations in the first quarter, using data to validate assumptions and cut underperformers. - Create self-serve onboarding flows that convert 30% of trial users to paid without sales handholding. - Partner with founders to align product vision with go-to-market, informing pricing and sales collateral. - Establish metrics dashboards tracking key outcomes like activation rate and churn, guiding all future builds. - Mentor the team on customer-centric thinking, embedding it into our remote-first culture. ### What We're Looking For You've led product at a seed or Series A SaaS startup, owning roadmap and shipping from zero to revenue. You talk to customers daily, synthesize their pain into features, and move fast in ambiguous environments—wearing engineering, design, and go-to-market hats as needed. You're hands-on with tools like Figma, Notion, or Amplitude, thrive on ownership, and have 5+ years in B2B product roles, ideally e-commerce or AI. ### Nice to Have Experience with AI/ML products, customer support workflows, or e-commerce integrations (e.g., Shopify, Zendesk). Prior exits or scaling to $1M ARR. ### Compensation & Benefits $160k-$190k base salary (US time zones, remote-first with occasional offsites), 0.75-1.5% equity (vesting over 4 years), unlimited PTO, and full health coverage. We prioritize impact over perks—your equity could be life-changing as we grow to $10M ARR. ### How to Apply Email your resume, a link to your portfolio or a product you've shipped, and 200 words on why you're excited to build our first product at resume@aicustomersupport.com. No agencies. (Word count: 428)
What makes these work
-
01Lead with stage and context
The most useful signal you can give a candidate is where the company actually is: funding stage, team size, ARR if relevant, and how long you have been operating. This filters out candidates who want a stable environment and attracts people who understand what early-stage means. Put this in the first two sentences of the description, not buried at the bottom.
-
02Name what the person will own
Startup roles are defined by ownership, not job functions. Instead of listing responsibilities as tasks, write them as domains or outcomes the person will own. 'Own the customer success function from scratch' is more honest and more compelling than 'manage customer relationships and reduce churn.' Ownership language also helps candidates self-select accurately.
-
03Be specific about what you are not
State explicitly what the role is not if there is a common misread. If there is no budget for paid acquisition, say that. If the engineering team does not do daily standups, say that. Candidates who need those things will opt out, which saves everyone time. Specificity about constraints is a signal of organizational honesty that strong candidates respond to.
-
04Separate must-haves from nice-to-haves
Studies consistently show that long requirements lists suppress applications, especially from women and underrepresented candidates. Keep hard requirements to the things that are actually disqualifying. Put everything else in a separate section labeled 'bonus' or 'nice to have.' A 5-item must-have list is more effective than a 14-item list where 9 items are aspirational.
More example scenarios
We are a 6-person B2B SaaS startup building contract management software for mid-market logistics companies. We have $1.8M in seed funding. We need our first full-stack engineer who will work directly with the two co-founders. The stack is React, Node.js, and PostgreSQL. The role is remote-first. We want someone who can ship features independently and is not waiting for a spec.
Full-Stack Engineer (Founding Engineer) at a seed-stage contract management startup. You will be the first dedicated engineer, working directly with the founders to build and ship product. Stack is React, Node.js, PostgreSQL. You own features end to end: scoping, building, deploying. No PM layer, no backlog grooming theater. The right person has shipped production code in a small team and is uncomfortable sitting still.
We launched a personal finance app for freelancers 4 months ago. We have 11,000 users, some paid traction, and a 3-person team. We are looking for a Head of Growth who can own acquisition and retention. Budget is limited so this person needs to be scrappy, not reliant on paid spend. Series A fundraise is likely in 6 months.
Head of Growth at a 3-person fintech app with 11k users and real traction. You will own the full funnel from acquisition to retention with a lean budget, meaning you will need to find organic, referral, and content levers before we scale paid. This is a founding team role with equity and a clear path to VP as we grow toward Series A. You have done this before at the zero-to-one stage and have the numbers to prove it.
We make sustainable packaging for e-commerce brands. 14 employees, $3M ARR, bootstrapped. We need someone to run day-to-day operations including supplier relationships, fulfillment coordination, and internal process documentation. This person will eventually manage a small team. We are based in Austin, TX, in-office 3 days a week.
Operations Manager at a bootstrapped sustainable packaging company in Austin. You will own supplier relationships, fulfillment coordination, and the internal systems that keep a 14-person company running without friction. Right now it is individual contributor work, and in 12 months you are building a team. This is not a remote role. If you want to see the direct impact of your work in a physical product business, this is the job.
We sell data observability software to data engineering teams at mid-market and enterprise companies. Average deal size is $40k ARR. We are three co-founders with a handful of design partners and need our first Account Executive who can close net new logos. We have some warm inbound from content but no formal SDR function yet.
Account Executive (First Sales Hire) at a data observability startup targeting data engineering teams. Average deal is $40k ARR. You will close net new logos, help us build a repeatable sales motion, and shape how we think about the sales process from scratch. There is inbound from content but no SDR to hand you pipeline. This role suits someone who has sold technical software to engineering buyers and does not need a playbook handed to them.
We are a 2-year-old marketplace startup with $1.2M ARR growing about 15% month over month. We are preparing for a Series A raise in the next 9 months. We need a fractional CFO, roughly 10-15 hours per week, who can own financial modeling, investor reporting, and help us get our data room ready.
Fractional CFO, 10-15 hours per week, for a marketplace startup at $1.2M ARR heading into a Series A. You will own financial modeling, build out investor reporting, and lead data room prep over the next 9 months. This is not a bookkeeping role. You have been through an early-stage raise before and know what institutional investors want to see before they wire money.
Common mistakes to avoid
-
Using enterprise job description templates
Copying a Google or Amazon JD template and swapping in your company name produces a description that signals bureaucracy and process to exactly the candidates you want to hire. Early-stage candidates who are good at their jobs have options, and a corporate-sounding description tells them this company does not know what it is. Start from scratch or use a startup-specific framework.
-
Hiding the stage or funding status
Founders sometimes omit funding stage, team size, or ARR because they think it will scare candidates away. The opposite is true for the right candidates. Burying the fact that you are a 4-person pre-revenue startup creates a mismatch that wastes everyone's time and erodes trust before the first interview. State your stage clearly and let candidates self-select.
-
Writing requirements as a wish list
A job description that requires 10 years of experience, an MBA, fluency in 5 tools, and the ability to build a function from scratch is describing a unicorn, not a job. Every requirement you add that is not genuinely disqualifying shrinks your applicant pool and signals that you have not thought through what you actually need. Write requirements based on the first 90 days, not the ideal future state.
-
Omitting compensation range
Not including a salary range is increasingly a dealbreaker for experienced candidates, and in several U.S. states it is now legally required. Ranges also save time: candidates who need more than you can offer will not apply, and candidates who are motivated by the mission over maximum comp will signal that by applying anyway. If equity is part of the offer, describe it in concrete terms, not just 'competitive equity package.'
-
Making the culture section generic
Every startup description says 'fast-paced environment,' 'collaborative team,' and 'move fast.' These phrases communicate nothing. If your culture is genuinely differentiated, describe a specific behavior or norm: 'We write decision memos instead of holding alignment meetings' or 'Engineers talk directly to customers every two weeks.' Specific culture details attract candidates who are actually compatible.
Related queries
Frequently asked questions
How long should a startup job description be?
Aim for 400-600 words for most roles. Long enough to give candidates a real picture of the company, the role, and what success looks like, but short enough to actually get read. If you need more than 600 words, you are probably trying to cover too much scope in one role or writing for an audience of one ideal candidate rather than a realistic pool.
Should a startup job description include salary range?
Yes, always include a range. It filters out candidates who need more than you can offer, which saves time on both sides. It also signals organizational transparency, which is a genuine signal to candidates evaluating early-stage companies. If the range is wide, that is fine, just note what determines where in the range a candidate might land.
What should a startup job description say about equity?
Be as specific as you can without disclosing the full cap table. State the range as a percentage or in options, the vesting schedule, the cliff, and ideally the current strike price. 'Competitive equity' means nothing to an experienced candidate. A candidate who is being asked to take a below-market salary in exchange for equity deserves to understand the actual math.
How do I write a job description for a role that doesn't exist yet?
Start with the problem you are hiring to solve, not the title. Write down the top 3-5 outcomes you need in the first 6 months and work backward to the skills required to produce those outcomes. This prevents the trap of copying a template for a role that is actually something different in your context. Once you have the outcomes, the title and structure follow naturally.
Can I use AI to write my entire startup job description?
AI can produce a solid first draft, but the output is only as good as the input you give it. Generic prompts produce generic descriptions. Feed the model specific details: funding stage, team size, stack, what the person will own, what you are not, and what success looks like in 90 days. Then edit the output to match how your team actually talks. The final version should not sound like it came from a template.
What's the difference between a job description and a job posting?
A job description is an internal document that defines the role, scope, and requirements for hiring and performance management purposes. A job posting is the candidate-facing version, written to attract applicants. For early-stage startups the two often collapse into one document, but it helps to think of the posting as sales copy: it should answer why a strong candidate would want this job, not just list what you need from them.