How to lead technical projects without authority: an engineer's guide

Technical leadership without a manager title is one of the most valuable skills an engineer can develop. It's the ability to influence decisions, align teams, and drive projects forward based on expertise and relationships rather than organizational authority.

Build your credibility first. People follow engineers who are technically excellent, reliable, and fair. Before you try to lead, establish a reputation for good judgment, thorough code reviews, and shipping reliable work. Credibility is earned through consistent behavior over time.

Listen before you advocate. Understand the constraints, priorities, and concerns of everyone involved. A technical lead who understands the product manager's timeline concerns, the QA team's quality concerns, and the operations team's stability concerns can propose solutions that address all of them.

Frame proposals in terms of outcomes, not technology. "Using this approach will reduce deployment time from 2 hours to 15 minutes" is more persuasive than "We should use Kubernetes because it's the industry standard". Connect technical decisions to business outcomes that matter to your stakeholders.

Build coalitions before making decisions. Discuss your approach with key stakeholders individually before the group meeting. Address concerns early and incorporate feedback. A decision that has been shaped by the people who need to implement it is more likely to succeed.

Write things down. Architecture decision records, project proposals, and status documents create shared understanding and a historical record. Written proposals also allow asynchronous feedback, which produces more thoughtful input than real-time discussion.

Share credit generously. When a project succeeds, highlight the contributions of everyone who helped. Engineers who feel appreciated for their work on your initiative will be eager to work with you again. When things go wrong, take responsibility and focus on fixing the problem rather than assigning blame.

Lead by example. Be the first to write the documentation, fix the gnarly bug, or help a teammate who's stuck. Technical leadership is demonstrated through actions, not titles. Engineers follow leaders who do the work they're asking others to do.

-

Rizwan Saleem | https://rizwansaleem.co