Career Advice
You Updated Your Resume After Applying. Does the ATS Even See It?
David Eric ·
Usually, no.
In four of the five systems most tech companies hire through, the recruiter reviews the resume that was attached to your application at the second you clicked submit. The file on your candidate profile is a different object. Swap it, improve it, rewrite every bullet, and the application they're reading still carries the old one. The exception is Ashby, and even there the recruiter has to choose to look.
This comes up constantly. The version I saw this week: an engineer applied through an iCIMS portal right before a holiday weekend, spent the next few days getting much better at tailoring, went back into the portal, replaced the resume on their profile, and then wondered whether the recruiter would ever see the stronger version. They won't, unless someone sends it to them. Below is what each system does with an updated resume, when withdrawing and reapplying is worth it, and the one email that beats both.
What actually happens to your resume when you submit?
Two things, and the difference between them is the whole answer.
First, the ATS makes an application record. That record belongs to one job, and it holds exactly what you sent: the resume file, the cover letter, your answers to the form questions. Greenhouse describes the recruiter's view plainly: they see "your resume, cover letter, answers to questions on the application form and any supporting documents," and they "review applications in the order they were sent." The file in that record is a snapshot. Most systems also parse it once, at submission, into searchable fields. iCIMS, for example, keeps a visual copy of your actual resume so recruiters see your formatting, and builds your searchable skills list from the full text of that file.
Second, if the system has candidate accounts at all, it keeps a profile for you: name, contact details, a default resume, your list of applications. That's the thing you log into. Workday calls it Candidate Home; iCIMS gives you a dashboard per employer; Greenhouse has MyGreenhouse; Ashby shows it on your application page. The profile is yours to edit. The application record, in most systems, is not.
So when you "update your resume in the portal," you're editing the profile. The recruiter isn't reading the profile. They're reading the application. And once you've submitted, the company, not the vendor, owns that record: Greenhouse tells candidates that "the company to which you apply becomes what's called the 'controller' of your personal information in your application," and that if you want to change anything, you contact the company, not Greenhouse.
What does each ATS do with an updated resume?
Here's the vendor-by-vendor version. Check the URL of the page you applied on to see which one you're dealing with: myworkdayjobs.com, boards.greenhouse.io or job-boards.greenhouse.io, careers-<company>.icims.com, jobs.lever.co, jobs.ashbyhq.com.
| ATS | Can you edit a submitted application? | Does a profile resume change reach an existing application? | What works instead |
|---|---|---|---|
| Workday | No. "You cannot change your application after submission." | No. Candidate Home lets you view or withdraw. | Withdraw and reapply while the posting is open, or email the recruiter. |
| Greenhouse | No candidate-side edit. Contact the company. | No. Applications are per-job snapshots; the company controls the record. | Email the recruiter. Reapplying can trip an auto-reject rule (below). |
| iCIMS | No. The dashboard "doesn't let you swap documents on a submitted application." | No. Profile updates don't change what's attached to the application. | Contact the recruiter, or withdraw and reapply while the posting is open. |
| Lever | No. There's no candidate account to edit from. | No. Each application attaches its own resume; only the hiring team can add or remove files. | Email the recruiter with the new file. |
| Ashby | No direct edit, but the application resume and profile resume are linked. | Partly. Recruiters see the application resume by default, with an option to view the latest profile resume if it's newer. | Update, then tell the recruiter there's a newer version to open. |
Workday is the strictest and the most common at large companies. The candidate-facing instructions that universities and enterprises publish for their Workday sites say the same sentence, nearly word for word: "You cannot change your application after submission." Candidate Home shows your submitted applications, and the action menu gives you two choices, view or withdraw. Uploading a new resume to your profile changes what pre-fills your next application. It doesn't touch the one already in a recruiter's queue.
Greenhouse has no candidate login for editing at all. MyGreenhouse exists to track your applications, and its own FAQ sends you to the company for any change. What Greenhouse does give companies is a set of application-limit rules: they can "restrict applications over a period of time," limiting how many applications a candidate can submit in a given number of days, and they can block rejected candidates from reapplying for a set period. Applications that break the rule are moved to rejected and labeled "blocked by auto reject rule." That's the trap in the withdraw-and-reapply plan on a Greenhouse board: if the company has set a frequency limit, your second, better application can be auto-rejected before a person sees it, and you'll never know which version they read.
iCIMS is the one from the story above, and the one that fools people most, because the portal looks like it should work. You get a real logged-in dashboard for each employer where you can see statuses, withdraw, set alerts, and update your profile. What it doesn't let you do is swap documents on a submitted application. The guidance from people who work these portals is consistent: to correct a resume after submitting, contact the recruiter, or withdraw and reapply while the posting is open.
Lever doesn't have a candidate portal. You apply on a hosted job page, the application creates an opportunity on the company's side, and the resume you attached is stored on that opportunity. Lever's help documentation on adding and deleting resumes is written for the hiring team, because they're the only ones who can. If you applied through Lever and want a different file on record, a human at the company has to attach it.
Ashby is the one place the profile and the application talk to each other. Ashby's March 2025 release notes on resume display say it directly: "The resume uploaded on the application form will be displayed on both the application and candidate profile. If the application's resume is updated, it updates both the application and candidate profile's resume." But read the review side too: when both exist, "you'll see the application resume. If the candidate profile's resume is more current, you'll see an option to view the latest resume." So on Ashby, an update surfaces as an option the recruiter can click. It is not the default view. If you don't tell them it's there, most won't.
For contrast, this is what a system built to allow updates looks like. USAJOBS lets you edit an application until the announcement closes, and it tells you exactly what the agency sees: "agencies will see both your old and new information. The agency will review your most recent submission." No private-sector ATS in the table above makes that promise.
Should you withdraw and reapply?
Sometimes. Three questions decide it.
Is the posting still fresh? This matters more than the resume. Recruiters work the pile top-down and the shortlist often exists within days; we've written the full recency case. If you applied yesterday and realized this morning that you sent the wrong file, withdraw and resubmit now, while your application would still land in the first tranche either way. If the posting is two weeks old, your new application goes to the bottom of a pile that has probably already been screened. A better resume at position 300 is still at position 300.
Which system is it? On Workday and iCIMS, withdraw-and-reapply is the documented path, and it works while the posting is open. On Greenhouse, check whether you're likely to hit an application-limit rule; a second application within a short window can be auto-rejected, and that status is invisible to you. On Lever and Ashby, there's no withdraw button on your side, so you're back to email anyway.
Was the first version actually wrong, or just weaker? "Wrong" means the wrong file, an old phone number, a role that no longer matches. Fix wrong. "Weaker" means you'd phrase three bullets better now. Every applicant would. If the first version was accurate and matched the core requirements, the recruiter's decision will not turn on the improved phrasing, and the cost of a duplicate record (two entries for you, a confused recruiter, a possible auto-reject) is real. Let it stand and spend the effort on the next posting.
If you do reapply, withdraw first where the system lets you, use the same email address so the records merge rather than duplicate, and don't play games with a second identity. Recruiters see duplicates, and a candidate who looks like they're gaming the board is an easy no.
What works better than either: one email, with the file attached
For a role you actually want, the highest-yield move is the boring one. Find the recruiter or hiring manager (the posting sometimes names them; LinkedIn usually does), and send this:
Subject: Updated resume for [Role], applied [date]
Hi [Name], I applied for [Role] on [date] through your careers site. I've since tightened my resume to speak to the [specific requirement, e.g. Kafka and payments-ledger work] the posting calls for, and I'd rather you have the current version. It's attached. Happy to answer anything.
Four lines. The attachment does the work. It puts the file in front of a human, which is the only place a resume was ever going to be read, it doesn't create a duplicate record, and it costs the recruiter nothing. If they want it in the system, they'll attach it themselves; in every ATS in the table, the hiring team can. If you never hear back, you've lost nothing the portal edit would have gained you.
One caution. Send it once. Don't send the updated file, then a follow-up, then another version. If you're still in the process and a screen is scheduled, bring the new resume up in the call instead: "I've updated my resume since applying, which version do you have?" Recruiters can see the upload date on the file, and they'll tell you.
How to stop this happening on the next application
The engineer in the story didn't have a portal problem. They had a sequencing problem: they got better at tailoring after the application went out, on a posting that was already a week old. That's the pattern to break.
→ Tailor before you submit, every time. Keep one base resume and rewrite it for the posting you're about to apply to: match the title, lead with the three things the description cares about, mirror the stack vocabulary. The ATS-proof resume guide covers what parsers actually rank.
→ Apply on the day the role opens, not the week after. The window where an application reliably gets read is short. Recency plus fit beats a perfect resume sent late; the data on volume is unambiguous about that.
→ Keep a copy of exactly what you sent, per application. Not "the resume," but the version that went to that company on that date. When a recruiter calls, you need to know what they're looking at. A folder named by company and date is enough.
→ Treat the portal profile as a pre-fill, not a record. It saves you typing on the next application. It is not where your candidacy lives.
The last two are the reason I built the application step into hirecomb the way I did: it scores each fresh posting against your real resume before anything is queued, tailors the file to that posting, applies from your own browser the morning the role goes up, and keeps the exact version it sent on each application's record. Because once it's submitted, that's the version that exists.
Send the right version the first time
FAQ
If I upload a new resume to my Workday profile, does the job I already applied to get it?
No. Workday locks applications at submission; the published candidate instructions for Workday sites state "you cannot change your application after submission." Candidate Home only lets you view or withdraw. The new profile resume will pre-fill your next application. For the existing one, withdraw and reapply while the posting is open, or email the recruiter the file.
Can I edit my Greenhouse application after submitting?
Not from your side. Greenhouse's candidate FAQ says the company you applied to controls your application data and that changes go through the company, not Greenhouse. Be careful with reapplying: companies can set application-limit rules that auto-reject a second application within a set number of days, and the rejection is labeled "blocked by auto reject rule" on their end, not yours. Emailing the recruiter the updated file is safer.
Does updating my resume on an iCIMS profile change my submitted application?
No. The iCIMS candidate dashboard lets you update your profile, check statuses, and withdraw, but it does not let you swap documents on an application you've already submitted. To correct a resume, contact the recruiter, or withdraw and reapply while the posting is still open.
Is it bad to apply to the same job twice?
It's risky when it creates a duplicate record or trips a limit rule, and pointless when the posting is already old enough that the shortlist exists. It's fine when the first application was genuinely wrong (wrong file, wrong details), the posting is still fresh, and you withdraw the first one where the system allows it, using the same email so the records merge. If you're only reapplying because you'd phrase things better now, send the recruiter the new file instead.
Sources: recruiter view and review order, Greenhouse, "What really happens after you apply for a job?"; data controller and changing an application, MyGreenhouse FAQ; application-limit and reapply rules, Greenhouse Support, "Set application limits for job posts". Workday post-submission rule and Candidate Home actions, Workday application instructions for external applicants (Washington and Lee University); the same wording appears on other employers' Workday instruction pages. iCIMS dashboard limits and correction path, NotchResume, iCIMS job application guide (2026); iCIMS candidate documentation, iCIMS Community, Candidate Guide. Lever resume handling (hiring-team side), Lever Help Center, "Adding and deleting resumes". Ashby application and profile resume behavior, Ashby product update, "Resume display" (March 7, 2025). Federal contrast, USAJOBS Help, "Update an application". Vendor behavior can change with releases and per-company configuration; where a company has customized its portal, its own careers FAQ wins.