Contrary to conventional wisdom, a distinguished engineer advises senior engineers to delegate the most challenging, interesting work. They should instead take on necessary but unglamorous tasks, which builds immense credit and allows junior engineers to grow faster on high-impact problems.

Instead of a traditional product roadmap, give engineers ownership of a broad "problem space." This high-agency model pushes them to get "forward deployed" with customers, uncover real needs, and build solutions directly. This ensures product development is tied to actual pain points and fosters a strong sense of ownership.

When hiring senior technical talent, the most valuable skill isn't just coding proficiency but the ability to take an abstract business problem—like designing a logistics system—and translate it into a functional technical solution. This skill demonstrates a deeper understanding that connects work to real-world value.

At Kayak, when a junior team member offered a valuable insight, they were immediately assigned ownership of the project. This tactic transforms meetings from passive status updates into active empowerment sessions, fostering a culture of ownership and accelerating talent development.

A critical career inflection point is moving from solely executing tasks (writing code) to influencing strategic decisions about what problems to solve. True value and impact come from being in the room where decisions are made, not just being the person who implements them.

Gain influence by curating a backlog of valuable "side quest" projects that address team pain points. Proactively offering these well-defined opportunities to other engineers helps them meet their career goals and establishes you as a key network hub and leader.

When a team understands each member's "why," they can self-organize to solve problems. Junior employees no longer need to escalate issues; instead, they can identify and pull in colleagues best suited for the task, fostering agency and execution speed.

To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.

An engineering team's velocity is often bogged down by non-engineering work, which can consume a significant portion of their time. A leader's primary role in accelerating projects is to identify and systematically remove these obstacles, freeing engineers to focus on creative problem-solving and core design tasks.