Six years at one company: customer support, then customer operations, then team lead. Listing only your final title hides the earlier work. Repeating the employer for every role can make internal moves look like separate jobs.
Use one employer heading, then list roles from newest to oldest with their own dates. Separate descriptions when the function or scope changed substantially. If only the grade or title changed, you can share a description while keeping the dates of each title visible.
Give the employer and each role their own dates
Put your full employment period next to the company, then the actual period beside each role. Attaching all six years to the team-lead title obscures when you began managing work.
For someone moving from customer support into operations, an entry could read:
Software company | Jul 2020–Jun 2026
Customer Operations Team Lead | Apr 2024–Jun 2026
- Assigned customer onboarding work, consolidated implementation blockers, coordinated priorities with product and implementation leads, and followed through on handoffs.
Customer Operations Specialist | Jan 2022–Mar 2024
- Checked onboarding materials, tracked missing information and open questions with customers and the implementation team, and produced a pre-launch handoff checklist.
Customer Support Specialist | Jul 2020–Dec 2021
- Handled product questions, reproduced reported problems and documented the steps, and added confirmed recurring issues to help documentation.
Each role contributes different information: coordination, onboarding handoffs, and troubleshooting. Earlier roles need representative work, not an exhaustive duty list. Recent work often deserves more space, but substantial earlier contributions still belong.
Share a description when only the grade changed
An engineer promoted to senior engineer while owning the same module need not repeat API development, incident handling, and releases twice. List both titles and their dates, followed by shared bullets. Introduce additional responsibility with “After promotion…” to show when it began.
For example: “After promotion, reviewed order-module designs and documented the impact of API changes and release checks.” If the new role involved managing people or owning a different business area, give it a separate description and assign results to the relevant period.
For a lateral move, show the role and department change directly. Moving from support to operations need not be presented as a promotion or accompanied by a paragraph explaining every transfer.
Describe a cross-role project fully once
A project spanning specialist and lead roles can sit in a project section with its dates and changing responsibilities. Keep the employment section focused on each role. Without a separate project section, put the full account under the role where your main contribution occurred and explain the transition briefly.
For example: “In 2023, contributed the materials checklist to an onboarding-process review; after becoming team lead in 2024, consolidated team feedback and revised the checklist.” Avoid repeating the same project result under both titles.
For concurrent responsibilities, distinguish your main role from an additional assignment. A temporary project-lead assignment can appear under the unchanged job title with its own dates. If you formally held two positions simultaneously, list both periods and label the overlap as concurrent.
Open ResumeMeow with the employer entry that currently shows only your last title. Add each role’s dates and representative work, then organize what needs a separate description and what can be combined.