You interviewed 40 candidates and can't remember which one said what

Keep what each candidate actually said in one place you can ask in plain language, not just scattered ATS fields. Drop every resume, scorecard, and post-interview voice note into a single memory as the round runs. Later you ask "who had the fintech background" and get the right person back in seconds, not forty reopened profiles.

You remember them clearly the hour after each interview. The candidate just walked you through a payments migration she led, named the exact stack, told you why she left, and what she wants next. You scribble two lines, mean to write the rest up properly, and then the next interview starts on time. By the third week of a high-volume round you have run forty conversations, and they have collapsed into a single blur of strong-but-which-one.

Then the hiring manager asks the question that should be easy: "Which of them had real fintech experience and was open to relocating?" You know one of them was perfect. You cannot remember her name, you cannot tell her apart from two other strong engineers, and the note you took says "good, follow up." So you reopen profiles, re-skim resumes, and in the worst case you bring someone back for a call you already had. That is a slower process, a worse candidate experience, and a real risk of passing on the right hire.

Why your ATS does not actually solve this

Most recruiters already run an applicant tracking system, and a good one does real work. As of 2026 the standard ATS stores every candidate profile, schedules interviews, collects structured scorecards from each interviewer, and averages those scores into a pipeline rating so strong candidates do not silently drop out. Centralizing interviewer notes on the profile is the whole point: when the next interviewer cannot see what happened in the last conversation, they ask the same questions, miss a red flag, or overlook something promising.

The gap is not storage. The gap is everything that does not fit a scorecard field. "She lit up when I described the on-call rotation." "He kept comparing himself to the last role, watch the motivation." "The quiet one actually gave the best system-design answer of the day." That texture is what predicts the hire, and it lives in your shorthand notes, your voice memos in the parking lot, and your head. The ATS has a notes box, but you have to stop, type, and tag it cleanly every time, and between back-to-back interviews you do not, so the box ends up with "good, follow up."

So the signal splits across tools. The structured scores sit in the ATS. The real read on each person sits scattered, or never gets written at all. And the question you actually need answered, "who said the thing I am now trying to remember," has no single place to land.

What recruiters actually do to remember (and where it breaks)

The habits are right. The storage is the problem.

Many recruiters record a quick voice note straight after an interview while the read is fresh. Plenty keep a running spreadsheet alongside the ATS with one line per candidate. Most download or screenshot the resume and the portfolio link a candidate sent so they can find it fast. Good interviewers write a two-line summary, the standout strength and the one concern, the moment the call ends.

Every one of those is the right instinct. They each create a fragment, and the fragments never end up in the same place. The voice note is buried in your phone recorder. The resume PDF is in a downloads folder with thirty-nine others. The spreadsheet line is three columns of shorthand you cannot decode a month later. When the hiring manager asks who had the fintech background, you cannot search across all of it at once, so you fall back on memory, and memory is exactly what failed you after interview number twenty.

Put what candidates said somewhere you can ask, not just store

The fix is not another field to fill in faster. It is one place for the whole round that takes whatever you already capture and lets you ask it back later in plain language.

That is the idea behind a tool like dEssence. It is a personal memory app, not a recruiting product and not an ATS, so it stays out of the workflow and just holds things. You save it, forget it, and ask for it later. The point for a recruiter is that the fragments you already create finally land in one searchable spot you can question in your own words.

Here is what that looks like across one busy round.

A resume comes in. You forward the PDF straight into dEssence. After the interview you hold your phone in the hallway and record a forty-second note: "Strong payments background, led a fintech migration, open to relocating, slight concern on management experience." That goes in. The portfolio link she shared goes in too. There are no folders, no tags, no organizing. Forty candidates, forty fragments, all in the same memory.

Then the hiring manager pings you with the question that used to send you reopening profiles: "Who had real fintech experience and was open to moving?" You ask dEssence in plain language and get back her name, the migration she described, the relocation note, and the resume itself, pulled from a voice note and a PDF you would otherwise be hunting through downloads to find. You answer in the same minute instead of promising to circle back.

The three save surfaces match how a recruiter actually works

Recruiting happens in three places, and dEssence has three co-equal ways to capture that line up with them.

The Telegram bot is the between-interviews tool: forward a resume or fire off a voice note from your phone the second a call ends, before the next one starts. The Chrome extension is the sourcing tool: save a LinkedIn profile or a portfolio page straight from the tab without breaking your flow. The web app is where you sit down at the end of the week and ask the synthesis question across the whole pipeline. Same memory underneath all three, so it does not matter which one you grab first.

This is memory you do not have to maintain. You are not building a candidate database by hand. You are dropping things in as they pass and trusting that you can ask for them later.

Honest about dEssence

An ATS and dEssence are different tools, and you will keep both. Your ATS runs the process: requisitions, pipeline stages, compliance records, scheduling, structured scorecards, and the audit trail every regulated hire needs. dEssence does none of that and is not trying to. It holds the messy read on each person and answers questions about it. If you want one system of record that also manages the hiring workflow, dEssence is not that system.

A few honest limits. dEssence is in beta, so expect rough edges and changing features. There is no native iOS or Android app yet, so on the go you work through the Telegram bot rather than a dedicated mobile app. It also has no team workspace, so it is your personal memory, not a shared hiring record a whole panel reads from. For a solo recruiter or a single hiring manager keeping their own read on a round, that fits. For a panel that needs shared, compliant candidate records, the ATS still owns that job.

Frequently asked questions

Is dEssence an applicant tracking system?

No. It is a general personal memory app that happens to work well for holding what candidates said. It does not run requisitions, pipeline stages, or compliance records. Keep your ATS for the process and use dEssence for the interview texture the scorecard fields cannot hold.

How do I keep forty candidates from blurring together?

You forward each resume and record a short voice note after each interview, all into one memory. When you need someone later you ask in plain language, for example who had the fintech background, and the answer pulls from what you saved about that person. There is nothing to file or tag.

Can I really just talk to it after an interview?

Yes. Record a voice note in the hallway and send it through the Telegram bot. Later you ask in your own words and get the read back, including details from that note. You do not have to transcribe or organize anything yourself.

Will it replace the scorecards I already fill in?

No, and it should not. Scorecards live in the ATS and feed the structured decision and the audit trail. dEssence holds the part that never fit a scorecard, the offhand read and the detail you would otherwise lose, and lets you ask across all of it at once.

dEssence is free during beta with no card required, so you can run a single hiring round through it and see whether you can answer the who-said-what question without reopening a profile. It will not replace your ATS, and it is early software with no mobile app yet, but for the half of every interview that never fits a scorecard, it gives you somewhere to put it and a way to ask for it back.