Leading Team Software Engineer

In this virtual panel, we explore what made people decide to become a leader and how they did it, and we'll find out if we really have to leave tech forever or if there's a way back into engineering. This TensorBlue analysis is based on reporting and source material from InfoQ (https://www.infoq.com/articles/leading-team-software-engineer/).

What Happened

InfoQ Homepage Articles Leading Tech People or Remaining a Software Engineer: What to Choose? Panel Discussion

Leading Tech People or Remaining a Software Engineer: What to Choose? Panel Discussion

During their career, software engineers may need to decide between going into management or staying in a tech position.

Good communication abilities, experience in building relationships, knowing how to design something, and being able to solve problems, are some of the skills that you can reuse in your management position.

To foster high-performing teams, give them time and space to do their work, trust them, and be transparent by sharing what you have with them.

In a staff+ you can combine engineering and people management responsibilities and remain involved in deep technical issues and problem-solving while driving vision and strategy.

If you feel a need to do tech work while being in a management position, you can spend time with tech engineers, do personal tech projects, or consider moving back to a tech position.

Sooner or later, software engineers come to a point in their careers where they can make their move into management positions. It could be a tech lead position, team leader, development manager, (senior) architect, staff plus engineer, or another position where they become responsible for managing tech people. One question senior tech people ask themselves is:s

Shawna Martell: When I first started in tech almost twenty years ago, I only knew of one type of leadership role, and that was people management. I didn’t hear about an "individual contributor (IC) career track" until I’d been working for more than ten years, and by then, I’d been a people manager twice. If I’d known there were other options, I might have taken a different path. Management is an important and valuable form of leadership. I won’t pretend I’ve ever felt "ready" for management or leadership. That’s imposter syndrome for you. When I was offered my first management role, I was very hesitant. What finally convinced me was my manager’s encouragement. Further proof of how important good managers are for any organization. But management and leadership aren’t synonyms. I’m a leader now, as a Senior Staff Engineer, but I’m not a manager. I didn’t feel ready to take on the leadership role of Senior Staff Engineer either, but again I was fortunate to be surrounded by people who encouraged me and offered to support me. I’ve taken every leadership role because people I trusted encouraged me to do it. I’ve stayed in leadership because it turns out to be work I really love. Leaders are organizers and cheerleaders and visionaries. They use their influence to make the people around them better.

InfoQ

Implications for Product and Engineering Teams

For TensorBlue readers, the useful question is not just what happened, but how this changes product architecture, engineering priorities, AI delivery, observability, team workflows, or executive decision-making.

• Review whether this changes your AI roadmap, platform architecture, or engineering operating model.
• Identify the specific workflow, reliability, governance, or developer-productivity lesson that applies to your organization.
• Convert the lesson into a small production experiment with measurable quality, latency, cost, adoption, or risk metrics.
• Document source assumptions clearly so teams do not overgeneralize from incomplete public information.

TensorBlue Takeaway

The practical opportunity is to turn this signal into a concrete implementation decision: better AI systems, stronger product instrumentation, more reliable automation, and clearer technical governance. Teams that connect public technology shifts to their own delivery systems will move faster without adding unnecessary complexity.