Most engineers focus on completing assigned work, but if you want to be a leader, you have to focus on outcomes.

• Identify recurring pain points. If deployments keep failing due to configuration issues, don’t just fix them—push for automation or better validation checks.
• Take responsibility for the team’s success. If onboarding for new hires is slow, document common issues and create a starter guide.
• Improve what slows the team down. If code reviews take too long, propose a structured review process and get buy-in from the team.

It's not about getting more work done. It's about how you can make your team more effective, so that you get the right work done better.

If there’s no formal leadership role, step into an informal one.

• Help junior engineers level up. When reviewing PRs, don’t just leave comments—explain why a change improves maintainability or performance.
• Run mini-training sessions. A 20-minute walkthrough on debugging, system architecture, or best practices helps everyone.
• Make documentation better. If common issues aren’t documented, write them up and share them. This small act makes you a go-to resource.

The fastest way to prove you’re a leader is when others naturally come to you for guidance.

If you want to get noticed, you need to look beyond your team to the goals of your entire company.

• Solve long-standing coordination gaps. If teams keep running into misaligned dependencies, create a shared roadmap and align with stakeholders.
• Own cross-functional projects. If multiple teams need to work together on an infrastructure change, step in as the unofficial lead and drive clarity.
• Improve collaboration tools. If discussions constantly get lost in Slack, set up a lightweight decision-tracking process.

Don't just be high performer, make everyone around you perform better.

Many engineers are hesitant to push for improvements because it is not their job, or they do not have the "authority". Forget that.

• Fix inefficient processes. If sprint planning is chaotic, suggest a clearer format and facilitate the next one.
• Push for better development practices. If deployments are painful, introduce small improvements like feature flags or automated rollback strategies.
• Highlight risks before they become failures. If a rushed project will lead to tech debt, call it out and suggest mitigations.

The more you drive positive change, the more people see you as a leader.

Tech leads don’t just write good code—they communicate in ways that drive action.

• Frame updates around impact: Instead of saying, “I added a caching layer,” say, “I reduced response times by 40%, improving the user experience.”
• Run effective meetings: If meetings lack direction, step up. Summarize key points, clarify decisions, and define next steps.
• Handle conflict professionally: If engineers disagree on a technical approach, step in and drive resolution—compare trade-offs, align priorities, and get consensus.

If people trust you to communicate clearly and make decisions, leadership becomes inevitable.

If there’s no clear growth path in your company, you don’t have to wait—you can build one yourself.

When you take action, leadership follows.

Becoming a leader in tech isn’t just about skill—it’s about shifting how you think and work. That’s exactly what Gregor Ojstersek and I explored in our recent article:

5 Mindset Shifts Needed to Grow from Engineer to Leader

In it, I break down:

✅ Why technical skills alone won’t make you a great leader

✅ How to shift from solving problems to enabling others

✅ The right way to give feedback that builds trust

✅ Why emotional intelligence matters more than you think

If you’re serious about growing into leadership, don’t miss it.

Read it here

1️⃣ Pick One New Habit

Choose just one thing to apply this week. Whether it's taking ownership of a team issue or improving communication, step-by-step action is key.

2️⃣ Share Your Growth

Post about your leadership journey on LinkedIn. What challenges are you facing? What have you learned? Talking about it builds credibility and attracts opportunities.

3️⃣ Learn From Other Leaders

Read the article I co-wrote with Gregor and follow both of us for more leadership insights. The fastest way to grow is by learning from those who’ve done it before.

Your leadership journey starts now. Which of these steps will you take first?

Cheers,
Gábor