How to describe your current job on a resume

Use present tense for duties, past tense for finished wins

The rule is simple. Anything you still do every day gets present tense: 'Manage a team of eight engineers across three time zones.' Anything you finished gets past tense: 'Launched a self-service portal that reduced support tickets by 30 percent in Q2 2025.' Mixing tenses in the same bullet is the most common mistake on current-role entries, and it reads as sloppy to anyone who notices.

A clean way to think about it: if you would still be doing it next Monday, write it in present tense. If it has a completion date or a final number attached, write it in past tense.

• Present tense: 'Lead', 'Manage', 'Oversee', 'Build', 'Coordinate', 'Report to'
• Past tense: 'Launched', 'Delivered', 'Reduced', 'Increased', 'Completed', 'Negotiated'

Write a strong job title and date line

Put your official job title first, then the company name, then the location, then the date range with the end date as 'Present'. For example: 'Senior Product Manager, Acme Corp, Austin TX, March 2024 to Present'. If your internal title is unusual or uses company-specific jargon, you may add a clarifying title in parentheses, but keep it honest. Do not inflate it.

In the US, Canada, the UK and Australia, leaving the end date blank or writing 'current' instead of 'Present' is acceptable but less standard. 'Present' is the clearest signal to applicant tracking systems and human readers alike.

Show scope before you show results

Scope tells the reader how big your world is. Results tell them what you did with it. Lead with scope in your first one or two bullets, then follow with results. Scope includes budget size, team size, number of clients, revenue line, geographic reach, or system scale.

A scope bullet looks like this: 'Oversee a $4 million annual marketing budget across paid search, social and email channels.' A results bullet that follows it looks like this: 'Grew organic traffic from 80,000 to 140,000 monthly sessions between January and September 2026.' Together they give the reader a complete picture without requiring them to guess at context.

• Team size: 'Manage a cross-functional team of 12 across product, design and engineering'
• Budget: 'Responsible for a $2.5 million operational budget'
• Client base: 'Support 60 enterprise accounts across North America and EMEA'
• System scale: 'Maintain infrastructure serving 1.2 million active users'

Quantify results even when the role is ongoing

Many people skip numbers on their current role because the job is not finished. That is a mistake. You do not need a final number to show progress. Use the data you have right now, and add a time frame so the reader understands it is a point-in-time figure.

If you cannot share exact figures because of confidentiality, use ranges or percentages rather than omitting numbers entirely. 'Reduced average onboarding time from 14 days to 9 days' is specific. 'Improved onboarding efficiency by roughly 35 percent' works if the exact days are sensitive. 'Improved onboarding' with no number tells the reader almost nothing.

1. Identify one metric that reflects your core output: revenue, cost, time, volume, error rate, satisfaction score.
2. Find the baseline from when you started the role or the start of the current year.
3. State the current figure and the time period: 'from X to Y between Month Year and Month Year'.
4. If the number is confidential, convert it to a percentage change or a relative range.

Write bullets that start with strong verbs

Every bullet in your current role should open with a verb, not a noun phrase or a pronoun. 'Responsible for managing' is weaker than 'Manage'. 'I oversee' is weaker than 'Oversee'. The verb-first format is standard in 2026 and expected by both ATS software and human reviewers.

Vary your verbs across bullets so the entry does not feel repetitive. If three bullets in a row start with 'Manage', replace two of them with 'Lead', 'Direct', 'Coordinate' or whatever is accurate. Below are verb categories matched to common functions.

• Strategy and planning: Lead, Define, Develop, Establish, Shape
• Operations and execution: Manage, Oversee, Coordinate, Run, Administer
• Analysis and reporting: Analyze, Track, Monitor, Evaluate, Report
• Collaboration and communication: Partner, Liaise, Present, Advise, Represent
• Building and creating: Build, Design, Create, Produce, Implement

Tailor the entry to each job you apply for

Your current role description should not be identical on every application. Read the job posting and identify the two or three duties or skills the employer emphasizes most. Reorder your bullets so those appear first. Swap in the employer's exact language where it is accurate. If the posting says 'stakeholder management' and you currently do that, use that phrase rather than 'cross-functional collaboration', even if they mean the same thing.

This is where Break-In Bad can help. When you enhance or build your resume through the platform, Omar asks you up to 20 questions about your current role, including scope, results and the language you use day to day. She then writes a tailored resume entry per job from the facts you confirm, matching the posting's wording without inventing anything. Every line is checked against what you said, and your original is kept so you can compare.

Common mistakes to fix before you submit

Even a well-written current role entry can undermine your application if it contains any of the following errors. Run through this checklist before you send the resume anywhere.

• Mixed tenses in the same bullet: pick present or past and stick to it based on whether the task is ongoing or complete
• No numbers anywhere in the entry: add at least one quantified result, even an approximate one
• Duties listed without context: add scope so the reader knows the size of what you manage
• Bullets longer than two lines: split them or cut the weaker half
• Generic verbs like 'helped', 'assisted' or 'worked on': replace with the specific action you took
• End date left blank: write 'Present' so ATS systems parse the date range correctly