The product

Week29, view by view.

A recruiter panel that opens from Teamtailor. Here is what it does, and what happens beneath the surface when you press Match.

The panel

Four views from the workflow.

Built to do one thing well: surface the strongest candidates you already have.

  1. AI search

    Write what you are looking for in plain language. The answer streams in with the tool steps visible, and the candidate cards land underneath with level and evidence.

  2. Job matching

    Import an ad from Teamtailor. The text of the ad becomes the requirements for the role, and the whole database is ranked against it.

  3. Results and comparison

    A ranked list with levels and requirement coverage. Select several candidates and set them against each other on relevance, experience, requirements, location and availability.

  4. The detail sheet

    The requirements, most important first, with a status and evidence for each, the candidate's own material, and the actions to pass along or save.

Ask in plain language and learn who meets the requirements, and why.

The AI search in Week29 with a question in plain language, an answer with evidence and candidate cards with match levels
The engine

What happens when you press Match.

No magic, and nothing that cannot be explained to an auditor.

The database is loaded

Candidates are pulled from Teamtailor with CV and free text. Changes are fetched continuously, so the database stays current without anyone syncing by hand.

The text is made searchable by meaning

Each candidate's material is split into passages at sentence boundaries and stored as vectors, so that the meaning stays together.

The whole database is ranked

The requirements for the role are compared against every candidate in the database, by meaning and by word matches. The order is deterministic: the same input gives the same result.

The evidence is produced

The key terms of the role are split into those that appear verbatim and those that are missing. For the missing ones we look for phrasings that only occur when the meaning is actually intended. That step is entirely deterministic, with no language model involved.

Guiding principles

Four things we do not compromise on.

Levels, not numbers

In the panel, matching is shown as Strong, Good or Possible, never as a percentage or a score.

Write actions are gated in code

The AI can propose passing candidates along, but never do it. The server checks every candidate against the database, not against the chat history.

Evidence, not assertions

Matches on meaning come with a quote from the candidate's own material. The quote is verbatim and never rewritten. The reasoning next to it is built from fixed rules, not by a language model.

Candidate text is untrusted text

A CV can contain instructions aimed at an AI. We sanitise all candidate text and flag profiles that look manipulated for human review.

Teamtailor

On top of the ATS you already chose.

Week29 replaces nothing. Your workflows stay in Teamtailor, and the result lands where you already work.

  • The match level is written back to the candidate card in Teamtailor.
  • The panel opens from Teamtailor and links back to the candidate.
  • Changes in Teamtailor follow along continuously, with nobody syncing by hand.

Built as a Teamtailor integration. Activation happens together with you.

The role list in Week29 with requirement profile, matching status and follow-up for each role
The role list: roles are imported from Teamtailor or created in the panel, and every row shows where the matching stands.
Your data, our engine

See it run against a real database.

We show the ranking, the evidence and the controls, and answer the questions about data and regulation. Thirty minutes is enough.