What a Customer Centricity Job Description Really Asks For

Most customer centricity job descriptions are written by people who have never had to operationalise the concept. They list "passion for the customer" as a requirement, demand "a customer-first mindset," and then describe a role that is, in practice, about producing quarterly NPS reports and presenting them to a committee that changes nothing. The candidate who can genuinely build customer centricity — who understands its mechanics, its politics, and its measurement — reads these descriptions and winces.

That gap matters. Defining customer centricity poorly in a job description is the first act of an organisation that will fail to achieve it. The words you use to recruit signal what you actually believe the work involves. And what most organisations believe — if their job descriptions are any evidence — is that customer centricity is a disposition, not a discipline.

It is a discipline. A rigorous one. This article unpacks what a customer centricity role genuinely requires, what the most common mistakes in these job descriptions reveal about organisational culture, and how to write — and read — one that reflects the real work of implementing customer centricity at scale.

What "Customer Centricity" Actually Means in a Job Context

Before you can write an honest job description, you need a working definition that survives contact with a Monday morning. Customer centricity, in operational terms, is the systematic alignment of an organisation's decisions, processes, and culture around the needs, expectations, and experiences of its customers — not its products, not its internal convenience, and not its legacy structures.

The word "systematic" is doing the heavy lifting there. Any individual can be customer-focused in a given moment. Customer centricity is what happens when that orientation is built into governance, measurement, incentive design, and process architecture — so it persists even when the champion leaves, the budget tightens, or the quarterly numbers disappoint.

A person hired into a customer centricity role is therefore not primarily a customer advocate. They are a systems designer — someone who identifies where the organisation's structures work against the customer and engineers the conditions under which better decisions become the default. That is a fundamentally different skill profile from "passionate about service."

Understanding this distinction is the foundation of every other requirement the role should carry. If you get the definition wrong, everything downstream — the competencies, the metrics, the reporting line — is built on sand.

Why Most Customer Centricity Job Descriptions Miss the Point

The most common customer centricity mistakes in job descriptions cluster around three failures: they confuse attitude with capability, they conflate measurement with action, and they underestimate the political difficulty of the role.

Confusing attitude with capability

Phrases like "customer-obsessed," "passionate advocate," and "champion of the customer" describe a feeling, not a skill. They are not wrong — genuine commitment to the customer matters — but they are insufficient. A role that requires someone to change how a bank's onboarding process works, or how a retailer's returns policy is designed, demands specific capabilities: process analysis, stakeholder influence, data interpretation, and the ability to translate customer insight into a business case that a CFO will fund.

Attitude is a threshold condition. It should be assumed, not listed as a headline requirement. The job description's job is to specify what the person will do and what they need to know to do it.

Conflating measurement with action

A significant proportion of customer centricity roles, as advertised, are actually research and reporting roles dressed in more ambitious language. The responsibilities read: "Manage NPS programme," "Analyse customer feedback," "Produce monthly CX dashboards." These are legitimate and necessary activities. But they are inputs to customer centricity, not the thing itself.

Measuring customer experience and improving it are different disciplines. A person who is excellent at customer feedback management — designing surveys, analysing results, building dashboards — is not automatically equipped to redesign the process that is causing the friction the dashboard reveals. The job description needs to be honest about which role this is: analyst, or change agent, or both. Conflating them produces candidates who can measure the problem but cannot fix it, or who can fix it but resent being asked to spend 60% of their time in spreadsheets.

Underestimating the political difficulty

Implementing customer centricity means telling powerful internal stakeholders that their processes, their metrics, or their incentive structures are working against the customer. That is not a comfortable conversation. It requires organisational credibility, executive sponsorship, and a level of commercial fluency that allows the CX professional to speak the language of the people they need to influence.

Job descriptions rarely name this. They describe a role that "collaborates cross-functionally" and "influences without authority" — but they do not acknowledge that this influence will frequently be contested, that the role will sometimes lose, and that resilience under that kind of pressure is a genuine competency worth screening for. Candidates who have never navigated that environment will be surprised by it. Candidates who have will recognise immediately whether the organisation is being honest about what it is asking.

The Competencies a Customer Centricity Role Actually Requires

Stripped of the aspirational language, a well-constructed customer centricity role — whether titled Head of CX, Customer Centricity Manager, or Director of Customer Strategy — requires a specific and learnable set of competencies. These are the ones that separate candidates who can genuinely improve customer centricity from those who can talk about it fluently.

• Journey architecture: The ability to map customer journeys at a level of fidelity that reveals operational root causes — not just emotional pain points — and to translate those maps into actionable redesign briefs. This is a technical skill, not an intuitive one.
• Metric literacy: Understanding not just how to collect NPS, CSAT, and CES, but what each metric measures, where each breaks down, and how to triangulate between them and operational data to form a defensible view of customer experience health.
• Business case construction: The ability to quantify the cost of poor experience — in churn, in support volume, in acquisition cost — and to present a credible return on CX investment. Without this, customer centricity remains a cost centre in the minds of those who control the budget. The CX ROI Calculator is a useful starting point for anyone who needs to build that case quickly.
• Behavioural design: Familiarity with the principles of behavioural economics — particularly how defaults, friction, and choice architecture shape customer decisions — and the ability to apply them to service and process design rather than just marketing.
• Change management: The practical knowledge of how to move an organisation from its current state to a different one — including stakeholder mapping, resistance management, and the sequencing of interventions so that early wins build the political capital for harder changes.
• Voice of customer programme design: Not just running surveys, but architecting a listening system that captures signal across channels, surfaces it to the right people at the right cadence, and closes the loop with customers in a way that builds rather than erodes trust.

None of these are captured by "passion for the customer." All of them can be assessed in an interview or a structured exercise. The job description that names them specifically will attract a fundamentally different — and more capable — candidate pool.

What the Reporting Line Signals About Seriousness

One of the most revealing elements of any customer centricity job description is buried near the bottom: the reporting line. Who this role reports to tells a candidate almost everything they need to know about whether the organisation is serious about achieving customer centricity or performing it.

A customer centricity lead who reports to the Chief Marketing Officer is, in practice, a brand experience function. The lens will be perception and acquisition. A role that reports to the Chief Operations Officer will be oriented toward efficiency and complaint reduction. Neither is wrong — but neither is the same as a role with genuine cross-functional authority to redesign how the organisation serves its customers.

The organisations that make the most progress on customer centricity tend to be those where the CX function has either a direct line to the CEO or sits within a transformation office with explicit board-level mandate. This is not always feasible, particularly in mid-sized organisations. But the job description should be honest about the reporting structure and what it means for the role's scope of influence. A candidate who has operated at the highest level of CX leadership will ask this question in the first interview. If the answer is evasive, they will draw their own conclusions.

Measuring Customer Centricity: What the Role Should Own

A customer centricity role without clear ownership of measurement is a role without accountability. But measuring customer centricity is more complex than tracking a single metric, and the job description should reflect that complexity.

The measurement framework a mature customer centricity function owns typically operates at three levels:

1. Perception metrics: How customers feel about the experience — captured through NPS, CSAT, and qualitative feedback. These are lagging indicators; they tell you what happened, not why, and not what to do about it.
2. Operational metrics: The process data that correlates with experience outcomes — first-contact resolution rates, wait times, digital abandonment rates, complaint volumes by journey stage. These are leading indicators when tracked correctly, and they connect CX performance to things operations teams already measure.
3. Cultural metrics: How customer-centric the organisation's internal behaviours are — captured through employee surveys, mystery shopping, governance audit, and the degree to which customer outcomes feature in leadership decision-making. This is the hardest layer to measure and the most important for long-term CX maturity.

The job description should specify which of these layers the role owns, which it influences, and which it depends on others to provide. Ambiguity here is not flexibility — it is a setup for failure.

The Behavioural Economics Dimension Most Job Descriptions Ignore

Customer centricity strategies that rely solely on listening to customers and removing their stated pain points will plateau. Customers are not always accurate reporters of their own needs. They describe what they want in the moment, not what would genuinely serve them. They are subject to the same cognitive shortcuts and biases that shape all human decision-making.

This is where behavioural economics becomes a genuine competitive advantage — and where most customer centricity job descriptions reveal a blind spot. The peak-end rule, identified by Daniel Kahneman and Amos Tversky, holds that people evaluate an experience not as an average of its moments but based on how they felt at its most intense point and at its end. A customer centricity professional who understands this will design service journeys differently — investing disproportionately in the moments that carry the most emotional weight rather than trying to optimise every touchpoint equally.

Similarly, loss aversion — the well-established finding that losses loom larger than equivalent gains — has direct implications for how organisations communicate service changes, price increases, or policy updates. A CX professional who can apply these principles to journey design is not just more effective; they are operating in a domain that most competitors have not yet entered.

The job description that asks for "knowledge of behavioural economics and its application to service design" will find very few candidates who can genuinely deliver it. That scarcity is precisely why it is worth asking for.

Examples of Customer Centricity Done Differently in Job Descriptions

The gap between organisations that are serious about customer centricity and those that are performing it shows up clearly when you compare how they write these roles.

A performative customer centricity job description leads with culture ("We put the customer at the heart of everything we do"), lists responsibilities that are primarily reporting and survey management, and asks for five years of experience in "a customer-focused environment." It could describe almost any service role in almost any industry.

A serious one opens with the problem the role exists to solve — "We have strong customer satisfaction scores at the transaction level and persistently high churn at the relationship level; we need someone who can find and close that gap." It specifies the authority the role carries, the stakeholders it will need to influence, the metrics it will own, and the organisational changes it will be expected to drive. It asks for evidence of having done this before, not just familiarity with the concept.

The difference in candidate quality between these two approaches is not marginal. The culture of customer centricity that an organisation builds is shaped, in part, by who it hires to lead it — and who it hires is shaped, in part, by how honestly it describes the work.

The Business Case for Getting This Right

There is a straightforward commercial argument for investing in a well-specified customer centricity role. Organisations that align their operations around customer needs consistently outperform those that do not — not because customer centricity is intrinsically virtuous, but because it reduces the friction that drives churn, lowers the cost of complaint resolution, and creates the conditions for the kind of word-of-mouth advocacy that no paid channel can replicate.

The business case for customer centricity is not abstract. It is built from the cost of a lost customer, the revenue from a retained one, the support cost avoided when a journey works as designed, and the acquisition cost saved when an existing customer refers a new one. A customer centricity professional who cannot construct that argument — who cannot translate experience improvement into financial terms — will struggle to secure the investment that makes improvement possible.

This is why commercial acumen belongs in the job description alongside empathy. Not instead of it — alongside it. The customer experience function that earns its seat at the leadership table does so by speaking the language of the people already sitting there.

How to Write — and Evaluate — a Customer Centricity Job Description That Works

Whether you are writing one or reading one, the following principles separate a job description that will attract and identify genuine capability from one that will attract the wrong people and frustrate them once they arrive.

• Start with the problem, not the culture. Describe the specific gap the role exists to close — not the organisation's values. Candidates who can solve the problem will self-select in; those who cannot will self-select out.
• Name the authority, not just the accountability. If the role is expected to change processes, it needs the authority to do so. If that authority is indirect, say so — and describe the mechanisms through which influence will be exercised.
• Specify the metrics the role owns. Not "contributes to" — owns. Accountability without ownership is a recipe for diffusion.
• Ask for evidence of change, not just experience of measurement. "Managed NPS programme" is a credential. "Redesigned the onboarding journey and reduced early churn by identifying the specific touchpoint driving it" is evidence of capability. Ask for the latter.
• Be honest about the politics. If the role will require influencing a sceptical operations director or a CFO who views CX as a cost, say so. Candidates who have navigated that environment will recognise the honesty and respect it.
• Include the reporting line and what it means. Not just the title of the person they report to, but what that reporting line implies for scope, access, and influence.

For organisations that want to assess their current state before defining the role, a structured CX maturity assessment can clarify which capabilities are already present and which the new hire will need to build from scratch — a useful input to both the job description and the onboarding plan.

The Candidate Who Can Actually Do This

The person who can genuinely implement customer centricity at an organisational level is rare. They combine analytical rigour with political intelligence, commercial literacy with genuine empathy, and the patience to build slowly with the urgency to deliver results that keep the function funded.

They have almost certainly worked in roles where they had to fight for budget, where their recommendations were ignored and then proved right, and where they learned to translate customer insight into language that moved people who did not start out caring about the customer. They are not cynical — cynics do not last in this work — but they are clear-eyed about what it takes.

The job description that finds this person does not promise that the organisation already has a strong customer culture. It describes where the organisation is, where it needs to get to, and what it will take to close that gap. It treats the candidate as an intelligent adult who can assess the challenge and decide whether they want it.

That honesty is, itself, an act of customer centricity — applied to the candidate experience. And it is a signal, to every serious candidate who reads it, that this organisation might actually mean what it says.