List your roles and responsibilities
Begin with a complete inventory of your paid roles, internships, freelance assignments, and other relevant work. For each position, record the employer, title, location if useful, dates, main responsibilities, tools, and notable outcomes. Write from memory and existing records before editing for length. Separate routine duties from contributions that improved a process, supported customers, reduced confusion, increased reliability, or helped a project move forward. Do not guess dates, figures, titles, or technical details. Accurate notes give you a reliable source when you later select the strongest material for a specific application.
Choose experience that supports the role
Review the offer and identify the work it appears to value: particular responsibilities, working environments, tools, or types of problems. Then choose experience that provides credible evidence for those needs. Recent work often deserves more space, but an older role can remain useful when it demonstrates a closely related responsibility. You do not need to give equal treatment to every position. Include enough context to make a role understandable, then remove details that do not help the reader assess your fit. Selection should be based on relevance and accuracy, not on making every job sound equally important.
Build a consistent entry structure
Use the same order for each role so the reader can compare entries quickly. A practical structure is employer and location, job title, dates, followed by a short set of contribution-focused statements. Keep dates and punctuation consistent throughout the document. Start each statement with the work itself, then explain the method, scope, or outcome when you can support it. Avoid turning every line into a list of tools. Technology matters when it clarifies what you did, how you worked, or what the work required. If a result is confidential or unavailable, describe the change without inventing a number.
Turn duties into evidence
A duty says what belonged to your role; evidence shows how you carried it out and why it mattered. Add context such as the type of customer, process, system, volume, constraint, or collaboration involved. Use precise verbs that describe the work without overstating your authority. For example, distinguish between preparing a report, reviewing it, and owning the reporting process. If you contributed as part of a group, state your part clearly. When exact outcomes are available, include them; when they are not, explain the observable change or deliverable instead of creating an impressive-sounding claim.
Edit for clarity and space
Read the section as someone unfamiliar with your career would read it. Remove repeated statements, internal jargon, and details that do not help explain your contribution. Combine similar tasks when one concise statement can cover them. Keep the strongest evidence near the beginning of each role, where it is more likely to be noticed. Check that every statement is understandable without an explanation from you. Fictional: true. Before: "Responsible for various customer and system tasks." After: "Resolved account access requests and documented recurring causes for the support team." The revised version identifies the work and its practical context without inventing a result.
Check the final section before sending
Perform a final accuracy and consistency review after the content is written. Confirm that employer names, titles, dates, locations, technologies, and descriptions match your records. Check that the section uses the same tense appropriately: past roles generally describe completed work, while a current role can include ongoing responsibilities. Read the document aloud or review it at normal viewing size to catch awkward wording and visual imbalance. Fictional: true. Before: "Helped with website updates." After: "Updated product pages in HTML/CSS and checked published changes before release." The second version gives useful detail while staying within a modest claim.