Member-only story
Working on projects with significant scopes and difficulties is one of the best ways to prove promo-worthy as we climb the engineer ladder. While having a large scope of projects is important, fine-tuning your behaviors on smaller scopes of projects is also necessary.
Smaller project scopes are less appealing to people who seeks promotions. But sometimes they are unavoidable due to teams’ priorities. In order to demonstrate promo-worthiness, we can still fine-tune our behavior on those projects because scopes and behaviors are independent.
For example, intermediate levels of software engineers, i.e. L4 at Google, require independence and significant level of self-driven decision making. On smaller scopes of projects, the design documents and the code implementations may be smaller. But during the design and implementation phases, the decision-making can still be demonstrated if we well documents them. We might encounter two types of implementation choices for the same logics, and we can document these decision-making process. Those artifacts can help your promotion process, together with larger scopes of projects.
