By Kim Talarczyk, founder of Demand Recruiting
Strong sales, marketing, and RevOps candidates check whether the role is clear, whether the targets are realistic, who they'll report to, how they'll get paid, how much runway you have, how mature your GTM setup is, and how involved you'll be. Founders who can answer those plainly before the first call tend to land the people they want.
Hiring your first seller, your first marketer, or the person who finally fixes your CRM feels like you're the one doing the choosing. You write the job post, you run the interviews, you make the offer.
But the people you most want are running their own evaluation, and they started before your first call. If you're a technical founder, this part can catch you off guard. You'd never ship a product without knowing what users check before they buy. Hiring for go-to-market works the same way. Strong candidates have a mental checklist, and they're scoring you against it.
Maybe you're still running sales yourself and it's time to hand it off. Maybe growth has stalled and you need the right person to get it moving. Maybe you lead a GTM team that needs more people, or you just raised and the target got bigger. Most of the companies I work with are B2B SaaS under $10M ARR, and these questions come up with almost every GTM hire. This guide walks through what strong sales, marketing, and RevOps candidates look at, and how to have honest answers ready before you open the role.
Good candidates do their homework, and GTM people are especially good at it because researching accounts is part of the job. Before they talk to you, most will look at your website, your LinkedIn page and yours personally, any funding news, who your customers are, and what current and former employees say about working there. They'll read your job post closely too.
What they're really checking is whether the story holds together. If your site says you sell to enterprise IT teams, your job post talks about SMB, and your LinkedIn describes a third customer, a sharp candidate notices before you ever meet. You don't need a polished employer brand. You need the basics to agree with each other.
It also helps to know what your candidates are reading. A lot of them are working through guides like my tech job search guide, which tells them to research companies hard and ask pointed questions in interviews. Assume they will.
Every candidate weighs these a little differently, but they come up again and again with sales, marketing, and RevOps people. For each one, think about what you'd say if they asked you directly, because they probably will.
The first question is simple. What will I own? Strong candidates want to know what's theirs, what isn't, and what success looks like at 90 days, 6 months, and 12 months. "Help us grow" isn't a role. "Own outbound pipeline for mid-market accounts and hit a number we set together by month four" is.
If you're not sure yet, that's normal. Work it out before you post. I use a practical starting framework for defining the role with founders and adapt it to the company, because real roles rarely fit neatly into one box.
Sellers will ask how the number was set, whether anyone has hit it, where pipeline is supposed to come from, and how long the ramp is. Sales candidates are actively being advised to ask what share of the team hits quota before they join (see this piece from The Modern GTM Executive). If you're hiring your first AE and nobody has carried a quota yet, say so. Then explain how you'll set it together once you have real data.
Marketers want to know whether they'll be measured on pipeline or on lead counts. RevOps candidates want to know what they'll actually be allowed to change. A target that sounds made up is one of the fastest ways to lose a strong person.
Will they report to you, or to a leader you haven't hired yet? If there's a chance a VP comes in above them in a year, tell them now. Good people can live with that plan. What they can't live with is finding out after they've joined.
This is less about the size of the number and more about how it works. For sellers, that means the split between base and variable, how commission is calculated, when it's paid, and whether there are accelerators above plan. For everyone, it means equity explained honestly. Tell them what it could be worth if things go well, and say plainly that it could be worth nothing.
You won't win every candidate on cash, and you don't need to. I wrote more about how to compete when you can't match big-company offers.
Early GTM hires are taking a real risk, so they want enough information to judge it. When did you last raise, or are you bootstrapped or profitable? Roughly how long is your runway? What milestones are you working toward? You don't have to share your board deck, but a vague answer here costs you more than an honest one.
Candidates want to know what they're walking into. Is there a defined ICP? Where does pipeline come from today? Is the CRM usable, or is it a graveyard? Is there any marketing or SDR support?
Be straight about whether they're inheriting a system or building one. Some of the best early candidates actively want to build. They just want to know that's the job, rather than finding out in week two that the "sales process" lives in your head.
Early GTM people are betting on you as much as the company. They want to know if you're still selling, what you'll hand off and what you'll keep, and how you make decisions. A founder who plans to stay in every deal forever is a very different job from one who wants to step back. Neither is wrong, as long as you're clear about which one you are.
Before you open the role, write down your answer to each of these. If you can't answer one, that's where to start.
| Question candidates ask | What a good answer includes |
|---|---|
| What will I own? | Clear scope, what's out of scope, and success at 90 days, 6 months, and 12 months |
| Is the target realistic? | How it was set, who has hit it, where pipeline comes from, and the ramp |
| Who do I report to? | Today's reporting line and any plan to hire a leader above the role |
| How does comp work? | Base and variable split, commission rules and timing, and equity explained honestly |
| How long is the runway? | Funding status or profitability, rough runway, and the next milestones |
| What will I inherit? | ICP, pipeline sources, CRM state, and any marketing or SDR support |
| How involved is the founder? | What you'll keep, what you'll hand off, and how decisions get made |
The seven areas apply to everyone, but each function leans on different parts of them.
Sellers go straight to the number. Expect questions about quota and attainment, where pipeline comes from, average deal size and sales cycle, and whether they'll have SDR or marketing support. They'll also want to know who they'll learn from if you're the only other person who has sold the product. If your motion is enterprise, it's worth reading what a good enterprise AE looks like in practice. If you're hiring your first outbound reps, see how to hire BDRs and SDRs for early-stage SaaS. If this is your first sales hire, here's how to hire your first AE.
Marketers ask about budget, what they'll be measured on, and where marketing's job ends and sales begins. They'll want to know what tools and data exist, and whether anyone will look at the numbers with them. If you're still deciding what kind of marketer you need, start with growth marketer vs head of growth. If it's your first marketing hire, see how to hire your first marketer. If the gap is pipeline, see how to hire a demand gen marketer.
RevOps people ask who owns the CRM, how clean the data is, and whether they'll have a real say in how revenue is reported and forecast. They're wary of roles that are really "CRM admin with a fancy title." If you're not sure you need the role yet, read when to hire RevOps in B2B SaaS. If you've decided you need one, here's how to hire a RevOps lead.
Most strong candidates don't drop out because of one bad answer. They drop out because the process tells them something about how the company runs.
A slow, disorganized process is the most common reason. When a week passes between steps with no word, good people assume the rest of the company moves that way too. I cover the causes in why B2B SaaS sales hiring takes longer than you think.
A fuzzy role is close behind. So is a story that changes depending on who's doing the interview. If your cofounder describes the job one way and you describe it another, candidates notice.
Overselling equity backfires. So does a founder who can't describe what success looks like at 6 and 12 months.
And posting a job and waiting rarely works on its own for the people you really want, because many of them aren't scrolling job boards. If you've posted and been buried in applicants who don't fit, here's what to do when you get 1,000 applicants.
Part of defining a role with me is getting clear on what the person will own and how to set them up to succeed, and most of these answers come out of that work.
If you're handing off sales for the first time, trying to restart growth that has stalled, adding people to a GTM team, or hiring against a bigger target after a round, the stakes on these hires are high. It can make sense to bring in someone who does this every day.
I work with founders and GTM leaders on sales, marketing, and RevOps hires, starting with defining the role before anyone gets sourced. You can start with a single search rather than a long retainer, or compare the three ways to work with me.
Tell me what you're working on and where things stand, and I'll reply within one business day.
Helping B2B SaaS founders and GTM leaders hire the sales, marketing, and RevOps people who move growth forward.
