Browser-first by default: the core session works in the browser. Local VM and advanced tooling are optional only.

Project Interview Guide

Short talk track for presenting the project clearly in an interview or portfolio conversation.

60-second version

  • This was a personal volunteer proof of concept with a real delivery objective: build a browser-first AI Night system for Scouts and Venturers.
  • I started in an unfamiliar technical space, investigated options, and corrected the architecture once the evidence showed browser-first was the lowest-friction participant model.
  • I then turned that into a managed project-light effort with stakeholder-specific content, validation, packaging, status tracking, and a clear distinction between validated work and external dependencies.
  • The result is both a working delivery system and a portfolio example of right-sized project management.

2-minute version

  • The project began with ambiguity and overlapping ideas about websites, local environments, and optional technical paths.
  • I treated it as a project-light effort: enough planning and control to manage scope, risks, and delivery quality, but not heavy enterprise ceremony.
  • A key decision was moving to a browser-first model and making advanced technical tooling explicitly secondary. That reduced participant friction, parent concern, and session-night support risk.
  • From there I built the role-based content, exercises, facilitator materials, platform model, validation flow, archive cleanup, and packaging outputs.
  • I also documented the PM thread so the work can be discussed as a controlled delivery effort, not just as a technical artifact.

Questions to be ready for

  • Why did you choose a project-light method instead of a full PM framework?
  • What changed during the project and how did you control that change?
  • How did you handle uncertainty in a domain that was new to you?
  • How did you decide what not to build?
  • What evidence shows the work is real and validated?

Strong supporting artifacts

  • Executive summary
  • Case study
  • Phases and status page
  • Participant workbook solution
  • Validation artifact and packaged overlay