List the evidence the role needs
For each target responsibility, ask what artifact could demonstrate it: code and tests, an analysis memo, a design case, a runbook or a project decision record.
A portfolio should fill evidence gaps rather than repeat the same tutorial in different colors.
Prefer finishable constraints
Choose one user, workflow and measurable outcome. Add one difficult constraint such as messy data, accessibility, reliability or migration.
Avoid planning a large platform whose unfinished scope prevents testing and explanation.
- Target responsibility
- User or stakeholder
- Constraint
- Finished output
- Reviewable evidence
- Limitations
Create variation across projects
Use projects to show different strengths: implementation, debugging, communication and decision making. Reusing one dataset or stack is acceptable only when the question changes meaningfully.
Remove copied tutorial language and cite external assets or code appropriately.
Maintain what you publish
Check deployments, dependencies, links and contact information. Archive broken projects rather than leaving insecure or misleading demos online.
State the date and scope of the work.
Official tool pages
Use these pages to verify current capabilities and terms. Links go to the providers or, for JobsScoutHQ, the relevant on-site directory.
Frequently asked questions
Can course projects go in a portfolio?
Yes when labeled and extended honestly. Explain your contribution and do not present guided work as an original client project.