Read a sample: 1. Your Resume as a Case for Advancement
You may already be doing work that belongs in a promotion conversation. Perhaps you train new colleagues, resolve problems before they reach your manager, or coordinate a project that crosses team boundaries. Yet when you open your resume, you find a list of duties that could describe almost anyone with your job title.
That gap is common. A job description tells people what a position is generally responsible for. A resume should show what you have done with those responsibilities—and why that experience is relevant to the work you want next.
A promotion resume is not a request for someone to reward your effort. It is a concise case that you can contribute at a higher level. It connects evidence from your experience to the needs of a particular role. The evidence might include improved processes, sound decisions, broader assignments, reliable follow-through, or leadership exercised without formal authority.
You do not need to exaggerate your title or claim credit for an entire team’s work. You do need to make the value of your contribution visible. This chapter will help you define the role you are aiming for, identify what a decision-maker needs to learn about you, and recognize the difference between a record of tasks and a case for advancement.
A resume for advancement must do two things at once. It must accurately represent your experience, and it must help a reader see how that experience prepares you for a larger challenge.
Those goals are related, but they are not identical. You may be excellent at completing your current assignments, yet a higher-level role could require you to prioritize competing requests, guide others, improve a process, or make decisions with less direction. A resume that emphasizes only the volume of routine work you complete may leave those other capabilities hidden.
Consider an employee who wants to move from a customer service position into a senior specialist role. The current job includes answering customer questions. The desired role still requires service skills, but it may also involve handling unusual cases, helping colleagues interpret procedures, and identifying recurring problems.
A task-focused resume might say:
> Responded to customer questions and documented cases.
That statement is accurate if the employee performed those duties. It also tells the reader very little about readiness for a more demanding position.
Now consider an advancement-focused version, based on a hypothetical employee’s actual contribution:
> Resolved nonroutine customer cases, documented recurring issues, and shared clarification with teammates to support more consistent responses.
The second version does not claim that the employee managed the team or redesigned the entire service operation. It shows the employee working through less routine situations and helping others respond more consistently. Those details give a reviewer something more useful to evaluate.
The distinction is not that every bullet must sound impressive. It is that each important statement should help answer a question about your fit for the role you want. A clear description of ordinary work can be valuable when that work is directly relevant. A list of ordinary duties, however, rarely makes the whole case on its own.
It is difficult to demonstrate readiness for a higher level if you have not defined what “higher” means for you. A new title may bring more pay or recognition, but the resume still needs to speak to the work behind that title.
Start with one realistic target role. It can be an internal promotion, a position at another employer, or a type of role you expect to pursue at several organizations. You can have more than one long-term goal, but choose one as the starting point for this exercise. A focused target makes it easier to decide which evidence belongs near the top of your resume.
Write a short answer to each of these questions:
- What position do I want next?
- What problems would someone in that position be expected to handle?
- What responsibilities would be broader, more complex, or less closely supervised than mine are now?
- Who would depend on that person’s work or judgment?
- What experience from my current or previous roles overlaps with those demands?
Your answers do not have to be complete. They are a working hypothesis, not a substitute for reading an actual posting or discussing the role with someone who understands it. In Chapter 2, you will examine role descriptions more closely and build a checklist of priorities. For now, your aim is to move beyond a vague goal such as “get promoted.”
For example, a hypothetical administrative assistant might write:
> I want to become an operations coordinator. The role appears to involve keeping work moving across teams, tracking deadlines, and resolving routine process problems with less supervision. I have supported scheduling and documentation, and I have also coordinated materials for a recurring cross-team meeting.
This statement identifies a direction and a possible bridge between current experience and future responsibilities. It also leaves useful questions open: How much authority does the coordinator have? Which processes matter most? Is cross-team scheduling a minor part of the position or a central one? Those questions can guide the employee’s research.
If you are considering a managerial role, separate the desire for a title from the actual responsibilities involved. Hiring, performance feedback, staffing decisions, and formal accountability may be part of the role. Facilitating a meeting or mentoring a colleague can be relevant evidence, but neither automatically…