Resume Tense: Past or Present for Your Current Job?

You are updating your resume for a job you want, and you reach your current role. You write "Manage a team of six." The next line is about the reporting system you built and finished last spring, so your hand hesitates: "Build" or "Built"? You are still in the job, so present tense feels right, but the project is done, so past tense feels right too. You scroll up, spot three more bullets with the same problem, and the whole page suddenly looks inconsistent.

It is a small thing that quietly makes a resume look careless. The fix is one rule, and it is not the one most advice leads with.

The takeaways

• Tense follows the action, not the job: if the thing is finished, use past tense, even inside your current role.
• Present tense is for what you still do every week; past tense is for results you have already delivered.
• Mixing both under one current role is correct, as long as no single bullet carries two tenses.

Should your current job be in present or past tense?

Both, depending on the line. Your current role takes present tense for the duties you still perform ("Manage a regional sales team") and past tense for the projects you have already finished ("Launched the loyalty program that..."). Previous jobs are simpler: everything in them is over, so every bullet stays in past tense.

The reason the "present tense for your current job" rule confuses people is that it is only half true. A current job holds two kinds of lines at once: things you keep doing and things you got done. Treating the whole entry as present tense forces your completed wins into a tense that no longer fits them. So the cleaner instruction is to read each bullet on its own and ask what it describes, an ongoing routine or a closed result.

What is the actual rule for resume verb tense?

Ask one question of every bullet: is this thing finished? If yes, past tense. If no, present tense. That single test settles the current-job problem without a table to memorize, because it ignores which job the line sits under and looks only at whether the work is done.

A duty you perform every week is not finished, so it stays present: "Coordinate the release schedule across three teams." A project with a clear end is finished, so it goes past: "Migrated the team off the legacy tool in Q1." Both can live under the same current role, and they should. Recruiters read past-tense lines as delivered outcomes and present-tense lines as your standing responsibilities, which is exactly the distinction you want them to see. The finished test is the whole rule; almost everything else about resume tense is a footnote to it.

Can you mix past and present tense in one job?

Yes, and inside your current role you usually should. The thing people fear is inconsistency, but the real inconsistency is forcing a finished result into present tense to match the lines around it. What you must avoid is mixing tenses inside a single bullet: "Manage the budget and reduced costs" reads broken. Keep each line in one tense.

A clean way to order it: list your ongoing duties first in present tense, then your completed achievements below in past tense. The eye moves from "here is what I run" to "here is what I have already delivered," and the tense shift does that work for you instead of looking like an error. This is the same logic behind writing bullets that show impact: your finished, provable results are your strongest lines, and past tense is what signals they are done.

The mistake that hides your best lines

Writing a completed achievement in present tense is the quiet error that costs you. "Increase regional revenue 18%" sounds like a target you are chasing. "Increased regional revenue 18%" sounds like a number you already put on the board. Same figure, but only the past-tense version reads as a result you can be held to.

When a strong, measurable win sits in present tense, a recruiter's eye files it as a routine responsibility rather than an accomplishment, and your best evidence gets skimmed past. The reverse matters too: do not push an ongoing duty into past tense, or it reads like you stopped doing it, which on a current job raises a question you would rather avoid. Match the tense to reality, line by line, and your achievements land as achievements.

When is past tense the safer choice everywhere?

When a present-tense line would be ambiguous, or you simply want one tense across the page, past tense throughout is widely accepted and hard to get wrong. Career resources like Indeed list it as a legitimate option, since a finished framing reads cleanly for completed and current work alike.

The case for it: past tense never makes a duty look abandoned, and it removes the judgment call on every line. The cost is that you lose the small signal present tense gives, the sense that you are actively running something right now. For most people the mixed approach reads better on a current role, but if you are staring at a bullet that could go either way, default to past and move on. Consistency on the page beats agonizing over one verb. For more on what recruiters scan first, browse the résumé and CV guides.

A quick check before you send

Before you export, run the finished test down the page once. Read every bullet and ask whether the action is done or ongoing, then confirm the tense matches. Watch the seam in your current role where duties end and achievements begin, since that is where mismatches hide. Make sure no single line carries two tenses. And check that your previous roles are fully past tense, including any line you copied up from your current job back when you got promoted.

This takes two minutes and removes one more reason for a hiring manager to think the resume was rushed. Verb tense will not get you hired on its own, but a page that handles it consistently reads like it was written by someone who pays attention, which is the impression every other line on it is trying to make too.