One of the hallmarks of a great engineer is the ability to execute.

An engineer who can execute gets things done. They crush tickets, pump out designs, spin up features, answer critical data questions, improve models, and prototype new ideas quicker than their peers.

How to Execute

Engineering projects are subject to many forces that jeopardize their success. New feature requirements, unexpected complexity, unclear data or experiment results, system failures, team churn, competing priorities, organizational tensions, and an infinite number of similar factors lurk like hyenas on the outskirts of every project.


A strong executor will cut through this noise to consistently deliver. They are ruthless prioritization machines. They strip each deliverable to its essence and simplify aggressively. They anticipate obstacles like a running back: charting a path, and then bobbing and weaving their way to success.

Bobbing and Weaving

But the true heart of execution is closing the loop. Executors understand that a project is in the most danger between its inception and the production launch of its V0 MVP. Every concurrent refactor and tooling migration presents a massive organizational and technical roadblock that a “not yet launched” system will need to overcome. The longer a project stays in this state, the more such refactors and technical migrations will appear, and the deeper the project will fall behind.

Launch, monitor, improve

Executors are determined to close the loop quickly. They remain focused through the noise, optimize their time, and cancel meetings when necessary. Execution is its own ability, distinct from technical acumen. Executors must know which corners to cut.

Execution is also distinct from technical leadership. The strongest executors do not always know the right systems to build, or how to build them. Similarly, the best technical leaders do not need to be the strongest executors. But any good technical lead must be able to mentor and support the executors on their team.

Building an Executing Team

Engineers who can execute are sought after commodities: the scrappy and determined lifeblood of an engineering organization who set the pace for the team. An engineering leader must be able to hire and retain strong executors to build a strong team.

Within an organization execution ability is easy to see. Strong executors consistently achieve their goals. As a result, most healthy organizations are naturally set up to reward strong executors. Good engineering leaders point their best executors at the most ambitious, most well formed goals in the organization.

However, execution ability can be harder to see from the outside. This skill set is almost entirely uncorrelated with status symbols like impressive universities or companies. Similarly, technical interviews do not emphasize execution ability.

All is not lost however: execution ability is highly correlated with prioritization skills, which is not too difficult to assess in an interview. Good prioritizers often have many examples of situations where they prioritized successfully. An engineering leader who can sniff out this skill will have a major advantage in building a highly successful team.