Screen inbound job applications from a Gmail jobs inbox

Your jobs@ inbox fills up with CVs that nobody has time to read. An Orkeste agent parses each application, scores it against the role criteria, and surfaces a ranked shortlist to the recruiter. No candidate is ever auto-rejected.

How the workflow runs

  1. Read jobs@ inbox: Agent watches your Gmail jobs inbox and downloads CV attachments.
  2. Parse application: Extracts structured candidate data: experience, skills, location.
  3. Score against role: Scores fit against the role brief with explicit reasoning per criterion.
  4. Recruiter reviews shortlist: Recruiter sees a ranked shortlist with reasoning and full CV linked.
  5. Tag and route: Recruiter advances or declines; only then is any reply sent.

Human-in-the-loop: No candidate is ever auto-rejected or auto-replied to; the recruiter makes every advance/decline decision.

Works with your stack

Related workflows

Questions about this workflow

How do you avoid bias?

Scoring reasoning is shown per criterion, demographic signals are excluded, and the recruiter sees the full CV — not just the score.

Can it handle non-English CVs?

Yes. Multilingual CVs are parsed and the score reasoning is produced in the recruiter's language.

Does it write to my ATS?

Yes, after recruiter action. The agent never advances or rejects in the ATS without human confirmation.