Run a job analysis
Choose the tasks a role really involves, rate their importance and frequency, pick the knowledge, skills and abilities, and save a dated record that drafts the hiring kit.
Transcript (1:45 video, captions in English)
- How to: run a job analysis
- WHAT IT'S FOR: Write down what the job involves before deciding how to hire for it
- What you need first. A role in Job architecture. Ideally linked to an O*NET occupation. Editor, admin or owner access
- STEP 1: Choose the Role, then Analyze this role. Under 1. Job analysis on the Hiring tools page
- STEP 2: Tick the tasks the job really involves. Add any missing ones with Add task
- STEP 3: Rate Importance and Frequency. Importance × frequency of 12 or more marks a task critical
- STEP 4: Keep the knowledge, skills and abilities. Needed on day one. In Notes, write who rated and how
- STEP 5: Select Save dated analysis. The record can't be edited, only replaced by a newer one
- STEP 6: Select Send to hiring kit. Then review and publish the drafts in the hiring kit
- THE SCIENCE: Rate with people who do or manage the job. Not from the title alone. General information, not legal advice
- Summary. Tick and rate the real tasks. Choose the day-one KSAs. Save, then send to the hiring kit
- Full guide: blisspointanalytics.com/help/job-analysis
A job analysis writes down what the job involves before you decide how to hire for it. Interview questions and requirements that trace back to rated tasks are easier to explain and defend.
What you need first
- A role in Job architecture (a job family and a level first). Without one, the Role list on the Hiring tools page is empty.
- Ideally, the role linked to an O*NET occupation, so the wizard starts with that occupation's tasks and skills. You can also start from Search O*NET without a role, but then the result can't be sent to a hiring kit.
- You need to be an editor, admin or owner to save one. Anyone in the company can read saved analyses.
Steps
- Open Hiring tools. Under 1. Job analysis, in Start a job analysis, choose the Role and select Analyze this role.
- 1. Choose the tasks: check the tasks this job really involves (O*NET's core tasks start checked), add any missing ones with Add task, and select Next: rate the tasks.
- 2. Rate importance and frequency: give each task an Importance (1 Not important to 5 Essential) and a Frequency (1 Yearly or less to 5 Daily). Select Next: knowledge, skills and abilities.
- 3. Knowledge, skills and abilities: keep the ones needed on day one. In Notes, write who rated and how.
- Select Save dated analysis. The record page shows the job description draft, interview questions and pay reference.
- Select Send to hiring kit to put the drafts on the role's hiring kit, then open the hiring kit to review and publish them.
The science in plain words
- Criticality is importance times frequency, from 1 to 25. A task scoring 12 or more is marked critical, and critical tasks become the job description's responsibilities.
- Rate with people who do or manage the job, not from the title alone. Two or three raters agreeing is better than one.
- The Uniform Guidelines on Employee Selection Procedures (29 CFR 1607.14) expect a selection procedure to rest on a review of the job. This tool helps you keep that record. It is general information, not legal advice.
Common questions
- Can I edit a saved analysis? No. Records are dated and can only be replaced by a newer analysis, so you can show later what a decision was based on.
- The role says "no occupation linked". Link it in Job architecture under Occupation, or add the tasks yourself.
- No pay reference? Set the role's pay range in Job architecture, or link it to an O*NET occupation.