Most growth companies are starved for experienced leadership. As they expand, continued growth builds up pressure on their existing leadership. This gets quite stressful! The rare executive manages to build an effective organization solely by investing in their existing team, but most supplement their organization with some external hires to maintain a balance of folks who’ve seen it before and folks who’re actively learning their role.| lethain.com
Long term, I believe that your career will be largely defined by getting lucky and the rate at which you learn. I have no advice about luck, but to speed up learning I have two suggestions: work at a rapidly expanding company, and make your peers your first team.| lethain.com
Shortly after a senior leader joins a new company, sometimes you’ll notice them quickly steer the organization towards a total architectural rewrite. Perhaps this is a switch from batch to streaming computation, perhaps a switch from a monolith to a services architecture, perhaps it’s a rewrite into a new programming language. If you take a few minutes to reflect, I bet you can identify several times where you’ve had this experience. Regardless of the proposed technical change, it’s a...| lethain.com
We use our Leadership Principles every day, whether we’re discussing ideas for new projects or deciding on the best way to solve a problem. It’s just one of the things that makes Amazon peculiar.| amazon.jobs
Standardizing on a given platform or technology is one of the most powerful ways to create leverage within a company: improve the tooling a bit and every engineer will get more productive. Exploration is, in the long run, an even more powerful force, with successes compounding over time. Developing an investment thesis to balance the ratios and timing of standardization and exploration is a core challenge of engineering strategy.| lethain.com
Fork this template on Google Docs Healthy engineering organizations make a lot of technical decisions. Many of those decisions impact multiple teams (Frontend, Backend) and functions (Engineering, Product, Customer Success, Finance). It’s normal to either feel like you’re moving too slow (“too many stakeholders in every decision”) or that your reckless pace creates frequent rework as issues are discovered late (“this problem would have been obvious if you’d just talked to Security...| Infrastructure Engineering
