Build a portfolio around evidence rather than screenshots

A screenshot proves that one screen existed. A reviewer needs to see the problem, decisions, executable checks and recovery path.

Inspect an evidence map

The delivery lab builds a fictional portfolio record.

from delivery_cases import portfolio_case

result = portfolio_case()
assert result["screenshots_only"] is False
assert result["claims_supported"] is True
assert result["external_client_work"] is False
assert result["reviewer"] == "pending"

Lead with a concise problem and scope. Link source/data manifest, runnable repository, setup, architecture, ADRs, tests/evals, results, logs/health, threat model, cost, demo and runbook. Include one failure and repair. Label fixtures, mocks, local deployment and fictional-client work.

Use screenshots or video to aid navigation, not replace source evidence. Remove secrets and personal data. State your individual contribution and unresolved limits. Do not turn course work into invented employment or business outcomes.

The FDE for Freshers course builds ten-plus artifacts and a fictional engagement around verifiable work.

Exercise

Audit one project claim by claim. For every sentence, link evidence or weaken/remove it. Ask a peer to reproduce the normal and failure demo.

Continue learning

This article is part of the FDE career entry and client-delivery practice sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Design a user acceptance test for a client simulation.
• Continue with Prepare for an FDE debugging interview exercise.

Reference: GOV.UK service assessment guidance.