Describe the decisions you owned, the work you performed and the people with whom you collaborated. Keep formal titles accurate, explain unfamiliar titles in plain language, and distinguish contribution from authority. Specific responsibility gives readers a fairer basis for assessing fit than inflated seniority labels.
Separate title from responsibility
Write your formal role title exactly as it was used, then describe what you actually did. Titles vary across organizations: a manager may coordinate projects without managing employees, and a lead may guide one workstream rather than an entire department. Clarifying responsibilities is more useful than upgrading the title for perceived status. If an internal title is obscure, add a plain-language explanation alongside it rather than replacing it with a more senior equivalent. Keep the original title visible.
Identify the period and setting of the responsibility. A temporary acting assignment, volunteer coordination role or independent project can demonstrate meaningful work, but each needs appropriate context. Make clear whether the scope was ongoing, limited to one engagement or shared across a team. Avoid combining several small responsibilities into wording that implies a permanent executive position. Readers need to know what authority accompanied the activity, not simply that you were present.
Describe decisions and contributions concretely
For a selected project, list the artifact you produced, the decisions you could make independently and the decisions requiring approval. Then choose verbs that match that record: drafted, analyzed, coordinated, implemented, reviewed or approved. “Led” is useful when you explain what was led and how. “Owned” needs an identifiable boundary. A sentence about reviewing interview notes and drafting recommendations communicates more than a broad claim of strategic leadership without a decision attached.
Include collaborators where they explain the work. If a senior colleague chose the method and you carried out the analysis, describe both parts. If you proposed an approach and another team implemented it, separate proposal from delivery. This detail does not diminish the contribution; it helps a prospective collaborator understand how you work. Keep confidential names out when necessary, but retain the distinction between your responsibilities and those of other participants.
Connect scope with the opportunity sought
Select responsibilities relevant to the work you want next and explain any practical limits. Someone offering independent research planning should show evidence of planning, not rely only on participation in research sessions. If you are expanding into a new area, describe the available preparation or practice work honestly and distinguish it from commissioned experience. You can express interest in broader responsibility without claiming you have already exercised it professionally.
Before publishing, check each seniority word against a concrete example. Ask whether someone who worked alongside you would recognize the description and whether a new reader might infer budget authority, people management or regulated expertise that you did not hold. Revise the sentence until its boundaries are clear. Keep the supporting factual notes privately so future edits do not gradually broaden the claim as the original project becomes less familiar.
Fictional example: explaining a coordination role
A fictional operations specialist, Tomas, coordinated a handbook update involving support, training and product colleagues. His draft profile calls him “head of operational strategy,” although his formal position was operations coordinator and the department director approved policy changes. He rewrites the project description to say that he maintained the review schedule, reconciled comments and drafted the final handbook structure.
Tomas adds that subject specialists supplied policy content and the director approved the release. His case study now highlights a sample comment-resolution log and explains how he organized competing edits. This description supports a conversation about coordination and documentation work without implying executive authority. The example is invented to illustrate wording decisions, not evidence of a real engagement or an assessment of Tomas’s competence.
A checklist for your next step
- Keep formal titles accurate.
- Name decisions you actually owned.
- Separate drafting from approval.
- Credit shared responsibilities.
- Check seniority words against evidence.
Common questions
Can I call myself a lead without managing staff?
Explain the workstream and authority you led. Do not let the title imply people management when your responsibility was coordination or technical direction.
How should I describe an acting role?
State that it was an acting assignment and give its period and responsibilities. Preserve the distinction from your permanent position.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.