Documentation — v1.0
Your intelligent
career partner.
Renqore is an AI-powered recruitment platform for agencies and hiring teams. It combines LLM-powered job matching with real-time job data to help you evaluate candidates against live listings — all in automated batches.
01 — Overview
What is Renqore?
Renqore is an AI-powered recruitment platform built for agencies and hiring teams. It sources jobs via the Adzuna API, evaluates candidates against live listings using an LLM, and produces structured fit scores — all in automated batches.
The platform is built around three ideas: automated batch evaluation, CV-aware job matching with AI scoring, and a collaborative workspace for teams to manage clients, jobs, and results.
Batch Evaluation
Group candidates into batches and run AI-powered job matching across all of them at once. Each CV is analysed against live job listings.
LLM Fit Scoring
Every job is scored 0-100 by an LLM based on how well it matches the candidate's CV, skills, and preferences. Detailed reasoning is provided for each score.
Team Workspace
Invite team members as admins, writers, or readers. Manage clients, track batch progress, and review results together.
CV Management
Upload candidate CVs (PDF/DOCX), extract text automatically, and attach to each client profile for AI-powered matching and review.
02 — How It Works
From batch to results
A batch evaluation flows through several automated stages before results appear.
-
01
Create a batch
Group candidates into a batch and configure their job search preferences — role title, keywords, location, salary range, and exclusions.
-
02
Job sourcing
For each client preference, Renqore fetches live job listings from the Adzuna API. If no results are found, the LLM suggests alternative queries to broaden the search.
-
03
LLM evaluation
Each job is evaluated against the candidate's CV text. The LLM returns a fit score (0-100), a detailed reason, and any warnings. Results are stored per client.
-
04
Review & action
Review results in the dashboard. Star promising matches, add manual job entries, and track progress across batches. Export or share results with your team.
03 — Getting Started
Your first session
Renqore supports both Google OAuth and email/password authentication. Once signed in and part of an organisation, you land on the dashboard where you can manage batches, clients, and results.
-
01
Sign in or register
Use Google OAuth or email/password to create an account. A new organisation can be created during onboarding.
-
02
Join or create an organisation
After signing in, create an organisation or accept an invite from an existing team. Your role (admin/writer/reader) determines what you can do.
-
03
Create a batch and add clients
Create a batch, add clients with their CVs and job preferences, then run the evaluation to match them against live job listings.
-
04
Set your LLM API key
Navigate to Settings in the sidebar and enter your Ollama API key. This key is used to run batch evaluations. The key is stored per organisation and can be updated by admins at any time.
-
05
Run evaluation & review results
Run a batch to match clients against live job listings. Each client's matched jobs are displayed with fit scores, company details, and apply links. Star promising matches for quick access.
04 — Batch Evaluation
Batch Evaluation
The core of Renqore is automated batch evaluation. Create a batch of clients, each with their CV and job preferences, and run a single evaluation that sources and scores jobs for every client simultaneously.
Behind the scenes, Renqore fetches live job listings from the Adzuna API for each client's preferences, then sends the CV text and job data to an LLM for evaluation. The LLM returns a fit score (0-100) with detailed reasoning for each job.
Client CVs
Each client profile can include an uploaded CV (PDF or DOCX). Text is extracted automatically and used by the LLM during job evaluation.
Starred Jobs
Star any job result in the client detail view to save it. Starred jobs are highlighted and can be filtered for quick access.
Each starred job retains its original data: title, company, location, salary, description, fit score, and apply link. Unstarring is equally simple and takes effect immediately.
05 — Data Export
Downloading your data
Any member of an organisation can download data at three levels. Each export produces a formatted Excel workbook with multiple sheets.
Organisation Data
Download org details, plan info, usage stats, member list (with names, emails, roles, join dates), and pending invites from the Organisation page.
Batches Data
Download a summary of all batches plus a full client roster with names, emails, preferences, and iteration status from the Batches page.
Client Data
Download a single client's profile, preferences, and all matched jobs — including fit scores, salaries, apply links, and starred status — from any client card.
06 — Usage & Quota
Evaluations & limits
Each organisation has a daily quota of 100 evaluations across a rolling 24-hour window. An evaluation is consumed each time a client's preferences are matched against live job listings.
You can track your usage from the usage panel, accessible via the progress bar in the sidebar. It shows iterations used, remaining quota, reset time, clients evaluated, and any failures in the current window.
07 — Organisation
Members & Roles
Every organisation has three member roles. Your role determines what you can see and do in the dashboard.
| Role | Permissions |
|---|---|
| Admin | Full access: manage members, change roles, invite people, delete batches, update org settings and API key. |
| Writer | Can create and run batches, add and edit clients, upload CVs, rename batches. |
| Reader | View-only access to batches, client profiles, and job results. Cannot modify anything. |
Invites
Admins can invite new members by email from the Organisation page. Each invite is assigned a role (admin, writer, or reader) and a unique link that can be copied and shared. Invites can be revoked at any time.
When a user accepts an invite, they are automatically added to the organisation with the assigned role. If they aren't signed in, they are prompted to authenticate first — the invite is preserved across the auth flow.
Settings
The Settings page allows admins to configure the organisation's Ollama API key. This key is required to run batch evaluations. It is stored encrypted per organisation and can be updated or removed at any time.
When saving a new key, Renqore validates it against the Ollama API before storing. If the key is rate-limited, it is saved anyway so that existing quota can be used.
Data & Privacy
All user data is stored in a private MongoDB database. Connections use TLS in transit. No user data is shared with third parties. The following data is held per account:
| Collection | What is stored |
|---|---|
| users | Name, email, hashed password (bcrypt), join date, activity flags. |
| clients | Client profiles, CV text, job preferences, matched job results with fit scores. |
| batches | Batch metadata, status, client counts, timestamps. |
| organizations | Org name, plan, member roles, settings. |
| fs.files / fs.chunks | Original PDF CV file stored via MongoDB GridFS. |
Account Management
All account operations are accessible from the Organisation page. Renqore supports both Google OAuth and email/password accounts. Your account data — including name, email, and joined date — is visible in the Organisation panel.
Each organisation stores its data separately. When you leave or are removed from an organisation, your personal account remains active with any other organisations you belong to.