HR People teams Recruiting

Claude for HR and People Teams: Keep Candidate and Employee Context Persistent

If you work in HR or people ops, you already use Claude for drafting JDs, screening questions, offer letters, and performance frameworks. The problem hits when you're three weeks into a search: Claude knows nothing about the role, the hiring manager's preferences, the candidates you've already passed on, or why you declined them.

You re-brief it. Every time. That's the tax on using Claude in HR without persistent context.

Stash gives Claude a place to store and retrieve that context — hiring pipelines, candidate notes, team preferences, employee records — so you brief it once and it knows in every session.

What HR teams store in Stash

What this looks like in practice

What's the status on the Senior Product Designer search?

You have 8 candidates in the pipeline. Three at final stage: Maya (strong portfolio, concerns about B2B experience), Jake (solid, but wants remote-only which doesn't fit the role), and Priya (your hiring manager's top pick — decision pending reference check). Two more at first interview this week. Roles unfilled 47 days.

Draft a message to Priya's referees.

Here's a draft based on her role and your standard reference questions...

That first response didn't require you to paste in a spreadsheet or re-explain the search. Claude pulled it from Stash in one call.

Setting up in 30 seconds

Step 1 — Add the connector Claude Settings → Connectors → Add custom MCP server → paste https://app.stashlite.com/mcp → Save
Step 2 — Sign in with Google Claude will prompt you to authenticate. One click. Your private record store is provisioned automatically.
Step 3 — Start saving context In a Claude conversation: "Stash a record in 'hiring-pipeline' — role: Senior Product Designer, stage: final, candidates: Maya, Jake, Priya. Priya is the hiring manager's top pick."

Concrete HR use cases

1. Active hiring pipeline

One collection per open role. Records for each candidate with status, notes, and next action. Ask Claude to surface all candidates at a given stage, or draft a message for the next step without re-explaining who they are.

2. Interview debrief capture

After each debrief, tell Claude to store the key points: what the panel liked, what they didn't, and the decision. Next time you brief a new panel, Claude can pull the pattern of what's worked and what hasn't for that role.

3. Offer and compensation history

Store what you offered, what they countered, and whether it closed. After six months of searches, you have a queryable record of real market data — not survey benchmarks.

4. Employee context for 1:1s

Keep a record per direct report: recent themes, development goals, concerns flagged, commitments made. Before each 1:1, ask Claude to surface the thread. You arrive with context. They notice.

5. Policy lookups

Store your leave policy, flex working rules, parental leave entitlement — once. Ask Claude questions about them without opening the policy document. Useful when managers come to you with edge cases at 4pm on a Friday.

Free tier and pricing

The free tier gives you 2,500 records and 50 queries per month. That's enough for an active search with 15–20 candidates and weekly queries without hitting the limit. Most HR teams or solo recruiters find they hit the free cap within 2–3 months of active use — at which point Pro is £8/month for 100,000 records and 1,000 queries.

Add Stash to Claude — free, no credit card Paste this in Claude → Settings → Connectors → Add custom MCP server:

https://app.stashlite.com/mcp

Sign in with Google, done. Your first records are one message away.

What Stash doesn't do

Stash is a record store, not an ATS. It doesn't send emails, schedule interviews, or integrate with your job board. It's the lightweight layer that makes Claude genuinely useful in your workflow — without replacing the tools you already use for tracking and communication. Think of it as Claude's notepad that persists between sessions.