Short answer
Show case studies that prove the workflows you want to be hired for, with clear responsibility, tools, results, evaluation, and safe redaction.
- Decide if this page applies to: Builders with several projects who need to choose which examples belong on a profile.
- Check first: The case matches the role category you want.
- Avoid this mistake: Choosing the most famous project instead of the most relevant one.
Use this page for
Turn ability into screenable proof
The point is not to list everything. Make it clear what you owned, what you can deliver, and which evidence needs protection.
Start
Decision context
Decision criteria
The case matches the role category you want.
Next action
Create Builder profile
Decision context
Choose cases by target role. A RAG role needs retrieval and evaluation evidence; an automation role needs workflow reliability; an agent role needs tool use and failure handling.
Evidence to inspect
Prefer cases with clear problem, personal responsibility, tool choices, result, maintenance notes, and privacy-safe proof.
Boundary and next step
A smaller set of relevant cases is stronger than a long list of shallow examples.
What you still need to confirm yourself
- Confirm whether the role scope, budget, timeline, and communication expectations fit you.
- Decide what client names, screenshots, files, or personal details should stay private.
- Use interviews or written follow-up to clarify responsibility, contract terms, and data access before starting work.
Decision criteria
Common mistakes
- Choosing the most famous project instead of the most relevant one.
- Hiding weak responsibility behind a long tool list.