bullshit job database: Best Practices for Success

You will not remember the details. That's not a personality flaw — it's how memory works under stress, and a job search is stress with a LinkedIn login. By the time you're three companies deep, the recruiter who dodged your salary question at Company A blurs into the hiring manager who overpromised at Company C, and the Glassdoor review mentioning "leadership churn" gets filed under "vague bad vibes" instead of "pattern." The fix isn't a better memory. It's a bullshit job database — not someone else's crowdsourced spreadsheet of horror stories, but your own, built in real time, tracking every signal you collect about every role you're chasing. Think of it less as a list and more as evidence: the thing that tells you what you actually learned when your gut is giving you nothing but static.

Want expert help putting this into practice? Bullshit Job Finder can guide you through it.

Why your memory is the weakest link in your job search

Job searching is a research project disguised as a series of one-off conversations, and most people treat it that way — a phone screen here, a coffee chat there, a scroll through reviews at 11pm — with nothing connecting the dots. The problem is that decisions made at the end of a search depend on comparing information gathered weeks apart, under completely different emotional states. You were calm and skeptical during week one's research. You are exhausted and grateful for any offer by week six. Without a written record, your brain quietly rewrites the early red flags to be less red, because by the time you need to compare them, you want the newer, shinier option to win.

A database fixes this by doing the one thing memory can't: holding information constant regardless of how you feel on the day you look at it. It doesn't get tired. It doesn't want the job. It just has the notes.

The fields actually worth tracking

Related: Bullshitjobfinder - Expert Advice for Finding Real Work.

Not every column is useful — a database with forty fields you never fill in is worse than none, because you'll abandon it by week two. Keep it lean but deliberate. The fields that earn their keep:

• Posting language flags — phrases like "fast-paced," "wear many hats," "work hard play hard," "rockstar," or a salary range wide enough to drive a bus through. Note the exact phrase, not your vibe about it.
• Response time — how long between each stage: application to first reply, interview to next step, offer to paperwork. Slow, inconsistent communication during courtship is the best case for how they'll treat you as an employee.
• Interviewer answers to your key questions — ask the same two or three pointed questions every interview (why is the role open, what does success look like at 90 days, what's the biggest challenge on the team right now). Log the actual answer. Vague or contradictory answers across interviewers are gold — but only if you wrote down both versions.
• Review-site sentiment — not just star ratings, but recurring words. If three unrelated reviews across two years mention "burnout" or "reorg," that's a pattern, not noise. Note the date range too — a rough 2022 and a clean 2025 is a different story than one that's been rough the whole time.
• Comp range and what's actually confirmed — the posted range, the number a recruiter said out loud, and whether it's written down anywhere. "They said around X" and "X is in the offer letter" are not the same fact.
• Gut-check notes, written immediately after each interview — two or three sentences, no editing. How did you feel leaving the call? What's one thing that nagged you? This is the field people skip and the one that matters most.

Write it down in the moment, not from memory later

The single biggest failure mode in DIY tracking is treating it as a wrap-up task — something you'll do "later" once you have a spare evening. Later never comes, and when it does, you're reconstructing instead of recording. The interviewer's exact hedge on "we're not really doing layoffs right now" gets softened into "seemed fine, I think." Write your notes within an hour, ideally in the elevator or the parking lot. Set a recurring reminder if you have to. The goal is capturing your first, unedited reaction — before you've had time to talk yourself into liking the role because you're tired of searching and this one at least called you back promptly.

Turn entries into a score so patterns jump out

See also: BullshitJobFinder - Expert Advice on Navigating the Job Market.

Notes are only useful if you can scan them fast when it matters. Add a simple scoring column — a basic 1 to 5 or a plain red/yellow/green tag — for each major category: communication, culture signals, comp transparency, role clarity. Don't overthink the scale; consistency matters more than precision. The point is to glance at a row and instantly see "three yellows and a red" instead of re-reading four paragraphs of notes under deadline pressure. Once you've logged five or six companies this way, the pattern usually announces itself — a company that scored well everywhere except comp transparency is a very different risk than one that scored poorly across the board but had a great free lunch.

Use the log to catch your own blind spots

This is the part most advice skips, and it's arguably the most valuable one. A database isn't just a record of employers — it's a record of you. Go back through past entries every few searches and look for a red flag you consistently note and consistently ignore. Maybe you always flag "no clear manager named" as a yellow, then take the job anyway because the mission excited you, and it's bitten you twice. That's not bad luck, that's a documented pattern in your own decision-making, visible only because you wrote it down honestly the first time instead of talking yourself out of the flag in the moment. Once you know your blind spot, build a rule around it — a hard no on that flag, decided in advance while you're thinking clearly, not mid-interview-glow.

Turn the finished log into negotiation leverage

By the time you're comparing offers, your database stops being a research tool and becomes ammunition. A recruiter who quoted "around X" and now offers less has a documented gap you can point to specifically. A company with a fast, consistent response time throughout the process has demonstrated operational competence worth weighing against a similar offer. Your notes on what each interviewer said about growth, scope, and team stability let you ask precise, informed follow-up questions instead of generic ones — which itself signals a serious, organized candidate. And if you're weighing whether a role is even worth pursuing before it eats more of your time, cross-reference your own findings against a tool built for exactly this kind of pattern-spotting, like Bullshit Job Finder, so you're triangulating firsthand evidence against a wider signal instead of relying on gut feeling alone.

None of this requires fancy software. A spreadsheet with a dozen honest columns, updated the same day you gather each piece of information, will outperform your memory every time — the difference between choosing your next job on evidence and choosing it on whichever conversation was freshest in your head.