I build InterviewAce , an AI tool for practising job interviews. This autumn I wrote two guest articles for other sites, and both turned out to be about something developers already like: treating a messy situation as a system you can measure.
One is for people interviewing for growth, CRO and product roles, where "tell me about an experiment you ran" is close to guaranteed. The other puts a price on a longer job search with a few lines of arithmetic you could run in a REPL. They are my own articles on other people's sites, so this is a guide to my work, not a neutral review.
Why engineers should care about the experiment question
You do not need a marketing title for this to matter. If you work on a product with real users, you have probably shipped something behind a flag, watched a dashboard and argued about whether the change worked.…