How we handle GDPR data-subject requests on a deadline
Legal
An agent connected to our applications inbox, the role's written rubric, and Google Calendar that scores each resume against the rubric with evidence and proposes interview slots for strong matches.
Every open role brings in more applications than anyone can read carefully, so screening gets rushed: a few seconds per resume, inconsistent from one reviewer to the next, and easy to drift from the criteria the role was actually written against. Good candidates get skimmed past and the standard moves depending on who is reading.
We run an agent on Kortix that does the first read consistently. Each application triggers a session that scores the resume against the role's written rubric, writes a structured screen with evidence, and proposes interview slots for strong matches. A person makes every advance-or-reject call; the agent never rejects anyone. This is how we screen our own inbound applicants.
The first read of a resume is where screening gets inconsistent. Volume forces it to be fast, and fast reads drift: the same resume gets a different verdict from a different reviewer, or against a criterion the role never listed. Strong candidates get missed and the bar moves with whoever is reading.
The usual fixes trade one problem for another. Keyword filters reject on the wrong signal and quietly drop good people. A rushed human pass is inconsistent by the afternoon. An AI screener that scores against its own idea of "good" is a fairness problem: opaque, unaccountable, and impossible to check.
On Kortix, each inbound application triggers an agent. The application spawns an isolated session (a cloud sandbox) with the role's written rubric and scoped access to Google Calendar. The agent reads the resume against the rubric, writes a structured screen — strengths, gaps, a score, and supporting quotes as evidence — and for strong matches proposes interview slots on the hiring manager's calendar. A person decides every case.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the resume-scoring skill and the 15-minute trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a resume triage agent in this workspace.
Create the agent agents/resume-triage.md. Its job is to screen each new application in Greenhouse against the role's written rubric, and propose interview times for strong matches. It may use the Greenhouse and Google Calendar connectors.
Create the skill skills/resume-scoring/SKILL.md with these rules:
Add a cron trigger application-screen-sweep to kortix.yaml. It runs the resume-triage agent every 15 minutes with the prompt "Load the resume-scoring skill and screen every new application in Greenhouse against the Role rubric."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect your applicant tracking system and the hiring manager's calendar. Credentials are brokered server-side and never enter the agent's machine.
Reads new applications and writes the structured screen back.

Proposes interview slots on the hiring manager calendar.
Merge the change request, then start a session with the resume-triage agent and send this prompt. Read the first screens against the rubric before you let the schedule take over.
Screen the new applications in Greenhouse.
The change request added this trigger to kortix.yaml. From now on the agent
runs every 15 minutes, each run in a new session on its own cloud computer. To
change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: application-screen-sweep name: Application screen sweep on: cron: "0 */15 * * * *" run: agent: resume-triage prompt: Load the resume-scoring skill and screen every new application in Greenhouse against the Role rubric.The agent has no reject or advance action. It writes a screen with evidence and proposes slots as tentative holds. The hiring manager reads the screen, decides, and confirms any interview.
Each new application gets one screen in Greenhouse. This is what a sweep looks like in the session:
Screened 6 new applications against the Role rubric. 1 is a strong match: it meets every required criterion and 3 of 4 preferred ones, so I proposed 3 tentative slots for the hiring manager to confirm. The other 5 screens are in Greenhouse with their quotes. No candidate was advanced or rejected.
Once it works, paste any of these into the same session.
Every day at 17:00, send the hiring manager one Slack message with the day's screens ranked by score, each with a link.
When three or more candidates are partially met on the same criterion, tell me and suggest a clearer wording for it.
In each sweep, screen referred applications before the others, and mark them as referrals in the screen.
The agent reads candidate applications and its output shapes hiring, so fairness and human judgment are built into the controls:
The first read is now consistent and checkable: every application is scored against the same written rubric with the quotes that support each score, and strong matches arrive with interview times already proposed. The hiring manager spends their time deciding on evidence rather than skimming resumes, and every advance-or-reject call stays with a person.