1. Use skips to build relationships and share insight
This is the very idea behind skip level meetings. You need them the most, when you’re not involved closely with the team’s work on a daily basis.
2. You get feedback about the in-between manager
Management doesn’t have hard metrics. You can only tell how well a manager is doing by getting feedback from their team. It’s not spying. Everyone should know about it, and you can either reward them or help them improve.
3. Skipping more than one levels can get taxing
Skip level one-on-ones are great. However, when you’re skipping two levels or more, you may need to streamline the process, and meet with an entire team.
This is barely the tip of the iceberg. If you want a deep dive into skip level meetings from two different points of view, check out the full interview:
Here are some key takeaways you can start working on right away:
1. Trust and psychological safety
It’s the manager’s job to create a space where the team members trust each other, and aren’t afraid to fail. This is the foundation of a happy team.
2. Realize that everyone is different
You need to understand that each person has different priorities. The Moving Motivator cards are a great way to lay down the groundwork for understanding each other.
Whatever position you’re applying for, go through the job ad, and tailor your CV. Highlight or add any relevant experience you might have.
2. Highlight achievements
Highlighting achievements, projects you’ve delivered and their impact is a great way to get attention. Very few applicants do this, but it shows a business mindset, and awareness of your work beyond the code you write.
Senior management certainly has to be on board, but it's best if your entire engineering department is clear on why creating a career ladder for them is necessary.
Here are some key takeaways from the interview for leveling up engineers:
1. Pair programming is the most effective way to learn. If you want developers to grow quickly, pair them up with a more senior engineer, and it's guaranteed that both people will take away a lot.
2. As an engineering manager you can hand out stretch projects to your developers.
They get an interesting piece of work, and get to see if they want to grow their skills in that direction. You get to see if they show promise for another role.
It's a win-win.