For companies

You find out at the reference
what you needed at the shortlist.

References happen after the interviews are spent. By then the choice is made, and a bad answer costs you the whole process, so it almost never changes anything.

One vacancy is enough to see it. We set it up on your own careers page.

An application as a hiring team sees it. Under each claim sits the confirmation behind it: employment and dates confirmed by HR from the company's own domain, the title corrected by the person's manager, and what they did confirmed by two colleagues.
What an application looks like before the first conversation.

What you get instead

A role is four facts, and they are answered separately.

Different people honestly know different things. HR has the employment, the dates and the title. A teammate knows what the person actually did. Asking one referee all four is how you get a confident answer from somebody who was not in a position to give one.

So each fact carries its own answer and its own source, and I do not know is recorded as itself rather than rounded to a yes or quietly dropped.

  • Worked thereUsually HR, often from the company domain
  • DatesWeighed against the referee's own overlap
  • TitleDisagreements are kept as corrections
  • What you didOnly counted from somebody close to the work
The page a referee sees: the claim restated, then four questions each with Yes, No and I do not know.
The referee makes no account. Four questions, about a minute.

The rules

Built so it cannot be gamed quietly.

A confirmation that can be replaced the same afternoon is worth very little. This is the part that decides whether any of the rest means anything.

Confirmed

Senior Backend Engineer

  • HR, from the records
  • Their manager
  • A colleague

Three people, on these words.

the title is edited

No longer counts

Lead Backend Engineer

  • HR, from the records
  • Their manager
  • A colleague

Kept on the record, so the candidate can see what was confirmed before they changed it. Counted for nothing.

  1. 01

    A confirmation is bound to the words it confirmed

    Change the claim and the confirmation stops counting for the part that changed. A record cannot be rewritten to inherit somebody else’s answer.

  2. 02

    A confirmed fact is held for thirty days

    Long enough that rewriting a claim to inherit its confirmations is slow enough to be visible rather than quiet.

  3. 03

    Nothing the candidate controls is counted

    A file somebody uploaded about themselves is shown to you and counted for nothing. Only an answer from a third party carries weight.

  4. 04

    Counting stops at three

    Nothing above the second confirmation changes what you learn. An uncapped count would become the thing candidates competed on.

  5. 05

    Every ending names a person or a reviewed rule

    A final decision on an application cannot be saved without one. The system refuses to store a rejection nobody stands behind.

Your careers page

At your own address, in your own colour.

Every company gets yourcompany.getrolepass.com, with your logo and your colour. Nothing on it carries our name.

A company's careers page on RolePass: their own logo on a full width band in their own blue, headed Careers at Thinkscoop Technologies, with a search box for job titles.
A company hiring on RolePass today. Their logo, their colour, their address, and not a mockup.

Applications land in one place, each carrying the record behind it rather than a PDF you have to take on trust. You can add resumes you already hold, see which of them fit a vacancy, and put the role to the people who do.

Anybody on RolePass who has said they are open to a change can be found for a role they fit and written to about it. They are not handed to you as a contact: you hear from them only if they say they are interested.

Decisions

Somebody stands behind every ending.

Automated screening is useful and it is also the thing that goes wrong quietly. A rejection nobody can account for is the one an employment tribunal, a regulator or a candidate will ask you about, and it is the one that is hardest to reconstruct a year later.

So a final decision cannot be saved without naming a person or a rule somebody reviewed. Rejections made by a rule go into a queue for a person to confirm, every read of a candidate's record is recorded against whoever made it, and the audit trail is scoped to your organisation at every source.

Before you ask

The things worth knowing first.

  • Where the data sitsOur own infrastructure in Asia Pacific (Mumbai). Files are private and reached only through short lived links, encrypted in transit and at rest.
  • Who sees a candidateYour organisation, and only for applications made to you. An agency's end client is never named to a candidate, and no other company can read your pipeline.
  • What is not built yetThere is no integration with an applicant tracking system. If you run everything through one today, this sits beside it rather than inside it.
  • How early we areEarly. You would be among the first, which means the roadmap is still shaped by the people using it.

The full detail is in the privacy policy, including what is kept and for how long.

Get started

One vacancy is enough to see it.

Tell us what you are hiring for and we will show you it on your own vacancies.

For the person

I want mine
on the record.

Your record, your applications and everything anybody has confirmed.

I am a candidate

Your CV, with witnesses.

For the team

I want to know
it is true.

Your jobs, your applicants, and who confirmed what before the first conversation.

I am hiring

The references, before the interview.

Nearly there

Which company’s
careers page?

Your account is the same one everywhere, so this only decides which page you land on.

The first part of the address on their careers page.