Why employers ask for a work sample—and what to scope

When an employer asks for a job application work sample, they want to see concrete evidence you can perform a task, communicate results, and think through tradeoffs. That doesn’t mean handing over confidential team deliverables or months of raw files. Your first step is to define the scope and confidentiality boundaries: what the sample must demonstrate, how much of the original material can be shared, and whether you should redact identifying information.

Quick scoping script

Ask the requester: “Which skill or outcome should the sample show? Is a one-page summary acceptable, or do you need source files? Do you require original client names or can I anonymize?” Getting answers up front prevents wasting effort and avoids accidental breaches.

Choose a concise project artifact

The most effective job application work sample is a single, focused artifact: a one-page case summary, a 2–4 minute screen recording, a cleaned dataset with a README, or a short code snippet with comments. The point is to make it easy for the reviewer to judge your ability in 30–90 seconds. Long portfolios are appropriate later; an initial sample should show a complete thought.

Examples of concise artifacts

• Design: One mockup with annotations (PNG) plus a 200–300 word rationale.
• Writing: One edited article or campaign email with a two-sentence brief and before/after highlights.
• Data/Analytics: A CSV with 100–500 rows and a 150-word summary of the method and findings.
• Project coordination: A 1-page timeline showing a specific deliverable you owned, plus your RACI line.

Explain your contribution honestly

Employers can usually tell when a sample is overstated. Be explicit about what parts you led, collaborated on, or only supported. Use a short contribution statement that accompanies the sample. Honesty builds trust and lets interviewers ask targeted follow-ups.

Mini-template: Contribution statement (use with your artifact)

Project title: [Short title]
My role: [e.g., lead analyst, content writer, UX designer]
Team size: [number]
My direct tasks: [3–6 concise bullet points]
Outcome: [measurable result or qualitative impact]
Confidentiality actions: [redacted names/data; permissions obtained]

Worked example: anonymizing a client report

Scenario: You led a 6-week market analysis for a client and an employer requests evidence of your analytic ability. You cannot share the client’s presentation due to an NDA. Here’s a step-by-step way to produce a compliant, useful sample.

1. Extract the core insight: choose the single finding that best illustrates your method (e.g., “identified three underpriced customer segments”).
2. Create a one-page summary: include objective, approach, three charts (or simplified tables), and a 150-word conclusion.
3. Anonymize and reduce: replace client names with descriptors, remove exact revenue figures if restricted, round numbers (e.g., $2.1M → $2M) and note this in the statement.
4. Add the contribution statement template filled in.
5. Estimate reviewer time: design the one-page summary so it reads in under 90 seconds; three simple charts are enough.

Numerical check: if a chart displays conversion rates, show percentages rounded to one decimal place (e.g., 3.7% → 3.7%). If the original dataset had 12,342 rows, share an anonymized sample of 500 rows and note the sampling method.

Common mistakes and how to avoid them

• Oversharing confidential details: Always re-read NDAs and get permission if unsure. When in doubt, anonymize and explain.
• Producing a disconnected fragment: The reviewer should not need the full project to understand your sample. Add context and a concise contribution statement.
• Submitting raw dumps: Raw logs, long slide decks, or unfiltered code without comments make evaluation harder. Curate the sample.
• Ignoring format instructions: If the job posting requests PDFs, do not send a Google Drive link unless asked.

Realistic variations for limited resources

If you lack permission to share past work or don’t have prior examples, build a short, realistic mock that demonstrates your skill. Treat it like a 1–2 day take-home project and label it clearly as hypothetical. Employers accept this when you show process and judgment.

Low-resource mock example

For a community volunteer applying to a fundraising coordinator role: draft a two-month micro-campaign plan (one page) with target audience, three tactics, and a simple budget table. Include an estimated reach calculation (e.g., email list 2,000 × 8% open rate × 2% click-to-donate = ~3 donations) to demonstrate analytical thinking.

Reusable checklist before you send

• Confirm scope: Did you clarify what the employer needs?
• Protect confidentiality: Redact or anonymize as required.
• Keep it concise: One page or 2–4 minute video is ideal.
• State your contribution: Use the mini-template with exact tasks.
• Format and delivery: Use requested file types, name files professionally.
• Time estimate: Add a 1–2 sentence note on how long the reviewer will need.
• Permission log: If you sought client or employer permission, keep that record.

Sources and scope

No external references are required for the practical steps in this article. I did not cite external research; the guidance comes from standard hiring practices and legal considerations around confidentiality. This draft is educational and not legal advice—if you have a binding non-disclosure agreement or complex intellectual property concerns, consult the agreement or a legal professional.

For related career guidance, see Better Lifestyle’s start-here page: Start here.

Use this workflow as a draft: a hiring manager may ask for variations, so keep samples modular and be prepared to discuss specifics during interviews.