Engineering Leadership Starts Before the Title

Source and AI note: This article is based on Gemini’s Devpractice on YouTube. It was generated and edited with the gpt-5.6-sol model.

Across three companies, the same developer joined as a server developer and later received several kinds of leadership role. The repeated pattern was that the appointment did not suddenly change his daily work. He had already been reviewing code, responding to incidents, leading a part of the team, or solving company-wide problems. The title arrived after the work was visible.

The first team-lead role followed from already looking after backend reviews and incident response. A later part-lead role was assigned after similar responsibility widened. Before becoming a director, he had spent about a year concentrating on company-wide problems. Executive responsibility changed the view of the company, and personnel authority can also be different, but the underlying work did not begin on appointment day.

This is why a title that creates an entirely new working identity may indicate that preparation came late. In a healthy engineering organization, the name of the role should formalize a capability the team has already observed.

Be able to cover the role without removing its owner

Preparing for leadership does not mean displacing a capable current lead. It means becoming able to cover meaningful parts of the role. When that person moves upward, changes teams, or leaves, the opportunity does not wait for someone to begin learning from zero.

At that moment, ambition alone is weak evidence. The candidate needs results, the ability to handle the work, and trust from the engineers who have worked closest with them. That peer confidence matters more than approval from people who did not share the work.

Title-first experiments put the team at risk

Some companies give a promising person the role first and expect growth to follow. It can work, but there have also been cases where a new title changed someone’s behavior and damaged the team. The experiment is not borne by the candidate alone.

The preferred order is therefore plain: do the work broadly enough that colleagues already recognize the capability, then let a formal opportunity confirm it. This assumes a reasonably healthy company rather than an arbitrary appointment system, but under that condition responsibility before title is the more natural path.