- What is a technical lead?
- What are the most important behaviours for technical leads to exhibit?
- What most inspired you about your previous technical leads?
- Why do you want to be a technical lead?
- What scares you most about being a technical lead?
- How do you measure success as a technical lead?
- What one thing would make your life as a technical lead easier?
- How much coding should a technical lead do?
- What responsibilities are you happy to delegate, and what do you want to control?
- How do you plan for your own absence, so you can rest on holiday?
- What qualities do you want your team to have, and how to you help them get that?
- How do you deal with conflicts in the team?
- How do you deal with external pressures on the team?
You can also find the questions at the CodeCraftConf Technical Lead session on Github if you would like to run the session yourself.
My thoughts, which may change during the session are:
A technical lead provides the direction, vision, enthusiasm, and occasionally the kick up the bum for the team, and helps to clear obstacles. They should lead by example and should care deeply about the wellbeing of the team, and the success of the project, which cannot succeed without a successful team. They should keep their technical knowledge, and domain knowledge up to date, as they are asked to make a lot of decisions, and whilst they should defer and demonstrate confidence in their team, they cannot get respect without the being able to make the decisions and ask tough questions to make sure the decisions made by the team are correct. I’ll cover the rest in a future post.
Source: CodeCraftConf by @codecraftuk