What SaaS Companies Actually Screen For in Senior Post-Sale Leaders

Job descriptions are the most honest documents in the hiring market. Nobody writes them to inspire. They get written by a hiring manager who has a gap, a scorecard, and a budget, and they tend to say the quiet part out loud.

So rather than career advice, here's a reading of what current senior Customer Success and Partnerships job descriptions actually ask for. Not what LinkedIn says these roles are about. What companies put in writing when they're paying for the outcome.

The first paragraph is usually a scorecard

Arbital Health's VP of Customer Success role expects ownership of ARR retention and expansion, NRR and GRR, forecast ownership, executive relationships, portfolio health scoring, company-wide Voice of Customer, and scalable tooling and playbooks. ChowNow's Director role asks for weekly renewal and expansion forecasting, health frameworks, early-warning systems, save playbooks, and fluency across NRR, GRR, churn, expansion ARR, adoption, and health scoring.

Read those twice and the pattern is hard to miss. Neither one leads with relationships. Both lead with numbers the person will be asked to defend in a room.

The word doing the most work there is "weekly." A weekly renewal and expansion forecast isn't a metric, it's an operating rhythm. It means someone is expected to look at a book of business every week, form a view, commit to it out loud, and be measurably wrong or right within a quarter. That's a different job from managing customer relationships well. Plenty of good CS leaders have never been asked to do it, and it shows the moment they're screened for it.

Coverage design became a screened skill

Newsela's Director of Scaled Customer Success role emphasizes a data-driven experience that mixes digital engagement, targeted human touchpoints, heavy automation, and tightly designed capacity models.

Capacity models. That's the phrase worth sitting with. It's an admission that the coverage question moved from "how many accounts per CSM" to "what does each account actually need, when, and delivered by what." Designing that is closer to operations engineering than account management, and it's now written into Director-level requirements rather than assumed to happen somewhere above the role.

The investment data points the same way. Gainsight's Customer Success Index 2025 shows that among CS teams increasing investment, 59% were increasing AI technology spend, 50% digital CS, and 27% CS Ops, with dedicated CS Ops teams rising to 56% of organizations in 2025. Companies are funding the machinery, then hiring people who can design what runs on it.

Partnerships roles now read like revenue mechanics

The shift is even sharper on the partner side. Couchbase's cloud partnerships role wants measurable multi-million-dollar ARR impact, executive partner relationships, marketplace optimization, and co-sell pipeline generation through AWS ACE, Microsoft Partner Center, and Google Cloud co-sell motions, plus the ability to connect Sales, Marketing, Product, and partner teams. Backblaze's ecosystem role explicitly asks for partner-sourced revenue, marketplace strategy, compensation models, deal registration, and fluency across both subscription and consumption-based models.

Those are named programs and named mechanics. Deal registration rules. Comp model design. Consumption billing. You either know how those work or you don't, and an interview surfaces it in about four minutes.

This is why the word "ecosystem" has quietly become a liability. It used to signal sophistication. Now it mostly signals that a candidate hasn't had to run the plumbing. The market evidence backs the shift: PartnerStack's 2026 GTM partnerships research puts alignment across teams as the biggest blocker to partner-driven revenue at 37%, and says only 42% of companies use multi-touch attribution across the funnel. Clazar and Partner Insight's 2025 work says 89% of companies are listed on a cloud marketplace while only 22% get more than 20% of revenue through it. Every one of those gaps is an operational problem, not a relationship problem, and hiring managers have started writing job descriptions accordingly.

The Director-to-VP line is forecast ownership, not team size

People assume the jump is about headcount. Based on what these roles actually specify, it's about two things: whether you own a forecast, and whether executives trust your number without re-checking it.

A Director can run a strong team, ship playbooks, and improve onboarding without ever carrying a commit. A VP is generally being hired to stand behind a retention and expansion number in the same room where Sales stands behind theirs. Everything else in the job description tends to be in service of making that number credible. Health scoring exists so risk is visible early. Early-warning systems exist so the forecast moves before the renewal date, not after. Voice of Customer exists so the explanation for a miss is grounded in something other than vibes.

If you want to test your own readiness for the jump, that's the test. Not headcount. Whether you'd bet your credibility on next quarter's retention number today.

The reporting line question, honestly

Gainsight's 2025 Index shows 25% of CS organizations globally reporting to the CRO or Head of Sales, while larger companies are more likely to have an established CCO. Gainsight is also direct about the risks: short-term revenue pressure, misalignment when CRO incentives focus only on new business, and CS drifting into a transactional posture. ChurnZero's 2025 analysis notes the same rise and argues leaders need to balance revenue metrics with customer outcomes and keep role boundaries clear.

My read is that CS under a CRO isn't the problem. Unbalanced scorecards are. A CS org can report anywhere on the chart and stay healthy as long as somebody protects the outcome metrics from being quietly traded away for this quarter's number. Where that protection doesn't exist, you get value destruction in slow motion: renewals held together by discounts, expansion booked ahead of adoption, and a health score that's green because nobody wanted to explain a red one.

Worth asking about in an interview, by the way. How the outcome metrics are protected is a more revealing question than who the role reports to.

What actually gets people screened out

Four patterns, and they're all avoidable.

Presenting Customer Success as a relationship function when the role was written as a forecastable commercial one. Talking about AI as a feature checklist instead of workflow design, data readiness, and controls. Speaking about partnerships in abstract ecosystem language without sourced and influenced revenue definitions, co-sell mechanics, or marketplace program knowledge. And leading with internal process language instead of customer evidence.

SaaStr's 30-60-90 expectation for a new VP of CS is blunt about the first month: analyze churn, expansion, onboarding, and time-to-value data, refine onboarding, implement health scoring, identify upsell opportunities, and roll out a scalable framework with a real AI component. Jason Lemkin's version of the test is simpler and harder. Does the candidate go talk to customers immediately and build strategy from those conversations, or from internal meetings, tools, and project plans?

Both tests point at the same thing. The market is screening for operators first, coaches second, and storytellers third. Not because relationships stopped mattering, but because the relationship part was never the scarce skill.

One caveat, since I've leaned on a specific set of sources. The job descriptions here are a sample of current postings, not a census, and the Gainsight, ChurnZero, PartnerStack, and Clazar research is vendor-produced. It's current and close to workflow reality, which is why it's useful. It's directional evidence, not industry law. Read enough job descriptions in your own target segment and you'll build a better picture than any survey will give you.

If this is the kind of thing you think about, there's more in the same vein on the blog: https://www.santiagomarin.net/blog