Break Out of Your Silo: The Path to Staff Engineer
3 factors to gain visibility and advance in your technical career ladder
One of the first things you have to do on your path to the Staff Engineer role is to build strong cross-department relationships.
You cannot advance from Software Engineer to more impactful roles, such as Staff Engineer or Principal Engineer, if people donโt know who you are.
In todayโs issue, I will explain 3 factors you can focus on to grow in the technical ladder related to being seen outside of your Engineering organization.
1. Start with Small Interactions
One simple way to start with this is by joining other chat channels outside of your team. An honest presentation opens many doors. Also, asking about what those teams are doing will demonstrate true interest and will give you a better reception.
Attending company meetings is another good way to start interacting with people in the organization. I encourage you to not focus only on the Engineering organization, but also on others, like Product, Support, Professional Services, etc.
๐๐ผ One thing I do from time to time is join production incidents from other teams. Doing so, you not only get more experience in thoseย ambiances but also provide support and care to other teammates. Just one rule to do this: Be supportive and help if you can; if you cannot, be quiet and give folks the space to work (they will appreciate it).
2. Collaborate on Cross-Team Projects
This is about being an active listener. You have to know which projects and initiatives are happening across the organization.
If you see an opportunity, jump into it. Remember this ๐๐ป
Itโs Better to Ask For Forgiveness Than Permission
For example, you noticed that a Staff Engineer has been assigned a small project, with a wide impact, and not many risks. Do not hesitate to send her/him a message like:
Hey, Iโve noticed that you have been assigned to project โXโ and itโs a field Iโm trying to learn and improve. May I ask if I can help you on your duties?
With a sentence like that you are demonstrating your willingness to learn, work, and collaborate with someone outside of your comfort zone.
๐๐ผ The outcome of this action is that you will help other departments achieve their goals and you will be seen outside of your organization.
3. Learn Key Business Metrics
You have to understand how the business works so you gain clarity on how your contributions align with and influence the companyโs larger goals.
The more clarity you get, the more you can focus your efforts on having an impact outside of your group or organization.
For example, maybe your team implements integrations with other APIs and puts the data in a database. Thatโs it? most likely not. That data could be used by the Professional Services team or Business Intelligence team to provide highly valuable reports to your CEO.
๐๐ผ Knowing the reach range of your work will help you to open your mind and find new ways to have an impact outside of your team.
โจ Takeaways
This newsletter issue focuses on a real-life case with actionable steps that have proven effective for many others before you. These insights come directly from my own experience.
Letโs wrap up for today with some takeaways for building relationships outside your team:
Begin with Simple Connections: Engage in Slack discussions, participate in all-hands meetings, or schedule casual conversations.
Partner on Cross-Functional Initiatives: Actively look for ways to assist other teams in reaching their objectives.
Familiarize Yourself with Business KPIs: Recognize how your efforts contribute to the companyโs overarching success.
๐๐ผ Strengthening cross-department connections makes you visible and builds trust with decision-makers.
We are more than โจ743 subscribersโจ, thank you all for your trust.
You rock! ๐๐ผ
๐๐ง ๐บ๐ฐ๐ถ ๐ฆ๐ฏ๐ซ๐ฐ๐บ๐ฆ๐ฅ ๐ต๐ฉ๐ช๐ด ๐ฑ๐ฐ๐ด๐ต, ๐ต๐ฉ๐ฆ๐ฏ ๐ค๐ญ๐ช๐ค๐ฌ ๐ต๐ฉ๐ฆ ๐. ๐๐ต ๐ฉ๐ฆ๐ญ๐ฑ๐ด!
๐๐ง ๐บ๐ฐ๐ถ ๐ฌ๐ฏ๐ฐ๐ธ ๐ด๐ฐ๐ฎ๐ฆ๐ฐ๐ฏ๐ฆ ๐ฆ๐ญ๐ด๐ฆ ๐ธ๐ช๐ญ๐ญ ๐ฃ๐ฆ๐ฏ๐ฆ๐ง๐ช๐ต ๐ง๐ณ๐ฐ๐ฎ ๐ต๐ฉ๐ช๐ด, โป๏ธ ๐ด๐ฉ๐ข๐ณ๐ฆ ๐ต๐ฉ๐ช๐ด ๐ฑ๐ฐ๐ด๐ต.
I'd also add:
> Become more familiar with the business context. For Senior+ engineers, I think that it's vital not only to solve coding problems but also to solve some critical business/domain-wise ones.
I like this quote: Itโs Better to Ask For Forgiveness Than Permission
Another way to put it: Tell, don't ask!