Portfolio

Who Portfolio is for

For engineers who finish a project, move on, and two years later cannot remember the numbers. Documenting it while you still know them is the entire idea, and it is the difference between a CV bullet that persuades and one that describes.

What Portfolio does

Portfolio holds a record per project: what it was, your role, the technologies, and — the part that matters — what changed as a result. It generates a narrative from those facts, and projects push directly into your CV rather than being retyped from a hazy memory of a system you have not touched since. It also links to the applications a project supported, so you can see which work you keep leaning on.

• →Per-project record of role, stack, outcomes and impact
• →AI-generated narrative from your recorded facts
• →One-click push into CV bullets
• →Links to the applications a project supported

How Portfolio works

1. 01

   Record the project while it is fresh

   Role, stack, and what actually changed. The specifics are what you will have forgotten in a year.

2. 02

   Capture outcomes, not activities

   What improved and by how much. This is the difference between a bullet that persuades and one that lists.

3. 03

   Generate the narrative

   A written account built from the facts you recorded, ready to adapt.

4. 04

   Push it into your CV

   Projects feed CV bullets and cover letters directly instead of being rewritten from memory each time.

What Portfolio does not do

Portfolio is documentation, not a public showcase — there is no published portfolio site, no shareable link and no hosting, so it feeds your applications rather than being one. It cannot import from GitHub or measure impact for you; the numbers come from you, and vague inputs produce vague narrative. It does not verify anything you record.

Common questions

Works well with