DEV Community

Cover image for Changing Level or Track Without Losing Leverage
Muhammad Ali Mughal
Muhammad Ali Mughal

Posted on

Changing Level or Track Without Losing Leverage

After a layoff, a lot of engineers do not apply for the exact job they just lost. An engineering manager decides to go back to hands-on work. A senior backend developer aims at platform or security roles because that is where the openings are. A staff engineer at a small startup applies for senior roles at a big company because the titles do not translate. All of these are reasonable moves, and all of them fail in the same way: the resume still describes the old job, so the ATS scores it against the wrong keywords and the recruiter reads it as a step sideways or down.

This post covers how I rewrite a resume when the level or the track changes, without hiding anything and without giving away negotiating leverage.

I wrote this with help from AI tools and checked it against my own hiring-panel notes and public recruiter guidance. I am a Principal Software Engineer in Karachi with 9+ years across product companies and agencies, and I have reviewed many resumes for exactly these moves.

๐Ÿ“š Series Navigation โ€” Resumes Through Layoffs, Gaps & Comebacks

Related earlier posts: Tailoring Without Lying: Mapping Job Description Keywords to Real Evidence ยท Career Switcher & Self-Taught Developer Resumes in 2026

How do I change level or track on my resume without looking like a step down?

Direct answer: Write the resume for the role you want, not the one you had. Lead with a headline naming the target role, re-order bullets so the evidence for the new level or track comes first, keep your real titles and dates, add one line of context where titles do not translate, and map the new job description's keywords to real work you already did.

Wooden step ladder leaning against a bookshelf, AI-generated

The four moves I see most

Move What the reader worries about What the resume must prove Lead with
Manager โ†’ senior/staff IC "Can they still code? Will they leave for the next manager job?" Recent hands-on technical work and a clear reason Systems you designed or code you shipped in the last 2 years
Senior IC โ†’ first manager "Have they ever led people?" Mentoring, hiring, delivery ownership Tech-lead scope, people you grew, projects you ran
Backend โ†’ platform / SRE / security "Do they know the new domain?" Real overlap with the new track Infra, on-call, CI/CD, auth or incident work you already did
Staff at small company โ†’ senior at large company "Is this title inflated?" Scope numbers, not titles Team size, traffic, revenue or users your work touched

The common thread: the reader has one specific doubt, and the top third of the page should answer it before they finish scanning.

Step 1: a target-first headline

The first line under your name is the cheapest place to fix the mismatch. An ATS also reads it, and many systems weight it heavily when matching job titles.

Before:
Engineering Manager | 6 years leading teams of 5-12

After (moving back to IC):
Staff Backend Engineer | Laravel, Node.js, PostgreSQL | Hands-on architect who also led teams of 5-12
Enter fullscreen mode Exit fullscreen mode
Before:
Senior Backend Developer (PHP, Laravel)

After (moving into platform):
Platform / DevOps Engineer | Kubernetes, Terraform, GitHub Actions | 7 years running the production systems I build
Enter fullscreen mode Exit fullscreen mode

Keep it truthful: the headline states the role you are targeting and the evidence you have. It is not a job title, so it does not claim you held a position you did not.

Step 2: re-sort the evidence, don't rewrite history

Your titles and dates stay exactly as they were. What changes is which bullets come first under each role, and which ones you drop. For an engineering manager going back to IC, the same job can look like this:

Engineering Manager, Acme Payments (2022 โ€“ 2025)
- Designed the idempotent payment retry service (Go, PostgreSQL) and wrote its core;
  cut duplicate charges from ~40/month to 0
- Led the migration from a PHP monolith to 4 services; reviewed every schema change
- Managed 7 engineers; hired 4, promoted 2
Enter fullscreen mode Exit fullscreen mode

Same job, but the management line moved to the bottom and the hands-on work is on top. For the opposite move, IC to manager, flip it: lead with mentoring, hiring loops you ran, and delivery you owned across a team.

A rule I use: the first two bullets of the most recent role should be things you would happily be asked about in a 45-minute deep-dive for the target role.

Step 3: map the new track's keywords to real work

A track change is where keyword gaps hurt most, because your past titles do not contain the new track's vocabulary. Take three or four real job descriptions for the target role and pull the repeated terms. A job description keyword finder does this quickly. Then build a mapping table for yourself:

Target keyword Where I actually did it Bullet that proves it
Terraform Wrote modules for our staging stack "Moved staging to Terraform; env rebuild 2 days โ†’ 40 min"
On-call / incident response Primary on-call 1 week in 4 "Ran 12 incident reviews; cut repeat incidents by half"
Observability Added OpenTelemetry to 3 services "Traced p99 latency to N+1 queries; fixed, p99 โˆ’60%"
Kubernetes Only local minikube Leave it out, or list under "Learning" with a real project

The last row matters. If you have no real evidence, do not add the keyword to a job entry. Put it in a learning or projects section with something concrete, or leave it out. Then check the result against a live posting with a resume vs job description match to see which important terms are still missing.

Step 4: handle titles that don't translate

Titles mean different things at different companies. "Staff Engineer" at a 15-person startup and at a 5,000-person company are different jobs, and "Engineering Manager" at an agency may have been mostly delivery management. Do not change the title. Add a one-line scope note instead:

Staff Engineer, Brightline (2021 โ€“ 2024)
Scope: one of 3 senior engineers in a 14-person product team; owned backend architecture
Enter fullscreen mode Exit fullscreen mode

This does two things. It stops a recruiter from thinking you are inflating, and it stops a big-company reader from assuming you will expect a staff-level offer when you have applied for senior.

Step 5: keep your leverage

People changing level often undersell themselves because they feel they are asking for a favour. A few habits keep your position strong:

  • Don't write "willing to take a step down" anywhere on the resume or in the summary. The headline already says what you want.
  • Keep the scope numbers. Team size, systems owned, budget, traffic. They justify pay even if the title is lower.
  • Explain the move once, positively, in the cover note or summary: "I want to spend most of my time building again" reads very differently from "management didn't work out."
  • Don't volunteer your previous salary. Talk about the range for the role you are applying to.

Common mistakes

  1. Sending the manager resume to IC roles with a new headline but the same bullets.
  2. Listing every tool from the new track's job description in a skills block with no evidence anywhere.
  3. Renaming old titles ("Engineering Manager" โ†’ "Lead Engineer") to fit. Background checks will catch it.
  4. A summary that apologises for the change.
  5. One resume for two tracks. If you are applying to both platform and backend roles, keep two versions.

Diagnostic checklist

  • [ ] The headline names the target role and your strongest evidence for it
  • [ ] Titles and dates match your real history exactly
  • [ ] The first two bullets of your latest role support the new level or track
  • [ ] Every keyword from the target job description that appears in a job entry has a real bullet behind it
  • [ ] Titles that don't translate have a one-line scope note
  • [ ] No apologetic or "step down" language anywhere
  • [ ] A separate version exists for each distinct track you are applying to

FAQ

Will an ATS reject me because my last title doesn't match the job title?

Not usually by itself, but title match is often weighted. A target-first headline and the right keywords in your bullets close most of that gap without changing your real title.

Should a manager going back to IC list management at all?

Yes, briefly. Leading people is a strength for senior and staff IC roles. Just put it after the hands-on evidence.

How recent does hands-on work need to be?

For senior IC roles, readers look for something in the last two years. If your recent role had little coding, a real side project or open-source work helps.

Is it OK to apply for a lower level on purpose?

Yes, if it fits what you want. Keep your scope numbers on the page so the offer reflects your experience, and discuss level openly in the first call.

How do I explain a track change in an interview?

One or two sentences on what pulled you toward the new work, followed by a concrete example of doing it already. Keep it about the future, not about what went wrong.

Do I need certifications to move into security or cloud roles?

They help with keyword matching and some screens, but real work you can describe matters more. Use a certification to support evidence, not replace it.

Next in this series, Part 6 covers keeping a resume ready all the time, so the next surprise doesn't start with a blank page.


Follow & Connect

Top comments (1)

Collapse
 
iictp profile image
IICTP •

The re-sort rather than rewrite idea is the part that stuck with me โ€” keeping titles and dates exact while moving the hands-on work to the top of the most recent role feels both honest and practical. The first-two-bullets rule is a sharp test for it, especially for a manager moving back to an IC role. Do hiring panels usually weigh that recent hands-on evidence more heavily than the management experience for a staff IC role, or does the leadership background still carry real weight there?