A current job on a resume sounds simple until the record changes while you are applying. The job is still active, yet one project has finished, another is only planned and a third belongs to a team. A stale end date, inflated title or vague present-tense claim can create contradictions with an application form or later interview. The useful task is to separate the employment relationship from the status of each piece of work.
This free guide begins with your own records and the vacancy, then shows a concrete CVura workflow for maintaining a reliable career foundation, creating a focused version and saving the exact submitted file with the opportunity. The app can organize versions and preparation; it cannot decide whether you are still employed, verify a result or guarantee a screening outcome. You must review dates, wording and permissions yourself.
A current job on a resume begins with the actual employment status
Check whether you are employed on the date you will submit the application. That sounds obvious, but a notice period, contract end, leave, internal transfer or delayed profile update can make an old document misleading. Use the employer's real name, the title you hold and the month and year you began that role. If an internal title is obscure, a brief clarification may help, but do not replace it with the title of the job you want. A target role belongs in your profile or application context, not in a historical employment record.
For an active role, a line such as “March 2024–Present” is a familiar English-resume convention. UC Santa Barbara Career Services recommends an organization, title, location and dates, using “Present” for current experience. That is a convention, not a statement that a contract can never end. If the application system requires a different date format, follow its fields and keep the meaning the same. Never invent a future end date merely to fill a blank.
If you have already left, stop using “Present,” even if your public profile has not yet been updated. Use the actual end month after checking payroll or personnel records when necessary. If you are on approved leave but remain employed, do not automatically turn that into a past job; first determine what the employer's field asks and what status is factually correct. Where a separation date is agreed but not reached, avoid presenting a plan as a completed event.
Keep the current role's timeline separate from project dates
An employment date range describes how long the role has been held, not how long every task lasted. Suppose you joined an organization in March 2024, completed a service redesign in December 2025 and still coordinate monthly reporting. Your role can correctly run to Present; the redesign is a completed project. Do not imply that the redesign is still under way just because it appears beneath a current position. A short bullet can name the completed period when it matters.
A promotion or internal move adds another layer. Keep the original and new titles, dates and employer relationship clear. If responsibilities changed substantially, separate the roles under the same employer so a reader can see what happened when. Do not move all achievements into the newest title merely because they fit the target vacancy. Our free promotion-on-resume guide goes deeper on that structure; here the priority is that the active role and older role do not collapse into one invented timeline.
For concurrent work, identify each relationship honestly. A side project, freelance client or volunteer commitment can overlap with a full-time job; overlap alone is not a defect. But different engagements need their own labels, dates and permissions. If the form asks for employment history, do not assume it treats volunteer activity as an employer. Preserve the distinction in your master record, even when a role-specific resume selects only the most relevant entries.
Write ongoing duties and finished results in the right tense
Use present-tense verbs for work you still do: “coordinate supplier requests” or “maintain a monthly reporting process.” Use past tense for a finished result even if it happened in the current job: “redesigned the intake form” or “trained a new cohort.” UC San Diego's resume guide makes the present-versus-past distinction for current and previous roles. It is a readability tool, not a magic ATS rule. If a sentence sounds awkward, rewrite it plainly rather than forcing grammar to do the work of dates.
Do not list a planned improvement as a delivered achievement. “Developing a prototype” and “launched a service” describe different states. If you are still testing, say so and explain your actual contribution. If the project is complete but the impact has not been measured, describe the deliverable or method without inventing a percentage. The most defensible bullet tells a reader what you did, for whom and with what observable scope.
A current role can contain a mix of duties and outcomes. Avoid making every line start with “responsible for,” which hides action, but also avoid converting a routine task into a grand result. For example, “maintain weekly stock reconciliations for three sites” is specific without a fabricated cost saving. “Created a guide used by the onboarding team” is a finished deliverable if you can verify that use. The tense should follow the status, not a template.
Select current-role evidence for this vacancy
Before opening a builder, read the vacancy once for real tasks, tools, audience and required qualifications. Mark which parts of your current role answer those needs. Then check each marked item against records you can explain: a project brief, published work, performance notes, training material or your own dated work log. Do not copy a skill from the advertisement into your job description unless you actually used it. A match label is not evidence of competence.
Choose two or three examples with different purposes rather than repeating the same claim. One can show a recurring responsibility, another a completed change, and a third collaboration or scope. If you cannot reveal a client or internal metric, describe the type of work within your permissions. A general phrase such as “regional service team” can be useful if it does not identify confidential people or projects. Never publish another person's data to make a bullet look concrete.
The current job may be your strongest evidence, but it need not monopolize the page. A previous role or project can demonstrate a requirement that the present role does not. Keep the chronology readable and let relevance guide detail, not truth. The guide to tailoring a resume truthfully shows how to choose evidence without turning missing experience into a false claim.
A concrete CVura workflow without rewriting history
In CVura, first review your saved career foundation. Confirm the current employer, formal title and start date against your records. Keep the same factual foundation when preparing more than one application; do not edit a true start date just to make a particular vacancy look better. If your role changed internally, record that change as a distinct experience or clearly described progression where the product permits, then inspect how it appears in the exported document. The app helps organize the record, not authenticate it.
Open the saved opportunity and compare its actual requirements with your verified examples. Create a role-specific resume version that foregrounds the most relevant current duties and completed results. Review every suggested phrase manually. If a suggestion upgrades a routine contribution into ownership you did not have, reject or rewrite it. If a score or fit signal is shown, treat it as a preparation aid; it cannot predict ATS parsing across every employer, a recruiter's judgment or an interview.
Export the version in the format the employer requests, reopen it and read the current-job entry from top to bottom. Check the date range, title, tense, numbers, confidentiality and links. Attach that exact file to the saved opportunity along with a copy of the vacancy and any submitted letter. Once submitted, keep an unchanged copy. Later edits to your career foundation are useful, but they should not silently replace the record of what a particular employer actually received.
Make the resume, form and interview account agree
Application portals sometimes ask separately whether a job is current and for an end date. Use the status control if one exists; do not type a fake future date to make the field accept the entry. If the portal has no clear current-job option, check its instructions or support rather than inventing a value. Compare the employer name, start month and title with the uploaded resume before submitting. A small mismatch may be explainable, but it is easier to fix before it becomes part of the record.
The cover letter may describe why you want a new role, but it should not imply that you have already left your current employer when you have not. In an interview, distinguish your continuing responsibilities from a finished project and from goals for the next job. A question about why you are considering a move can be answered truthfully without criticizing colleagues or claiming that a resignation is complete. Our job-change interview guide offers a separate method for that conversation.
If your situation changes while an application is active, update your private tracker and decide whether the employer needs a corrected document through the channel it provided. Do not overwrite a previously submitted file in your own records. You may have sent a truthful resume on Monday and left the company later; both statements can be correct at their respective dates. Recording the sequence prevents an accidental contradiction at a later stage.
Search discreetly without making the record evasive
Being employed does not require you to publicize a job search at work. Use personal contact details on an application, keep files on your own authorized devices and avoid inserting confidential employer material into an external tool. Check your workplace policies before using examples, documents or devices. A resume can state your current employer and role accurately without revealing internal initiatives, unreleased products, customer identities or colleagues' private information.
Some applications ask whether they may contact your current employer. Answer that field honestly and use any available preference or explanation for timing. Do not list a manager as a reference without permission. Avoid promises about notice period or start date until you know your contractual and practical position. These are employment-specific matters; the resume should not imply a guaranteed availability date that has not been agreed.
Keep the application package limited to what the employer requests. A public portfolio link can expose more than the resume itself; test permissions before sharing. Redaction is not enough if names or internal systems remain recognizable. If a relevant achievement cannot be shared safely, use a less detailed but accurate description and prepare to discuss your method at an appropriate level in an interview.
Recheck the current job before every submission
A current-role entry is a moving record. Reopen it when a new responsibility begins, a project finishes, a promotion takes effect or employment ends. For each vacancy, verify what was true on the submission date. The check is short: employer and title, start date, current status, tense of each bullet, evidence for outcomes, permissions and consistency with form fields. The purpose is not to refresh every word each week, only to prevent a stale fact from traveling into a new application.
Read the exported PDF or DOCX rather than trusting the editor preview. Confirm that dates have not wrapped ambiguously, the current role is identifiable and every claim survives a follow-up question. Check the actual file attached in the portal. If the employer specifies a format or asks for a full employment chronology, follow that instruction even if your preferred resume is shorter. A file that looks polished but answers the wrong question is not ready.
Finally, keep the submitted version with the vacancy. When an interview invitation arrives, you can see the exact wording the employer saw and prepare specific examples without guessing which draft you used. CVura can keep this version and opportunity connected, but your review remains decisive. Neither the word “Present” nor a fit signal can guarantee that a hiring team will interpret the application as you intend.
