Interview prep that lives across six tabs and one voice memo

Your interview is at 9 a.m. tomorrow. The prep lives across six Chrome tabs, a 14-minute voice memo from a podcast, and three screenshots from Glassdoor. Saving was easy. Pulling the one thing you need at 8:47 a.m., while a recruiter watches your face on a Zoom thumbnail, is the problem.

It's Tuesday evening. You've been prepping for a product role at a mid-size SaaS company since Sunday. The recruiter's email is somewhere in your inbox, the JD is in a tab you keep meaning to print, and the hiring manager's name came up on a podcast you half-listened to during a run on the river path. You opened the Voice Memos app and said two sentences about it before your phone rang. The Glassdoor thread on the company's interview loop is bookmarked. A Reddit thread from r/cscareerquestions has one comment that mentioned the take-home format. Your friend Maya, who left the company last year, sent a Slack DM you starred but didn't reply to.

Why "I'll find it later" stops working at 8 p.m. Monday

You did the work. You sat through three episodes of the podcast where the company's VP of Engineering talked about how they think about uncertainty in roadmaps. You took two screenshots of the Glassdoor interview question list. You read every comment on the Reddit thread about whether the take-home is paid. You wrote a voice memo to yourself: "Ask about the metrics they use to evaluate the PM-engineering handoff."

The work is done. You saved the work.

Now it's 8 p.m. Monday and the interview is in 14 hours. You open Chrome and you have 47 tabs. The interview tabs are in there somewhere. The voice memo is named "New Recording 38." You search your Slack for Maya's name and get three months of unrelated standups. The Reddit thread is a URL, but you can't remember which subreddit. You bookmarked it, but your Chrome bookmarks haven't been touched since 2023 and the folder labeled "Job Search" has 91 entries.

Storage is not the problem. You stored everything. Retrieval is the problem. Every minute you spend retracing your own clicks is a minute not spent rehearsing your two-sentence story about the time you killed a project the team had spent six months on.

What you actually have versus what you saved

Count the surfaces. The Glassdoor reviews are in Chrome. The voice memo is in iCloud, on your phone. The Reddit thread is a Chrome tab you'd lose if your laptop restarted. The two LinkedIn profiles of people on the team are open in incognito because you didn't want your visits to ping their notifications. The JD PDF is in your Downloads folder, named "Senior_PM_JD_FINAL_v3.pdf." The Slack DM from Maya is in a workspace you joined for a freelance gig two years ago. The screenshots from a YouTube career advice video are in your camera roll, somewhere between Saturday's dog photos and a screenshot of a Venmo split.

What you have is six different storage systems. What you needed was one answer to one question: what does this company actually care about in the interview loop?

Reading back what's there is the part nobody warned you about. You can't search a podcast. You can't search a voice memo unless you transcribed it first. You can full-text search Chrome history, but only if you remember the words on the page. Saving feels productive in the moment, and the saved thing is invisible unless you can name it. At 8 p.m. on Monday, with the interview at 9 a.m. Tuesday, you can't name half of what you have.

How to make five sources answer one question

The fix is upstream of the panic. You don't need a better folder system. You need a way to ask a question and have your own past saves answer it. That's the shape of the problem: not "where is the thing," but "what did I learn, in my own words, across everything I collected."

In practice that means three habits, and one of them is the one you're already doing.

Habit one: save without sorting. When you find the Glassdoor thread, save it. When the podcast hits a useful 90 seconds, drop a voice memo. When Maya sends a DM, screenshot it and move on. Don't tag it. Don't file it. Don't open a "Company X" folder. The cost of sorting at save-time is what makes you stop saving by Wednesday.

Habit two: keep the source attached. The Reddit comment matters because of the thread it sat in. The voice memo matters because you remember which run you were on. When you save, save with context: the URL, the date, what you were doing when you grabbed it. Clipping with context is the part that turns a clip into something you can use a week later.

Habit three: ask, don't search. Search wants exact words. Asking works the way searching by meaning rather than keyword works: you type "what's the take-home format I read about" and the tool finds the Reddit comment, even though the comment said "at-home assignment" and not "take-home."

That third habit is the one most people skip, because most tools don't support it. Apple Notes lets you search by word. Notion lets you search by word and tag. Both are good at what they do. Neither will pull back a podcast quote you transcribed in a voice memo unless you remember the exact word you used. That's the moment you discover that storage and recall are different problems.

Honest about dEssence

dEssence is our tool, so consider the source. It's memory you don't have to maintain: save from a Chrome extension, Telegram bot, or the web app at dessence.ai, then ask in your own words later. Save it, forget it, ask for it later. No folders, no tags, no organizing. For the interview-prep scene, that means the Glassdoor tab, the voice memo, the Reddit thread, and Maya's screenshot land in one place and answer one question, even when the question doesn't use the same words as the source.

Real tradeoffs you should know about:

It's in beta. The paid tier isn't finalized, so "free during beta" means free for now, not a forever promise. There's no native iOS or Android app yet, so the voice-memo-on-a-run capture path goes through the Telegram bot or the web app rather than a dedicated mobile button. The free tier caps how much you can archive. There's no team or shared-collection feature, so if you and Maya wanted a shared interview-prep pile, you'd each keep your own.

If your prep workflow runs entirely inside Notion or Apple Notes and you only search by typed keyword you remember, you may not need a different tool. The case for trying something else is the moment you realize you spent 40 minutes looking for the one comment you already read.

Frequently Asked Questions

Q: How do I stop re-finding the same article every week?

The pattern is recall, not storage. Save once, write a one-line note about why you saved it, and put it somewhere you can ask in your own words. The problem with most saved-things archives is the same: things you saved are invisible without a retrieval layer.

Q: Can I transcribe a voice memo and search it?

Yes. The shift is asking by meaning rather than typing the exact phrase. A 14-minute memo where you said "they care about handoff metrics" should answer a later question like "what does this team value in cross-functional work" without forcing you to remember either phrase.

Q: What about Notion's AI search?

Notion's in-workspace search has gotten better over the last couple of years. The gap is cross-surface: it doesn't reach into your Glassdoor tab, your voice memo, your Slack DM, or your screenshots unless you copy them in first. The interview-prep scene is mostly that copy-in tax.

Q: How much prep is enough for a 9 a.m. interview at 8 p.m. the night before?

Less than you think, if the prep is retrievable. Reading back your own notes for 30 minutes the night before, and 15 minutes the morning of, beats a four-hour cram you can't access during the call.

The day of the interview, you don't want to be the person reciting a doc. You want to be the person who said something specific that surprised the hiring manager, in your own words, in the moment, because you remembered a 90-second podcast quote from Tuesday's run. dEssence is free during beta, no card, with a free-tier archive cap and no team workspace, but the point isn't the tool. The point is that prep is wasted if you can't pull it back. Whatever you use, build for retrieval first.