So you’ve put a lot of time time into coding.
You’ve been doing this for a while: you’ve worked with different technologies and solved different problems with different people.
And now you are wondering what is next for you.
Should you learn more tech?
Should you start leading people?
What you do know is that you want to tackle bigger problems, and have a bigger impact.
You know that the individual growth path doesn't do it for you anymore.
Maybe people around tell you should go for the Tech lead role, that you have all it takes already.
But you are not sure.
Starting to get some clarity
It’s ok to feel scared and confused about this role. It’s a big step.
There are some things you can do to start addresing this:
Find out your work style
This can give you some insights on what from your work style might attract you to the Tech Lead role.
What are you currently doing that requires leadership skills?
Eg.: leading an initiative, mentoring people with less experience
Assess where you are on Tech Lead skills
Pull up the Tech Lead expectations list in your current company
Rate yourself on each expectation on a scale from 1 to 10 (10 being awesome)
An 8? Why an 8?
Whatever the number -> think about examples from your day to day that justify that number
Anything lower than a 10? -> What is it missing for you to get to a 10?
If you cannot come up with anything, you might already be a 10 😉
Get feedback
Apply the same 1->10 methodology with people around you
Create a form where you ask people to rate you from 1 to 10 on each Tech Lead expectation:
On a scale from 1 to 10 how do you feel I am doing in the <> topic?
Ask them for examples to support the number:
“Please share one example”
“What is missing for me to get to a 10?”
⚠️ The goal is not for you to rate 10 in every aspect! ⚠️
You don’t need to know everything about the role before jumping into it.
No one expects you to do so!
Even more, there are skills required in the Tech Lead role that can only be developed in the role because you need access to people and visibility that you cannot get in a Senior Developer role.
Check for inconsistencies between your assessment and the feedback
Identify blind spots: you might have more skills than you thought or you might get some clear improvement areas that you can start working on right away.
How do you feel about going for the Tech Lead role now?
Still not sure?
Stop overthinking! The best way to really know is to try it out.
Just go for it!
Is never the perfect time to do anything so if you are thinking about it, you should go for it now.
Look for an opportunity in your current job
Display interest: tell everyone around that you want to go for this role, most importantly your manager.
Extend your search beyond your current job
Do a quick search on LinkedIn for Tech lead roles.
Find one that is interesting to you, that you think: .. Hmm , I could do this 🤔
Keep in mind: the Tech lead role means different things in different companies.
Find a role that aligns with your view on the Tech Lead role.
Take each expectation from the job description and think about examples from your experience that can prove you can meet that expectation.
Update your CV.
Apply, and see how far you get in the process!
You might be closer than you think! 😉
The best part about just trying it it’s that it saves you time: overthinking, going back and forward.
You either get the role or
you get a list of things to improve that you can start working on right away.
Reminder: leadership skills can be learned and developed just like any tech skill.
What if I realise I don’t like the Tech Lead role?
Simple!
You can always go back to doing what you were doing before. 🙂
All that knowledge does not go away.
Need help?
➡ Let’s talk about it! Book a free call with me here
➡ Or just reply to this email with your questions
➡ If you are not already subscribed and want to see more content like this press the button
Next edition: First 30 days as a Tech Lead
Thank you so much for being here! ☀️
Remember: you are not alone on this journey 😊
Until next time,
Ane