ShipLog
Your impact, with receipts.
Performance review season should not be an archaeology exercise. ShipLog keeps a running, evidence-linked record of what you actually shipped and why it mattered — written continuously, not reconstructed in a panic.
- built for
- Individual contributors
- Staff+ engineers
- Engineering managers
Why this exists
Why ShipLog exists
Engineering careers are evaluated on a written record, and most engineers do not keep one. So twice a year the same thing happens: a frantic scroll through merged pull requests, a half-remembered incident, and a self-review that undersells eight months of work because the evidence expired.
The people who do well in that process are not always the people who did the most. They are the ones who wrote it down.
ShipLog is the boring habit made automatic — capture continuously, link the evidence, and let review season be an export rather than an excavation.
Capabilities
What it actually does.
Continuous brag doc
Entries are captured as work happens, linked to the PR, incident or doc that proves it. Six months later the evidence is still there.
Impact, not activity
Prompts that push past "shipped feature X" to the outcome, the scope and the people it unblocked — the three things review calibration actually weighs.
Ladder mapping
Your entries mapped against your company's own engineering ladder, so gaps are visible while there is still time to close them.
Under the hood
Specifications.
- Status
- Incubating — waitlist open
- Sources
- GitHub · Linear · Jira · manual
- Privacy
- Personal by default; nothing shared without an explicit export
- Target
- Q1 2027
Questions
The ones people actually ask.
Can my manager see this?
Only what you choose to export. ShipLog is a personal record first — if it were a surveillance surface, nobody would write anything honest in it.