Why We Built Pickr: The Recruiting Problem Nobody Is Solving

I built Pickr because I watched a team make the same hiring mistake on hire forty that it had made on hire four, and nothing in the software noticed. Every applicant tracking system I used was an excellent filing cabinet and a useless colleague. Pickr exists to close that gap: recruiting intelligence that compounds instead of merely accumulating.

That is the short answer. The longer one includes the parts that still do not work, because a founder story made only of wins is marketing.

Four years of agency hiring, and every ATS I could buy

For four years I ran ScalingPPL, a recruitment agency placing people into startups and scale-ups across Europe. Hundreds of searches, dozens of clients, and an invoice attached to every time we got it wrong. I saw both sides from that seat: running the search as an agency, and sitting in the debrief with the client's own hiring team, who had to live with the person we sent.

Across those years I used every major ATS and a long tail of smaller ones. Several are genuinely good software. Greenhouse's process discipline is real, and a company that needs structured, auditable hiring at enterprise scale should buy Greenhouse. Ashby's reporting is the deepest available anywhere, and I say that as someone who now competes with them. Bullhorn holds agency operations together at a scale nothing else touches, and an agency whose life is contracts, timesheets and back-office integration should stay on Bullhorn.

Not one of them ever got better at hiring.

They got better at storing hiring. Every year the search was faster, the dashboards denser, the integrations broader. The quality of the judgement was the same in year four as in year one, because that judgement lived in people's heads and the software only kept its output.

The rejection reason that told me nothing

A client's head of engineering called me about a candidate. Had we spoken to him the previous year? She had just seen him on LinkedIn as a staff engineer at a company everyone in the market can name, and she wanted to know why we had passed.

I opened the ATS. The record was complete and completely useless. Name. Rejected at final stage. A date. A dropdown reason: "Not a fit."

The real reasoning had existed. Three of us argued about him for four minutes on a Thursday debrief call, and the disagreement was genuine: scope of ownership against depth of systems experience. It lasted exactly as long as the call. What survived was three words from a dropdown menu.

Two weeks later the same client rejected a different candidate with the same three words, and I could not put the two decisions next to each other and ask whether they were consistent, because there was nothing to compare. The system held a perfect record of what we decided and no record at all of why, which meant the organisation could not learn from its own hiring even in principle.

Why interviewer feedback never arrives

The second frustration never stopped. I spent a real share of every week chasing interviewers for feedback that never came, and I tracked who owed me what in a spreadsheet, because the reminders inside the ATS were ignored by everyone, including me.

For years I thought this was a discipline problem. It is not. Look at what you are asking a hiring manager to do: three days after the conversation, from memory, log into a system she opens once a month and fill in an empty form that gives her nothing back. Of course it does not happen. In many teams she does not even have an account, because seats cost money and finance capped the licence count at the recruiters. So the feedback arrives as a Slack message or a sentence in a corridor, and it never touches the record.

That is why interviewer and hiring manager seats in Pickr are free and will stay free. It reads like a discount. It is the only way the evidence ever gets captured. The mechanics of why scorecards fail in practice are worth a piece of their own, and I wrote one: the hiring manager scorecard guide.

Recording recruiting instead of doing it

The category was designed around custody, not judgement. Applicant tracking. The name is honest: track the applicants, keep the audit trail, prove you were fair. The recruiting itself stayed with the humans, and the software's contribution was a place to put the residue.

That was a reasonable design when software could not read a CV properly, could not listen to an interview, could not notice that two rejection reasons contradicted each other. It stopped being reasonable a while ago. Most of the rest of the stack has calcified around the same assumption, which is the argument in why the recruiting stack is broken.

What I actually wanted to build

Pickr is the AI-native recruiting system that treats every finished hire as evidence for the next one, so the reasoning behind a decision outlives the meeting it was made in.

Three things follow from that, and they are the whole product idea:

1. Evaluation belongs inside the process, not at the edges. Every candidate is scored continuously against what the role actually requires, on evidence of skills including adjacent and transferable ones, rather than on which words appear in a CV.
2. Reasoning has to be captured at the moment it exists. Interviews are transcribed and scorecards arrive pre-filled with evidence mapped to each criterion, so an interviewer edits a draft instead of confronting an empty form on Friday. When someone rejects a strong candidate without a documented reason, Pickr asks for it while it is still in their head.
3. Outcomes have to come back. What happened to the people you actually hired changes how the next ones are evaluated. That holds whether you are an agency measuring which placements stayed or an in-house team measuring which hires grew, and the full shape of the idea is in the AI recruiting brain.

What Pickr has not solved

The problem	Where Pickr is today	Still on you
Reasoning evaporating after the debrief	Captured at the moment of the decision, tied to the criteria it relates to	Somebody still has to say the sentence out loud
Scorecards that never arrive	Drafted from the interview, free seats for everyone who gives feedback	People who will not open any system at all
Keyword matching instead of evaluation	Continuous scoring on evidence of skills, adjacent and transferable included	A brief that never defines what good looks like
Hiring that never improves	Outcomes of past hires feed back into how candidates are evaluated	Enough history, and enough hires, for the loop to mean anything
Reporting depth	Solid process reporting: time per stage, drop-off by stage, scorecard completion	Ashby is deeper. If reporting is the whole job, buy Ashby

Two of those deserve more than one line.

The first is cold start. The compounding is the entire premise, and compounding needs history. A team that arrives with no usable hiring record gets a good evaluation system and very little learning for the first months. Pickr imports your historical hiring data when you switch systems, and what comes across is usually thin: a stage, a date, a dropdown reason. You cannot reconstruct judgement that was never written down. For a search where you see five candidates and hire one person a year, the loop barely turns at all.

The second is harder, and I do not think anyone in this category has solved it. Learning from your outcomes means learning from your preferences, and your preferences contain your past mistakes. Evaluating on evidence of skills rather than pedigree helps. So does redacting personally identifying information from AI prompts by default, which is how Pickr runs, with candidate data hosted in Germany and the processing agreement included. Keeping the decision with a human, with the reasoning written down where a colleague can challenge it, helps most. None of that is the same as saying the problem is closed, and I would not trust a vendor who told you otherwise.

There is also a version of this where the software is not your problem at all. That is why the first thing we offer is a diagnosis rather than a demo: the free recruiting audit is eight questions and about two minutes with no signup, or a deeper read-only connection to your current ATS that turns your real hiring history into a report on funnel drop-off by stage, where you run slower than comparable teams, and how often scorecards actually get filled in. If it tells you the constraint is a process habit rather than a licence, fix the habit and keep the system you have. That is a cheaper answer than anything I sell.

I built Pickr because I got tired of software that remembered everything and understood nothing. If your hiring works, agency or in-house, if the reasoning behind your last forty decisions is written down somewhere a colleague could read it, and if your fortieth hire went better than your fourth for reasons you can name, you do not need us. If none of that is true, the question is not which system stores your candidates best. It is which one will still be teaching you something a year from now.