What an Interview Can't Measure, Put Somewhere Visible

Conclusion first: a one-hour interview cannot measure the most valuable thing a hands-on builder has.

Why? An interview measures real-time expression — how you talk, how smoothly it comes out, how fast you react on the spot. But the ability to take a system from zero to one is years of accumulation: the pits you stepped in, the trade-offs you made, the messes you cleaned up. That does not compress into one hour. No interviewer, however good, can compress it. So in the same hour, the fluent talker has a natural edge, and the person with deep accumulation may never be seen.

To be fair about it: fluency is not a sin — communication is a legitimate part of an engineer’s job — and interviewers don’t have a better instrument; an hour is an hour. Nobody is at fault here. The problem is bandwidth: interviews measure expression, and expression is not accumulation.

My fix isn’t to complain about the system. It’s to route around the bandwidth limit: put the work where it can be seen. Build a tool, ship it publicly. Write the process up as posts. Write the decisions down as docs. If you want to know what my field is and how deep the work goes, you don’t need to hear me talk — look at what I’ve made. This site is the implementation of its own argument: every post you’re reading, every card on the tools page, is something you can verify without ever interviewing me.

This path has a cost: building things and writing them up takes time. What it buys is concrete: a full record of everything I’ve done along the way — and it’s mine, not company IP. At work I build the company’s product; on my own time, the same skill set goes into my own things. So wherever I end up, the capability travels with me, ready to build whatever system a team needs built. That’s the profession. This site is my work journal: field by field, a record of what I’ve actually done.