One Hiring Drive, Five Recruiters: Splitting AI Screening by Role

On June 22, 2026, an HR lead onboarding her team onto HireQwik said something in a working session that I wrote down word for word: “I would only want to look at each role.” She had five people screening in one workspace. One was hiring backend engineers, one was running a campus drive for trainee analysts, one was filling sales roles, and two were splitting a support hiring push. And every one of them was opening the same interview list and scrolling past four other people’s candidates to find their own.

We had already fixed this in one place. Since May, the inbox had been scoped so a recruiter saw only the job descriptions they owned. But the interview list and the shortlist were still org-wide. So a recruiter hiring for a senior engineering role had a clean inbox and then, one click later, a list full of marketing candidates. That half-fix was arguably worse than no fix, because it taught people to trust a filter that stopped working on the next screen.

This post is about what we changed, why ownership has to follow the role and not the recruiter, and how to set up multi-recruiter AI screening so the team splits the work without the TA lead losing sight of the drive.

Why a shared screening workspace breaks at three recruiters

A single recruiter running AI screening has no visibility problem. Everything in the workspace is theirs. The trouble starts when a second and third person join, because an AI screen produces a lot of output per candidate: a resume score with evidence, a call recording, a transcript, a tier from Strong Go to No Go. Multiply that across four open roles and a few hundred applicants each, and the list stops being a list and becomes a haystack.

What teams usually try first is a naming convention. Prefix every job description with the recruiter’s initials, then search. It works for about a week. Then someone clones last quarter’s role and forgets to rename it, someone goes on leave and a colleague picks up their roles, and the prefixes stop meaning anything. We have written separately about renaming a job description mid-campaign, and the short version is that a label is a poor substitute for a real ownership field.

The second thing teams try is separate workspaces per recruiter. That solves the noise and creates a worse problem: the TA lead now has five dashboards and no single view of the drive. Nobody can answer “how many Strong Go candidates do we have across all roles this week” without opening five tabs and adding by hand.

The fix is neither. It is one workspace, where each role has an owner, and every view is filtered by that ownership by default.

How role ownership works in practice

The rule is short enough to fit in one sentence: a recruiter sees the roles they own, plus any role nobody owns yet, and an admin sees everything.

That rule now applies the same way on three screens, which was the entire point of the change:

• Inbox. New applicants arriving from a Google Sheet, referral form or file upload show up only for the recruiter who owns that job description.
• Interviews. The list of scheduled, completed and cancelled AI interviews is filtered to the recruiter’s roles, and so is the previous/next navigation inside a candidate profile.
• Shortlist. Resume screening jobs are scoped the same way, so a recruiter’s shortlist view does not include another team’s runs.

The Excel export follows the same scope. That detail matters more than it looks. An export is the thing that leaves the tool and lands in a hiring manager’s inbox, and a filter that applies on screen but not on export is a filter that leaks.

Two deliberate exceptions keep real work from disappearing. First, roles with no owner stay visible to everyone, so a workspace that existed before ownership was introduced keeps working exactly as it did. Second, interviews that are not tied to a job description at all, such as some bulk drive campaigns, stay visible to the whole team. Hiding them would have made genuine candidates vanish from every view, which is the one failure a filter must never cause.

Who owns what: Owner, Admin and Member

Ownership of roles only works if ownership of the workspace is clear too. HireQwik has three levels:

Until July, the person who created the workspace became admin and everyone they invited became a member, permanently. There was no way to promote anyone. One HR team told us, plainly, that there was “no option to give an admin role,” and our own Team Management screen was telling people to promote colleagues using a control that did not exist. That was embarrassing, and it was fixed on July 13.

Now an admin can invite someone directly as an admin or a member, and change a member’s level later from the team list. Three guards make sure a workspace can never lock itself out:

1. The owner cannot be demoted or removed. The person who holds the account is always there.
2. The last admin cannot be demoted. If only one admin is left, the system refuses the change.
3. Nobody can change their own level. A promotion or demotion always needs a second admin, which is the same principle as least privilege in access control: nobody should be able to widen their own access.

Assigning roles to recruiters without a meeting

An admin assigns an owner in one of two places. On each job description there is an owner dropdown listing the team. And in Team Management there is a Role assignments card that lists every job description in the workspace against a dropdown of members, so a TA lead can set up an entire drive in one pass instead of opening ten roles one at a time.

Reassignment is where this earns its keep. When a recruiter goes on leave in the middle of a campus season, the admin changes the owner on their four roles, and those roles’ inbox, interviews and shortlists move to the colleague’s views straight away. Nothing is copied, nothing is re-screened, and the candidate history comes along with the role. A level change, such as promoting someone to admin, applies on the server immediately; the person sees their new admin menus the next time they reload the page.

What the TA lead sees that the recruiters do not

The risk with any filtered view is that the person accountable for the whole drive ends up seeing less. So admins are deliberately left unfiltered by default. A TA lead opening the interview list sees every role across every recruiter, which is the view they need on a Monday morning to spot that one role has two hundred completed interviews and nobody has reviewed them.

When the same admin is also hiring for a role themselves, which in a team of five is common, a My roles toggle on the interview list narrows the view to their own job descriptions. The toggle lives in the page address, so a TA lead can bookmark “my roles” and “everyone” as two separate links and switch between them.

A useful weekly routine for the lead looks like this:

1. Open Interviews with the full view and sort by tier. Look for roles where Strong Go candidates are piling up unreviewed.
2. Open Team Management and check the Role assignments card for any role still showing no owner. Unowned roles are visible to everyone, which means in practice nobody is watching them.
3. Switch to My roles and do your own review last, so your own hiring does not eat the time meant for the team view.

One more thing sits at the workspace level on purpose: Slack and Microsoft Teams alerts. An admin chooses the channel once for the whole organisation, and members can see that setup but not change it. That keeps a single place where the team hears about completed screens and high-scoring candidates, whoever owns the role, rather than five recruiters each wiring up their own private channel that nobody else can see.

Automation stays a per-role decision

Splitting work by role also means splitting the riskiest settings by role. In HireQwik, auto-reject and auto-advance are opt-ins set on each role, never workspace-wide defaults. That is intentional in a multi-recruiter setup. The recruiter hiring five hundred campus trainees might reasonably switch on auto-decide bands for clear No Go outcomes, while the recruiter hiring two senior engineers should almost certainly review every candidate by hand. A single global switch would force one of them into the wrong behaviour.

The same logic applies to stopping work. Every screening run and every drive has its own stop control, so a recruiter who notices a mistake in their own role can stop that screening campaign without touching a colleague’s drive that is running correctly next to it.

Common mistakes when splitting AI screening across a team

We have watched a handful of teams set this up. The same four mistakes come up:

• Leaving roles unowned. Unowned is a backward-compatibility state, not a setup. An unowned role is visible to all five recruiters, and a role everyone can see is a role everyone assumes someone else is handling.
• Assigning by candidate, not by role. Some teams want to split one large role’s applicants between two recruiters. Ownership follows the job description, so the cleaner move is two job descriptions (for example, one per campus or one per city) with one owner each. It also makes each shortlist easier to hand to the right hiring manager.
• Making everyone an admin. It feels friendly and it removes the filter that solved the problem in the first place. Keep admin for the people accountable for the whole drive; usually that is one or two people.
• Sharing a login. Two recruiters on one account means one ownership identity, one set of views and no way to tell who approved which candidate. Invite each person separately; it costs nothing and it keeps an honest audit trail of who did what.

That last point has a compliance edge too. India’s Digital Personal Data Protection Act, 2023 sets expectations around how personal data is handled and who processes it. Limiting each recruiter’s day-to-day view to the candidates they are actually hiring is simply good data hygiene, independent of any single regulation.

Setting up a five-recruiter drive in one sitting

If you are about to run a hiring push with a team, this is the order that avoids rework:

1. Invite the team with the right level from the start. One or two admins, everyone else as members.
2. Create one job description per real hiring decision. Split by location or campus if different people will own them.
3. Assign every role an owner from the Role assignments card before any applicant arrives. The inbox starts filtering from the first resume.
4. Let each owner set their role’s automation. Knockouts, rubric and any auto-decide bands are per role.
5. Connect intake per role, whether that is a Google Sheet, a referral form or a folder of resumes, so new applicants trigger screening straight into the owner’s inbox.
6. Give the TA lead two bookmarks: the full interview list and the My roles view.

Once that is in place, a five-person team runs one drive in one workspace, each recruiter sees a list short enough to actually finish, and the person accountable for the whole thing still sees the whole thing. That was all the HR lead in June was asking for.

If your team is about to split a hiring season across several recruiters, book a demo with your real roles and we will set up the ownership with you on the call.