This is the stack for the interview itself — the hour that produces the hiring decision and, at most companies, the worst record of it. It assumes you already source candidates and already run an ATS. The constraint it addresses is evidence: five interviewers, one candidate, and a debrief that runs on memory and tone of voice.
Buying it in 2026 is a different exercise than it was two years ago, because the category stopped being independent. Zoom announced its acquisition of BrightHire on 13 November 2025 and closed it that December; BrightHire — the company that named the interview-intelligence category — now sells under Zoom Business Services with its own brand, team, and domain intact. Pillar went first: Employ acquired it in March 2025 and rebranded it the AI Interview Companion, native inside Lever, Jobvite, and JazzHR. Metaview is the last independent of the three. The practical consequence: the recorder you should buy is now largely decided by the ATS and conferencing platform you already run, not by a feature bake-off.
So the stack is Greenhouse as the rubric and the record, exactly one recorder chosen against it, and your conferencing platform as the capture surface.
If you want the whole hiring loop rather than the interview stage, that is the AI-augmented recruiting stack. If your problem is measuring technical skill rather than capturing judgment, that is the technical hiring stack. This one goes deep on one hour.
How the pieces fit
- Greenhouse is the rubric, and it goes first. Interview kits and scorecards are first-class objects, which is what makes the rest of this stack worth buying: a kit defines the competencies each interviewer is accountable for, and the scorecard is where the answer lands. A recording attached to a defined competency is evidence. A recording attached to nothing is a video library nobody opens. Greenhouse is also the trigger surface — stage transitions are what tell the recorder which loop it is sitting in.
- BrightHire is the recorder when interviewer coaching is the reason you are buying. Recording and transcription are the spine; Interview Planning drafts the plan before the loop opens, AI Interview Notes returns a filled scorecard, Interview Insights grades interviewer behavior, and BrightHire Screen runs an asynchronous first-round screen against a recruiter-defined rubric. Zoom’s product page lists Greenhouse, Ashby, Workday, Lever, Rippling, BambooHR, and Gem as supported ATS platforms, and both parties state that Microsoft Teams and Google Meet stay supported and that a Zoom license is not required to run it.
- Metaview is the recorder when you want a price before a sales call. Same core job — joins the call, transcribes, writes a structured scorecard draft into Greenhouse, Lever, or Ashby — with published, self-serve, per-user pricing. It is now sold by agent (notetaker, sourcing, application review) rather than as a single bundle, which changes how you size it.
- Pillar is the recorder if your ATS is an Employ product. Real-time question prompts, competency guidance, auto-generated scorecards, native inside Lever, Jobvite, and JazzHR. It belongs in this stack as an alternative to the Greenhouse pairing rather than a companion to it: on Greenhouse it is an integration competing with two vendors that built for Greenhouse first.
- Zoom, Microsoft Teams, or Google Meet is the capture surface — and the consent surface. It is not a neutral pipe. It is where the recording notice appears and where the recorder joins as a visible participant, which is the fact your candidates and your counsel will both ask about.
The handoffs that make it a stack
Each arrow is an event, not a habit.
A req opens and the recruiter builds the loop in Greenhouse — kits per stage, competencies per interviewer. That kit is the object the recorder reads: when Greenhouse advances a candidate to an interview stage, the scheduled event carries the kit’s competencies into the recorder, so the notes come back shaped like the scorecard instead of like a transcript. The calendar invite carries the recording notice and, where AI analysis is involved, the consent request — before the call, not in the first 30 seconds of it. The interview runs, and the recorder joins the Zoom, Teams, or Meet call as a participant and captures it. Within minutes of the call ending a drafted scorecard lands on the Greenhouse candidate record, and the interviewer edits and submits it — the draft is not the submission, and the moment you allow it to be, you have automated the appearance of structure rather than the practice. The debrief then runs against submitted scorecards with timestamped clips behind the contested ones, which is the difference between “I didn’t get a strong signal” and a 90-second replay. Afterward the interviewer analytics read the same corpus: who talks 70% of the time, who never asks their assigned competency, whose ratings never move with the panel’s.
Why this combination
Because interview intelligence is worth nothing without a rubric, and a rubric decays without evidence. Structured interviewing is the precondition here, not the output — where no competency is assigned per interviewer, recording produces a larger pile of the same unstructured judgment, at a per-seat price.
The load-bearing rule: one recorder, and the ATS owns both the rubric and the trigger. Two recorders on one funnel produce two scorecard drafts and no canonical record, and interviewers will submit whichever one loaded faster. Letting the recorder own the rubric — defining competencies in the recording tool instead of in Greenhouse — puts your hiring criteria inside the layer you are most likely to replace, and this is a category where two of the three vendors changed owners inside 18 months.
What it costs
Budget $25K-$100K a year for a 50-250 hire loop, ATS included, with the ATS as the dominant line.
- Greenhouse does not publish pricing and meters per employee rather than per recruiter, so the bill scales with company headcount. Series B and up typically runs $20K-$80K a year. If you are on Core and want the Real Talent identity-verification and fraud-detection layer, it sits in Plus and Pro — a required line item for that job, not an upsell you can defer.
- BrightHire publishes no numbers. Three packages — Recruiters, Teams, Enterprises — plus Screen sold standalone or bundled, all routed to a demo. Vendr publishes anonymized data from 57 purchases as of February 2026: a median of $18,000 a year, with $15K-$35K at 5-15 users and under 100 interviews a month, $35K-$75K at 15-50 users and 100-300 interviews, and $75K-$150K+ above that.
- Metaview publishes per-user monthly tiers — free, $100 for Pro, $300 for Max, Enterprise quoted. Because it now sells by agent, confirm which tier the notetaker you actually want sits in before you size seats: the usage limits printed on the pricing page are stated per agent, and the sourcing agent’s limits are not the notetaker’s.
- Conferencing is a cost you already carry. Treat it as sunk. This stack is not a reason to change conferencing platforms, and if a vendor tells you it is, that is the acquisition talking.
The unit that matters is cost per recorded interview, not cost per seat. At 800 interviews a year, BrightHire’s $18,000 median is roughly $22 an interview; 15 Metaview Pro seats is $18,000 at list, the same money with a number you can compute before a sales call. Both are cheap against what they displace — the 20-40 minutes each interviewer spends reconstructing a scorecard from memory, times five interviewers, times every onsite. That is where the return sits, and it is worth more than the coaching analytics that get top billing in the demo.
Common variations
- Metaview first, BrightHire on the coaching trigger. Start on published pricing and prove the notes loop. Move when you have a named owner for interviewer analytics and a standing monthly slot for them to review it — BrightHire’s premium over Metaview is largely that coaching layer, and it bills the same whether or not anyone reads it.
- Pillar instead, when you are on Lever, Jobvite, or JazzHR. Native beats integrated on those three, and the budget case is better. On Greenhouse it is the wrong pick, and that is the whole rule.
- Swap Greenhouse for Ashby. Ashby’s native analytics answer the interviewer-calibration questions without a reporting upgrade, and both BrightHire and Metaview support it. Choose it when you are selecting an ATS now rather than replacing a working one.
- Notes only, no AI screener. BrightHire Screen and its equivalents run first-round interviews with no human present. That is a different purchase carrying different disclosure obligations, and buying the notes layer alone is the defensible starting point. Add the screener when your first-round volume, not your curiosity, forces it.
When this stack is the right pick — and when it isn’t
Pick it when you run 50-250 hires a year through multi-interviewer loops, your debriefs are the weak link, and you already have kits and scorecards defined. It is also the right pick when someone has asked you to show why a specific hire was made — a recording tied to a defined competency and a submitted scorecard is the only artifact that answers that question a year later.
Skip it in three cases. Below roughly 30 hires a year, the same recruiter usually sits in most of the interviews and the memory problem this stack solves is not yet real. If your hiring is high-volume hourly, the interview is a screening question set rather than a judgment loop — that is the high-volume recruiting stack. And if your loop has no rubric, fix that first with the interview loop builder; recording an unstructured interview yields an unstructured recording with a transcript attached.
What this stack does NOT replace
- Sourcing and scheduling. Nothing here fills the calendar. Candidates have to arrive from somewhere, and the panel still has to be booked.
- The hiring decision. The recorder produces notes, clips, and a drafted score. Weighing them is the panel’s job, and the debrief stays human — see interview loop design and the debrief summary workflow for the shape that survives contact with a disagreement.
- Skills assessment. Capturing judgment well is not the same as measuring whether someone can do the work. That is a separate layer with separate vendors — the technical hiring stack.
- Your consent and disclosure obligations. Recording consent is jurisdictional, and AI analysis raises the bar again. Illinois’ Artificial Intelligence Video Interview Act (820 ILCS 42) requires advance notice that AI may be used to analyze the interview, an explanation of how it works and the general characteristics it evaluates, and written consent — and it bars evaluating applicants who have not consented. On request you must delete the video within 30 days, including backups held by anyone you shared it with, which is a data-retention requirement your recorder’s default settings will not satisfy for you. Where AI ranks or scores candidates, NYC Local Law 144 and its bias-audit and notice duties attach to you, not to the vendor. Run the AI interview compliance audit before the first recorded loop, and read AI screening bias before you turn on scoring.
- Quality-of-hire measurement. This stack tells you how the interview went and how the interviewer performed. Whether the people you hired turned out to be good at the job is measured after they start, against performance data no recorder holds.