How to Land a CX or Support Leadership Role (From Someone Who’s Hired For Them)

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, because 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. 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.

I’ve been writing about job searching on this site since 2008. This piece now replaces all of it.

Start With a Question You Probably Haven’t Asked

Before the resume, before the search, one question: what do you do now, and are you happy doing it?

I’ve watched a lot of good support leaders run hard at a new job without ever asking that. They were unhappy, they assumed the job was the cause, and they went looking for the same role at a different company. Then eighteen months later they were unhappy again, for the same reasons, with a different logo on the badge.

Sometimes the answer really is a new employer. Sometimes the answer is that you want out of the function entirely, or that you want the next level up rather than a lateral move, or that the thing grinding you down is one person and not the job. Those lead to completely different searches. Work out which one you’re running before you write a single application.

Treat the Search Like a Job

The single most useful thing I ever wrote about job hunting was also the simplest, back in 2010: treat your job search like a job.

That means hours, a schedule, and a record. Not evenings when you have energy left over. Block real time, track every application, note who you spoke to and when you said you’d follow up. A serious search at Director level runs three to six months and involves dozens of conversations. You cannot hold that in your head, and the candidates who try are the ones who miss a follow-up with the company they actually wanted.

Keep a simple sheet. Role, company, date applied, source, contact, next action. That is the entire system. It is unglamorous and it works, and it is the difference between running a search and drifting through one.

The Resume Mistake That Kills Most 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 are what I’m actually looking for.

Here’s what an 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 before and after. Not “improved response times” but “reduced median first response time from 17 hours to 2 hours over 18 months.” Not “improved customer satisfaction” but “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 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, 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.

Two pages. Reverse chronological. No photo, no skills bar chart, no rating yourself four stars out of five on leadership.

Getting Past the Machine First

None of that matters if a human never sees it.

Most mid-size and large employers screen with an applicant tracking system before anyone in HR opens your file. The ATS is not reading for quality. It is matching the language in your resume against the language in the job description, and a strong candidate who used different words to describe the same experience gets filtered out alongside the genuinely unqualified ones.

This is the part that makes people angry, and I understand why. It is also not going away, so you work with it.

Take the job description and read it as a keyword list. If it says “customer success” eleven times and your resume says “client services” throughout, you have a matching problem, not a credibility problem. Mirror the employer’s vocabulary where it is honestly true of your experience. If they call it voice of the customer and you called it your VOC programme, write it their way.

Tools like Jobscan will score a resume against a specific posting and show you which terms are missing. I would not pay for one indefinitely, but running two or three real applications through one teaches you the pattern fast, and after that you can do it yourself.

Keep the formatting boring. Text boxes, multi-column layouts, headers and footers, and unusual fonts all parse badly. A clean single-column document in a standard typeface gets read correctly by every system. Save as whatever format the posting asks for, and if it doesn’t say, send a PDF.

Tailor per application. Not a fresh resume every time, but a genuine pass over the summary and the top three bullets so they answer the posting in front of you. Fifteen tailored applications will beat a hundred identical ones. That is not motivational advice, it is just how the filter works.

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 hiring at 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 more useful than “Director, Customer Support at Company X.”

Your About section has 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 the scale you’ve operated at, or the specific problem you’re unusually good at solving.

The activity signals matter more than people realize. A Director of Support who never posts, never comments, 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 visibly engaged with the profession: sharing opinions about AI in the contact centre, commenting on industry research, occasionally writing up what they learned from something that went wrong. Once or twice a week is plenty.

This is the quiet version of what people call thought leadership, and at management level it works better than it has any right to. Having a public position on how support should be run is itself a qualification for running support. It is also the only part of your search that keeps paying out after you’ve taken the job.

The Roles That Never Get Posted

A large share of senior CX and support roles are filled before they are ever advertised. I have seen the number put at eighty percent, and I would not repeat that figure as fact because nobody has ever shown me the working. What I can tell you from hiring is that when I have needed a Director, my first move has been to think about who I already know, and my second has been to ask the people I trust. The posting comes third, if at all.

So build the list before you need it. Pick fifteen to twenty companies you would genuinely want to work for, follow them, learn who runs support there, and pay attention to what they say publicly. When a role opens you will already know whether you want it, and you will have somewhere to start other than the apply button.

Company targeting works better at our level than most people expect. Approaching a support leader at a company you admire, with a specific and informed reason for the conversation and no ask attached, lands far more often than a cold application does. Not always. But the conversation costs you twenty minutes and it occasionally turns into a role that was never going to be posted.

Networking gets a bad name because it is usually described as something transactional. The useful version is much duller: stay in touch with people you have worked with, be helpful when they ask, and be specific when you need something. A contact who cannot hire you can still tell you what the hiring manager is actually worried about, which is worth more than another application.

Working With Recruiters

Recruiters are useful at this level and it is worth understanding what they are actually for.

A recruiter is paid by the employer, usually on commission, when a placement sticks. That shapes everything. They are motivated to fill the role, and they are motivated to fill it with someone who will not leave in six months. It does not make them your adversary, but it does mean their interests and yours overlap without being identical.

What a good one gives you is intelligence. They know what the hiring manager is nervous about, what the last person in the seat got wrong, whether the salary band is real, and how many other candidates are in play. Ask those questions directly. A recruiter who will not answer them is not going to be much use to you.

Work with two or three, not ten. Tell them honestly what you are looking for and what you will not take. And never let one submit you to a company you have already approached yourself, because it creates a fee dispute that gets resolved by dropping the candidate.

Using AI Without Sounding Like It

Every candidate now has access to the same writing tools, and I can tell.

I have read cover letters this year that were clearly generated, and the tell is never a factual error. It is that they are fluent, well structured, and say nothing a hundred other candidates couldn’t have said. They describe the role back to me. They contain no numbers. They have the texture of something written by someone who has never run a queue.

Used well, these tools are genuinely good at the mechanical parts of a search. Reformatting a resume for a specific posting. Pulling the requirements out of a long job description. Drafting a first pass at a follow-up note. Rehearsing answers out loud before a screen, which I cover in the companion piece on turning an interview into an offer.

Used badly, they flatten the one thing you have that nobody else does. Your specifics. The 17 hours to 2 hours. The reorganisation that failed the first time. The escalation that taught you something uncomfortable about your own routing logic. No model can produce those, and they are the entire reason to interview you.

Write the first draft yourself, badly if necessary, then use the tool to tighten it. That order matters.

The Metrics That Signal Senior Credibility

When you’re applying for a Director or VP role, the hiring manager is looking for evidence that you understand the full financial and operational picture, not just the service delivery layer.

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. Knowing the number is not.

Cost per contact and cost to serve. Most support leaders at 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. I’ve written separately about why support is not a cost center but gets defunded anyway, and this is the vocabulary that argument lives in.

Deflection rates and self-service adoption. Increasingly central to executive CX conversations because it connects support investment directly to cost structure. If you’ve built or improved a self-service capability and can show the deflection impact, that’s a powerful story. ICMI publishes benchmark ranges worth knowing before you quote your own numbers in a room.

SLA attainment over time. Not “we hit our SLA.” What was the trend, what broke it, what did you do. The ability to narrate SLA performance across quarters tells a hiring manager you understand operations. If you want the underlying model, I’ve laid out how I design tiered service levels a team can actually hit.

Escalation rates and root cause. Senior leaders understand that escalations are signals, not just problems to be managed. If you’ve built a root cause process and used it to drive product or process change, that demonstrates real operational maturity.

How to Answer “Tell Me About a Time You Improved a CX Metric”

This is the most common interview question for these roles, and most candidates answer it wrong.

The wrong answer gives a clean before-and-after and stops. “We improved our CSAT from 74% to 89% by implementing a new training program.”

The right answer 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 adequate staffing. When I dug into the data, the issue wasn’t headcount. It was routing logic sending complex technical cases to Tier 1, 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. It is what separates a Director-level candidate from a Manager-level one.

The Questions That Signal You’re a Senior Candidate

The questions you ask 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 nobody has solved yet.

“How does the support function report into the executive team, and how often does the VP of Support present to the board?”

“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 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 one is the most useful question in the entire process. The answer tells you more about whether you want the job than anything else in the interview will.

Red Flags in the Job Description

Not every role is worth applying for, and some descriptions tell you what you’re walking into before you speak to anyone.

“You’ll wear many hats” at Director level usually means the function is underfunded and understaffed. At that level you should be building and delegating.

No mention of reporting structure or budget ownership. Ask directly before applying. A Director of Support who doesn’t own a budget and has no direct line to a VP or the C-suite 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 they want a system operator, not a strategic leader.

“Fast-paced environment” plus a very long responsibility list plus a salary range at the low end of market. That combination usually means high attrition in the role and leadership that hasn’t decided what the function is for.

No mention of the customer anywhere in the description. I have genuinely seen Director of Support postings that are entirely inward-facing: tickets, SLAs, agent management, no reference to a customer at all. That tells you exactly where the function sits in the priority stack.

The One Thing Most CX Leaders Get Wrong

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 and CSAT and 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. Same work. Different language, and the second one gets funded. The discipline of translating operational results into business language is the same one I write about on datadrivenops.co, and it is the skill that separates the two levels.

Getting from Director to VP is a different conversation, and one I’m still navigating myself. What I can tell you is that the translation is where it starts.

I’m writing this as a Director. Someone who has hired for these roles at Manager and Director level, and who has been on the receiving end of the process too. I’m not going to pretend I have the VP playbook figured out. What I can tell you is what gets resumes to yes and no at the level I operate at.

If you’ve got the interview and want the part that comes next, that’s here.