How to show technical leadership on a resume without a management title

You show technical leadership without a management title by writing bullets about decisions other engineers followed: the design you wrote and the team adopted, the migration you planned across services, the incident you ran, the engineer you mentored until they could work alone. Keep your official title as the job title and describe the lead work in the bullets.

This post is for senior and mid-level engineers who did tech lead work with no direct reports and want the resume to show it without overstating it.

What counts as technical leadership on a resume?

Leadership on an engineering resume means other people's work changed because of yours. Writing good code alone does not show that. Writing the plan that four engineers built against does. These six kinds of work show it most clearly:

• Design docs and RFCs. You wrote the proposal, people reviewed it, and the team built what it described.
• Leading a migration. You planned the order, split the work, and decided when the old system could be switched off.
• Incident command. You coordinated the response, made the call to roll back or fail over, and wrote the postmortem.
• Mentoring with an outcome. With your help, someone became independent on a system, took over on-call, or was ready for a promotion.
• Hiring loops. You designed an interview, ran technical rounds, or trained other interviewers.
• Cross-team alignment. You got two or more teams to agree on an API, a schema, or a shared deadline.

Each of these needs a result to count. "Wrote design docs" is an activity. A bullet that names the decision and what happened after it shows leadership:

Before:
- Wrote technical design documents for new features

After:
- Wrote the RFC for moving payment retries from cron jobs to a Kafka-based queue; reviewed by 3 teams and adopted as the design for all retry logic in the payments domain

If your on-call work included running incidents, our post on putting on-call and incident work on a resume covers how to write it in detail.

How do you write a leadership bullet?

Put three things in the bullet: what you decided or coordinated, how many people or teams it involved, and the end state. The verb should describe the leadership act ("planned", "ran", "coordinated", "set", "chose"), not the coding.

Before:
- Worked on the migration to Kubernetes with the platform team

After:
- Planned and coordinated the move of 22 services from EC2 to Kubernetes across 4 teams: set the migration order and wrote the cutover checklist; all 22 moved with no customer-facing downtime and the EC2 fleet was shut down in Q3 2024

The "Before" version could describe any engineer who touched the migration. The "After" version describes the person who owned it.

Mentoring needs the same treatment. Name who you mentored, at what level, and what changed for them:

Before:
- Mentored junior developers

After:
- Mentored 2 junior engineers through their first on-call rotations; both now take primary shifts without a shadow

Our staff software engineer resume example has a mentoring bullet under the current role: "Mentored 7 senior and mid-level engineers, resulting in 3 internal promotions." It gives the number of people and an outcome. Be careful with "resulting in": a promotion has many causes, so write it only if you can explain your part, or use the softer "3 of whom were later promoted".

If the lead work has no number at all, describe its scope instead. Our post on resume bullets without metrics shows how.

Can you write Tech Lead if it was not your official title?

Usually not as the title on its own. Use your official title, and add the lead role next to it when your company used it and your manager would confirm it. A reference or employment check may confirm only your official title and dates, and a resume that disagrees with that record is harder to defend than one that explains the difference. What an employer releases varies by company and country, so ask your HR team if you are unsure. Keep LinkedIn consistent with whichever format you choose.

These formats are fair when the role was real:

Brightwave Analytics, Berlin, Germany
Senior Software Engineer (Tech Lead, Payments) | Mar 2022 – Present
- Tech lead for the 5-engineer payments API team; set the quarterly technical plan with the product manager and moved the team from monthly to weekly releases

Brightwave Analytics, Berlin, Germany
Senior Software Engineer | Mar 2022 – Present
- Acting tech lead for the payments team from Jan 2024, after the previous lead moved to the platform group

Use the first when "Tech Lead" was a recognized function on your team: it appeared in the org chart, the team page or your performance review. Use the second when the role was temporary or informal.

These over-claim:

• Writing "Tech Lead" as the only title when the HR title was "Software Engineer".
• Writing "Engineering Manager", or "Team Lead" at a company where that title means people management, when nobody reported to you.
• Writing "Tech Lead" because you led one project for six weeks. That belongs in a bullet, not the title line.

A published example keeps a temporary lead role out of the title. In our lead backend engineer example, the role before the person became Tech Lead at NordicPay in 2021 stays "Senior Backend Engineer", and the interim role is the last bullet under it:

NordicPay Solutions, Stockholm, Sweden
Senior Backend Engineer | 2018 – 2021
- Developed and maintained Node.js microservices powering core account and transaction APIs for 1.2M+ users.
- Optimized database access patterns, lowering query response times by 50% and enabling real-time account updates.
- Introduced automated integration testing pipeline, improving release reliability and decreasing major incidents by 30%.
- Acted as interim team lead during manager transitions, successfully shipping two major features on schedule.

Resume example

Lead Backend Engineer Resume Example

Interim lead work shown as a bullet, under the official senior title.

View the full example

"Team lead during manager transitions" could mean technical lead or acting manager. If you write a bullet like this, say which parts you covered (planning, code review, stand-ups, one-to-ones) and add the team size and how long it lasted.

A few awkward cases come up often:

• Your official title is "Team Lead" or "Lead Engineer", but nobody reports to you. Keep the title, because it is what a check will confirm. Make the first bullet say what you lead: "Technical lead for 4 backend engineers; line management sits with the engineering manager."
• Your company has a formal "Lead" grade and you were not on it. Use the bullet approach. The grade means something specific at that company.
• Your startup had no formal titles, or the lead role rotated per project. Use the title you were hired with, and write "Tech lead for the X project" in the bullets, with dates if it was not the whole role.
• You got the tech lead role with no title change or pay rise. If it was announced and you held it for months, the parenthetical format is fair.
• You did lead work as a contractor through an agency. Use the role name from your contract or statement of work, and describe the lead work in the bullets.
• You were promoted into a Tech Lead title later. List both titles under the same company, as described in how to show a promotion on a resume.

How senior, tech lead and staff scope differ in a bullet

The same project reads differently depending on how much of it you owned. Here is one piece of work, moving a monolith's billing module into its own service, written at three levels:

Senior engineer:
- Built the Go billing service extracted from the Rails monolith: wrote the invoice and payment endpoints and the dual-write layer used during cutover

Tech lead:
- Led the billing extraction with 3 engineers: wrote the design doc, split the work into 6 milestones, ran the weekly sync with the finance team, and completed the cutover a month ahead of the contract renewal deadline

Staff engineer:
- Defined the pattern for extracting domains from the monolith, starting with billing; the design doc and dual-write library became the standard for the next 4 extractions across 2 departments

The senior bullet is about what you built. The tech lead bullet is about the team's plan and its delivery. The staff bullet is about decisions that other teams kept using after the project ended. Write the version that matches what you did, not the level above it.

The published staff example shows the cross-team level in two bullets under the current role: "Architected unified API gateway adopted by 9 product teams, reducing duplicated codebase by 60%" and "Collaborated with product and infra leads to align technical vision across a 70-engineer org". Both are about reach across teams, not about one team's delivery.

What should you not claim?

Do not claim people management you did not do. Tech leads guide work. Managers are usually responsible for hiring decisions, performance reviews, pay and headcount. If you did not do those, avoid wording that suggests you did.

Before:
- Managed a team of 6 engineers

After:
- Tech lead for a team of 6 engineers: ran sprint planning and design reviews and owned the technical roadmap for the search service

"Managed" and "led a team" are often read as line management. Name what you led instead: the design, the planning, the technical decisions. When you apply for manager-track roles, where the difference matters most, you can add "(no direct reports)" to make it explicit before an interviewer has to ask.

Hiring needs the same care, because "hired" implies you made the decision:

Before:
- Hired 12 engineers

After:
- Interviewed about 40 backend candidates as a technical round interviewer and trained 4 new interviewers on the system design round

Write "hired" only if the decision was yours.

Where leadership goes on the page

Put the strongest leadership bullet first under each role. The first bullet is the one every reader sees, so it should be the one that shows your level.

Mention the lead work in the summary as a plain fact, with its scope: "Senior backend engineer; tech lead for the payments team since 2022." Do not list "leadership" or "mentoring" in the skills section. Those are claims, and the bullets are where you show them.

If your target is an engineering manager role, compare your resume with our engineering manager resume example. The bullets there that cover hiring, reviews and team growth are the areas a hiring manager will ask you about.