Scoring the Skill Factor: Education, Experience, and Know-How

Scoring the Skill Factor: Education, Experience, and Know-How

Skill is the factor everyone thinks they understand, which is exactly why it gets scored badly. Raters drift toward the résumé of the person in the chair instead of what the job requires, and degrees start to count as points whether or not the work needs them.

That drift costs you twice. Over-credit credentials and you inflate grades for jobs with fancy requirements on paper. Under-credit hard-won experience and you under-grade skilled trades, senior analysts, and anyone without a degree. Both errors show up in a pay-equity review.

In this guide you will define the skill factor, split it into three scorable sub-factors, build a five-degree scale with point values, and run a worked example. You will also see the one rule that keeps skill scoring honest: score the job, not the person.

TL;DR

• Skill measures the knowledge, training, and ability a job requires, not what the current employee happens to have.
• Score it in three sub-factors: formal knowledge, experience, and breadth or complexity of skills applied.
• Define each degree by the minimum a new hire needs to perform the job, and require evidence from the job questionnaire.
• Weight it heavily, often 25% to 40% of total points, then test it against your benchmark jobs.
• Never score the degree alone. Equivalent experience can earn the same degree as a credential.

What the skill factor measures

The point-factor method scores every job against the same set of compensable factors. Skill is one of the four classic categories, alongside effort, responsibility, and working conditions.

The U.S. Equal Pay Act regulation gives you a clean anchor. Under 29 CFR 1620.15, skill is assessed using experience, training, education, and ability, and it is measured by the performance requirements of the job. Two points from that rule belong in your rater guide. Skills a job does not require do not count. And an employee's efficiency on the job is not a measure of skill.

Other methods build the same idea into a major dimension. In the Hay method (Korn Ferry's approach), know-how covers the knowledge, practical skills, and people skills a job requires, according to the Government of Newfoundland and Labrador's description of the method. If you want to compare approaches, see our guide to Hay vs Mercer IPE.

A clean definition for your plan: skill is the combination of knowledge, training, and ability that a job requires a competent new hire to bring, or to build quickly, to perform it fully.

Split the factor into three sub-factors

One blended skill score hides what raters are judging. Three sub-factors make scoring repeatable and expose double counting.

Formal knowledge. What body of knowledge does the job require? This ranges from basic literacy and on-the-job instruction up to a professional license or an advanced degree. Always define a degree by the knowledge needed, then list acceptable routes: a degree, a certification, an apprenticeship, or equivalent experience.

Experience. How much time does it take to become fully proficient? Count the time to reach full performance, not the tenure of the person currently in the job. A role that takes six weeks to learn is a different degree than one that takes six years.

Breadth and complexity of skills applied. How many distinct skills does the job combine, and how hard are they to apply? A technician who diagnoses faults across three systems uses a broader skill set than one who runs a single machine. Include interpersonal and technical skills if the job needs them.

Some plans add a fourth sub-factor for language or technical certification. Add it only if your jobs vary on it in a way the other three cannot capture. If you are unsure how many factors your plan can support, read how many compensable factors to use.

Build a five-degree scale

Define each degree by what a competent new hire must bring to the job. Here is a scale you can adapt for formal knowledge:

And for experience:

Write the "or equivalent" language into every degree. Without it, raters turn your scale into a credential check, and jobs held by people without degrees get systematically under-graded.

Our guide to factor degree definitions covers how to word each level so two raters land on the same one.

Assign points and weight

Skill usually earns more weight than effort or working conditions, because it separates grades reliably across a wide range of jobs. A common range is 25% to 40% of total points. If you use 35% of a 1,000-point plan, you have 350 points to distribute across three sub-factors.

You do not have to split evenly. A professional-services firm might give formal knowledge 150 points, experience 120, and breadth 80. A manufacturer might shift weight toward experience and breadth. Whatever you choose, use an accelerating progression across degrees, because the jump from a bachelor's level to an advanced professional level is larger than the jump from degree 1 to 2. For example, with 150 points for formal knowledge:

• Degree 1: 15 points
• Degree 2: 35 points
• Degree 3: 65 points
• Degree 4: 105 points
• Degree 5: 150 points

Then test the weights. Score ten benchmark jobs, convert points to a rank order, and ask whether the order matches what leaders already believe is sensible. Our article on compensable factor weighting shows how to run that check.

Want to see this scored in software? You can model your own sub-factors, weights, and degree definitions in PointFactors and watch every job move. Start free.

A worked example

Take two jobs in a 1,000-point plan with the weights above (formal knowledge up to 150, experience up to 120, breadth up to 80).

Job A: Senior Compensation Analyst. Needs a bachelor's degree or equivalent, builds pay models, and takes about three years to reach full performance. Combines survey analysis, statistics, and policy interpretation.

• Formal knowledge: degree 4 (105 points)
• Experience: degree 4 (about 72 points on a 120-point scale)
• Breadth: degree 3 (about 32 points on an 80-point scale)
• Total: 209 points

Job B: Maintenance Electrician. Needs a trade certification or equivalent apprenticeship, about four years to full proficiency, and diagnoses faults across electrical, controls, and hydraulic systems.

• Formal knowledge: degree 3 (65 points)
• Experience: degree 4 (about 72 points)
• Breadth: degree 4 (about 52 points)
• Total: 189 points

The analyst edges out the electrician by 20 points, driven by formal knowledge. But notice that the electrician's broader skill mix closes most of the gap, and that no bachelor's degree was required to earn degree 4 on experience. That is the point of scoring sub-factors separately.

Common scoring mistakes

Scoring the person instead of the job. A receptionist with a master's degree does not hold a degree 5 job. Score the minimum the job requires, not the highest credential on file.

Treating degrees as the only route. Without "or equivalent" language, skilled trades, veterans, and self-taught specialists get under-graded. That is a fairness risk as well as an accuracy problem.

Counting rare or trivial skills. If a skill is used once a year, it should not lift the degree. Set a rule for "regular," such as 20% of working time, and enforce it.

Mixing skill with responsibility. Needing deep expertise to make a decision is skill. How far that decision reaches is responsibility. Write down where each demand lives so it is not paid twice. Our guide to the responsibility factor covers the other side of that line.

Skipping rater calibration. Skill scores drift fastest when raters work alone. Have your committee score three or four sample jobs together first. Our guide to job evaluation calibration shows how.

FAQ

Is skill the same as performance? No. Skill is what the job requires. Performance is how well the employee does it. The Equal Pay Act regulation says efficiency on the job is not a measure of skill, and job evaluation is not performance evaluation.

How much should skill weigh? Typically 25% to 40% of total points. Use the high end for professional and technical structures and the low end for plans covering mostly hourly, task-based work. Validate against your benchmark jobs.

Should education and experience be separate factors? Often they work better as sub-factors inside skill. Make them separate factors only if your organization wants each visible in reports and your jobs vary independently on both.

How do I score a job where people reach competence through different paths? Score the requirement, not the path. Define the knowledge and time to proficiency, and list every acceptable route in the degree definition.

Does a license automatically mean degree 5? Not automatically. Check the knowledge the license represents. A required license for a narrow task may sit at degree 3, while a professional license with deep theory sits at degree 5.

How do I handle skills that are only occasionally used? Count them only if they are a regular, required part of the job. A rare skill that does not meet your "regular" rule should not move the degree.

How often should I revisit the scale? Review it when technology changes the knowledge a job needs, when you restructure, or during a re-evaluation cycle. For most teams, a light annual check is enough.

Where to go next

Start with benchmark jobs at the ends of your range. If a mailroom clerk lands at degree 1 and an attorney at degree 5 without argument, your definitions work. If raters disagree on the middle degrees, tighten the language before scoring the full job set.

For the bigger picture, read our guide to the point-factor method, and see how this fits the full job evaluation process. Our companion piece on the working conditions factor covers the lightest-weighted factor. To build and test your own scale without spreadsheets, start free with PointFactors or see pricing.

Justin Hampton is the founder and CEO of PointFactors.