When you join an interview on interviewing.io, the platform runs a lightweight client that watches a few signals. Understanding exactly what it sees helps you avoid accidental rule violations and focus on what really matters: showing your skills.

How the Platform Monitors Your Session

Browser Focus and Tab Switching

  • The client records when the browser window loses focus. If you click away to another tab, a timestamp is logged.
  • It does not capture the content of other tabs, only the fact that you left the interview window.
  • In most loops, a brief loss of focus (under a few seconds) is tolerated, but repeated switches can trigger a warning.

Copy‑Paste Activity

  • Interviewing.io can detect a paste event inside the interview editor. The event itself is logged, but the actual text is not stored.
  • This means the platform knows you pasted something, but it cannot read the clipboard contents.
  • Using copy‑paste for code snippets is fine as long as you own the code and it complies with the interview's honesty policy.

Proctoring and Video Recording

  • The web client accesses your webcam and microphone, creating a continuous audio‑video stream.
  • The stream is stored for review, mainly to verify identity and to resolve disputes.
  • The system can detect when you are sharing your screen via the built‑in screen‑share option, but it does not monitor external screen‑sharing apps.

Detecting External AI Tools

  • There is no built‑in AI‑detector that parses your speech or typed answers for language‑model signatures.
  • The platform relies on self‑reporting and post‑interview audits. If you claim a solution is yours when it isn’t, the interviewers may notice inconsistencies.
  • Some companies integrate third‑party plagiarism checkers, but this is optional and varies by client.

What the Platform Cannot See

CapabilityVisible to interviewing.ioNot Visible to interviewing.io
Desktop apps (e.g., IDEs)❌✅
External browser windows❌ (only focus loss)✅
Clipboard contents❌ (event only)✅
Network traffic outside the interview page❌✅
Use of local AI assistants (e.g., VS Code Copilot)❌✅

In short, the system watches the interview page, not your whole computer. Anything you do outside that window remains private, provided you don’t bring it back into the interview space in a way that violates the rules.

Common Candidate Concerns

“Will my code editor be recorded?”

No. The video feed captures only what your webcam sees. If you place a camera on your screen, it could be recorded, but typical IDE windows are not captured.

“Can they tell if I used ChatGPT?”

Only if the output looks noticeably different from your usual style or if the interviewers ask follow‑up questions that reveal gaps. There is no automatic AI‑signature detection.

“What if I need to look up a function reference?”

A quick tab switch is logged, but it’s acceptable if you explain why you needed the reference. The key is honesty—mention you looked it up if the interview asks for it.

“Is screen‑sharing allowed?”

Screen‑sharing is allowed only when the interview explicitly requests it (e.g., a live coding session). Unsolicited sharing may be flagged as a breach of privacy.

Staying Within the Rules

  1. Keep the interview window in focus – If you need to check something, do it quickly and return. Explain your action if asked.
  2. Use copy‑paste responsibly – Paste only code you wrote or that you have the right to share. Avoid pasting large blocks of external material without attribution.
  3. Be transparent about AI assistance – If you used a tool like Copilot to generate a snippet, say so when prompted.
  4. Follow the platform’s honor code – Most interviewers expect you to own the work you present. Violations can lead to disqualification.

How Call Assistant Can Help (Briefly)

When you practice answering questions aloud, Call Assistant can listen and suggest concise, resume‑grounded responses. It also helps you stay on topic during follow‑ups, reducing the temptation to look away from the interview window.

How to Practice This

  1. Simulate a real interview – Record yourself on camera, keep the interview tab active, and answer a set of typical questions.
  2. Review the recording – Note any moments where you lost focus or used copy‑paste. Adjust your workflow to minimize those events.
  3. Run a mock session with Call Assistant – Use it to rehearse concise answers and keep the conversation flowing without needing to switch tabs.

FAQ

  • Q: Does interviewing.io store the text I type? A: It stores the final answer you submit, but it does not keep a log of every keystroke. The platform only records paste events, not the clipboard content.
  • Q: Can the platform detect if I’m using a second monitor? A: No. It only knows whether the interview window is active; what’s on a second screen is invisible to it.
  • Q: What happens if I accidentally share my screen? A: The recording will show the shared content. If the sharing was not part of the interview brief, the interviewers may consider it a breach of confidentiality.
  • Q: Are there any penalties for a brief loss of focus? A: Usually not, unless it becomes a pattern. Interviewers may ask why you switched away if it happens repeatedly.

Frequently asked questions

Does interviewing.io store the text I type?

It stores the final answer you submit, but it does not keep a log of every keystroke. The platform only records paste events, not the clipboard content.

Can the platform detect if I’m using a second monitor?

No. It only knows whether the interview window is active; what’s on a second screen is invisible to it.

What happens if I accidentally share my screen?

The recording will show the shared content. If the sharing was not part of the interview brief, the interviewers may consider it a breach of confidentiality.

Are there any penalties for a brief loss of focus?

Usually not, unless it becomes a pattern. Interviewers may ask why you switched away if it happens repeatedly.

#interviewing.io#detection#remote-interviews#candidate-guidelines#AI-tools