A dry run job application in ApplyEze is a full rehearsal on a real posting: the app opens the employer's form in a browser you can see, fills it from your profile, uploads the resume it wrote for that posting, plus a cover letter when the form asks, and never clicks Submit. Nothing reaches the employer. ApplyEze makes the app this post describes, so read it as the vendor's account, written to be checkable: everything below is something you can watch happen on your own screen. This page covers what a dry run does and never does, what to look at while it runs, how lanes behave, when to switch to live, and what a dry run cannot tell you.
Why test before you trust
Handing your job search to software is a real decision. In Huntr's Q3 2025 survey of 527 job seekers, 52% said they would trust AI to apply on their behalf and 48% preferred to keep direct control. Automated applying is also common: a 2025 Greenhouse survey of more than 2,200 job seekers in the US, UK and Ireland found that 22% use automated bots to submit applications. Both are vendor surveys. The useful point is that the people in the second group should be able to see exactly what goes out under their name, and a dry run is how you see it without sending anything.
What a dry run does, and what it never does
| A dry run does | A dry run never does |
|---|---|
| Opens the real application form on the employer's platform | Click Submit |
| Fills every field it can from your profile, and reuses your saved answers for work authorization and EEO questions | Send anything to the employer |
| Uploads a resume written for that posting, and a cover letter when the form asks (each made as PDF and DOCX and read back by a parser check before upload) | Stop on a required question your saved answers do not cover: it still fills it, so that answer may not come from you |
| Runs in a visible browser window you can watch, by default | Act as an approval step for that particular application |
The last row matters. A dry run is a test of your setup on real forms. It is not a queue of finished applications waiting for your sign-off, and it does not turn into one. When you are satisfied, you switch to live and later runs submit.
Watching the browser fill the form
The browser is visible by default. You see the same pages a person applying by hand would see: the employer's job page, the form, the upload fields, the questions. Headless mode is optional and hides the windows, which is useful later but defeats the purpose of a dry run.
What you will notice on a first watch:
- It works through the form you would see. Some forms are one page; others run across several pages, and you watch each one being filled.
- Uploads are written for the posting, not a generic file. The resume, and the cover letter when the form asks for one, are the ones written for that posting.
- Dropdowns and radio buttons are filled from saved answers. Work authorization and EEO questions come from what you saved, when you saved an answer.
- A missing answer does not end the run. When a required question is not covered by your saved answers, ApplyEze still fills it rather than stopping the run, so that answer may not come from you. A dry run is where you catch that: you see the answer it wrote and can save your own before you go live.
What to check during a dry run
Keep this list next to you for the first two or three dry runs. It is ordered the way most forms are.
| Section of the form | What you should see | What would be wrong | What to fix |
|---|---|---|---|
| Name, email, phone, location | Exactly what is in your profile | An old email, a typo, a missing country code | Edit your profile |
| Resume upload | A resume written for this posting | Wrong file, or a skill you could not talk about in an interview | Read the tailored resume. There is no step to remove a skill before a live run, so be ready to discuss it |
| Cover letter upload | A letter written for this posting, when the form asks for one | A letter for another posting, or a claim you would not stand behind | Read the letter; correct the source resume or profile |
| Work history and education fields | Your employers, titles, dates, schools and degrees as you entered them | Any date, title or school that differs from yours | Correct the source resume or profile |
| Work authorization and sponsorship questions | Your saved answers, applied consistently | An answer that contradicts another on the same form | Update the saved answer |
| EEO and voluntary self-identification | Your saved choices | A choice you did not make | Update the saved answer |
| Final page | The form complete, Submit not clicked | The run stopping earlier | Note the field it stopped on |
Two items deserve a closer look.
The resume. ApplyEze writes a resume for each posting, and a dry run is the best moment to read one, before anything is sent. ApplyEze brings the posting's named skills and tools onto your skills line, even when your own record does not list them. There is no step to remove one before a live run, so use this dry run to see what it writes, and be ready to discuss anything on the page. A certification the posting asks for is not added unless you hold it. Your employers, job titles, dates, schools, degrees and certifications come from your own record, and code rejects a rewrite that adds a figure, employer, school or credential your record does not hold. Read the resume the way a recruiter would. More on how the tailoring works is in resume keyword matching.
EEO pages. These differ from employer to employer, and they are changing. The Department of Labor removed the rule (41 CFR 60-741.42) that required federal contractors to invite applicants to self-identify a disability, effective 21 September 2026, and OFCCP's forms page says the disability self-identification form is discontinued from that date. Forms you meet may or may not have caught up, so check how your saved answers land on the forms you actually meet.
Running dry runs in parallel lanes
ApplyEze runs up to 10 applications in parallel, each in its own browser window, with 3 by default. Each lane is its own browser window working on its own form, so you can watch several at once.
How to use lanes for testing:
- First dry run: one lane. You want to watch every field on one form without your eyes jumping between windows.
- Next: the default three. If your matches span several platforms, for example Greenhouse, Lever and Ashby, include one of each so you see how your profile fits each kind of form.
- Then: as many as you can follow. More lanes test more forms at once, but only if you can still see what each window is doing. Raise the count when checking has become routine.
When to switch to live
There is no fixed number of dry runs to do first. Use the evidence.
| What you saw in your dry runs | What it means | Next step |
|---|---|---|
| Forms completed, uploads correct, answers right, on each platform you care about | Your profile covers the questions you are meeting | Switch to live |
| One platform answers a question as you saved it, another does not | A gap specific to that kind of form | Add the answer, dry run that platform again |
| A work authorization or identity answer you did not give | Your saved answers do not cover it, so ApplyEze filled it anyway | Add the saved answer, then dry run again |
| The tailored resume shows a skill you cannot discuss | ApplyEze brought a skill the posting named onto your skills line | There is no step to remove it before a live run, so be ready to discuss anything on the page |
| Contact details wrong anywhere | Profile error | Fix it before any live run |
What a dry run cannot show you
Being clear about the limits is part of trusting the result.
- What happens after Submit. A dry run stops before it, so it cannot show the employer's confirmation page, a confirmation email, or an error that only appears when the form is sent.
- Every employer's form. Two employers on the same platform can ask different questions. A clean dry run on one Greenhouse form makes the next one likely, not certain.
- Platforms outside the list. ApplyEze completes applications on 12 platforms: Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, Oracle Recruiting Cloud, JazzHR, BambooHR, Rippling, Pinpoint and Recruitee. Workday and Oracle need a connected application inbox. A dry run will not make other platforms work.
- How the employer responds. Whether a recruiter reads the application, and whether it leads to an interview, is outside anything a test run can show.
- A promise about later runs. Postings close and forms change. A dry run tells you how your profile meets the forms you tested on the day you tested them.
Dry run compared with an approval step
Some tools take a different approach. Tsenta's changelog says that since 1 July 2026, "when an application is ready, Tsenta pauses right before the final submit and shows you everything it filled in", and that "nothing gets submitted until you say so". If you want to approve each application individually, that design fits you better.
ApplyEze does not hold live applications for approval. Its model is to test first, with dry runs you can watch, then run live with the same visible browser. Which fits depends on whether you want to approve every application or to check the setup and then let it run. For how the rest of the pipeline works, from matching to submit, see how job search automation works, and for how ApplyEze guards against sending the same application twice, see duplicate job applications.