Last week, I interviewed a friend who got to Staff (IC6) at Google by 28 in an unusual way.

Developing Dev's resource offers insights, tutorials, and resources for software developers and technology enthusiasts. Readers can learn about coding best practices, software architecture patterns, and emerging technologies. With articles, tutorials, and code samples, Developing Dev provides  guidance and expertise for building software applications and advancing technical skills.

The Developing Dev

A software engineer who quickly advanced to Staff IC6 at Google shares insights on how working fewer hours but focusing on impactful projects can accelerate career growth. Key skills include understanding what work drives the biggest impact and managing the soft skill of saying 'no' effectively. It's important to be selective with your work to protect your time and ensure career advancements.

What You Work On >> How Hard You Work

But how can we get ourselves assigned that impactful work? You talked about how to say no to protect time for the impactful work, but who’s assigning us the impactful work? Is it referring to the side projects? As juniors, we get assigned all kinds of maintenance tasks and have fewer chances of getting assigned the big, impactful upcoming features. How can we say no to those tasks or at least ask for a part in those newer features where most of the growth and impact lies?

Saying no to work seems so foreign to me. I work on a very small team, and just about everything that comes down the pipeline is always mission critical. It’s very rare we say no to anything. Good read to see another perspective.

Time management is a key part of getting work done. The more I work in the IT field, the more time management I have to do lol.
Don’t forget to stretch your back!!!

Fascinating, if mercenary, perspective.