Create a compact digital evidence pack to share in interviews
Prepare a 1–3 file digital evidence pack you can share in interviews—what to include, how to format it, timing, email and screen-share scripts, and privacy tips.
Interviewers often ask for examples, artifacts, or proof of impact. Instead of fumbling through multiple links or screenshots, a compact digital evidence pack gives you a clean, rehearsed way to show your work.
This guide walks you through what to include, how to structure 1–3 concise files, when and how to share them in different interview formats, and how to protect sensitive information so you look prepared without oversharing.
Why a compact pack beats scattered links
Interviewers appreciate clarity. Sending five different links, a messy Google Drive with unclear filenames, or trailing into a long portfolio walkthrough wastes time and raises doubts about your organization.
A compact evidence pack—one short PDF plus one optional slide or code snippet—lets you surface the exact artifacts that back your claims, keep control of the narrative, and adapt to live or asynchronous interview formats.
- Saves interviewer time: they see the key evidence fast.
- Keeps the story focused: every file maps to a specific claim or answer.
- Reduces risk: you share only what you intend to, not entire repos or private data.
Decide the pack format and size
Aim for 1–3 files total. Each file should be scannable in under two minutes. Typical combinations work well: a one-page impact summary (PDF) plus a 3–5 slide quick case study (PDF) or a short runnable code snippet (single file or Git link).
File types to use: PDF for readable, camera-agnostic content; single-slide PDFs for visual storytelling; a single Gist or small repo for code, with clear README and a single runnable example. Avoid sending full design files, unfiltered datasets, or long slide decks.
- Essential: one-page impact summary (PDF, 1, max 2 pages).
- Optional: short case study (3–5 slides or 1–2 page PDF) focused on one project.
- Optional: one short code sample or live demo link with explicit instructions.
What to put in the one-page impact summary
This page is your elevator-proof. Lead with a 1-line role story (who you were, the context), a concise problem statement, the actions you took (3 bullets max), and measurable outcomes. If metrics aren’t available, use comparative outcomes (before vs after) or qualitative impact tied to stakeholders.
Add one short evidence line for each claim: link to a report, a screenshot reference (see next section), or a quotation from a stakeholder. Keep formatting minimal—clear headings, bold numbers, and an at-a-glance metrics row.
- Top: 1-line role story (one sentence).
- Middle: problem → actions (3 bullets).
- Bottom: outcomes with 1–3 metrics and source notes (e.g., “A/B test +12% conversion; internal KPI deck Q3”).
- Footer: one-line note on data sensitivity or permission if needed.
How to craft a 3–5 slide case study
Use slides only to show process and a clear artifact. Slide 1: context and objective. Slide 2: the constraint or key insight. Slide 3: the solution and your role. Slide 4: results (charts or bullets). Slide 5 (optional): what you’d do next or trade-offs you made.
Keep visuals simple—one chart or screenshot per slide with a short caption tying it to your contribution. If you show UI or internal dashboards, blur or redact sensitive elements and include a note about what was removed.
Preparing a short code or demo file
If your role requires code samples, pick a single small example that demonstrates the skill the interviewer cares about. Include a README with a few lines: what the file shows, how to run it, and expected output. Make the demo runnable in under five minutes.
Prefer links to small public gists or repos. If anything references proprietary work, recreate a minimal example that mirrors the approach without disclosing company secrets.
- One runnable example, well-documented.
- A README with run instructions and expected results.
- Clean commit history optional; the focus is clarity, not polish.
Privacy, permissions, and sensitive content
Never share raw internal documents, customer PII, or anything covered by an NDA. If your evidence is derived from internal work, either reconstruct a redacted version that preserves the learning, or summarize the impact without sharing screenshots.
Add a short permission line on your one-page summary, e.g., “Redacted for privacy; available to discuss further under NDA.” This shows respect for former employers and avoids awkward follow-ups.
- Redact or recreate: never leak raw internal data.
- Note permissions on the summary so interviewers know why a screenshot might be missing.
- If asked for more detail, offer to share in a follow-up with appropriate controls (NDA, private meeting).
Practice sharing the pack in the formats you’ll encounter: email, chat link, and screen share. Rehearse a 30–60 second narrative for each file so you can introduce it cleanly and move on.
A compact digital evidence pack signals preparation and respect for the interviewer's time. It gives you agency to prove key claims without oversharing—use it to make your strongest evidence visible and easy to discuss.