Build a professional FDE portfolio from anonymized evidence

Professional experience is valuable evidence, but a public portfolio must not expose client identity, records, credentials or confidential measurements. Strong anonymization often means recreating the proof rather than redacting a screenshot.

Build the decision artifact

Describe the problem class and your role at a safe level. Redraw the architecture, rebuild a minimal adapter with synthetic fixtures and recompute metrics on an authored dataset. Explain one failure, repair, trade-off and operational drill. Obtain authorized review before using any employer or client material; omission of a name alone may not remove identifying detail.

The commercial leadership lab makes the artifact inspectable with authored inputs:

from leadership_cases import portfolio_case

result = portfolio_case()
assert result["complete"] is True
assert len(result["forbidden"]) == 4
assert result["client_permission_claimed"] is False
assert result["reviewer"] == "pending"

The fixture contains seven recreated artifacts and a forbidden list covering client name, real record, credential and confidential metric. It claims no client permission and leaves reviewer status pending.

Protect the decision from weak evidence

Metadata, timestamps, schema names and distinctive numbers can re-identify a client. Review source history, screenshots and logs. If authorization is uncertain, use a fully simulated engagement and state that boundary prominently.

Keep these artifacts for review:

• synthetic brief and fixture provenance
• redrawn architecture and recreated code
• recomputed evaluation plus failure narrative
• privacy/IP review and explicit limitations

This practice aligns with the discovery, productisation, client enablement, technical leadership and capstone sequence in the FDE for Professionals course. The course link describes the pathway; the local scenario is fictional and does not claim a client engagement, investment result, hiring decision or certificate.

Practice task

Replace every client-specific element in one project story with an authored equivalent. Ask a reviewer whether they could infer the organization or confidential result.

Continue learning

This article is part of the Commercial judgement and delivery leadership sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Prepare for an enterprise AI architecture interview.
• Continue with Defend an enterprise AI capstone before a review panel.

Reference: UK NCSC: Information Risk Management.