A new function becomes visible before it becomes official: a head of growth asks for analysts, store operations wants trainers, product wants a new trust team, and suddenly HR has five roles with no pay bands, no benchmarks and no internal equity logic. If compensation is built casually here, the company either overpays for ambiguity or loses the very people needed to make the new function work.
Compensation structure is the architecture of salary ranges, incentives, benefits and rules used to pay roles fairly and competitively.
For a new function, start with business purpose, not salary numbers: what capability is being built and which roles create value?
Use a funnel: define roles, evaluate jobs, benchmark market pay, create pay bands, design incentives and set governance.
The hardest trade-off is external competitiveness versus internal equity: paying market rates without disturbing existing teams.
Track compa-ratio, range penetration, offer acceptance, pay mix, regretted attrition and pay equity gaps.
Incentives should reward what the function controls: avoid giving a support function a sales-style plan if outcomes are indirect.
The strongest interview answer separates job worth, person worth and performance worth.
Big Picture: Compensation Design Is a Funnel, Not a Salary Guess
When a new function is created, HR is not merely deciding “how much to pay.” It is converting a business need into roles, levels, pay ranges, incentive logic and review rules that can scale without creating chaos.
A strong compensation structure narrows a broad business need into clear, defensible pay decisions.]
<h2>Core Explanation: How to Build Compensation for a New Function</h2>
<p>The big idea is simple: <strong>pay the role for its value, pay the person for their capability, and pay performance for results</strong>. Most poor compensation designs mix these three and become impossible to defend.</p>
<p>A new function creates extra ambiguity because there may be no internal precedent. For example, a company launching an AI governance team, quick-commerce dark store planning function, creator partnerships team or omnichannel retail operations function may not have old job descriptions or salary bands to copy. HR must build the logic from first principles.</p>
<h2>The Six-Step Process</h2>
<roadmap-steps
data-steps='[
{"title":"Clarify the business mandate","desc":"Define why the function exists, what outcomes it owns and whether it is strategic, enabling or support-oriented."},
{"title":"Build job architecture","desc":"List roles, reporting lines, career levels and decision rights before discussing salary."},
{"title":"Evaluate job worth","desc":"Assess each role on skill, accountability, problem-solving, impact, people responsibility and scarcity."},
{"title":"Benchmark the market","desc":"Use relevant peer companies, role families and location data; do not compare a niche digital role only with traditional industry averages."},
{"title":"Create pay bands and pay mix","desc":"Set minimum, midpoint and maximum for each level, then decide fixed pay, variable pay, benefits and long-term incentives."},
{"title":"Install governance","desc":"Define approval rules, exception handling, annual review cycles and equity checks so the structure survives growth."}
]'>
</roadmap-steps>
[[FIGURE: {"layout":"flow","items":[{"label":"Role Clarity","note":"What is the job?"},{"label":"Job Evaluation","note":"How valuable?"},{"label":"Market Pricing","note":"What pays outside?"},{"label":"Band Design","note":"What range?"},{"label":"Review Rules","note":"How maintained?"}]} | caption: The sequence prevents the common error of starting with market salary before defining job value.]
<h2>The Four Design Choices HR Must Get Right</h2>
<p>For a new function, compensation design usually fails at one of four points: unclear levels, wrong peer benchmark, badly chosen incentive metric or weak governance. Use this matrix to make the trade-offs explicit.</p>
[[FIGURE: {"layout":"matrix","xAxis":"Market scarcity","yAxis":"Business impact","items":[{"label":"Strategic Scarce","note":"Premium pay, retention focus"},{"label":"Critical Scarce","note":"Market lead selectively"},{"label":"Core Stable","note":"Structured internal equity"},{"label":"Support Stable","note":"Cost discipline"}]} | caption: Pay premiums should be reserved for roles that are both scarce in the market and important to business outcomes.]
<data-table
data-headers='["Design Choice", "What it decides", "Interview-ready logic"]'
data-rows='[
["Job family", "Which group the role belongs to, such as sales, analytics, operations, product or HR", "Do not force a new role into an old family if skills and market pricing are different."],
["Leveling", "How junior, mid, senior and leadership roles differ", "Levels should reflect scope, decision rights, complexity and accountability."],
["Pay positioning", "Whether the company pays below, at or above market median", "Lead the market only for scarce, high-impact roles; match market for stable roles."],
["Pay mix", "The split between fixed pay, variable pay, benefits and long-term rewards", "Variable pay should match controllable outcomes, not broad company results alone."],
["Governance", "Who approves offers, exceptions, increments and band movement", "Without governance, every urgent hire becomes a one-off exception."]
]'>
</data-table>
<h2>Worked Example: Creating a Pay Band for One New Role</h2>
<p>Assume an Indian beauty-commerce company is creating a new role: <strong>Omnichannel Inventory Planner - Level 2</strong>. Market benchmarking suggests that comparable roles cluster around an illustrative midpoint of ₹12 lakh fixed CTC. HR decides to build a range from 80% to 130% of midpoint.</p>
<data-table
data-headers='["Calculation", "Formula", "Result", "Interpretation"]'
data-rows='[
["Minimum", "₹12 lakh × 80%", "₹9.6 lakh", "Entry point for qualified but developing talent."],
["Midpoint", "Market reference point", "₹12 lakh", "Fully competent performer for the role."],
["Maximum", "₹12 lakh × 130%", "₹15.6 lakh", "Experienced high performer before next-level promotion."],
["Candidate offer", "Offered salary", "₹11.4 lakh", "Below midpoint but within band."],
["Compa-ratio", "₹11.4 lakh ÷ ₹12 lakh", "0.95", "Healthy if the candidate is close to fully competent."],
["Range penetration", "(₹11.4 lakh - ₹9.6 lakh) ÷ (₹15.6 lakh - ₹9.6 lakh)", "30%", "Leaves room for future increments within the level."]
]'>
</data-table>
<p>The result is defensible because the offer is not just “what the candidate asked for.” It is anchored to role value, market data and internal progression room.</p>
<h2>Key Compensation Metrics to Track</h2>
<p>Good compensation structures are maintained through measurement. The numbers below help HR detect whether the new function is competitive, fair and financially sustainable.</p>
<data-table
data-headers='["Metric", "Formula or definition", "What good looks like"]'
data-rows='[
["Compa-ratio", "Employee salary ÷ salary range midpoint", "Around 0.95-1.05 is healthy for a fully competent performer; below 0.80 or above 1.20 needs review."],
["Range penetration", "(Salary - range minimum) ÷ (range maximum - range minimum)", "0%-100% is inside band; 40%-60% is typical for an established performer."],
["Offer acceptance rate", "Accepted offers ÷ total offers made", "Above 80% is generally strong; a lower rate may signal weak pay positioning or poor role clarity."],
["Variable pay mix", "Target variable pay ÷ total target compensation", "Strong when it matches role control; sales roles may carry higher variable pay than policy or enablement roles."],
["Regretted attrition", "High-performing voluntary exits ÷ average headcount", "Lower is better; sudden spikes in the new function may indicate market underpay or career path issues."],
["Pay equity gap", "Average pay difference after controlling for role, level, location and performance", "Smaller is better; unexplained gaps should trigger corrective review."]
]'>
</data-table>
<h2>Definitions You Should Be Able to Say Clearly</h2>
<tip-box data-type="info" data-title="Canonical Definition" data-icon="📘">
<p><strong>Dessler:</strong> Employee compensation means “all forms of pay or rewards going to employees and arising from their employment.”</p>
</tip-box>
<ul>
<li><strong>Compensation structure:</strong> A formal system of pay ranges, incentives, benefits and rules for different roles and levels.</li>
<li><strong>Job evaluation:</strong> A systematic method to determine a job’s relative worth inside the organization.</li>
<li><strong>Salary band:</strong> The minimum, midpoint and maximum pay range assigned to a role or level.</li>
<li><strong>Market benchmarking:</strong> Comparing pay against relevant external roles, industries, geographies and talent competitors.</li>
<li><strong>Internal equity:</strong> Fairness of pay among employees with comparable role value, capability and performance.</li>
</ul>
<h2>Case Study: Nykaa and the Compensation Logic for an Omnichannel Function</h2>
<tip-box data-type="info" data-title="Case Study - Nykaa" data-icon="🏆">
<p>Nykaa’s move from online beauty commerce into omnichannel retail shows why a new function needs a separate compensation architecture, not borrowed pay bands from either pure e-commerce or traditional retail alone.</p>
</tip-box>
[[GOLD-IMAGE: A modern beauty retail counter in soft pink tones, with a store associate helping a customer while a tablet shows generic inventory tiles without readable text or logos | caption: Omnichannel roles sit between store experience, digital data and supply chain execution.
Situation: Nykaa built its brand around online beauty discovery, content-led commerce and a wide assortment. As the business expanded into physical retail and omnichannel experiences, the company needed roles that connected store operations, beauty advisory, inventory planning, CRM, category teams and digital demand signals.
The compensation challenge: These roles do not fit neatly into one old salary structure. A beauty advisor role has retail service characteristics, a store operations role has execution and people-management demands, and an omnichannel planner may need analytics, inventory and category understanding. If HR simply copied traditional retail pay, it could underpay digital capability. If it copied e-commerce pay, store economics could become unsustainable.
The move: A sound structure would separate the function into role families: store experience, retail operations, omnichannel planning and category support. Each family would have levels, pay bands and incentives linked to controllable metrics. For example, store advisors could have fixed pay plus service and conversion-linked incentives, while planners could have stronger fixed pay with bonuses linked to availability, markdown discipline and forecast quality.
Outcome and lesson: The lesson is not that omnichannel teams should be paid more everywhere. The lesson is that a new function often combines multiple labour markets. The primary driver of a good structure is accurate role segmentation, supported by market benchmarking, pay mix design, career path clarity and governance.
How AI Changes Compensation Structure Design
AI is changing compensation work in three practical ways, especially when a company builds a new function with limited historical data.
Faster job architecture: HR teams can use generative AI to convert business objectives into draft job descriptions, skill clusters and level differentiators. The human check is essential because AI may over-standardize nuanced roles.
Sharper market sensing: AI tools can scan job postings, skill requirements and compensation disclosures where legally available to detect emerging role premiums, especially for AI governance, cyber risk, growth analytics and product operations roles.
Pay equity diagnostics: Machine learning can flag unexplained pay gaps by role, level, location, tenure and performance. The caution is bias: if historical pay data is biased, the model may reproduce it unless audited.
Use NotebookLM: upload a company annual report, recent job postings and your compensation notes, then ask, “What new functions is this company building, what skills do they require, and how should fixed pay, variable pay and governance differ by role family?”
Interview Relevance
“Assume a fast-growing Indian consumer-tech company is creating a new AI-led customer experience function. How would you design the compensation structure for this function?”
Say one sentence that shows maturity: “I would not over-incentivize the function on outcomes it does not fully control; I would link incentives to controllable service, productivity and quality metrics.”
Common Mistake
The biggest mistake is jumping straight to salary numbers. It costs candidates because it sounds transactional and ignores role design, internal equity and governance. The one-line fix: start with job architecture, then evaluate worth, then benchmark pay.
What to Revise Next
This is a natural capstone for compensation and HR design. Now do a final review by connecting the full journey: job analysis, job evaluation, salary bands, incentives, benefits, performance management and pay equity. If you can solve one integrated HR case using all of these, you are interview-ready.
Mark Lesson Complete (Build a Compensation Structure for a New Function - Interview-Ready HR Case Framework)
