I’ve reviewed hundreds of applications for support and CX leadership roles over the past 15 years.
Most of them made the same mistakes. Not because the candidates weren’t qualified — many of them were — but because they were presenting themselves like generic managers instead of CX leaders. They were writing resumes and doing interviews as if the hiring manager couldn’t tell the difference between someone who had genuinely run a support operation and someone who had just been adjacent to one.
I’ve been on both sides of this process. I’ve applied for these roles, and I’ve hired for them. What follows is what I actually look for — and what consistently gets applications moved to the no pile before I’ve finished reading the first page.
The Resume Mistake That Kills Most CX Leadership Applications
The weakest thing you can write on a CX leadership resume is “managed a team of X people.”
Every candidate writes it. It communicates almost nothing. Managing three people is different from managing thirty, which is different from managing a hundred and sixty across three continents. Scale matters. Complexity matters. And the metrics that came out of that management — those are what I’m actually looking for.
Here’s what a CX leadership resume entry should contain, in order of importance:
Scale: How many people? How many tiers? How many channels? Across how many locations? Give me the actual numbers. “Led a 69-person global support team across North America, Europe, and Latin America” tells me something. “Led support team” tells me nothing.
Metrics you moved: I want to see before and after. Not “improved response times” — “reduced median first response time from 17 hours to 2 hours over 18 months.” Not “improved customer satisfaction” — “improved CSAT from 74% to 89% over two years.” If you can’t point to a metric you materially changed, you haven’t made the case that you actually led anything.
Budget: Support leaders who have managed significant budgets and understand the financial dimension of the function are rare. If you’ve owned a budget, say so and give the number. $2M and $12M tell very different stories about your operating level.
What you built: Did you build a process that didn’t exist before? Stand up a new tier? Launch an offshore team? Implement a new platform? The people I want to hire have built things, not just maintained them.
What Your LinkedIn Profile Actually Needs
Most CX and support leaders have LinkedIn profiles that read like a list of job titles and responsibilities. That’s not a profile — that’s a CV summary. And it won’t get you noticed by anyone who’s actually hiring at the Director level.
Your headline should not be your job title. Your title is already listed under your name. Use the headline to say what you’re known for. “Director of Support Operations | ITIL Expert | Building and scaling global CX organizations” is infinitely more useful than “Director, Customer Support at Company X.”
Your About section needs to do one job: make the right hiring manager want to talk to you in the first sentence. It shouldn’t start with “I am a passionate customer experience professional with over X years of experience.” Every profile starts that way. Start with what makes you different. What’s the scale you’ve operated at? What’s the specific problem you’re particularly good at solving?
The activity signals matter more than most people realize. A Director of Support who never posts, never comments on industry content, and has no visible point of view on the function looks like someone who is just doing a job. The candidates who stand out are the ones who are visibly engaged with the profession — sharing opinions about AI in the contact centre, commenting on industry research, occasionally sharing what they’ve learned. You don’t need to post daily. Once or twice a week is enough to signal genuine engagement.
The CX-Specific Metrics That Signal Senior Credibility
When you’re applying for a Director or VP of Support role, the hiring manager is looking for evidence that you understand the full financial and operational picture — not just the service delivery layer.
The metrics that signal senior credibility in CX leadership interviews:
CSAT, CES, and NPS — but in context. Anyone can quote a CSAT score. The question is whether you understand what drives it, how you’ve influenced it, and what its limitations are. If you can articulate why CSAT went up and what you had to change to get there, that’s credibility. If you just know the number, that’s not enough.
Cost per contact and cost to serve. Most support leaders at the manager level don’t think about this. Directors and VPs have to. If you’ve never calculated cost per contact or used it to make a business case, start now — and be ready to talk about it in interviews.
Deflection rates and self-service adoption. This is increasingly central to executive-level CX conversations because it directly connects support investment to cost structure. If you’ve built or improved a self-service capability and can show the deflection impact, that’s a powerful story.
SLA attainment over time. Not just “we hit our SLA.” What was the trend? What broke it? What did you do to fix it? The ability to narrate SLA performance across quarters tells a hiring manager you actually understand operations.
Escalation rates and root cause. Senior CX leaders understand that escalations are signals, not just problems to be managed. If you’ve built a root cause analysis process and used it to drive product or process changes, that demonstrates genuine operational maturity.
How to Answer “Tell Me About a Time You Improved a Customer Experience Metric”
This is the most common interview question for CX leadership roles, and most candidates answer it wrong.
The wrong answer gives a clear before-and-after metric and stops there. “We improved our CSAT from 74% to 89% by implementing a new training program.”
The right answer does three things: establishes the context and the diagnosis, explains the strategic decision behind the intervention, and quantifies the outcome while acknowledging what you’d do differently.
“When I joined Q4, the support organization was averaging 17-hour first response times despite having adequate staffing. When I dug into the data, the issue wasn’t headcount — it was routing logic that was sending complex technical cases to our Tier 1 team, who were then holding them while they escalated internally. We redesigned the routing model, implemented skill-based distribution, and added an AI triage layer for initial classification. Within 8 months, first response time was down to 2 hours. The lesson I took from it was that headcount is almost never the answer to an SLA problem — the answer is almost always in how work flows through the system.”
That answer tells me how you think, not just what you did. That’s what separates a Director-level candidate from a Manager-level candidate in an interview.
The Questions That Signal You’re a Senior Candidate
The questions you ask in a CX leadership interview matter as much as the answers you give. Most candidates ask about team size, tools, and culture. Senior candidates ask about strategy, accountability, and the problems that haven’t been solved yet.
Questions that signal you’re thinking at the right level:
- “How does the support function report into the executive team, and how often does the VP of Support present to the board or C-suite?”
- “What’s the current cost per contact, and how has that trended over the past two years?”
- “What’s the relationship between support and product when a systemic issue is identified? Who owns the fix?”
- “What does success look like for this role in the first 90 days — and in the first year?”
- “What’s the biggest unresolved operational challenge the team is facing right now?”
That last question is particularly useful. The answer will tell you more about whether you actually want the job than anything else in the interview.
Red Flags in CX Leadership Job Descriptions
Not every role is worth applying for, and some job descriptions tell you clearly what you’re walking into before you’ve spoken to anyone.
“You’ll wear many hats” in a Director of Support job description usually means the function is underfunded and understaffed. At Director level, you should be building and delegating, not wearing hats.
No mention of a reporting structure or budget ownership. If the job description doesn’t mention who the role reports to or whether it carries budget responsibility, ask directly before applying. A Director of Support who doesn’t own a budget and doesn’t have a direct line to a VP or C-suite executive is a manager with a better title.
A list of tools as requirements rather than outcomes. “Must have experience with Salesforce, Zendesk, and Freshdesk” as the primary technical requirement suggests the organization is looking for a system operator rather than a strategic leader. Senior CX roles should be evaluated on outcomes, not tool familiarity.
“Fast-paced environment” combined with a very long list of responsibilities and a salary range at the low end of market. This combination usually means high attrition in the role, unclear expectations, and leadership that hasn’t figured out what the function should actually do.
No mention of the customer or the customer experience in the description. This sounds obvious, but I’ve seen Director of Support job descriptions that are entirely inward-facing — focused on tickets, SLAs, and agent management with no reference to the customer at all. That tells you where the function sits in the organization’s priority stack.
The One Thing Most CX Leaders Get Wrong About Executive Presence
Getting a Director of Support role requires demonstrated operational competence. Getting from Director to VP is a different conversation — one I’m still navigating myself. What I can tell you is that the translation from functional metrics to business language is where that transition starts. But that’s a post for another day.
The support leaders I’ve seen stall out at Director level almost always have the same problem: they present their work in functional terms — tickets, CSAT, SLAs — without translating it into the financial and strategic terms that resonate at the executive table.
“We improved CSAT by 15 points” is a functional result. “We improved CSAT by 15 points, which our analysis suggests reduced churn by approximately 3%, representing roughly $2.4M in retained ARR” is an executive conversation.
I’m writing this as a Director — someone who has hired for CX and support leadership roles at the Manager and Director level, and who has been on the receiving end of that process too. I’m not going to pretend I’ve got the VP playbook figured out. What I can tell you is what gets resumes to yes and no at the level I operate at.
Hutch Morzaria is a CX and Support Leadership professional with 19 years of experience building and leading support organizations across SaaS, Fintech, and enterprise technology. He has held Director-level roles at Q4 Inc, AudienceView, Johnson Controls, and others, and holds ITIL Expert certification across V3 and V4.
