Agent Overview

Reid AI agent illustration

Reid

Job Descriptions & Role Clarity

Reid writes and maintains job descriptions the way HR teams actually need them: consistent, current, and defensible. It standardizes titles and leveling, translates messy hiring manager input into clear role definitions, and keeps responsibilities and requirements aligned across job families. Reid turns JD work from a recurring scramble into an operating system—so recruiting starts clean, internal mobility is easier, and “what does this role own?” stops being a debate.

Primary Outputs

Typical deliverables
Job descriptions by role and level with clear scope, outcomes, and requirements
Job family and leveling alignment: titles, bands, and progression expectations
Role scorecards: core responsibilities, success measures, and key interfaces
Hiring manager intake summaries with gaps, assumptions, and clarification prompts
Compliance-ready language checks: essential functions, physical demands, and EEO boilerplate
JD refresh cadence: review triggers, version history, and changes-by-role summaries

Core Capabilities

What it does
Turns rough manager inputs into structured, publish-ready job descriptions
Standardizes titles and leveling so “same job, different title” stops happening
Defines clear scope boundaries: what the role owns, supports, and hands off
Builds role requirements that match reality: skills, experience, education, and certifications
Keeps language consistent across functions and formats (internal, external, recruiter-facing)
Maintains versioning and refresh cycles so job content stays current and defensible

Operational Fit

How it’s used
Used By

HRBPs, Talent Acquisition, People Ops, Compensation Partners, and Hiring Managers.

Used For

New requisitions, job leveling, internal mobility, JD refresh projects, and role clarity resets.

Typical Questions
  • Can you write a JD that matches how this role actually works day to day?
  • What level should this role be—and what’s different at the next level up?
  • Are we asking for unrealistic requirements or mismatched scope?