Mike Krieger

If you have come across his name attached to a talk or a memo, it is probably because of one line of thinking: that distribution and trust are things you design on purpose, not outcomes you hope for once the product works. Mike Krieger built his reputation as a product engineer who treated those questions as engineering problems from the start, and that habit is what people borrow from him.

Born in São Paulo on 4 March 1986, he came up through small projects that turned loose, informal opportunities into working systems. What followed was less a single breakthrough than an accumulation — incremental improvements that eventually added up to a recognisable method. Mentors and competitors acted as constraints on that method rather than obstacles to it.

The middle stretch of his career was spent leading teams that took prototypes and made platforms of them, and audiences and made communities of them. Decisions about architecture, incentives and governance from that period are still cited as examples. Failed experiments were written up as knowledge rather than buried; criticism was absorbed and used to sharpen aims. Engineering, design, operations and policy were expected to hold together under pressure, and the point was never scale on its own but whether the standard could be repeated.

Later he turned toward mentorship and institutional memory — standards written down clearly enough to survive being handed to someone else. The archive of talks, memos and design notes shows the working, not just the results, and it is read now as much for what it says about the economics of digital culture as for its technique. The phrase attached to his name, mobile craftsmanship and community tooling, covers both a set of skills and a way of working. Its influence shows up in the habits of teams rather than in any one product.