How to Safely Screen Share in a Job Interview (Live Coding & Portfolio Reviews)

To screen share safely in a technical interview, present from a clean, dedicated setup: a fresh or guest browser profile with no logged-in accounts, Do Not Disturb on, every unrelated app and tab closed, and any secrets or personal details in your project blurred before you start. The goal is that the interviewer sees your code and your thinking — not your job hunt, your current employer's tools, or an API key in your .env.

Interviews are one of the most exposing screen shares you'll do: you're usually on your personal machine, often nervous, and the person watching is a stranger evaluating you. This guide focuses on the candidate sharing their screen in a live-coding round or portfolio review, then adds a short note for interviewers who share too.

What actually leaks when a candidate shares

In a live-coding interview you typically share a browser tab, an editor, or your whole screen. Each of these can carry more than you intend:

• Bookmarks and open tabs. A bookmarks bar or tab strip that names your *current* employer's tools, or reads like an active job hunt — other companies' careers pages, competing offers, Glassdoor — is awkward at best and a confidentiality problem at worst.
• Notifications. A Slack message from your current team, a recruiter's email, or a calendar reminder for another interview sliding into frame mid-answer.
• Other applications' materials. Your resume with a home address and phone number, an offer letter, a reference doc, or messages open behind your editor.
• Secrets in the coding project. A .env file, hard-coded API keys, database URLs or tokens visible in your file tree, terminal or a committed config — the classic live-coding leak.
• Personal information. Autofilled emails and addresses, a password-manager popup, browser autofill suggestions, or your name and account details in the corner of an app.

How to prep a clean setup

Spend five minutes before the call and none of the above can happen:

• Use a fresh or guest browser profile with nothing logged in and an empty bookmarks bar — or a separate profile you keep just for interviews. See hiding your taskbar and bookmarks.
• Turn on Do Not Disturb (macOS Focus, Windows Focus Assist) and quit chat and mail apps so nothing pops in. More in hiding notifications while screen sharing.
• Close everything unrelated — other tabs, documents and apps. Share a single window or tab rather than your whole screen when the format allows.
• Open only the project you'll code in, and blur or remove secrets first — move keys to environment variables you don't display, and blur the .env or config if it must be visible. The advice in hiding API keys in tutorial videos applies just as well here.
• Do a 30-second dry run: share to yourself, look at exactly what's in frame, and blur anything you missed.

For the things that must stay on screen but shouldn't be readable — a .env, a personal detail, a header naming your employer — blur them in the page with BlurFirst:

1. 1

   Set up a clean profile

   Open a fresh or guest browser profile with no accounts logged in and an empty bookmarks bar. Pin BlurFirst so it's ready.

2. 2

   Silence and close

   Turn on Do Not Disturb, quit Slack and mail, and close every tab and app you don't need for the interview.

3. 3

   Blur secrets and personal info

   Press Ctrl/⌘ ⇧ Y, then click any element — a .env block, an API key, your email in a header — to blur just it, or drag a box over a region. Run Scan to auto-detect keys, emails and phone numbers locally in one pass.

4. 4

   Keep the panic key ready

   If a notification or unexpected page loads mid-interview, press Ctrl/⌘ ⇧ H to blur everything instantly, then reveal your code again.

5. 5

   Share and stay calm

   Share your tab, editor or window. The blur is painted into the page as real pixels, so it survives Zoom, Meet, Teams and any recording the interviewer makes.

A pre-interview checklist

1. Open a fresh or guest browser profile — no logged-in accounts, empty bookmarks bar.
2. Turn on Do Not Disturb and quit chat and mail apps.
3. Close every unrelated tab, document and application.
4. Move secrets to environment variables; blur any .env, key or token that must be on screen.
5. Blur personal details — your address on a resume, autofilled emails, account info in app corners.
6. Do a 30-second dry run by sharing to yourself and checking what's in frame.
7. Keep the panic shortcut (Ctrl/⌘ ⇧ H) in mind in case something loads unexpectedly.

A note for interviewers who share

If you're the interviewer, the same hygiene applies with one extra duty: don't expose other candidates. When you screen-share an applicant-tracking system, a shared calendar, a spreadsheet of applicants or a scorecard, other people's names, scores and notes are often one column or tab away. Share a single window, blur the surrounding rows and columns, and keep your hiring team's chat out of frame. It's basic fairness to candidates and, where personal data is involved, a data-minimisation habit worth keeping.