Can interviewers tell if you are using AI?

Often, yes, especially when someone is reading. But usually not in the way people imagine. In most stories of people being caught, it was not software spotting software. It was a person watching their eyes, hearing a strange pause, and then asking a follow-up question they could not answer.

This is one of the questions job seekers ask most, in many versions:

“Can companies actually tell if you're using AI in an interview?”

Glassdoor Community

“Has anyone ever used interviewcoder and is it detectable?”

Blind

The most upvoted posts we found on this come from the hiring side. A post on r/csMajors titled “Stop using cluely, any engineer worth interviewing with isn’t being fooled” has more than 700 upvotes. Another on r/leetcode claims several well-known tools are detectable in coding rounds. Those posts are worth taking seriously, but they are not the whole picture either. Canva’s engineering team wrote in 2025 that hidden AI use was getting harder to spot, which is one reason it started letting candidates use AI openly.

I’ll go through what interviewers actually notice, what the coding and proctoring platforms can and cannot log, where companies are heading, and where using AI is fair and where it is not. At the end there is a straight account of what our own product, PiriPiri AI, does and does not hide.

What makes an interviewer suspect AI on a video call?

Amazon is one of the few companies whose internal guidance on this has been reported. According to Business Insider, which saw the documents in early 2025 (summarised by ITPro), Amazon told candidates not to use generative AI tools in interviews unless explicitly permitted, and told interviewers what to look for. The signs on that list were candidates typing while being asked a question, appearing to read rather than respond, and eyes wandering. Recruiters online describe the same things in plainer words:

“it's incredibly obvious to the interviewer so don't.”

X, @jeremyl

Your eyes move like you are reading

When you are thinking, your eyes tend to drift: up, to the side, at nothing in particular. When you read, they move along a line in short jumps and snap back at the start of the next one. On a webcam that steady back and forth is often visible, even when the text sits close to the camera. One hiring manager replying on X described a candidate who was “clearly reading something from her screen”, and said it was an instant no.

A long pause, then a perfect paragraph

Real answers start rough. You say “so, the project I’d pick is…”, then you correct yourself and go back to fill in a detail. An answer that arrives after six silent seconds as a tidy, well-ordered paragraph with three neat points sounds like something that was written.

Words you would not normally use

If your small talk is casual and your answers suddenly say “I spearheaded a cross-functional initiative to drive alignment”, the change in voice is obvious. By the time the real questions start, the interviewer has already heard how you talk, and the gap is easy to hear.

The follow-up question falls flat

This is the real test, and good interviewers use it on purpose. You give a solid answer about cutting page load time by 40 percent. They ask, “What did you try first that didn’t work?” or “Who disagreed with you?” A generated answer can sound detailed, but you cannot add to a story you did not live. The details run out quickly, and the interviewer sees it happen.

Typing when nobody asked you to type

On a behavioural call there is no reason to type. If your shoulders move and keys click every time a question starts, the interviewer hears it. A Meta engineer on Blind put it bluntly, asking how it is not obvious when someone types furiously for every question.

Can an interviewer tell if you are copying code in a live coding round?

“Can interviewer guess if I am copying code from GPT in virtual coding round?”

Blind

Coding rounds leave more evidence than a conversation, because the work is on the screen and often recorded. The signals are different from a behavioural call.

• Code that appears in large blocks. Real code grows in fits and starts, with typos, renames and half-finished lines. One engineer posted on X in 2023 about a candidate who pasted a working solution in all at once; when the team ran the question through ChatGPT, the output was almost identical.
• Correct code, no story. The interviewer asks why you chose a hash map over sorting, or what happens with an empty input. If you wrote it, you can usually answer, even if slowly. If you copied it, you are guessing.
• Trouble changing it. A common move is to ask for a small change after you finish: handle duplicates, return the index as well, make it work on a stream. One interviewer posted on X about three candidates with strong CVs who could not extend their own code with a minimal feature request, and one admitted AI had written a function he could not explain.
• Style that does not match the person. Comment blocks on every function, variable names nobody types by hand, and a perfect docstring written in 40 seconds by someone who struggled with the warm-up.

Thinking out loud helps here even if you are doing nothing wrong. Say what you are trying before you type it. An interviewer who has heard your reasoning is far less likely to be surprised by the code that follows.

What can HackerRank, CoderPad and HirePro actually detect?

You do not have to rely on forum rumours here. These platforms document what they log, and this is what their own pages said in October 2026.

HackerRank

HackerRank’s Proctor Mode, for tests created after its July 2025 release, can take screenshots of your screen every 15 seconds, dropping to every 5 seconds after something looks off. It flags attempts to leave full screen or switch tabs. It watches the webcam for whether you are present, for more than one face, and for phones or tablets in the frame. It flags a new monitor plugged in during the test, can disable copy and paste in the editor, and looks for patterns of typing and deleting text that may suggest you are talking to someone. An eye and head movement check, looking for repeated glances away followed by typing, is listed as limited availability. Screenshots are checked for things like AI assistants, tutorial sites, browser extensions and screen recorders.

CoderPad

CoderPad is used for live coding with an interviewer watching. According to its documentation, it alerts the interviewer when code is pasted from outside the pad and when the candidate leaves the editor, for example by switching tabs. Every pad keeps a full playback of edits, runs, cursor movements and paste events, so a reviewer can replay how the solution was built after the call. CoderPad’s own documentation is careful here. It says pasted code does not always mean misconduct, since you might paste from your own editor, and that alerts are prompts for clarification, not grounds for automatic disqualification.

HirePro and other proctoring suites

HirePro, which many Indian freshers meet in campus hiring, sells a proctoring product whose listings describe face matching against your ID, detection of a second person on camera, warnings when you change tabs or leave full screen, a secure browser, and audio checks for extra voices. Parakeet AI users raised a feature request titled “Detected by HirePro and other apps”, which tells you candidates have run into this in practice.

What they cannot do

None of these tools reads your mind, and none of them is proof on its own. A tab switch could be a candidate checking the documentation the interviewer allowed. A paste could be from their own editor. What these flags do is give the interviewer a reason to ask harder questions, and those questions are where a borrowed answer usually shows. If a test is proctored, the honest assumption is that it was built to stop outside help, and the right move is to take it without any.

Why are companies going back to in-person interviews?

In August 2025 the Wall Street Journal reported (as summarised by heise and Computerworld) that Google, Cisco and McKinsey were bringing back face-to-face rounds for some roles, partly because of AI use and candidate fraud on video calls. The head of an IT recruiting firm told the paper that about one in three of its corporate clients were asking for in-person interviews again, up from roughly 5 percent the year before. Sundar Pichai said Google makes sure there is at least one in-person round “just to make sure the basics are there.”

For you, this means two things. The final round at a large company may well be in a room, with a whiteboard and no screen. And anything you claim in an earlier online round can be checked there. Someone who got through two video rounds by reading answers has nothing to stand on in the third.

Are some companies now allowing AI in interviews?

Yes, and that is part of the honest picture. In June 2025 Canva’s engineering team published a post titled “Yes, you can use AI in our interviews”. It replaced one of its coding rounds with an AI-assisted one, saying it wanted to see how engineers use AI tools the way they will on the job: breaking down a problem, checking what the tool gives back, and fixing it when it is wrong. Meta began testing a similar AI-enabled coding interview in 2025, according to reporting by 404 Media and Business Insider.

Notice what these rounds test. Not whether you can get an answer out of a model, but whether you can judge it. Canva wrote that its stronger candidates did not just accept whatever the AI produced. These open policies are still the minority in the reporting so far, and Amazon’s guidance goes the other way. So the only safe rule is to read the invitation or ask the recruiter what is allowed in each round.

What if you get accused of using AI when you were not?

This happens, and it is upsetting. A Blind post titled “Got accused of using AI in interview” describes a Stripe coding round where the interviewer asked the candidate to highlight a word with their cursor while they were explaining their code. The point of that request is to check that the shared screen is live and is the one being typed on. The candidate felt accused, lost focus, and was rejected a few hours later.

If an interviewer asks you to do something like this, treat it as a routine check, even if it does not feel like one. Some things that help:

• Just do it, and say something light: “Sure, there you go.” Then carry on where you were.
• If you naturally look away to think, say so early: “I tend to look off to the side when I’m working something out.” Said early, it heads off a doubt before it forms.
• Offer to share your whole screen rather than a single window if they seem unsure.
• Narrate your thinking. Half-formed thoughts said out loud are what real problem solving sounds like, and they leave no long silence for doubt to fill.
• Keep notes on paper, not in another window, if you want a list of your stories in front of you, and mention it: “I’ve got a few notes here about my projects.” Most interviewers are fine with that when you say it up front.

Is it allowed to use AI during an interview?

There is no single answer, because it depends on the employer, the round, and where you live. Three things to check before any interview:

1. The employer’s rules. Read the invitation email and any candidate guide. Some say no AI at all, some allow it for specific rounds, and many say nothing. When they say nothing, you can ask: “Is it fine to use AI tools in the coding round, or would you rather I didn’t?” Breaking a stated rule can get you removed from the process, as Amazon’s guidance spells out.
2. The platform’s terms. A proctored test usually comes with a statement you agree to before you start. That agreement is the rule for that test.
3. Recording and transcription laws. Any tool that transcribes a call is processing what the other person says. In the United States, federal law allows recording with one side’s consent, but a group of states, including California, require everyone on the call to agree. Other countries have their own rules, often under data protection law. This is not legal advice; if you are unsure where you stand, look up the rules for your location and the interviewer’s, or ask before the call.

Is using AI to prepare different from reading answers off a screen?

People talk about “using AI in interviews” as one thing. It is really three, and they carry very different risks.

Preparing with AI before the interview

This is allowed almost everywhere and it is where AI helps most. Paste the job description and your CV into a chatbot and ask for the ten questions you are most likely to get. Ask it to play the interviewer and push back on your weak answers. Have it check whether your project story has a clear result. Then practise out loud, without the screen, until you can tell each story in your own words. None of this is visible on the day because it lives in your head.

Glancing at a short prompt when you are stuck

This is the grey zone. Picture the moment your mind goes blank on “Tell me about a time you handled conflict”. A note that says “payments migration, disagreed with PM on launch date, shipped a week later with fewer bugs” is enough to get you talking. You glance once and then talk about something you really did. It looks like someone checking their notes, because that is what it is. Whether this is acceptable depends on the employer, so the rules in the section above apply.

Reading full answers word for word

This is the version interviewers catch, for every reason on this page. Your eyes track the text, your voice goes flat, the words do not sound like you, and the first follow-up exposes it. It also does not work in the long run. If you get the job on answers that were not yours, you then have to do the job.

What does PiriPiri AI hide, and what can it not hide?

PiriPiri AI is a desktop app for macOS and Windows that listens to both sides of a live call (your microphone and the interviewer’s audio on your computer), transcribes them, and drafts short answers on a small floating overlay using your CV, the job description and the role you pick. Since this page is about being seen, here is what is true about it.

What is true

• The overlay asks the operating system to leave it out of screen capture, so it does not appear when you share your screen or record in the usual way. On Windows 10 (version 2004) and later the window is removed from captures. Developer documentation for this setting notes that some newer Mac capture tools may still pick such windows up, so do a test call with a friend on the exact app you will use (Zoom, Meet, Teams or Webex) before you rely on it.
• No bot joins the meeting. Nothing appears in the participant list, and the app works with Zoom, Google Meet, Microsoft Teams, Webex and others because it runs on your own machine.
• After the call, the live transcript and notes are saved to your account, so you can review what you were asked and how you answered. That is useful whether or not you used a single prompt.

What is also true

• Leaving the overlay out of a capture does not hide your behaviour on camera. Your eyes and your pauses are still visible, and every signal described above still applies.
• It cannot give you experience you do not have, and follow-up questions go straight to that.
• It does nothing about a phone camera, a proctor watching your webcam, or a rule that says no AI. If the employer or the test says no outside help, do not use it in that round.

How to use it so it helps rather than hurts

Choose a concise answer style and treat each draft as a reminder of which story to tell, then look at the interviewer and tell it yourself. Use the deep dive hotkey (Cmd+Shift+6 on Mac, Ctrl+Shift+6 on Windows) only when you want more detail to prepare from, not to read out. Try it in a mock interview with a friend before any real one, so you learn how little of a draft you actually need to look at. There is more on how the category works in what an AI interview copilot is, and answers about screen sharing and supported apps in the FAQ.

Questions people ask

Where to go next

Most of what keeps you from looking like you are reading is preparation. Start with how to prepare for an interview, and if your worry is freezing, read what to do when your mind goes blank. For coding rounds, the coding interviews page and a one-week coding plan cover the practice side. If you are weighing whether a copilot is worth paying for at all, see is an AI interview copilot worth it, or compare the tools.

If you decide to try PiriPiri AI, it is about $2.50 an interview with one-time packs, no subscription, and 3 free sessions to start, so you can run a practice call and a screen share test before a real interview. Full prices are on the pricing page.