In this guide
A technical portfolio is most useful when a reviewer can understand the problem, inspect the method, and see what you checked. A complicated dashboard with unexplained assumptions may reveal less than a small, well-documented exercise. Start with a narrow question and material you are entitled to use.
Boston’s Analytics Team page, checked October 2, 2026, links to Analyze Boston for municipal open data. Public availability does not remove the need to inspect a dataset’s documentation, permissions, and privacy risks before using or redistributing it.
Choose a safe demonstration
A self-created synthetic dataset is often the simplest starting point. Make clear that the records are invented and that findings describe the demonstration only. If using public data, preserve the source, retrieval date, relevant license or terms, and known limitations. Avoid unnecessary person-level details even when they are publicly visible.
Do not transfer a former employer’s files, code, credentials, internal screenshots, or customer records into a personal portfolio. Removing names is not always enough to make an artifact safe. Recreate the general method with synthetic inputs when you can do so without revealing protected information or violating obligations.
Give the project a bounded question
Choose something that can be answered within a small, reviewable artifact. For data work, this might involve detecting inconsistent categories or explaining missing values. For software work, it might involve validating a fictional request form or testing a simple transformation. For technical operations, a mock troubleshooting checklist may be more relevant than an unrelated app.
Hypothetical example: a learner creates invented maintenance requests with missing dates and duplicate identifiers. The project flags those conditions, explains how they are handled, and produces a summary of the synthetic records. It does not claim to measure Boston operations or recommend staffing changes.
Show the checks alongside the result
- Describe what each input field means.
- Record assumptions and choices about missing or inconsistent values.
- Include at least one normal case and one edge case.
- Explain how someone can reproduce the output.
- State what the project does not establish.
For an analysis, examine denominators, units, time periods, and exclusions before drawing conclusions. For code, show relevant tests and expected behavior when input is invalid. A chart’s visual polish does not compensate for an incorrect comparison, and a successful demonstration does not prove reliability under every condition.
Write for a reader outside your specialty
Open with a short summary of the problem and why the method is useful. Then provide the technical detail needed for inspection. Explain acronyms, label charts clearly, and include a text description of the main finding. Use accessible colors and avoid requiring a viewer to distinguish information by color alone.
Make authorship transparent. Identify your own contribution, collaborators’ contributions where appropriate, and substantial outside tools or templates. If a tool generated code or analysis, verify it and be prepared to explain it. Do not claim independent expertise in a method you cannot yet inspect.
Decide whether the portfolio belongs in the application
Check the posting and submission instructions before adding links or attachments. A portfolio is not a replacement for required qualifications, experience entries, or requested materials. If sharing is permitted, provide the smallest relevant artifact and test its access from a signed-out view without exposing a private folder.
- Remove secrets, private records, and unnecessary metadata.
- Verify every source and permission statement.
- Label synthetic and self-directed work prominently.
- Test links, files, and reproduction steps.
- Keep an exact copy of the version you shared.
Use the six-week learning plan to keep the project manageable, then run the materials quality check. A strong portfolio demonstrates careful work and honest limits, not an unsupported claim that a practice project makes you ready for every municipal technical role.
Related reading: Build a Six-Week Municipal Career Learning Plan, Give Your Application Materials a Final Quality Check.