Manage hiring work

Use Hiring to keep a job’s public state, shared applicant pipeline, reviewer decisions, and AI-assisted questions in the right scope.

Before you begin

You need access to the intended Hiring organization. The controls you see depend on both your organization role and your assignment on the selected job. Use synthetic or otherwise approved candidate data when demonstrating these workflows outside the recruiting team.

The signed-in user’s My profile is separate from organization recruiting and from the applicant-only Talent portal account.

Complete your personal profile

1. Open https://hiring.infra.one/personal-profile.
2. Under My profile, complete Personal Info, Location, Role, and Experience.
3. After choosing a target role, complete Skills when the selected role has a skills section.
4. Complete Career and Share.
5. If Hiring reports Cannot submit yet. Complete the remaining profile sections., return to the first incomplete section.
6. Finish every required section and confirm Completed the profile before reviewing the profile preview.

This profile belongs to your signed-in Infra One platform user. It is not the Talent portal applicant profile and does not submit a job application.

Current profile limits are 60 characters each for first and last name, 160 for contact email, and 100 characters for relocation destinations. You can add up to 10 work-history entries, 10 education entries, and 10 skills. In each work entry, company, title, and location accept 100 characters and the summary accepts 1,000; in each education entry, school and field of study accept 100 and a custom degree accepts 50. Engineering, design, science, and recruiting profiles require one to four specializations; engineering and design also require a portfolio URL. Describe yourself in a short phrase accepts 200 characters, while the two longer Share responses accept 2,000 characters each.

Manage a direct job

1. Open the organization’s Jobs page.
2. Use Search jobs… to find the job.
3. The job opens on Applications. Select Job details, then Edit, when its candidate-facing content needs to change.
4. For a draft, choose Publish when it is ready for applicants.
5. For a published job that should stop offering new application entry, choose Close.

A direct close is one-way: Hiring has no local reopen action. Closed jobs are initially hidden from Jobs by Status ≠ Closed; remove that filter to find one again.

A job synchronized from a connected applicant tracking system displays This job is synced from the connected ATS and is managed there. Edit can still open, but saving cannot update the synchronized job. Publish and close actions are unavailable or rejected. Make those changes in the connected system.

Closing prevents a new or refreshed Talent application wizard from opening. The current product does not re-check the job state when someone submits a wizard that was already open, so closing is not an atomic submission cutoff.

Organize the applicant pipeline

1. Open Applications, or choose Review applications from a job.
2. Use Search applications… to search candidate name or job title. The organization-wide page offers Job, Status, and Assessment filters; a single job’s page offers Status and Assessment.
3. Choose the table or Kanban layout.
4. In Kanban, move an applicant only when their shared pipeline status should change.
5. Open an applicant to inspect the application details and documents before taking action.

Hiring saves your selected layout for this browser view. Existing saved layouts also receive the Applied on column once, without replacing saved column widths; you can hide it again if it is not useful.

For an imported application, Stage keeps showing the current ATS stage. Hiring’s shared Status follows it until the first local status selection or Kanban move. That move permanently transfers Status ownership to Hiring: later syncs can update Stage but no longer replace Status, and the local change is not pushed back to the ATS.

Record a rapid-review decision

1. Open Applications and select Review. A single positive Job filter changes the link to that job’s stack; search, status, assessment, negative, and multi-job filters do not narrow rapid review.
2. Read the application presented in the review stack.
3. Optionally add a one-to-five rating and a private reviewer note.
4. Choose Advance, Maybe, or Reject.
5. Use Undo to reopen only the latest decision recorded in this visit, or Skip to leave the application undecided.

Rapid review snapshots submitted applications in the selected organization or job when the visit begins, newest application first. It does not reuse the applicant browser’s search, status, or assessment filters. Refreshing or reopening review rebuilds the snapshot and resets the visit’s undo history.

The rapid-review decision is your assessment. It does not by itself replace the applicant’s shared pipeline status. Stack cleared means the current visit has no card left to present; a card you skipped can still be undecided and return after refresh.

Ask about applicants

1. Open the applications for one job. Ask Ori is available only when AI features are enabled and you have review access for that job.
2. Select Ask Ori.
3. Use Ask about these applicants… to ask for a comparison or assessment grounded in that job’s applicant set.
4. Check important conclusions against the underlying applications before using them in a hiring decision.

Use job-scoped AI chat

1. From Jobs, switch to AI Chat.
2. Choose All jobs for an organization-wide hiring question, or select one job title to focus the conversation.
3. Start a new chat and ask the question.
4. Check the displayed job scope before relying on the answer. Changing the scope clears the selected open conversation so that a previous chat is not silently reused under a new scope.

Only jobs from the current organization can become the scope. A stale or foreign job reference is discarded rather than used for retrieval.

Manage organization Hiring settings

1. Open the Settings group in the Hiring sidebar. Only settings you can manage are shown.
2. Use Team to add organization members to the Hiring team pool, choose Standard or Limited access, and review Roles & permissions. A job admin, the job creator, or an organization admin can assign a pool member as reviewer, hiring manager, or job admin; a hiring manager cannot manage the team. Removing someone from Team removes their job assignments, and the job editor keeps at least one assigned job admin. Creator and organization-admin access does not depend on those assignment rows.
3. Treat Limited as display metadata, not an enforced view-only boundary. Limited members can still receive any per-job role. An organization member who creates a job is assigned job-admin access and, when no pool row exists, is added or re-added as Standard. Use organization membership controls when Hiring access must be prevented.
4. Use Email templates for Hiring’s applicant communications, Scorecard templates for reusable review structure, and Notifications for organization Hiring notification settings.
5. Use Connector settings only when the organization synchronizes an applicant tracking system. Keep the API token in an approved secret source. Test connection before Save is recommended, but the product does not require a successful test before saving.

Connected jobs remain managed by the connected applicant tracking system. Never copy a live connector token into documentation, support messages, or screenshots.

Success check

Your personal profile reaches its preview when you complete it. In organization work, the job has the intended public state, the applicant shows the intended shared pipeline status, your rapid-review decision is recorded separately, and the chat header reflects the job scope you selected.

Troubleshooting

• Edit, Review, or pipeline controls are missing: compare your organization and job-team roles with Hiring permissions and states.
• Skills is absent from the personal profile: choose a target role first. The section appears only for target roles that have a configured skills list.
• A profile step rejects the entry: check the profile caps above, including the 4-specialization, 10-entry, and 10-skill limits.
• A Settings entry is missing: it appears only with the matching organization management capability.
• A saved view looks different: check the selected table or Kanban layout and its visible fields. Applied on may have been added once to an older saved layout.
• A closed job disappeared: remove or edit the default Status ≠ Closed filter on Jobs.
• The wrong conversation disappeared after selecting a job: this is intentional when the AI scope changes; start or select a conversation in the new scope.
• A synchronized job cannot be changed: Edit can render, but saving fails because the ATS owns the job. Manage it in the connected applicant tracking system.

Related pages

• Hiring permissions and states
• Troubleshoot Hiring
• Use Talent portal