You09:20
Applied through the careers page. Six years of Go, mostly payments.
A thread per candidate, from CV to offer
The CV, then each interviewer’s scorecard under their own name. At Friday’s debrief, List shows where every candidate stands.
Start free trial
14 days of Pro. No card needed. Ends automatically. Choose to continue with Pro for $99.99 a year ($8.33 a month). See monthly pricing
At a glance
- For
- Hiring managers and small teams without a hiring system.
- You keep
- A folder for the role, shared with the interviewers at Can add notes, and a thread for each candidate.
- Nothing to set up
- The CV, then each interviewer’s scorecard under their own name.
- The moment
- At Friday’s debrief, List shows every candidate with the last note: who passed which stage, and who is waiting to hear from you.
- Plan
- Pro Only the one who shares needs Pro. Interviewers join free.
Before
Seven candidates for one backend role. The CVs sit in the careers inbox, and three interviewers fill in the score spreadsheet three different ways. At the debrief someone asks what Ana said about on-call, and the only person who knows is on holiday.
Why a thread, not a spreadsheet and direct messages
Each interview, signed
Every interviewer adds a scorecard under their own name, with the date.
The same scorecard every time
Copy the table from the first interview, so every stage scores the same things.
One place to answer from
When the candidate writes back, the CV, the scores and what she asked for are in one thread.
The moment
After Friday’s debrief: every candidate for the role, and where each one stands.
List
- Waiting
Backend engineer
Ana Ribeiro
Offer sent on 16 October. She answers by the 23rd.
- Active
Backend engineer
Tom Becker
Technical interview with Ken on Tuesday at 14:00.
- Done
Backend engineer
Lea Park
Not this time. Told her on 12 October, with feedback.
A thread, over time Example
Your workspace starts empty.
Backend engineer
Ana Ribeiro
Mon 5 Oct
The CV first.
Thu 8 Oct
Your scorecard, as a table everyone reuses.
You15:10
Screening call: next stage.
Skill Score Why API design 4 Explained retries without being asked Debugging 3 Slow start, then found it On call 3 Wants a lighter rotation
Wed 14 Oct
Ken’s interview, under his name.
Ken17:30New
Technical interview: hire.
Skill Score Why API design 4 Clear on retries and idempotency Debugging 4 Found the bug in 12 minutes On call 3 Wants one week a month at most Priya answers the question from the first call.
Priya17:45New
System design: strong. Asked about our on-call; one week a month works for her.
Fri 16 Oct
Waiting on her answer, and the note says until when. Waiting
You11:00
Debrief: offer. Sent today; she answers by the 23rd.
Thu 22 Oct
Done. Done
You18:10
Ana accepted. She starts on 1 December.
Limits
- Notes about candidates are personal data: keep what the decision needs, and delete a candidate’s thread when your policy says. ThreadPage doesn’t delete it for you.
- Interviewers see each other’s notes. For independent scores, ask each to add theirs before reading the others.
- There’s no careers page or CV inbox: add each CV yourself.
- Notes aren’t end-to-end encrypted.
Start with one thread.
Start free trial
14 days of Pro. No card needed. Ends automatically. Choose to continue with Pro for $99.99 a year ($8.33 a month). See monthly pricing
1:1 notes for each of your direct reports
Private notes per person: 1:1s, wins, worries and what each of you promised. When reviews come, the year is already there.
Free nothing to set upA weekly meeting in one thread
Keep each meeting’s decisions and actions in the same thread. Before the next meeting, read what was agreed and what is still open.
Free nothing to set up