Job Analysis, Competencies and Talent SegmentationIntroduction and contextStrategic talent acquisition begins before a vacancy is advertised. It begins with a disciplined answer to a deceptively difficult question: what work must be performed, under what conditions, and what evidence indicates that a person can perform it successfully? Job analysis, competency design and talent segmentation provide the architecture for answering that question. A job description describes work. A person specification describes the attributes required to perform that work. A competency framework explains the behaviours, capabilities and knowledge associated with effective performance across jobs or job families. Talent segmentation then differentiates roles and talent pools according to strategic value, scarcity, risk and development potential. Together, these tools convert business strategy into evidence-based hiring requirements. Poorly designed requirements create predictable problems: inflated qualifications, vague behavioural language, biased screening, unrealistic expectations and weak selection validity. Conversely, a skills-based and strategically segmented approach can widen access to talent, improve internal mobility, support workforce planning and enable more defensible recruitment decisions. Learning objectivesBy the end of this chapter, the reader should be able to: - Explain the purpose, scope and methods of job analysis.
- Develop effective job descriptions and person specifications.
- Distinguish tasks, duties, responsibilities, competencies, skills and qualifications.
- Construct and use competency frameworks and skills-based job architectures.
- Identify critical roles using strategic, operational and risk-based criteria.
- Segment talent and roles for differentiated acquisition and development strategies.
- Apply job redesign principles when work, technology or organisational priorities change.
- Evaluate ethical, legal and governance risks in requirements definition.
1. From organisational strategy to hiring requirementsA hiring requirement should be traceable to organisational purpose. The logic can be represented as: Strategy → capability requirements → work and roles → competencies and skills → assessment evidence → acquisition decision For example, a bank pursuing digital fraud prevention may require capabilities in real-time analytics, threat detection, regulatory interpretation and cross-functional incident response. These capabilities must then be translated into roles, accountabilities, observable behaviours and assessment methods. Simply adding “excellent communication skills” or “five years’ experience” does not provide sufficient evidence of strategic fit. Three distinctions are especially important: - Work is the set of activities and outputs required by the organisation.
- A job is a relatively stable bundle of responsibilities performed by one person or position.
- A role is a broader contribution that may change across projects, teams or organisational boundaries.
Modern organisations increasingly recruit for roles and capabilities rather than narrowly bounded jobs. However, flexibility should not mean ambiguity. A role can be adaptive while still having clear outcomes, decision rights and evidence requirements. Job analysis and work analysisJob analysis is a systematic process for collecting and interpreting information about work, including tasks, outputs, responsibilities, context, relationships, tools and performance standards. Traditional job analysis often assumes that jobs are stable and individual. Work analysis is broader: it examines how work is distributed among people, teams, technology, contractors and automated systems. A sound analysis asks: - What outcomes does the work produce?
- Which activities are essential, and which are incidental?
- What decisions does the role make?
- What knowledge, skills and other characteristics support performance?
- What environmental, physical, emotional or regulatory demands exist?
- Which activities are performed by humans, technology or both?
- How might the work change over the planning horizon?
2. Methods of job analysisNo single method is universally superior. The method should match the complexity, stability and risk of the work. | Method | Main evidence | Strengths | Limitations |
|---|
| Structured interviews | Incumbent and supervisor accounts | Rich contextual information | Subject to recall and political bias | | Observation | Actual activities and conditions | Useful for visible, routine work | Misses infrequent cognitive work | | Work diaries | Time-sequenced activities | Captures variability and interruptions | Burdensome and sometimes incomplete | | Questionnaires | Standardised task or competency ratings | Efficient across many roles | May oversimplify complex work | | Critical incident technique | Examples of highly effective or ineffective behaviour | Produces performance-linked evidence | Requires skilled elicitation | | Document analysis | Procedures, outputs, metrics and regulations | Efficient starting point | Documents may be outdated | | Workshops | Collective interpretation by experts | Builds validity and ownership | Dominant participants may distort conclusions | | Data analysis | Performance, workflow and labour-market data | Supports evidence-based decisions | Correlation does not establish causation |
A robust process normally triangulates at least three sources. For example, analyst interviews may be combined with workflow data and critical incidents. The analyst should distinguish facts from opinions and current requirements from aspirations. Critical incident techniqueThe critical incident technique asks knowledgeable participants to describe specific episodes in which performance was notably effective or ineffective. Each incident should identify the situation, the action taken and the result. General statements such as “the employee was proactive” are weaker than evidence such as “when a key supplier failed, the employee established an alternative supply route within four hours while preserving compliance controls.” Critical incidents are particularly useful for identifying behavioural competencies and designing structured interview questions. They should not, however, be treated as a complete description of the job, since unusual incidents may not represent normal performance. Analysing task importanceTasks can be rated on dimensions such as frequency, difficulty, consequence of error and strategic importance. A low-frequency task may still be essential if failure creates serious safety, legal or reputational risk. Therefore, frequency alone should never determine whether a requirement is included. A simple prioritisation matrix can classify tasks as: - Core: essential to the role’s principal outcomes.
- Critical: failure creates substantial safety, legal, financial or strategic consequences.
- Supporting: contributes to effectiveness but is not independently decisive.
- Incidental: useful or occasional, but not suitable as a primary selection criterion.
3. Job descriptions and person specificationsThe job descriptionA job description should communicate the purpose and boundaries of work without pretending that every future activity can be predicted. Its typical components are: - Job title and job family.
- Organisational location and reporting relationships.
- Job purpose or contribution statement.
- Key outcomes and accountabilities.
- Principal duties or activity areas.
- Decision authority and escalation requirements.
- Key internal and external relationships.
- Work context, location and conditions.
- Measures or indicators of effective performance.
- Development, progression or role-breadth information.
The strongest descriptions are outcome-oriented. “Prepare monthly management reports, identify material variances and recommend corrective action” is more informative than “perform reporting duties.” Outcome statements also support selection, onboarding and performance management. A job description should state genuine flexibility, such as “other responsibilities reasonably consistent with the role’s purpose,” but this clause should not be used to conceal unlimited or unrelated demands. The person specificationThe person specification translates job requirements into attributes sought in a candidate. It commonly covers: - Essential and desirable knowledge.
- Technical and transferable skills.
- Behavioural competencies.
- Relevant experience or demonstrated capability.
- Qualifications, licences or certifications.
- Physical, scheduling or environmental requirements where genuinely necessary.
- Values and motivation relevant to the work.
A crucial distinction is between minimum entry requirements and indicators of likely performance. A degree may be legally required for a regulated profession, but in another role it may merely be a historical proxy for analytical ability. Where possible, organisations should assess the underlying skill directly. Essential versus desirable criteriaAn essential criterion is one without which the person cannot safely, legally or effectively perform the role after reasonable onboarding. A desirable criterion may improve performance but is not indispensable. Inflating desirable criteria into essential requirements reduces applicant diversity and may exclude capable candidates with non-traditional backgrounds. Each criterion should pass three tests: - Job relevance: Is it demonstrably related to work outcomes?
- Evidence: Can it be assessed consistently?
- Proportionality: Is it necessary at the stated level?
4. Competencies, skills and qualificationsTerminology varies across organisations, so definitions must be explicit. - Knowledge is information and understanding relevant to work.
- Skill is the learned ability to perform an activity to a defined standard.
- Ability is a more general capacity to perform a class of activities.
- Competency is an integrated pattern of knowledge, skill, behaviour and judgement associated with effective performance in a context.
- Qualification is a credential awarded by an authorised body; it is evidence of learning, not necessarily proof of current performance.
- Capability is the potential to apply and develop competence across changing circumstances.
Competencies should be expressed in observable terms. “Strategic thinker” is ambiguous unless translated into behaviours such as “identifies long-term implications, evaluates competing scenarios and connects recommendations to organisational priorities.” Types of competencyA useful architecture distinguishes: - Core competencies: expected across the organisation, such as ethical conduct or collaborative working.
- Functional competencies: associated with a profession or job family, such as financial modelling or employee-relations practice.
- Leadership competencies: involving direction, decision-making, influence and stewardship.
- Technical competencies: involving tools, systems, methods or specialist knowledge.
- Role-specific competencies: distinctive requirements of a particular position.
Competency models should avoid becoming long catalogues. Usually, a small number of high-value competencies with behavioural indicators is more useful than dozens of loosely defined attributes. Proficiency levelsProficiency levels describe increasing complexity, autonomy and impact. A four-level scale might be: | Level | Typical description |
|---|
| 1. Foundational | Performs defined activities with guidance and follows established procedures | | 2. Proficient | Performs independently in familiar situations and solves routine problems | | 3. Advanced | Handles complex or novel situations, coaches others and integrates knowledge | | 4. Expert/strategic | Shapes standards, makes high-consequence judgements and influences organisational direction |
Levels should be anchored by evidence, not years of experience alone. A person may reach advanced proficiency quickly in one context and remain at a foundational level after many years in another. 5. Skills-based job architectureA job architecture organises work into families, levels, disciplines and progression paths. A skills-based architecture places demonstrable capabilities at its centre rather than treating the job title or degree as the primary unit of value. A practical architecture may contain: - Job families: broad domains such as human resources, technology or operations.
- Sub-families: narrower disciplines such as talent acquisition or compensation.
- Levels: differentiated by scope, complexity, autonomy, influence and accountability.
- Skills taxonomy: common names and definitions for technical, professional and transferable skills.
- Proficiency indicators: evidence of application at each level.
- Career pathways: possible lateral, vertical and project-based movement.
Skills-based architecture supports internal mobility because employees can be matched to opportunities through adjacent capabilities, not only previous titles. It also supports more precise sourcing and assessment. However, skills should not be considered in isolation. Effective performance may depend on context, judgement, relationships, motivation, access to resources and organisational design. A skills taxonomy is therefore a decision aid, not a complete theory of human performance. 6. Competency framework developmentA defensible framework can be developed through the following sequence: Step 1: Clarify purposeDecide whether the framework will support recruitment, development, succession, pay, workforce planning or several purposes. A framework designed for development may need broader capability descriptions than one used for high-stakes selection. Step 2: Identify strategic capabilitiesReview strategy, operating model, customer expectations, regulation, technology and workforce risks. Identify capabilities that will differentiate performance over the relevant planning period. Step 3: Analyse effective performanceUse interviews, observation, critical incidents, performance evidence and expert workshops. Include high performers, typical performers and relevant stakeholders. Relying only on high performers can reproduce idiosyncratic habits that are not actually necessary. Step 4: Define competencies and behavioural indicatorsEach competency should have a concise definition and observable indicators. Indicators should describe actions and decisions rather than personality labels. Step 5: ValidateCheck whether competencies distinguish effective from ineffective performance, are understandable to users and are appropriate across demographic and cultural groups. Subject-matter experts can rate relevance, but ratings should be supported by empirical performance evidence where available. Step 6: Map to assessment and developmentFor every competency, specify suitable evidence: work samples, structured interviews, simulations, portfolios, technical tests or reference evidence. A competency without a feasible assessment method is not necessarily useless, but it is not yet operationalised. Step 7: Review regularlyTechnology, regulation and work design change. Frameworks should have an owner, review cycle, version control and a process for retiring obsolete requirements. 7. Talent segmentation and critical-role identificationTalent segmentation is the deliberate grouping of roles, skills or talent pools so that acquisition and development resources can be differentiated. It is not a claim that people have unequal human worth. It is a resource-allocation approach based on organisational requirements. Segmenting rolesA role can be assessed using several dimensions: - Strategic contribution.
- Consequence of vacancy or failure.
- Scarcity of required capability.
- Time required to build competence.
- Replaceability and availability of alternatives.
- Regulatory, safety or reputational exposure.
- Degree to which technology may substitute for or augment the work.
One useful conceptual model is a two-axis matrix using business impact and talent scarcity. Roles with high impact and high scarcity generally justify proactive pipelines, succession planning and differentiated attraction. Roles with lower scarcity may be supported through efficient, standardised recruitment. The matrix is a heuristic, not a mechanical formula. Identifying critical rolesA critical role is one for which sustained vacancy, poor performance or loss of capability would materially threaten strategic or operational outcomes. Criticality is a property of the role and its organisational context, not simply of seniority. A frontline safety specialist or cybersecurity engineer may be more critical than a senior title with readily available substitutes. A structured process involves: - Identify strategic and operational outcomes.
- Map roles that materially enable those outcomes.
- Estimate vacancy impact, time to replace and time to proficiency.
- Assess external scarcity and internal bench strength.
- Consider legal, safety, customer and reputational consequences.
- Validate ratings with business leaders and workforce data.
- Review the classification as strategy and technology change.
Segmenting talent poolsTalent pools may be segmented by current proficiency, potential, career interest, mobility, location, work authorisation, availability or adjacent skills. Segmentation must be used carefully. Labels such as “high potential” can become self-fulfilling and may reproduce managerial bias. More defensible practice combines multiple evidence sources, makes criteria transparent, offers development access broadly and permits review or challenge. Segmentation should guide investment, not permanently restrict opportunity. 8. Job redesign and the changing nature of workJob redesign is the intentional modification of tasks, relationships, technology, autonomy or work conditions. It may be triggered by automation, restructuring, employee experience concerns, safety requirements, customer changes or skills shortages. Important redesign approaches include: - Job enlargement: adding tasks of similar complexity.
- Job enrichment: increasing autonomy, responsibility and decision authority.
- Job rotation: moving employees among related activities to broaden capability.
- Work simplification: standardising or decomposing tasks for efficiency.
- Socio-technical redesign: jointly optimising technology, people and work processes.
- Team-based design: allocating outcomes to teams rather than isolated individuals.
Redesign should begin with the work outcome, not with a predetermined technology solution. Analyse which tasks require human judgement, empathy, accountability or physical presence and which can be automated or augmented. Then revise role purpose, competencies, training and assessment. For example, introducing an AI-supported recruitment system may reduce manual CV searching but increase the need for data literacy, validation of model outputs, candidate communication and bias monitoring. The role has not disappeared; its task mix and risk profile have changed. 9. Evidence-based hiring requirementsRequirements should be connected to valid assessment evidence. A simple evidence map can be used: | Requirement | Observable evidence | Suitable assessment |
|---|
| Data interpretation | Explains patterns and limitations in a dataset | Work sample or case exercise | | Stakeholder influence | Gains agreement while handling disagreement | Structured behavioural interview | | Technical configuration | Produces a functioning, compliant solution | Job-related technical test | | Ethical judgement | Identifies risks and justifies a defensible action | Situational judgement exercise | | Written communication | Produces clear, accurate decision material | Writing exercise |
Selection validity improves when the assessment method resembles the work and scoring rules are established in advance. Structured interviews should ask candidates the same core questions, use anchored rating scales and record evidence separately from impressions. A qualification, job title or employment history may be useful evidence, but it should not automatically substitute for direct demonstration. Skills-based hiring can recognise equivalent learning gained through employment, projects, community activity or professional practice. 10. Ethical, legal and governance considerationsJob analysis and talent segmentation have direct consequences for access to employment. Important safeguards include: Fairness and non-discriminationCriteria must be job-related and applied consistently. Requirements that appear neutral may create adverse impact if they disproportionately exclude protected groups without sufficient justification. Organisations should review applicant progression by stage and investigate unexplained disparities, while recognising that statistical disparity alone does not prove unlawful discrimination. Accessibility and reasonable adjustmentPhysical, scheduling and communication requirements should be stated only when genuinely necessary. Selection processes should provide reasonable adjustments and should distinguish essential job demands from conventional ways of performing them. Privacy and data governanceJob analysis may involve employee interviews, performance records, workflow data and algorithmic profiles. Data collection should have a legitimate purpose, appropriate access controls, retention limits and clear communication. Sensitive personal data should not be collected merely because it might be interesting. Algorithmic decision-makingAI tools may assist with skills extraction, job matching or labour-market analysis, but historical data can encode past exclusion. Organisations should test for disparate outcomes, document model purpose and limitations, maintain human accountability and provide routes for correction or review. An algorithm should not be treated as objective merely because it is statistical. Credential inflation and social justiceUnnecessary degree requirements can restrict opportunity and reproduce socioeconomic inequality. Removing a credential is not enough; employers must replace it with valid evidence of capability and provide realistic onboarding where skills can be developed. 11. Contemporary developmentsSeveral developments are reshaping this field: - Skills-based organisations increasingly organise work around capabilities and projects rather than rigid positions.
- Internal talent marketplaces use skills profiles to match employees with projects, learning and vacancies.
- Generative AI can draft job descriptions and identify skill clusters, but human review is essential to prevent vague, biased or fabricated requirements.
- Workforce ecosystems combine employees, contractors, partners and technology, requiring analysis beyond conventional headcount.
- Portable and demonstrable skills such as portfolios, certifications and work samples may supplement traditional credentials.
- Continuous redesign is becoming more important as automation changes task composition faster than formal job architectures are revised.
The strategic challenge is to achieve flexibility without sacrificing clarity, fairness or accountability. 12. Illustrative case: redesigning talent acquisition in a health-technology firmBackgroundMedData Services, a fictional health-technology firm, provides clinical data platforms to hospitals. It planned to expand into predictive analytics. Its existing job descriptions were copied from older software roles and required a computer science degree, five years of experience and “excellent communication” for nearly every technical vacancy. ProblemRecruiters struggled to distinguish data engineering, clinical analytics and implementation work. Vacancies remained open for long periods, while hiring managers rejected candidates with strong portfolios but non-traditional qualifications. The organisation also underestimated the importance of privacy, clinical interpretation and stakeholder adoption. AnalysisA cross-functional team analysed strategy documents, customer complaints, workflow records, interviews with incumbents and twenty critical incidents. It found that successful performance depended on five capability areas: - Data engineering and quality control.
- Statistical and analytical reasoning.
- Health-data governance and privacy.
- Translation of technical results for clinical users.
- Collaborative problem-solving during implementation.
The team separated essential requirements from trainable requirements. Knowledge of health-data privacy was essential because errors could create legal and patient-safety consequences. Familiarity with the firm’s proprietary platform was trainable and therefore not made an entry requirement. Approach and solutionThe firm created three job families: data platform, applied analytics and client implementation. Each family had four proficiency levels, with indicators based on scope, autonomy and consequence of decisions. The new person specifications accepted several forms of evidence, including degrees, professional certifications, relevant portfolios and demonstrated project outcomes. The recruitment process used a job-related data-quality exercise, a structured interview on stakeholder communication and a scenario concerning privacy escalation. An AI tool was used only to cluster incoming applications by declared skills; recruiters audited results and candidates could request human review. OutcomeWithin two recruitment cycles, the firm reported a broader qualified applicant pool, clearer hiring-manager discussions and better alignment between assessments and actual work. The organisation did not treat these early outcomes as proof of causal success; it established a twelve-month evaluation using time-to-fill, quality-of-hire indicators, candidate experience, adverse-impact monitoring and retention. Learning pointsThe case illustrates that skills-based hiring is not simply the removal of degree requirements. It requires work analysis, explicit proficiency standards, valid evidence, redesigned assessment and governance. It also shows that critical-role identification should include privacy and implementation risk, not only technical scarcity. Challenges and limitationsJob analysis is not free from judgement. Incumbents may protect status, managers may exaggerate requirements and analysts may mistake current practice for necessary practice. Competency frameworks can become bureaucratic, culturally narrow or detached from performance. Talent segmentation can create privileged groups and reduce attention to roles classified as less critical. Skills taxonomies may become obsolete quickly, while AI systems can amplify historical bias. These limitations do not invalidate the tools. They require disciplined governance: transparent definitions, multiple evidence sources, stakeholder challenge, periodic review, outcome monitoring and an explicit distinction between evidence and assumption. Best-practice principles- Start with organisational outcomes, not inherited job titles.
- Analyse work using multiple evidence sources.
- Write outcome-based descriptions and observable requirements.
- Separate essential criteria from desirable or trainable attributes.
- Use skills and demonstrated capability alongside credentials.
- Anchor proficiency levels in complexity, autonomy and impact.
- Link every major requirement to an appropriate assessment method.
- Identify critical roles using impact, scarcity, risk and time-to-proficiency.
- Use segmentation to allocate support, not to label people permanently.
- Review requirements as technology, regulation and strategy change.
- Audit fairness, accessibility, privacy and algorithmic decision-making.
- Evaluate hiring outcomes rather than assuming that a sophisticated framework is effective.
Chapter SummaryJob analysis establishes what work involves, why it matters and what conditions shape performance. Job descriptions communicate purpose, outcomes, accountabilities and context, while person specifications identify the knowledge, skills, competencies and other attributes required. Effective requirements are job-related, observable, proportionate and assessable. Competency frameworks integrate knowledge, skills, behaviours and judgement into proficiency levels. Skills-based job architecture organises job families, levels, skills and career pathways around demonstrated capability rather than titles or credentials alone. Talent segmentation differentiates roles and talent pools according to strategic impact, scarcity, risk, replaceability and development needs. Critical roles are defined by consequences and capability risk, not simply seniority. Job redesign is necessary when technology, strategy or work conditions change. AI may support analysis and matching, but it does not remove the need for human validation, privacy protection, fairness monitoring and accountability. The central principle is traceability: every hiring requirement should be connected to real work, meaningful evidence and a defensible organisational purpose. Key TermsJob analysis: Systematic study of work, including tasks, outputs, responsibilities and context. Work analysis: Examination of how work is distributed among people, teams, technology and other contributors. Job description: Document describing a role’s purpose, outcomes, duties, relationships and context. Person specification: Statement of the knowledge, skills, competencies, experience and other attributes required for a role. Competency: Integrated pattern of knowledge, skill, behaviour and judgement associated with effective performance. Skill: Learned ability to perform an activity to a defined standard. Capability: Potential to apply and develop competence across changing situations. Qualification: Credential awarded by an authorised body as evidence of learning or professional standing. Critical incident technique: Method using specific examples of highly effective or ineffective behaviour. Competency framework: Structured set of competencies and proficiency indicators used across roles or job families. Proficiency level: Defined degree of autonomy, complexity and impact in applying a skill or competency. Job architecture: Organisational structure of job families, disciplines, levels and progression paths. Skills-based hiring: Hiring that evaluates demonstrable capabilities rather than relying primarily on titles or credentials. Talent segmentation: Grouping roles or talent pools to differentiate acquisition, development or retention strategies. Critical role: Role whose vacancy, failure or capability loss would materially threaten organisational outcomes. Job redesign: Intentional modification of tasks, autonomy, relationships, technology or work conditions. Adverse impact: Disproportionate negative effect of a selection practice on a protected or relevant group. Structured interview: Interview using standardised questions, scoring criteria and evidence-based ratings. Job-relatedness: Degree to which a requirement is demonstrably connected to successful work performance. Review QuestionsShort Answer Questions- What is the difference between a job description and a person specification?
- Define competency and distinguish it from skill.
- Why should essential and desirable criteria be separated?
- What is meant by a critical role?
- Identify two risks associated with AI-supported talent segmentation.
Long Answer Questions- Explain the process of conducting a rigorous job analysis and evaluate the strengths and limitations of at least four methods.
- Discuss how a competency framework can be designed, validated and linked to recruitment assessment.
- Explain the principles of skills-based job architecture and its implications for internal mobility.
- Critically evaluate the use of business impact and talent scarcity as dimensions of talent segmentation.
- Discuss how job redesign should respond to automation while preserving fairness, accountability and meaningful work.
Analytical / Application Questions- A logistics company requires a university degree and five years of experience for all supervisory roles. Design a process to determine which requirements are genuinely essential and propose alternative evidence where appropriate.
- A cybersecurity analyst is difficult to recruit, but the organisation has strong internal employees with adjacent data and risk skills. Apply critical-role analysis and propose a differentiated acquisition and development strategy.
- An organisation uses an AI tool to rank applicants according to inferred skills from CVs. Develop a governance plan covering validity, adverse impact, privacy, human review and candidate challenge.
Multiple Choice Questions with AnswersQuestion 1Which statement best distinguishes a job description from a person specification? A. A job description identifies required candidate attributes, while a person specification lists organisational goals. B. A job description describes work and accountabilities, while a person specification describes attributes required for performance. C. A job description is used only after hiring, while a person specification is used only for payroll. D. A job description focuses on personality, while a person specification focuses exclusively on salary. Correct Answer: B. A job description describes work and accountabilities, while a person specification describes attributes required for performance. Question 2Which method is especially useful for identifying observable behaviours associated with highly effective or ineffective performance? A. Critical incident technique B. Payroll analysis C. Organisational charting D. Credential verification Correct Answer: A. Critical incident technique Question 3Which criterion is most likely to be an appropriate essential requirement? A. A preferred university attended by previous employees B. A familiar software package that can be learned during onboarding C. A legally required professional licence for regulated practice D. A manager’s preference for applicants with a particular accent Correct Answer: C. A legally required professional licence for regulated practice Question 4In a skills-based job architecture, proficiency levels should primarily reflect: A. Years since graduation only B. Job title length and salary range only C. Complexity, autonomy and impact of application D. The number of candidates in the external labour market Correct Answer: C. Complexity, autonomy and impact of application Question 5A role is most likely to be classified as critical when it: A. Has the most senior-sounding title B. Is popular among current employees C. Has high consequences of vacancy or failure and limited substitutes D. Requires the longest job description Correct Answer: C. Has high consequences of vacancy or failure and limited substitutes Question 6Which is the best example of an outcome-oriented job-description statement? A. Demonstrates professionalism B. Works hard and remains positive C. Prepares monthly variance reports and recommends corrective action D. Has excellent communication skills Correct Answer: C. Prepares monthly variance reports and recommends corrective action Question 7What is a central ethical risk of using historical recruitment data in an AI selection tool? A. The tool may reproduce patterns of past exclusion or bias B. The tool will always eliminate the need for human judgement C. Historical data cannot contain any information about work D. The tool automatically makes all decisions legally valid Correct Answer: A. The tool may reproduce patterns of past exclusion or bias Question 8Which action best supports valid skills-based hiring? A. Accepting any self-reported skill without verification B. Linking each important requirement to job-related assessment evidence C. Replacing every qualification with an unstructured interview D. Using personality labels instead of observable behaviours Correct Answer: B. Linking each important requirement to job-related assessment evidence Question 9Job enrichment differs from job enlargement because job enrichment primarily adds: A. Tasks of similar complexity B. Autonomy, responsibility or decision authority C. More applicants to the recruitment funnel D. Additional employment benefits Correct Answer: B. Autonomy, responsibility or decision authority Question 10Why should talent segmentation not be treated as a permanent label of employee worth? A. Because segmentation is intended to guide resource allocation and may reflect changing evidence and context B. Because all roles have identical strategic and capability requirements C. Because critical roles never require differentiated investment D. Because employee development should be unrelated to organisational strategy Correct Answer: A. Because segmentation is intended to guide resource allocation and may reflect changing evidence and context
|