What “Zero Footprint” Actually Means — And Why Only One Interview Copilot Has It

Defining “Footprint”

A footprint is any artifact of running software that is visible to a party other than the user. In the context of a live interview with screen sharing, footprints include:

• 01Taskbar button — an entry in the Windows taskbar that reveals a running application
• 02System tray icon — an icon in the notification area that indicates a background process
• 03Window chrome — title bar, borders, close/minimize/maximize buttons that identify a window
• 04Browser tab — a tab in the browser tab bar with a page title and favicon
• 05Extension icon — an icon in the browser toolbar indicating an active extension
• 06Click target — a focusable surface that can be accidentally clicked, stealing focus from the coding environment
• 07Screen capture visibility — the window appearing in screen share, screen recording, or screenshot output

Each is a detection surface. Each can reveal to an interviewer that you're running additional software. Zero footprint means eliminating all of them — not most, not the obvious ones, all of them.

How faFAANG Eliminates Every Footprint

Footprint 1: Taskbar

skipTaskbar: true is set on all three BrowserWindows (control, pane, pane_history) at creation time. No taskbar entry exists for any faFAANG window. If the interviewer looks at your taskbar, they see your coding environment, your video call, and nothing else.

Footprint 2: Window Chrome

All three windows are created with frame: false and transparent: true. No title bar. No border. No close button. No minimize/maximize buttons. No visible window decoration of any kind. The windows render their content directly onto the screen with no surrounding chrome.

Footprint 3: Browser Tab

faFAANG is a native Electron desktop application. It does not run in a browser. There is no browser tab with a page title and favicon. There is no URL bar showing a suspicious domain. There is no tab to accidentally leave visible in the browser's tab bar. The browser has zero knowledge that faFAANG exists.

Footprint 4: Extension Icon

faFAANG is not a browser extension. There is no extension icon in any browser toolbar. There is no manifest.json to scan. There is no extension ID that proctoring tools can detect. Interview platforms that scan for known AI copilot extensions will find nothing, because there is no extension to find.

Footprint 5: Click Target

In Coding Mode, the pane window runs in click-through mode by default. It is non-focusable, meaning it cannot receive mouse clicks or keyboard input. All mouse events and keyboard input pass directly through to the underlying application — CoderPad, HackerRank, or whatever coding environment is beneath it.

You cannot accidentally click the overlay. You cannot accidentally tab into it. You cannot accidentally give it focus. It is readable — you can see the content — but interactionally invisible. When you need to toggle interactivity (e.g., to scroll in Experience Mode), you press Ctrl+W, a global hotkey that fires without changing focus.

Footprint 6: Screen Capture Visibility

SetWindowDisplayAffinity(hwnd, WDA_EXCLUDEFROMCAPTURE) is applied to all three windows. This Win32 API call instructs the Windows Display Infrastructure to exclude these windows from all capture output. The exclusion happens at the compositor level — before any screen capture tool sees the pixel data.

Zoom, Google Meet, Microsoft Teams, OBS, Windows Snipping Tool, third-party screenshot utilities — none of them can capture these windows. The windows exist in a capture-excluded layer that only the local display renders.

The Live Interview Scenario

To make this concrete, walk through a realistic scenario:

You're 30 minutes into a coding interview on CoderPad. The interviewer is on Zoom. They ask you to share your entire screen. You share it.

What the interviewer sees: Your desktop. CoderPad in a browser tab. The Zoom call window. Your text editor if you have one open. Nothing else. No overlay. No extra windows. No taskbar buttons. No browser extensions. A clean, normal-looking developer workstation.

What you see: Everything the interviewer sees, plus the faFAANG overlay positioned alongside your code. The pane window shows AI-generated suggestions. The control window is available for commands. The pane_history window holds previous responses.

The overlay exists in a capture-excluded layer that only your local display renders. The Zoom capture pipeline never sees these pixels. They are excluded at the Windows Display Infrastructure level before the capture API can access them.

The interviewer asks you to Alt+Tab. You do. They see your open windows — the browser, Zoom, maybe VS Code. faFAANG's windows don't appear in the Alt+Tab list because they're configured with skipTaskbar: true and no standard window properties that would surface them in the task switcher.

The Zero Footprint Checklist