Hiring overview
Understand how Hiring brings job publishing, applicant review, and role-scoped recruiting work into one organization surface.
Hiring is Infra One’s organization workspace for creating jobs, publishing them to a public job board, and moving applicants through a shared recruiting process. Applicants use the separate Talent portal to apply and follow their own applications.
Three connected surfaces
| Surface | Who uses it | What it does |
|---|---|---|
| Hiring | Organization members, job team members, and organization admins | Creates and manages jobs, reviews applicants, and manages the hiring pipeline. |
| Public job board | Anyone | Lists published jobs and opens their public details without requiring sign-in. |
| Talent portal | Applicants | Verifies an applicant by email, collects an application, and shows that applicant’s submitted applications. |
Opening hiring.infra.one routes directly to your only accessible organization. With two or more, Hiring first asks you to Select an organization; with none, it returns to the Venture dashboard. Availability also depends on Hiring being enabled for your user account.
Jobs and applications
A direct job starts as Draft. Publishing makes it discoverable on the public job board and allows applicants to begin an application. Closing removes it from discovery and blocks newly opened or refreshed application wizards while preserving its recruiting history. Direct jobs cannot be reopened locally. The Jobs page initially hides closed jobs with a removable Status ≠ Closed filter. Closing is not an atomic cutoff for a wizard that was already open.
Hiring keeps two kinds of applicant decisions separate:
- the shared pipeline status, such as Screening, Interview, or Offer sent;
- an individual reviewer’s Advance, Maybe, or Reject decision in rapid review.
This lets a reviewer record a recommendation without silently changing the team’s shared pipeline.
For an application imported from an applicant tracking system, Stage continues to show the current ATS stage. Hiring’s shared Status follows that stage until a recruiter first changes the status or moves the card in Kanban. That first local move permanently transfers ownership of Status to Hiring: later syncs still update Stage, but no longer overwrite Status, and Hiring does not push the local move back to the ATS.
Personal profile and organization settings
My profile is the signed-in platform user’s Hiring profile. It is separate from the applicant account on Talent portal and does not require selecting an organization. Its guided sections cover personal information, location and work authorization, target role, experience, skills, career preferences, and sharing details.
Within an organization, authorized admins may also see a Settings group for Team, Email templates, Scorecard templates, Notifications, and Connector settings. Each entry appears only when the user has its matching management capability.
Direct and connected jobs
Jobs created in Hiring are managed in Hiring. A job synchronized from a connected applicant tracking system stays owned by that system. Edit still renders and can open the edit form, but saving cannot update the synchronized job; publishing and closing are unavailable or rejected. Make all such changes in the connected system.
Access follows the work
Personal-profile access, organization access, and job-team access answer different questions. An organization member can work with jobs, while organization admins manage organization-wide applications and Hiring settings. Assigned job reviewers, hiring managers, and job admins receive progressively broader access to a specific job.
For the complete matrix, see Hiring permissions and states.