Notes eat the answer
A recruiter typing the last answer is not listening to this one. The follow-up that would have mattered does not get asked.
New
Pay as you go: hours from $9 that never expire
Your recruiters stop typing. Your clients get a submittal they can check.
Interview Signal runs on the recruiter's own computer, beside Zoom, Teams, Meet or a phone screen. It keeps the question guide in front of them, suggests the follow-up the last answer earned, fills a scorecard with the candidate's own words, and writes the client submittal before the call has ended.
Nothing joins the meeting. No participant appears. Works on phone screens, which meeting-bot tools cannot record at all.
Runs beside the call you already make
- Zoom
- Microsoft Teams
- Google Meet
- Softphones and dial-ins
- A mobile on speaker
Notes come out shaped for Bullhorn, Greenhouse, Lever and JobAdder, or as a Word document and a CSV row.
The problem
It is not the interview. It is the thirty minutes after it.
Every recruiter scores differently
Two people interview the same candidate and submit two different pictures. Clients notice, and it is the agency's name on both.
The submittal is written at 9pm
Thirty to forty-five minutes per candidate, from memory, hours later — which is exactly when a strong quote becomes a vague adjective.
Watch
Three desks, the same thirty minutes.
A recruiter with fourteen interviews in a day, a hiring manager with twenty a week, and an engineering lead who paid for three bad hires. None of the films runs past two minutes.
Fourteen interviews, six roles
A recruiter who is not an engineer. The job description goes in, the questions come out, and the report for the hiring manager is ready when the call ends. 1 minute 34.
Twenty interviews a week
The questions are ready before the call and every answer is scored during it. 46 seconds.
Three bad hires
What changes when every interviewer asks the right questions and scores the same way. 52 seconds.
Dramatized scenarios. The presenters are AI-generated, and the people and figures in the films are illustrative.
How it works
Four steps. None of them is an IT project.
-
01
Paste the job description
You get eight to fourteen questions and a scorecard for that role, with what a strong answer contains written next to each question. Edit anything. It is saved for the whole team, so every recruiter runs the same interview.
-
02
Start the call as you always do
Zoom, Teams, Meet, a softphone, a mobile on speaker. Interview Signal listens through your own computer's microphone and audio output. Nothing joins the meeting and no participant appears, so nobody clams up.
-
03
Interview. Watch the guide, not a notepad
Questions tick themselves off as they are covered; must-asks stay pinned until they are not. After a substantial answer, three follow-ups appear, built from what the candidate actually just said. The scorecard fills as you go, each score carrying the quote it came from.
-
04
End the call with the submittal already written
In your agency's template, in your format. Edit a line, then copy it, save it, export a Word document, add a CSV row, or email it from your own address.
Evidence
The scorecard quotes them, or it says nothing.
Every score carries the candidate's own words. Those quotes are checked against the transcript, word for word. Anything the app cannot find in what was actually said is deleted, and the area is flagged for you to probe rather than scored on confidence.
That is the difference between a scorecard you forward to a client and one you have to re-check yourself first.
Quote check · Hands-on ownershipExample
Priya · specific
I saw the error rate jump, rolled the deploy back myself, and wrote up the incident the same afternoon.
Marcus · vague
I led the migration to the cloud.
Probe
No quote survives for Marcus here, so the area is flagged for you to ask about instead of being scored on how confident he sounded.
- Questions per role
- 8–14
- and a scorecard, from one pasted job description
- Follow-ups
- 3
- after a substantial answer, built from what the candidate just said
- First kit
- 30sec
- about that long to generate, then a few minutes to edit
- Bots in the meeting
- 0
- nothing joins the call and no participant appears
What you get
What your recruiters have in front of them
A live guide that ticks itself
Must-asks pinned until covered. Comp, notice period, availability and work authorisation stop being the thing someone forgot.
Follow-ups from what was just said
Junior recruiters ask the question your best recruiter would have asked, in the moment, not in the debrief.
A submittal in your template
Five formats to start from — executive one-pager, technical, sales, executive search, contract — or write your own.
A weekly coaching note
Per recruiter: interviews run, must-asks covered, follow-ups used, scorecards finished. Built from coverage, not opinion.
No bot
Why nothing joins the meeting
Candidates behave differently when a bot is watching
A named participant in the call, recording, is a visible third party in what is supposed to be a conversation. People get careful. Careful answers are worse answers, and worse answers make worse submittals.
Half your interviews are phone screens
A meeting bot cannot join a phone call. Capturing your own computer's audio handles softphones, dial-ins and a mobile on speaker, which is where a lot of first-round screening actually happens.
Nothing to roll out
No calendar permissions, no meeting-platform admin, no IT ticket. Install it, sign in with the address your admin invited, and use it on the next call.
Consent stays yours to handle
A read-aloud notice is built into every role, and pausing capture is one button that is always visible. Notice and consent rules differ by country and by US state, and the consent guide sets out the common cases.
Where it lives
The interview stays on the recruiter's computer
Written to the recruiter's own machine
- Transcripts
- Notes
- Evidence quotes
- Candidate names
- Submittals
Never uploaded.
What reaches us: counts and durations
- How long the interview ran
- How many questions were covered
- How many scorecard areas were filled
That is what makes the team's coverage report work, and it is all of it.
Questions
Questions people ask first
Does the candidate see anything?
No. Nothing joins the meeting and no participant appears. Interview Signal is a window on the recruiter's own computer, which is why we also ask recruiters to read the notice at the start — see the consent guide.
Does it work on phone screens?
Yes, and that is one of the main reasons it exists. It captures your computer's own audio, so a softphone, a dial-in or a mobile on speaker all work. Meeting-bot tools cannot record a phone call at all.
Where do the recordings go?
There is no recording to store. Audio is transcribed as the interview runs and the transcript is written to the recruiter's own computer. It is never uploaded. The security page lists exactly what reaches us, field by field.
Does it push into our ATS?
Not yet. Today you get copy-ready notes shaped for Bullhorn, Greenhouse, Lever and JobAdder, plus a CSV row and a Word document. Native ATS push is on the roadmap and we are not going to put a date on it.
What if it does not save us time?
Run twenty interviews in the first thirty days. If your recruiters are not saving at least thirty minutes per candidate on notes and submittals, refund the month and cancel from inside your account. One button.
How long does setup take?
Install, sign in, paste a job description. The first kit takes about thirty seconds to generate and a few minutes to edit into something you are happy with.
Guides
Free guides for people who run interviews
Templates, question banks and the consent rules, useful whether or not you ever use the product.
Start free
See it on one of your own roles
Watch a full interview in the app first, then run one of your own. Every account starts with twenty free minutes and no card: paste a real job description and you see the guide, the follow-ups and the submittal on a role you are actually filling.
Questions first? Write to [email protected] and a person replies within one working day.