Sign in

Job Requisition Generation

Compress the 3-5 day requisition creation cycle into a single guided conversation, generating comp-benchmarked, approval-routed, audit-ready job requisitions in under 30 minutes.

  • AI-assisted
  • Talent Acquisition
  • Hiring Manager
See it in action
Reduction in elapsed requisition creation time
85-90%
Reduction in coordinator labor cost per req
~86%
Reduction in rework cycles from comp/leveling errors
~75%

One seat opens. Req is approved.

See the requisition agent take a backfill from a resignation to an approved req package.

Req TS-1042

Backfill · Software Engineer II, Seattle WA

  • AI
  • 85-90% less elapsed time
  1. Intake
  2. Organize
  3. Evaluate
  4. Deliver

Stage 1 · Intake

Backfill started

Manager clicked Start New Requisition after a resignation

New case

Intake open
Requester
Hiring manager · Platform Engineering
Role
Software Engineer II · Backfill confirmed
Location
Seattle WA · Hybrid
Request
Backfill req after a resignation
Case packet · 3 sourcesComplete

Incoming

  • Action menuStart New Requisition clickedReceived
  • Intake form5 phases completed in chatReceived
  • Knowledge baseJD library queried for a matchReceived

Stage 2 · Organize

Template matched

Existing Software Engineer II JD found and adapted

Pulled together

Intake complete
  • Role identitySoftware Engineer II, Platform Engineering
  • Org contextTeam size 8, reports to Engineering Manager
  • JD template matchedExisting Software Engineer II JD, manager chose to adapt

Matched record

Template
Software Engineer II JD
Source
Knowledge base
Choice
Adapt template
Update
New scope and must-have skills added

Stage 3 · Evaluate

Level and comp set

L4 band assigned, Seattle comp pulled from two sources

Checks applied

Comp benchmarked
  • Leveling bandL4 assigned for Software Engineer IILeveling framework
  • Seattle market compCurrent data from Levels.fyi and LinkedIn SalaryWebSearch
  • Headcount typeBackfill confirmed, not new headcountIntake form
Deciding finding

Standard routing applies

This is a backfill, not new headcount, so the req follows standard approval routing.

Approval routing

Engineering Director
Required
Head of Talent
Required
Routed via
RequestApproval

Stage 4 · Deliver

Req package delivered

Approved PDF and DOCX archived, recruiter draft created

Approved

Approved req, ready for the ATS

Both approvers signed off via RequestApproval, so the PDF and DOCX were generated with a current Seattle comp range.

Formats
PDF + DOCX
Archive
Google Drive
Recruiter
Gmail draft

Comp sources

Levels.fyi

And LinkedIn Salary

Human step

Engineering Director

And Head of Talent approve

Audit trail

  1. Intake completed5 phases10:02
  2. JD template adaptedL4 band assigned10:08
  3. Approval receivedEngineering Director, Head of Talent10:20
  4. PDF and DOCX archivedGoogle Drive, Gmail draft created10:24

Under 30 minutes, one conversation

One requisition, end to end. Illustrative case, sample data.

Use cases.What starts it, what it does, what you get.

  1. Use case 1

    Backfill Requisition for a Mid-Level Engineer

    Starts when

    A software engineer on the team resigned and the hiring manager opens the agent to start a backfill requisition.

    1. Hiring manager opens the chat window; the agent displays the action menu, the manager clicks 'Start New Requisition'.
    2. The agent walks through 5 intake phases: (1) Role Identity, title 'Software Engineer II', department 'Platform Engineering'; (2) Org Context, team size 8, reports to Engineering Manager; (3) Location, hybrid, Seattle WA; (4) Headcount Type, backfill confirmed; (5) Scope, key responsibilities and must-have skills.
    3. The agent queries the knowledge base and finds an existing Software Engineer II JD. It surfaces the match and asks: 'Adapt this template or generate from scratch?' The manager chooses to adapt.
    4. The agent updates the JD with the new scope details, assigns the appropriate leveling band (L4), and runs WebSearch against Levels.fyi and LinkedIn Salary to pull current Seattle market comp data.
    5. Because this is a backfill (not new headcount), standard approval routing applies, the agent routes to the Engineering Director and Head of Talent via RequestApproval.
    6. After HITL approval is received, the agent generates both PDF and DOCX versions and archives them to Google Drive, then creates a Gmail draft to notify the recruiter.

    The hiring manager receives a fully formatted, approved job requisition package (PDF + DOCX) with a current-market comp range and a clear approval audit trail, ready to post in the ATS, within a single conversation session.

  2. Use case 2

    New Headcount Director-Level Requisition with Executive Approval

    Starts when

    A business unit leader has received headcount approval in planning and asks the Head of Talent to open a net-new Director of Data Science requisition.

    1. Head of Talent opens the agent and clicks 'Start New Requisition' from the action menu.
    2. Intake phases capture: Director of Data Science, Analytics org, Director/L6 level, New York or Remote, new headcount (not a backfill), team will grow from 4 to 9 ICs.
    3. The agent checks the knowledge base, no existing Director of Data Science JD is found, and generates a new job description from scratch, incorporating org-level leveling guidelines.
    4. WebSearch pulls comp benchmarks from Radford and Glassdoor for Director-level Data Science roles; both sources are cited in the comp section.
    5. The agent identifies two escalation flags: (1) Director+ level triggers CHRO and CFO as required approvers; (2) new headcount triggers mandatory Finance BP approval.
    6. RequestApproval is invoked, the agent pauses and waits for HITL sign-off from CHRO, CFO, and Finance BP before generating output documents.
    7. Once all approvals are confirmed, the agent generates PDF and DOCX, saves to Google Drive, and queues a Slack message to notify the assigned recruiter and business unit leader.

    A fully compliant Director-level requisition with documented executive approvals, dual-format deliverables, and an archived record in Google Drive, with zero manual chasing of approvers by the TA team.

Works with your systems

The systems this agent reads from and writes to, connected inside your environment.

  • LinkedIn Search (salary data & role benchmarks)
  • Technical Writing Skill (JD quality)
  • ATS Direct Push (Greenhouse / iCIMS / Lever MCP)

See it in action.A conversation that moves the work forward.

Sample scenarios built in ACTAVA. Actions and outputs are illustrative.

Agents › Job Requisition Generation

Illustrative example

I need to open a new role on my team.

Job Requisition Generation

I start with a short action menu so you can begin the requisition right away. The intake then runs one focused phase at a time.

Next step

Click Start New Requisition to begin the first intake phase.

Example complete

1 of 4

Where this agent works.The industries it serves, and customers doing similar work.

Put this agent to work on your cases.

We'll show it running against your own workflow, connected to your systems, with your team approving what matters.