I work as a senior iOS engineer on a team with 2 iOS developers (including me), 2 Android developers, and 3 backend developers. While we are all senior engineers, one backend developer, one iOS developer, and one Android developer have been at the company longer and possess deeper knowledge of our systems. As a result, they have more influence over priorities and how the team operates.
I’m trying to make a bigger impact and carve out my own space, but I’m finding it challenging because it feels like there isn’t much room for me to step up.
What are my options to navigate this situation effectively?
That Android engineer pretty much sounds like the position I'm currently in my org. So the perspective that I can share is how did I get into this position.
I'd boil down my experience to 2 themes:
Hope this helps!
Thanks for the detailed insights. I will start doing that :)
Jonathan gave a lot of excellent points with very specific tactics on finding scope. On the other hand, I have a higher-level, broader approach that starts off with a simple realization: (almost) Every senior engineer wants to get to staff.
Let's keep up the simple ideas: In order to get to level X, you need to be able to create scope for level X-1. So if the senior iOS engineer on your team wants to become a staff iOS, they need to be able to create high-quality projects that are comfortably senior level.
Tactically, this means my recommendation is to just talk to the senior iOS engineer and see what big, ambitious ideas they have on their backlog. Reassure them they can bring on the "sushi grade" and raw ideas are okay - It's expected for high-performing senior engineers to work through lots of ambiguity anyways. An interesting way you can tease out these ideas is to have a 1 on 1 with them and ask them a question like this: "If you had a magic wand and could solve any problems across the team, what would you do?".
Software engineers are always looking for projects and scope, but those are downstream artifacts. In order for those to exist, you need to start off with a problem. If you have just a problem, that is enough to create scope.
All of this rests on the assumption that your goal right now is more to solidify your reputation as a high-performing senior engineer, not start seriously pursuing the jump to staff.
Here's some other resources I recommend checking out as well: