Crux is when you’re learning and digging deeper technically. How do you approach taking ownership and growing your impact on not just the project but across the team and larger axis?
I feel like there's 2 separate goals here:
Becoming More Independent
This is actually something I haven't thought too much about, but I would frame my thoughts here across 2 core tactics:
Building Larger Scope
To set expectations, this is a process that usually takes a long time, even if you're very hard-working and talented. It can take longer if a company is more traditional and focused on levels (this holds back talented junior engineers) and shorter if the company is rapidly growing and everyone gets more scope than they can chew by default (i.e. rocket startups).
I like Alex's answer, the other thing to add is "act with urgency". A great way to increase impact is to just jump in.
Usually there'll be some buffer built in for project planning, and that gives engineers the permission to properly plan things out and perhaps slow down. Instead, the best engineers hit the ground running on day 1, and make meaningful progress a lot faster.
I think that both of these answers are great so far. I've been working with mentees a lot as there is such a plethora of information out there and they're getting hit with it at 70 hrs a week rather than taking it slower and using the 20-30 hrs they would have spent working bootstrapping themselves instead. To aid this, I've cultivated a lot of material I've looked at in my own right and share at a pace they find appropriate. All titles are available and I've also curated a YouTube playlist with a lot of helpful content from 1 hr webinars I've watched along the way. But engaging mentors, building learning roadmaps, picking up bit by bit is a good way to rock this.