Book a demo

The interview client

Why interviews need their own client.

The cheating that actually works doesn't happen in the browser or in the call. It happens on the desktop, a few pixels away, where neither one can see. You can't close that gap from the outside, so we built the interview to run somewhere that can. It opens for the interview and closes when it ends.

Book a demo See how it works

The architecture

Each layer can only see its own layer.

This isn't a preference. It's how software works. A tool can only observe the layer it runs in, so integrity that stops at the browser or the call has a blind spot the size of the whole operating system.

The limit

A browser sees the browser. A call sees the call.

A browser extension can inspect the browser tab and nothing beyond it. A bot that joins a call can observe what happens in that call. Both are useful, and both are blind to everything running natively on the computer beside them. That is precisely where the newest assistance tools choose to live.

The answer

Make the meeting the thing that sees.

Bolt integrity onto someone else's meeting tool and you're always a layer behind it. So the interview runs in Capifiq instead: the app your candidate joins is the same one checking the room: for the length of the interview, and not a minute longer.

The blind spot

What only a device-level layer can surface.

These are the tactics a browser extension or a bot joining a call cannot catch, because none of them live in the browser or the call.

Native overlays

Answer windows drawn on top of the interview by desktop software that lives outside the browser entirely, invisible to anything watching only the tab.

Remote-control sessions

A second person quietly driving the machine from elsewhere, so the answers on screen aren't coming from the candidate at all.

Virtual machines and sandboxes

The real interview running inside a disguised environment, with assistance tucked into the layer the call never sees.

System-level interference

Tampering with the display, the camera path, or the desktop itself: happening below the browser and below the call, where only a device layer reaches.

Capifiq describes what it surfaces, never the recipe for how. New tactics appear constantly; the device layer is what lets coverage keep up with them. See the full picture of what we detect →

The trade-off, neutralized

A device-level layer, without the device-level intrusion.

A client that can see the device could be heavy-handed. Capifiq's is deliberately the opposite: it does the one job it exists for, and nothing else.

What it is

  • A roughly 30-second, guided setup before the interview starts.
  • Active only for the scheduled session, then closed.
  • Runs in ordinary user space: no admin or root privileges.
  • Surfaces findings as sealed, timestamped evidence for a human to review.
  • Candidates are told clearly, in advance, with rights and a review process.

What it never does

  • Lock down, block, or restrict anything on the computer.
  • Run before the interview starts or after it ends.
  • Monitor persistently in the background.
  • Take control of the machine or demand elevated privileges.
  • Decide an outcome, a qualified person always makes the call.

Capifiq surfaces the finding. The interviewer makes the judgement. It never accuses automatically, and its evidence is never the sole basis for a decision.

Two jobs, one client

The desktop and the conversation, watched by one session.

Help can hide on the machine or in the answers themselves. Cover one and you've left the other wide open, so Capifiq covers both, in the same session, with no handoff between them to get wrong.

The device

Surfaces on-device assistance the conversation can't reveal: overlays, remote control, virtual machines, display tampering, and new vectors as they appear.

The call

Every interview is recorded and transcribed, and the transcript shares one clock with the session timeline so any moment can be found again.

See the interview record →

Questions

Common questions about the interview client.

Does the candidate have to install something separate?
No. Joining the interview and running the integrity check are the same thing. The candidate opens their join link, goes through a roughly 30-second guided setup, and is in the interview. There is no second download to explain.
How long is it on the candidate's machine?
Only for the scheduled interview. It is closed afterward and does not run in the background before or after the session.
Does it take over or lock down the computer?
No. It runs in ordinary user space, never takes admin or root privileges, and never blocks, terminates, or restricts anything. It is an integrity check for the interview, not a lockdown of the machine.
Does Capifiq decide whether someone is cheating?
No. It surfaces findings as sealed, timestamped evidence. A qualified person on the hiring side reviews them and makes the judgement, and it is never the interviewer who conducted the session. They are barred from reviewing their own interview. Capifiq never accuses automatically and is never the sole basis for a decision. Candidates have documented rights and a review process.

Get started

See the device layer on your own interviews.

Book a walkthrough and see what turns up on the desktop that a browser or a call would never have shown you.

Book a demo Request a pilot