Skip to main content

Concepts

Why the video stays in the browser

The interview happens in a Daily.co room rendered inside Jobby.dev — never a Zoom or Teams link. Why this design choice, and what we trade for it.

Last updated

Short answer: the live interview happens inside a Daily.co room rendered as an iframe inside Jobby.dev. We never hand out a Zoom or Teams link, and we never ask either side to install anything. This is a deliberate design decision — here's the rationale.

The problem with the "send a calendar invite" default

The traditional pipeline ends every screen with the same five-minute ritual: confirm the candidate's timezone, generate a Zoom or Teams link, send a calendar invite, and pray that:

  • The candidate has the right desktop client installed.
  • Their corp firewall doesn't block the WebRTC ports.
  • Single sign-on for the recruiter's domain hasn't expired.
  • The candidate hasn't accidentally joined the wrong meeting.

For an on-demand model where the interview starts within minutes of a match, that ritual breaks. There's no time to install a client, request firewall changes, or chase a calendar invite that landed in spam. Browser-only is the only way the on-demand promise holds.

What we trade for it

Browser-only video isn't free. We pay for the choice in three places:

  1. WebRTC limits.Mobile browsers — especially older iOS Safari — don't support every codec or every screen-share path the desktop clients do. We test the supported feature surface on every release; the unsupported features are documented as warnings on the relevant interview page.
  2. Recording.Cloud recording happens server-side via Daily.co. Local recording (the Zoom / Teams pattern of writing an .mp4 to the user's disk) doesn't exist — that's a feature of the desktop client, not the protocol. If your compliance regime requires per-side local recording, surface that during procurement.
  3. Bandwidth budget.The Jobby.dev page wraps the Daily.co iframe; both consume bandwidth in the user's browser tab. We strip everything else from the interview page (no marketing chrome, no analytics scripts, no chat widget) so the budget stays predictable. See seeker troubleshooting for the bandwidth floor.

Why Daily and not a homegrown stack

Building WebRTC from scratch is a five-engineer-year project that Jobby.dev shouldn't take on. Daily.co handles SFU routing, TURN relays, codec negotiation, browser quirks, and a quality-of-experience SDK we'd otherwise re-write. Our differentiation is the on-demand matching layer, not the video transport.

Why an iframe and not a redirect

The interview page stays at jobby.dev/interview/<match_id>. Both sides see Jobby.dev branding, the report-card UI loads immediately when the room ends, and we can render queue / role / billing context next to the video without a context switch. A redirect to a Daily-hosted URL would lose all of that.

Related reading