Faisal Journals
๐ŸŸก KANGAROO HEALTH

Loom Audit Guide

Step-by-step panduan merekam video audit menggunakan Loom: script per scene, tab preparation, dan delivery tips.

๐ŸŽฌ Loom Audit Guide

Overview

Loom videos are powerful for demonstrating your QA skills without live coding. Perfect for showcasing your technical test, explaining your approach, or doing a pre-interview walkthrough.

Why Loom?

  • Demonstrate communication skills
  • Show technical depth beyond resume
  • Bypass live coding anxiety
  • Stand out from other candidates
  • Let them see your thought process

Audit Video Types

Type 1: Technical Test Walkthrough

Purpose: Showcase your completed technical assignment Length: 5-10 minutes When: After submitting technical test

Type 2: QA Framework Demo

Purpose: Show you can build a test framework Length: 10-15 minutes When: During application or before interview

Type 3: Platform Audit

Purpose: Demonstrate initiative and healthcare interest Length: 5-8 minutes When: After researching KangarooHealth


Pre-Recording Checklist

Tab Preparation

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚                    YOUR SCREENS SHOULD BE:                   โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚                                                              โ”‚
โ”‚  โœ… Clean browser with ONLY relevant tabs open               โ”‚
โ”‚  โœ… No personal tabs (email, social media, etc)              โ”‚
โ”‚  โœ… Bookmark bar hidden or organized                         โ”‚
โ”‚  โœ… Dark/light mode consistent                              โ”‚
โ”‚  โœ… Zoom at 100% for readability                            โ”‚
โ”‚  โœ… Fresh terminal (if showing code)                        โ”‚
โ”‚  โœ… GitHub repo ready and public/private shared               โ”‚
โ”‚  โœ… Loom extension installed and logged in                    โ”‚
โ”‚  โœ… Test running smoothly (no flaky failures!)               โ”‚
โ”‚                                                              โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Environment Setup

ElementRecommendationWhy
BackgroundClean desk or virtual backgroundProfessional
LightingFace well-lit (not backlit)Clear visibility
AudioUse headset mic, test audio firstNo echo/distortion
CameraEye-level, slight angleNatural look
Screen resolution1080p or higherCrisp code display

Tools to Have Open

  1. Terminal with your project
  2. GitHub repo (relevant page)
  3. Browser with application under test
  4. Notes (if needed for script)
  5. Loom ready to record

Script: Technical Test Walkthrough

Scene 1: Introduction (30 seconds)

"Hi [Name], I'm Faisal. For this video, I'll walk you through my
technical test submission for the Senior QA Automation Engineer
position at KangarooHealth.

I'll cover: the approach I took, key design decisions,
how I handled the requirements, and a quick demo of the working code."

๐ŸŽฏ Keep it brief and enthusiastic

Scene 2: Project Structure (1 minute)

"Here's my project structure. I organized it with a clear
separation between E2E tests, API tests, and shared utilities..."

SCREEN: Show folder structure in terminal
SPEAK: Explain each directory's purpose

๐ŸŽฏ Show clean, professional organization

Scene 3: Framework Architecture (2 minutes)

"Let me explain my framework design. I chose the Page Object
pattern because..."

SCREEN: Show key files (playwright.config.ts, base classes)
SPEAK: Explain design decisions and trade-offs

๐ŸŽฏ Demonstrate strategic thinking, not just code

Scene 4: Demo - Run Tests (2-3 minutes)

"Now let me show you the tests running. I'll execute the full
suite, then zoom in on a specific E2E test..."

SCREEN: Run `npx playwright test` in terminal
SPEAK: Comment on what you're seeing
ACTION: Click on a passing test to show the output

๐ŸŽฏ Show tests passing, explain any interesting patterns

Scene 5: Code Deep Dive (2-3 minutes)

"Let's look at one specific test to explain my approach..."

SCREEN: Open a test file
SPEAK: Walk through the code line by line

Include:
โ€ข How I structured test data
โ€ข Assertion strategy
โ€ข How I handled async/waits
โ€ข Page Object usage

๐ŸŽฏ Demonstrate code quality and QA thinking

Scene 6: CI/CD Integration (1 minute)

"Finally, I added GitHub Actions for CI..."

SCREEN: Show GitHub Actions workflow file and recent runs
SPEAK: Explain the pipeline stages

๐ŸŽฏ Show DevOps competence beyond test writing

Scene 7: Closing (30 seconds)

"That's the overview of my technical test submission.
Key takeaways:
1. Page Object pattern for maintainability
2. API + E2E test coverage
3. CI/CD pipeline for automated runs

The repository link is in the description.
Happy to discuss any part in more detail.

Thanks for watching!"

๐ŸŽฏ Clear summary, call-to-action, professional close

Script: QA Framework Demo (For Application Phase)

Scene 1: Hook (30 seconds)

"Before you decide to interview me, I want to show you
something that demonstrates my QA thinking.

I built a Playwright test framework from scratch for a
similar healthcare platform use case..."

๐ŸŽฏ Grab attention immediately

Scene 2: Problem Statement (1 minute)

"Here's the problem: Testing a device-agnostic platform
requires covering multiple device types, protocols, and
data formats.

My approach was to..."

SCREEN: Show diagram or architecture
SPEAK: Frame the problem clearly

๐ŸŽฏ Show problem-solving ability

Scene 3: Solution Walkthrough (5-8 minutes)

SCENE 3A: Device abstraction layer (2 min)
"First, I created a device factory pattern..."

SCENE 3B: Test data management (2 min)
"To handle test data, I built..."

SCENE 3C: CI/CD pipeline (2 min)
"For continuous testing, I integrated..."

SCENE 3D: Reporting (1 min)
"I added Allure reporting for..."

๐ŸŽฏ Progressive complexity, technical depth

Scene 3: Results (30 seconds)

"Results:
โ€ข Test execution time reduced by 60%
โ€ข Coverage increased to 85%
โ€ข 3 critical bugs caught before production

Code is available at [link]. Questions welcome!"

๐ŸŽฏ Quantifiable impact, professional close

Recording Tips

Do's

TipWhy
Pause before speakingAvoid ums, stutters
Use cursor highlightingHelp viewers follow
Speak slower than normalClarity on video
Pause recording during setupLoom allows pause!
Preview before finalCatch mistakes early
Keep videos under 10 minRespect viewer time

Don'ts

MistakeHow to Avoid
Long pausesScript key points
Racing through codeSlow down deliberately
MumblingSpeak clearly, project voice
Messy screenClean up before recording
No sound checkTest audio before recording
Forgetting to recordLoom extension shortcut ready

Loom Settings

Quality:           1080p (or highest available)
Camera:            On (or off if not confident)
Microphone:        Headset preferred
Shortcuts:         Set up before recording
Editing:           Trim start/end
Thumbnail:         Auto-generate or custom

Keyboard Shortcuts (Mac)

ShortcutAction
โŒฅ + RStart/Stop recording
โŒฅ + PPause
โŒฅ + SStop
โŒฅ + TToggle camera
โŒฅ + MToggle mic

Delivery Checklist

Before hitting send:

  • Watch full video once
  • Check audio is clear
  • Verify all links work
  • Add timestamp chapters (optional)
  • Write clear description with links
  • Copy video link
  • Test link in incognito window

Email Template

Subject: QA Framework Demo + Technical Test Submission

Hi [Name],

I recorded two videos to complement my application:

1. Technical Test Walkthrough (7 min)
   [Link]
   Covers my approach and key design decisions

2. QA Framework Demo (12 min)
   [Link]
   Shows how I'd tackle device-agnostic testing

Code repository: [GitHub link]

Happy to discuss any part in detail.

Best regards,
Faisal Affan

Action Items

  • Set up Loom account (lovely.studio or loom.com)
  • Clean up browser and prepare tabs
  • Install Loom extension
  • Test audio/video quality
  • Write script for your video type
  • Record introduction scene first
  • Practice with one test recording
  • Record full video
  • Review and trim if needed
  • Share via email or LinkedIn
Edit on GitHub

Last updated on