The log is the artifact. There is no certificate.
One entry per mock, and any lesson day you want to keep. Write it from your attempt. If you write it after reading the reference, you are logging the lesson, not yourself.
Use TEMPLATE.md. Copy it into private notes. This site only ships the template. Do not commit your writeups here: they are your gaps, not the course.
What goes in
- The problem, in one line, as it was given.
- The assumptions you actually locked, including the ones you later think are wrong.
- A score from 1 to 4 on each rubric dimension, with evidence from your page.
- One gap. Not a list. The gap decides the next thing you practice.
Scores do not get rewritten after you read the reference. You may add a single amendment line.
Rubric dimensions
The same six every mock. Day 7 defines the anchors. Later mocks do not invent new axes.
- Requirements
- Estimates
- API and data
- Design
- Deep dive
- Failure and ops
A senior interview is mostly 3s. A staff interview wants a 4 on the deep dive and on failure, not a 4 for drawing more boxes.
Kit hookup
When the kit exists, its design log is this template, not a second format. The kit grader may quote your entry. It may not design the system for you. You do not need that grader to fill the template.