…time. While he was making an important decision, it was like many other important design decisions. If he made the right one, his work would be lost to obscurity. Yet, if he screwed the design or engineering up, it would be all anybody would talk about.
…rove conversions by 0.4%. But if you look at the whole experience, it’s really starting to degrade. That’s the type of result you get when you myopically optimize your product based on data points and single-digit improvements to conversion, without considering the overall experience.
…on leading to accelerated development releases leading to compounding product growth. Increasingly, a company’s ability to compete and innovate on a product is driven by how successfully it can apply analytics to mine for insights across vast, unstructured data sets from disparate sources. In other words, the future belongs to data-informed companies.
…Look for examples of times when they’ve compromised on scope in order to deliver something quickly. Though it can be tough to build something you know is imperfect, great engineers are willing to make the compromises that deliver value to users faster.
Great engineers want to know that users are benefiting from their product. Ask about who uses something that they’ve built, and why it’s useful to those specific people. After all, users are ultimately the ones who decide whether we did a good job.
Great engineers care about not just what they’re working on, but why it’s important. Ask about what they’re working on right now, and why it’s important to them. Mission is important, and nobody should feel great about working on something ‘because they told me…