5 Actionable Takeaways For (not just) aspiring Tech Leads
From The Conversation About Tech Lead Role with Anemari Fiser
In the last episode of Software Engineering Tales with
, we explored the role of the tech lead from all possible angles.Challenges, myths, common pitfalls, and how to transition into it successfully.
Anemari shared insights from her experience as a former tech lead at Thoughtworks, as well as her work training and coaching over 300 tech leads in the past three years.
Here are five key takeaways from our discussion:
1. Define the Tech Lead Role Clearly
Sometimes the lines between a tech lead and a team lead get too blurred.
While some companies separate these roles, one focusing on technical decisions, and the other on people management, it is not very common.
And that can be a source of issues.
Because many organizations merge them, the role might not be set clearly.
This lack of clear boundaries and definitions can lead to conflicts or inefficiencies if expectations are not explicitly defined.
According to Anemari, the solution is simple but often overlooked: clear communication and most importantly - setting expectations early.
2. Shift Your Skills from Engineer to Leader
A common mistake companies make is just promoting their best engineers into tech lead positions without preparing them for the shift in responsibilities.
Technical expertise is crucial, a must-have. However, success in this role requires strong people skills. The mindset shift can be massive.
Facilitation, alignment, stakeholder communication, and conflict resolution - all can be daily tasks for the tech lead.
Many tech leads struggle because they attempt to maintain their full coding workload as they used to while taking on leadership duties, leading to burnout and frustration.
3. Master Time Management
One of the most frequent struggles Anemari encounters with (fresh) tech leads she mentors is time management.
Many new tech leads try to do everything!
Continuing to code extensively while managing meetings, aligning stakeholders, and guiding the team.
The reality is that something has to give.
Effective tech leads learn to delegate, prioritize, and accept that their value now comes from enabling the team rather than being the top individual contributor.
4. Be Intentional About Learning and Growth
Staying relevant in tech is a constant challenge, but Anemari advises against learning just for the sake of learning.
Instead, she recommends being intentional.
You should understand what skills are necessary for your current or future role. After that, you can integrate learning into your day-to-day work, and set clear goals to measure progress.
Also, without proper boundaries, the drive for continuous learning can lead to burnout.
And burnout is always a huge setback.
5. Make Your Work Visible
A crucial yet often overlooked factor in career advancement is visibility.
Many engineers and tech leads do great work but fail to showcase it effectively. According to Anemari, "Spend twice as much time showcasing your work as you do completing it."
Whether it's through documentation, presentations, or proactive stakeholder communication, ensure your contributions are recognized, don't just wait for others to notice them.
It can be essential for career growth.
Remember, No One Is Perfect
Even the best tech leads make mistakes, and Anemari shared a particularly painful lesson from her own experience.
During a critical project, Anemari’s team and the client reached a deadlock over a key technical decision.
With high stakes and a looming deadline, she worked hard to find common ground, going back and forth between both sides to reach an agreement.
But time was running out. In the end, she made the decision to go with the client’s choice.
It was only then that Anemari realized the unintended impact of her approach.
Her team felt blindsided, thinking they had more say in the decision than they actually did. By keeping the discussion open for too long, she unintentionally added to the uncertainty, making the final choice feel sudden and disempowering.
Her mistake? Trying too hard to get consensus instead of taking ownership of the decision.
You can watch the whole conversation packed with information on YouTube:
 | A guest post by
|