Roles
Same engineer, different job to be done. Each page opens with a scenario from that role's actual week, not a puzzle, and shows the order I would work in.
None of these pages contain a skills list or a proficiency bar. A requirement is answered by the system where I met it, or it is not answered.
A background job has been failing quietly for eleven days. It retries, so nothing alerted. Some records are duplicated and some are missing, and nobody knows which. That is the week this role is actually for.
Finance says the reported figure is wrong. Engineering says the query is correct. Both are right, which means the disagreement is not about the query at all, it is about which definition is the real one.
A feature has been in progress for three weeks. The API is done, the interface is done, and it does not work, because the two were built against different assumptions and neither person was wrong.
Support says the system is slow. The traces say every request is fast. Both are true, and the gap between them is where the actual product problem lives.
A customer opens a ticket saying they can see a record that is not theirs. Everything else stops, because that sentence is the worst one a multi-tenant system can produce.
Two engineers disagree about an approach. Both arguments are good. The team has been circling it for two weeks and the cost of the delay now exceeds the difference between the options.
Timezone is usually the first thing a distributed team checks and the last thing a candidate explains properly. So here is the arithmetic, and what I actually do with the hours.
The condensed version of all of it is on the CV .