Recruiting · Production

BrightHire offloads video recording infrastructure to Recall.ai to free engineers and cut costs

The problem

BrightHire's self-built video recorders for Zoom, Google Meet, and Microsoft Teams required two full-time senior developers and a devops engineer to maintain, generated one or two incidents per week, and kept the engineering team constantly firefighting rather than building customer-facing features.

First attempt

BrightHire's internally built recorders used web scraping to join meetings and were brittle; every incident was urgent, and the team spent significant engineering effort on maintenance rather than product development.

Workflow diagram · grounded in source
1
Recall.ai API records interview
integration
“Recall.ai relieved BrightHire of the burden of video recordings with a reliable, cost-effective API”
2
AI generates notes and highlights
ai_action
“Use AI to write job descriptions and interview plans, take interview notes, provide interview highlights”
3
Hiring insights delivered
output
“empower better, faster hiring decisions”
Reported outcome

Recall.ai substantially reduced weekly incidents, saved money on labor and compute, and freed the engineering team to deliver features across all platforms.

Reported metrics
weekly incidents before Recall.aiat least one or two issues per week — maybe a few more on bad weeks
incidents after switching to Recall.aisubstantially fewer issues than we had before
Time to build each integration2-3 months
Engineers dedicated to maintaining integrations2 full-time senior developers and a devops engineer
Show all 6 reported metrics
weekly incidents before Recall.aiat least one or two issues per week — maybe a few more on bad weeks
incidents after switching to Recall.aisubstantially fewer issues than we had before
time to build each integration2-3 months
engineers dedicated to maintaining integrations2 full-time senior developers and a devops engineer
time saved handling Zoom API change3-4 weeks of work for an engineer ended up getting done in a week
labor and infrastructure cost savingssaved BrightHire money across both resource-draining variables: labor and infrastructure
Reported stack
Recall.aiZoomGoogle MeetMicrosoft TeamsGCPSlack
Source
https://www.recall.ai/customers/brighthire
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Recall.ai substantially reduced weekly incidents, saved money on labor and compute, and freed the engineering team to deliver features across all platforms.

What tools did this team use?

Recall.ai, Zoom, Google Meet, Microsoft Teams, GCP, Slack.

What results were reported?

weekly incidents before Recall.ai: at least one or two issues per week — maybe a few more on bad weeks; incidents after switching to Recall.ai: substantially fewer issues than we had before; Time to build each integration: 2-3 months; Engineers dedicated to maintaining integrations: 2 full-time senior developers and a devops engineer (source-reported, not independently verified).

What failed first in this deployment?

BrightHire's internally built recorders used web scraping to join meetings and were brittle; every incident was urgent, and the team spent significant engineering effort on maintenance rather than product development.

How is this recruiting AI workflow structured?

Recall.ai API records interview → AI generates notes and highlights → Hiring insights delivered.

Related recruiting cases