[srdeveng]

IME, as someone who leveled up from jr to eventually sr in the same org over a 10yr period, the best advice I can give is be confident in your skills and be willing to take calculated risks.

Teams are always chasing deadlines and resolving unforeseen issues as they arise. The go-getter willing to volunteer to fix a problem that isn't already on their plate gets noticed.

You won't be assigned 'save the day' type work outright as a jr, but the team will find itself in a tight spot, and you need to volunteer to go above and beyond to help fix XYZ even though it's outside your domain.

If you succeed, you have everything to gain. Fail? You're the jr, at least you gave it the old college try while chipping away at your key tasks.

[mrisoli]

Leveling up in the same org is all about the company's cost.

Some companies(especially bigger ones with names that attract new grads) will deny you a promotion if they believe you are cheap to replace(denying a promotion often leads to employee unsatisfaction which causes them to leave).

Most companies, especially if they are having problems finding new engineers, will just give you a promotion to keep you happy and because they can't afford the time and costs of losing and employee, find and train the next one.

However, I think the article is more about personal improvement than proper leveling up within an organization, in which case it's not about being noticed.

[SomeStupidPoint]

Also, if the problem is above your skill level: take something routine off the plate of a senior engineer to free them up to tackle the big problem.

The work was going to get reassigned anyway, because it's more important that the senior guy fix a release blocking issue than do that work, but it makes you a proactive part of the solution, even when you can't directly contribute: you're still helping make sure all the ducks are in a row for release.