What happens after you click Submit on a job application

Short answer: your application stops being a document and becomes a database record — a candidate attached to one specific job, parked in the first stage of that job's pipeline, waiting for a person to open it. No score is calculated. A rule may close it before anyone looks, but that rule was written weeks before you arrived, and it checks an answer you typed into the form rather than judging your resume.

Greenhouse, Workday and Ashby all publish how this works, in help pages written for the recruiters who configure them rather than for you. Read from that side, most of what job seekers argue about turns out to be a checkbox somebody ticked before the posting went up — whether you get a confirmation email, which applications get read first, how many days a rejection sits in a queue before it is sent. The rest of this post is those settings, named.

The first minute, in order

What the system does between your click and the recruiter's screen

The sequence is the same across Greenhouse, Workday and Ashby; only the names of the stages differ.

1. 1
   The form posts

   Your answers and your file go to the employer's own tenant of the applicant tracking system (ATS). No email is sent to a recruiter at this point.

2. 2
   The parser reads the file

   Software scans the resume and auto-fills the fields it recognises. Greenhouse cannot parse a file larger than 2.5MB, and it also names columned layouts, complex tables, graphics, spaced-out letters and resumes uploaded as an image.

3. 3
   A candidate record is created

   Your name, contact details and form answers become structured data attached to one job. The file itself is stored as an attachment beside it.

4. 4
   Rules fire

   Duplicate matching, source tracking, any auto-reject conditions the employer configured, and the confirmation email — if the employer turned it on.

5. 5
   It enters the review stage

   In Greenhouse this is Application Review, automatically the first stage in every job's interview plan. Your application waits there until a reviewer advances or rejects it.

Notice what is not on that list. Nothing ranks you against the other applicants, nothing compares your resume to the job description and produces a number, and nothing forwards you to a hiring manager. The parser's job is transcription, not assessment. Which is exactly why a Graphic Designer who submits a beautifully typeset two-column portfolio resume can arrive as a candidate record with a blank name field and no phone number — Greenhouse lists columned layouts and image-based files among the things its parser cannot read.

A failed parse is not a rejection, and it is worth knowing what the fallback is. Greenhouse's own guidance to recruiters when parsing fails is to "manually input the candidate's details into the fields," which is a task nobody enjoys and some people skip. Greenhouse also documents that the parser deliberately skips what it judges to be fake data — placeholder names like "First Last," or company names along the lines of "Company 1." Anonymised sample resumes get treated as noise on purpose.

What actually changed when you pressed the button

That table is not a rhetorical flourish. Each row marks the difference between an action that changes your odds and an action that changes nothing, and most application advice fails because it is written against the left column. A Graphic Designer who spends an evening reformatting a portfolio PDF is working on the left column. Fixing a blank contact field is working on the right one.

Who opens it first, and in what order

The queue is real, and its order is a setting. Ashby lets a reviewer "specify the order in which applications are reviewed, either starting with the newest application or the oldest." Those two choices produce opposite experiences for the same person. Newest-first means the applicant who submitted at 11pm on the day the post went live is read after everyone who came later; oldest-first means that same applicant is read first and the latecomers wait.

In Greenhouse, Application Review "is a unique stage that is automatically added as the first stage in every job's interview plan," and the reviewer has two buttons: advance and reject. Reject opens a workflow where they choose a rejection reason and send or schedule the email. Advance moves you to whatever the hiring team put next — a phone screen, a portfolio walkthrough, a paid test.

Greenhouse also surfaces a "Review priority" link covering referrals, internal applicants and agency submissions. So a Graphic Designer applying cold sits in the general queue, while the same designer referred by someone inside the company lands in a group the reviewer can jump straight to. That is the whole mechanical advantage of a referral. It is worth considerably more than any rewording of your summary line.

The set of people who can do this is also smaller than most applicants assume. Ashby requires "elevated access hiring manager privileges or higher on the job to review applications," so the queue is not open to the whole company; it belongs to a named recruiter and hiring manager. When those two are travelling, interviewing, or covering four other requisitions, the queue does not move. That is the ordinary reason for a fortnight of silence, and it has nothing to do with your file.

Why you got no confirmation email

Because the employer switched it off. Greenhouse says so on its own candidate-facing page: organizations "can configure job posts to send confirmation emails to candidates when they have applied for a job. However, some organizations opt not to send these confirmation emails."

That page then points candidates back to the employer's own recruiting team, and a separate Greenhouse page is blunter still: "MyGreenhouse and Greenhouse Support can't see a company's internal hiring decisions or contact recruiters for you." So there is nobody at the vendor to appeal to. A missing email is not a failed submission, and it carries no information about you. Two Graphic Designer applications sent the same afternoon can produce one auto-reply and one silence, purely because two employers configured the same field differently.

Can it be rejected before a human reads it?

Yes — on conditions the employer wrote in advance, and only from your form answers.

Ashby's auto-reject "will evaluate all new applications" once it has been configured and switched on. The rules are built on application form fields, with operators including is empty, is not empty, equals, contains, starts with, ends with and "similar to", joined by and, or and not. It reads the structured answers, not your resume prose, and it does not run backwards: Ashby notes that auto-reject "doesn't currently support applying the rule to historical applications."

Here is the part worth arguing about. Ashby also lets an employer "configure the number of business days to delay the rejection email to candidates," which means the rejection that landed on Thursday for the application you sent on Monday may have been decided the instant you clicked, with three days of silence added on purpose. A polite four-day rejection is not evidence that a human weighed you; the delay is a field in a settings panel. That is not a complaint about employers — the delay usually exists to spare people the sting of an instant no — but it does mean response timing tells you far less than job seekers read into it.

The practical consequence is narrow and useful. Check your answers to the short screening questions harder than you check your resume. Work authorisation, location, years of experience, degree, on-site availability: a Graphic Designer who ticks "no" to office attendance on a hybrid requisition can be archived by a rule before the portfolio link is ever clicked.

What a rejection is, inside the system

Not a deletion. In Greenhouse, rejecting from Application Review launches a workflow in which the reviewer picks a rejection reason, answers whatever custom questions the company has configured, and then sends or schedules the email. Ashby's equivalent is archiving: the reviewer clicks archive, "select[s] an archive reason, and optionally email[s] the candidate a rejection email." Optionally is the word to sit with.

So the Graphic Designer whose application went quiet in March may be a closed record with a reason attached — wrong seniority, no motion design, req cancelled — that was never sent anywhere. The reason exists. It is written down. It is simply internal, and neither the vendor nor its support team will retrieve it for you.

What the status page will and will not tell you

What each system shows the applicant after submission

Candidate-facing visibility, from each vendor's own documentation. Almost all of it is optional for the employer.

	Greenhouse (MyGreenhouse)	Workday (Candidate Home)
An account you can log back into	Yes	Yes, where the employer set up Candidate Home
A visible application status	Only if the employer chooses to share it	Draft and submitted applications are listed
Statuses set automatically	Applied, Hired, Application closed	—
Optional statuses the employer picks	In review, Initial screen, Technical interview, Assessment, Reference check, Offer and others	—
Half-finished applications kept	—	My Draft Applications
Withdraw your own application	—	Yes, where the employer configured it
Support can tell you why you were rejected	No	No

Greenhouse is blunt about the limits. "You may see a high-level status, but not every step or decision in the hiring process," and "a status may stay the same until the hiring team shares a new update." Neither MyGreenhouse nor Greenhouse Support "can see a company's internal hiring decisions or contact recruiters for you." Workday's Candidate Home is more generous in one direction only: it lets you withdraw, complete tasks the employer sends you, and reopen drafts you never finished, while telling you nothing about the decision.

Read a status page for what it is. It confirms the application exists and shows you whether it has been closed. It does not tell you where you stand against anyone else. A Graphic Designer sitting on "In review" for six weeks and one sitting on it for six days are looking at the same word.

If you applied to the same company twice

This is the edge case people worry about most, and Workday documents the answer. Workday automatically merges two candidates when "First Name and Last Name are exact matches and at least 1 of these fields is an exact match: Phone Number, Email Address, LinkedIn URL," among a few others. One condition matters more than the rest: Workday "doesn't automatically merge 2 candidates if at least 1 of them has a registered Candidate Home account."

The practical fallout is small but real. Apply to one Graphic Designer opening with a personal address and to a second opening at the same company with a different one, and you can leave two unlinked records behind, so a recruiter searching your name sees half your history. Use one email address per employer, spelled identically, every time. Where the career site offers an account, make it and reuse it.

How long until you hear back?

The size of the market your application joined, July 2026

7.3MJob openings

5.1MHires

3.1MQuits

BLS reported 7.3 million job openings and 5.1 million hires in July 2026, an openings rate of 4.4 percent against a hires rate of 3.2 percent. Openings carry over from month to month. A posting still live three weeks after you applied is behaving normally rather than ignoring you.

The churn underneath is the other half of the picture. Total separations also ran at 5.1 million in July 2026 — 3.1 million quits, 1.7 million layoffs and discharges. Each departure is a seat that may or may not be refilled, which is why postings arrive in bursts rather than at a steady rate.

Now the caveat, which matters more than the figures. JOLTS counts openings, hires and separations — it does not count applications, and no federal series measures the time between submitting a form and getting a reply. Anyone quoting an average days-to-response is quoting a vendor's sample of its own customers, not public data. What JOLTS does support is narrower and still useful: hiring at national scale runs on a monthly clock, so a two-week silence sits comfortably inside the normal band.

For a Graphic Designer the arithmetic is tighter than average. BLS put employment at 253,100 in 2025, projects a 2 percent decline through 2035, and still expects roughly 16,000 openings a year, most of them from people leaving the occupation rather than new roles being created. A shrinking field with steady churn means real openings, spaced further apart, each drawing a deeper queue.

When you do follow up, keep it to four lines and send it to the address that confirmed your application:

Hi — I applied for the Graphic Designer role (req 4412) on 12 August and wanted to confirm my application is sitting in the right queue. Happy to send additional portfolio work if that would help. Thanks for your time.

The one thing to get right

Before you submit anything else, reread your answers to the short screening questions — the dropdowns and the yes/no boxes, not the resume. Those answers are the only part of your application a rule can act on by itself, they are the part you can still change in thirty seconds, and an archived application never reaches the queue where a person would have opened your work. For a Graphic Designer that is the difference between a portfolio link being clicked and a record being closed with a reason you never see.

If retyping the same fields into every one of these forms is what is slowing you down, the platform answers the screening questions from your resume so the answers that decide the outcome get your attention instead.