Add to Chrome
← All articles
Guides6 min read

How to Record a Screen Demo for a Job Application or Portfolio

A step-by-step guide to recording a polished screen demo that shows employers or clients exactly what you can build — no watermarks, no uploads, no complicated software.

A written resume describes what you can do. A screen demo shows it. Whether you’re applying for a developer role, a design position, a customer success job, or a freelance contract, a two-minute video walkthrough of something you’ve built or a workflow you’ve mastered lands differently than a bullet point.

Here’s how to record one that looks professional — without paying for software or waiting through a render queue.

What makes a good demo recording

Before you hit record, it helps to know what you’re trying to achieve. A good demo recording has three characteristics:

It shows the real thing. Not a slide deck about the thing, not a description of the thing — the actual product, workflow, or output running live. If you built a web app, show the web app. If you’re applying for an operations role, record yourself working through a real (anonymized) example in the tools the job uses.

It’s short. Two to four minutes is enough for almost any demo. Attention drops fast when someone watches an unsolicited video, so every section should earn its place. Cut to what matters.

It has a clear structure. Open with what you’ll show (ten seconds), show it, close with the outcome or what it enables. No dead air, no hunting around for things to click.

Before you start: prepare the screen

Think of your desktop as a stage set. Before you record:

  • Close unrelated tabs and apps. A toolbar full of personal tabs or a notification from a messaging app introduces noise — and can leak personal information you didn’t mean to share.
  • Use a clean browser profile if you’re demoing a browser-based tool. Your production profile with all its saved passwords and history is usually the wrong context for a portfolio recording.
  • Zoom in. The person watching is probably on a laptop screen. If you’re demoing a web app at full 1440p resolution, text and UI elements will be tiny. Bump your browser zoom to 125–150% for anything text-heavy, or shrink your browser window to a 1080p-like viewport.
  • Clear your desktop if you’ll be switching windows. Desktop clutter in the background when you alt-tab out of a browser looks unprofessional.

Step 1: Set up ScreenKit

Install ScreenKit from the Chrome Web Store. It’s free, requires no account, and adds a small icon to your Chrome toolbar. Because it runs entirely inside Chrome, there’s nothing to configure on your machine.

Click the ScreenKit icon and choose your capture source:

  • A browser tab is the right choice if you’re demoing a web app, a browser-based tool, or any workflow that lives in the browser.
  • An application window is right for desktop software like a design tool, a code editor, or a productivity app.
  • The full desktop is right if you need to switch between multiple apps as part of the demo.

Step 2: Configure audio and camera

For a job application demo, narration matters. A silent walkthrough forces the viewer to guess what’s significant. A short spoken explanation — “here I’m configuring the API connection” — turns a click into a decision they can evaluate.

Toggle on your microphone in ScreenKit before recording. Keep the narration tight: describe what you’re doing and why, not what you can see on screen (they can see it too).

If you want your face on screen — a talking-head overlay in the corner — enable the camera bubble. It’s optional, but for roles where communication and presence matter (sales, customer success, consulting), it adds personality. For purely technical demos, it can be distracting; skip it.

Step 3: Record the demo

Hit record and walk through your planned structure:

  1. Open with a one-sentence context. “This is a dashboard I built for tracking support ticket resolution times.” Don’t spend more than fifteen seconds on setup.
  2. Walk through the key interactions. Show the most impressive or relevant parts first. If someone stops watching after a minute, they should have already seen the main point.
  3. Use ScreenKit’s annotation tools to draw attention to specific elements as you go — circle a metric, draw an arrow to a button, highlight a result. These visual cues do the work of “look at this” without requiring the viewer to follow your mouse.
  4. End with the outcome. “This reduced average resolution time from 48 hours to 6 hours over the first month.” Concrete results, briefly stated.

Step 4: Review and trim

After stopping the recording, ScreenKit drops you straight into a preview. Use the built-in editor to:

  • Trim the start and end (most recordings have a few seconds of dead time on each end)
  • Add any static annotations you want to hold across a section
  • Cut anything where you hunted around or repeated yourself

Export as WebM (for uploading to a portfolio site or attaching to a job application) or copy to clipboard if you’re embedding it directly.

Where to include it

In a GitHub README. A short GIF or embedded video of your project in action is among the most effective improvements to a technical portfolio. It tells the reviewer in fifteen seconds whether the project is worth reading about.

In a portfolio site. A demos section with two or three recordings of your best work — each under three minutes — is more persuasive than a longer written description.

In a job application email. “Here’s a two-minute walkthrough of [relevant project]” with a direct link or attachment stands out in a way that another resume attachment doesn’t.

In a follow-up. If you’ve had an interview and been asked to elaborate on a project, a five-minute recorded walkthrough sent the same day is a much more memorable follow-up than a written email.

Common mistakes to avoid

Recording your full desktop when only the app matters. A tab-only or window-only capture is cleaner and hides distractions.

Starting without a plan. Even a rough outline — what you’ll show, in what order, ending where — prevents the wandering-around quality that makes demos feel unprepared.

Using a watermarked tool. A watermark on a job application demo signals either that you didn’t bother to find a free tool or that you used a trial version of something expensive. ScreenKit is free with no watermark; there’s no reason to accept one.

Making it too long. If you can’t make the point in three minutes, make a two-minute demo of the most important part and offer to walk through the rest in a call.

Ready to record? Add ScreenKit to Chrome and film your first demo in the next ten minutes. Your portfolio will look different tomorrow than it does today.