Beyond the Job Title: Pricing Hybrid and Emerging Roles in a Skills-Based World

The hardest jobs to price are not the most senior or the most specialized. They are the ones that sit between familiar categories.

A requisition arrives for an AI Enablement Manager. At one company that job is training, change management, and adoption. At another, the same title covers workflow automation, systems integration, and data governance. Another role blends product strategy with data analysis. The titles sound recognizable, but the responsibilities and required skills do not line up cleanly with any single survey benchmark. Hybrid, here, describes the job and not the commute.

There is usually pressure to answer quickly, so teams often default to the closest title anyone can name. That is how a range ends up defending a title instead of a job, and how similar work gets priced two different ways in two different departments.

The answer is not to abandon survey data. It is to understand the work well enough to determine which market data is relevant.

How do you price a job with no survey match?

The practical sequence:

1. Define and level the role before searching for a title.
2. Map the skills and proficiency required to perform the job.
3. Compare a small set of adjacent benchmarks instead of forcing one weak match.
4. Validate the result against internal comparables and current hiring evidence.
5. Document the assumptions, confidence level, and review date.

A disciplined pass through that sequence will show whether the team has enough evidence to make the decision or needs deeper analysis.

Why does title-based pricing break down?

A title is useful for locating possible benchmarks, but it is not enough to validate the match. Hybrid and emerging roles often combine responsibilities that once belonged to separate jobs. Salary.com's Have AI, Remote Work, and "Frankenjobs" Broken Benchmarking? explores how blended work and changing skill requirements are making clean title-to-benchmark matches harder to find.

The same title can represent very different work. A Data Analyst may produce routine reports in one organization and build advanced forecasting models in another. Pricing both roles from the title alone could overvalue widely available skills or undervalue deeper technical proficiency, judgment, and accountability. Different titles can also describe substantially similar work. A defensible match therefore looks at the role's purpose, responsibilities, scope, level, required skills, and talent market, not the label alone.

The job must also be separated from the person performing it. An employee may bring an additional certification, programming language, or industry specialty that the role does not require. Those skills may influence development, mobility, or placement within the range, but they do not automatically change the market value of the job itself.

What is skills-informed job pricing?

Skills-informed job pricing is a skills-based approach that keeps the job as the anchor. It uses what the job actually requires, and how deep those requirements run, to decide which market benchmarks and internal comparables are relevant.

Job architecture establishes the role, family, level, and career relationships. Skills data shows what the role requires, how it differs from adjacent jobs, and how advanced those skills must be. Market data values comparable work. Internal comparables test whether the result makes sense inside the organization. Salary.com's guidance on job architecture and leveling explains why that structure is the foundation for scalable and defensible pay decisions.

This does not mean paying a premium for every skill in a job description or creating a new range for every unusual combination. Skills improve the benchmark decision. They do not replace market data, job architecture, or professional judgment.

How does the five-step pricing process work?

1. Define and level the role

Start with the business need, not the proposed title. Define why the role exists, the outcomes it owns, its continuing accountabilities, its decision authority, and the level of impact expected. Establish the level before selecting a market result, using consistent factors such as scope, complexity, influence, knowledge, risk, and accountability.

Then decide what kind of job you have, because the type changes where you look. An expanded role keeps its main purpose and usually keeps its existing benchmark. A true hybrid draws on two disciplines that both matter, such as a designer who also owns front-end build work, so no single benchmark fits. An emerging role is real, lasting work that surveys have not caught up with. A niche role is well established but thinly covered. An overloaded role is different: it has picked up unrelated duties through vacancies, restructuring, or weak design.

Compensation should not make weak job design permanent by pricing it. If the work does not form a coherent role, clarify, separate, or reassign it before setting a range.

Leveling is not a minor administrative step. Salary.com's 2026 State of Pay and Compensation Practices report found that 22% of organizations do not use job leveling to inform their pay structure. When leveling is disconnected from the pay structure, the highest-paying candidate benchmark can quietly become the level-setting method, even when the role's internal scope does not support it.

2. Map the required skills and proficiency

Once the role is coherent and leveled, list what someone must actually be able to do. Start with the core skills of the main discipline, then the ones borrowed from the second. Add any technical, regulatory, or specialist requirements. Then add the skills that make the rest usable: judgment, communication, problem solving, and working across teams.

For each skill that matters, ask whether it is required or just preferred, whether it is common to the field or the thing that sets this job apart, how often it is used, and at what depth. Then ask the question teams skip: does the benchmark you have in mind already include it? A skill is more likely to change the price when it changes the job's output, risk, or recruiting market, and when that value is not already reflected in the benchmark.

Doing this once is analysis. Doing it the same way every time is harder. In free-text job descriptions the same skill picks up three different names and "required" quietly blurs into "preferred". Skills Library uses consistent skill names and defined proficiency levels, so the next person pricing a hybrid role works from the same reference.

3. Build the adjacent benchmark set

Do not begin by asking which single title matches. Ask which established jobs represent the role's primary purpose, secondary discipline, organizational level, and recruiting market. The result may be a small set of adjacent survey lines rather than one perfect match.

That set is evidence to evaluate, not a command to average every number. Four outcomes are common:

• Anchor on one benchmark when a single job covers the main purpose, level, and talent market.
• Blend two benchmarks when both disciplines are a real, continuing part of the job and both match at the same level.
• Use a close match with an adjustment when a required skill changes who you have to recruit and the benchmark does not already cover it.
• Place the job internally for now when outside evidence is too thin, then revisit as the market fills in.

Hours are a clue, not the test. A skill used a few hours a week can still set the price if it carries the most technical difficulty, the most regulatory exposure, or the most risk in a bad decision.

Can you blend two survey benchmarks? Yes, when both disciplines are a real part of the job and both matches are solid. CompAnalyst Market Data Max can support hybrid-job pricing once the underlying job architecture and skills mapping have already established which benchmarks are relevant. A blend is not right just because each benchmark contains one task from the job. Weight what the analysis found, and do not let the weighting replace it.

Should a hybrid title get a pay premium? No. A new title is not evidence of higher value. An adjustment can be right when a required skill changes who you have to hire, what level of proficiency is required, and which talent market you must recruit from. Check first that the benchmark does not already cover it.

4. Validate against internal comparables

Compare the proposed placement with jobs at the same level, adjacent roles in the relevant career ladders, positions with similar decision authority, and jobs that compete for the same internal or external talent. Check the relationship to the manager, possible direct reports, existing ranges, and grade relationships.

External benchmarks show what adjacent work costs. Internal job architecture shows whether the placement is coherent. A market calculation that creates compression, breaks a career relationship, or places the role above jobs with greater scope needs another look.

5. Document confidence and revisit

Use current hiring evidence to test the recommendation. Relevant job postings can show recurring skill requirements, advertised ranges, competitor hiring activity, and where demand is moving. Candidate expectations, time to fill, offer acceptance, and retention patterns show whether that market pressure is appearing in practice. SalaryIQ provides current job-posting intelligence that can add context to HR-reported benchmarks.

Document the benchmarks considered, the skills that affected the selection, any weighting or adjustment, the internal comparables reviewed, and the areas where confidence remains limited. Set a review date. An emerging-role price can be defensible without pretending it will remain final as the work and market mature.

How would this work for a Product Marketing and Data Analyst?

Consider a role that analyzes customer, competitor, product, and campaign data, builds dashboards, and turns those findings into positioning and go-to-market recommendations. It uses SQL and business-intelligence tools, but it does not build machine-learning models or own data engineering.

The first step is to identify the role's primary purpose. In this case, the employee is using data to make product-marketing decisions. That makes Product Marketing Analyst or Product Marketing Manager the strongest starting benchmark, depending on the level of the role.

Marketing Analytics Analyst can provide useful secondary evidence because analytics is a meaningful part of the work. A Data Scientist benchmark should be rejected because the role does not require advanced modeling, experimentation, or machine-learning expertise.

Business Intelligence Analyst is worth a look only if the role builds data models or owns reporting for the wider business. Here it does not.

For this role, the compensation team would most likely:

1. Use product marketing as the primary market anchor.
2. Compare the result with marketing analytics data.
3. Consider a weighted blend only if analytics represents a substantial and continuing part of the role.
4. Validate the final placement against internal product marketing, marketing analytics, and business-intelligence roles at the same level.

The important point is that using SQL or building dashboards does not automatically make this a data-science job. The role's business purpose and required level of analytical proficiency determine which benchmarks are relevant.

How can the same AI title lead to different benchmarks?

An AI Enablement Manager may sound like one identifiable job, but the title can describe very different work.

At one company, the role helps employees adopt approved AI tools through training, communication, and guidance. That work needs teaching, facilitation, and change-management skills. The closest benchmarks come from learning and development, organizational development, change management, or program management.

At another company, the same title covers finding automation opportunities, building AI-enabled workflows, managing system integrations, and handling data governance. That work needs process analysis, defining technical requirements, and systems integration skills. The closest benchmarks are business systems, IT program management, automation, or digital transformation.

One title, two jobs, two different hires, two different markets. The title does not set the benchmark. The work does. An AI label tells you the work may be changing. It does not tell you the level or the price.

Why does a skills taxonomy make the process repeatable?

A compensation team can work through one unusual job by hand. The harder problem is doing it the same way six months later, in a different department, for a job nobody has seen yet.

That is what a taxonomy is for. Once skills and proficiency levels are defined, they carry forward. The next hybrid role gets compared against jobs that are already mapped, at a known level, on the same scale. Career paths hold together because the steps between jobs are described in the same terms. And the basis for last year's decision is easier to retrace when someone asks why the range looks the way it does.

Skills Library standardizes the skills and proficiency levels. JobArchitect Max connects them to job content, levels, career relationships, approvals, and market pricing.

How should job architecture evolve as roles change?

Salary.com's 2026 State of Pay and Compensation Practices report, based on responses from 525 participating organizations, found that 51.4% had a formal job architecture in place, while 18.3% had no plans to build one. Those figures matter because hybrid and emerging roles expose the limits of an architecture that cannot show how jobs, skills, levels, and market relationships fit together.

These roles should not be managed indefinitely through improvised titles, forced survey matches, and undocumented exceptions. As the work changes, the architecture should change with it. That means updating job content, mapping required skills and proficiency, clarifying levels, and preserving sensible relationships across job families. Market data still anchors the pricing decision, but job architecture makes that decision consistent and understandable inside the organization. Your architecture needs to evolve alongside how roles are actually being created, not catch up to them after the fact.

Start with the work. Price the skills the job requires. Use market data to anchor the decision and use job architecture to keep it coherent.