Follow up on a job application about one week after you apply, or after the review window the posting named, whichever is later. Send one short email to the recruiter or hiring manager: name the role and the date you applied, add one line of evidence they did not already have, and ask a single question about next steps. If that gets no answer, send one more note roughly a week later and then stop. Two well-timed messages are the whole of a good follow-up, because a third one stops being about the job and starts being about how the wait is going for you.
Should I follow up after applying
Yes, once. It matters less than you hope and costs less than you fear.
People ask this question in one of two moods. Either they are convinced a follow-up is the secret handshake that gets the application read, or they are terrified it is the thing that gets them quietly binned. Both moods are wrong in the same direction: they treat the message as far more powerful than it is.
Here is the honest shape of it. A follow-up will not rescue an application that does not fit the role. It will not talk anyone past a requirement you do not meet. What it can do is small and real. It puts your name in front of a human being at a moment when they are actually looking at the pipeline, it demonstrates that you can write a clear paragraph and ask for one thing, and it gives you a second chance to say the one sentence you wish you had led with. On a shortlist of people who look similar on paper, that is not nothing.
It also fixes the failure that actually costs people jobs, which is not being forgotten by an employer. It is forgetting the employer. Applications pile up, the weeks blur, and the role you were most excited about in week two goes unchased in week five because it is buried under fourteen newer ones. The follow-up is the ritual that stops that happening.
So the answer is yes, follow up, and follow up once, deliberately. The rest of this page is about doing it in a way that reads as professional rather than anxious, because the difference between those two is almost entirely timing and specificity.
How long after applying should I follow up
The timeline, from the day you hit submit.
There is no rule anyone enforces here, but there is a range that reads as normal to the person on the other end. Pick a date at the moment you apply and put it somewhere you will see it, because the date you never pick is the follow-up you never send.
Day 0. Read the posting for the rules, then set a date.
Before you close the tab, look for two things. Does the posting name a review window or a decision date, and does it say no phone calls or no follow-ups. If it names a date, your clock starts when that date passes. If it asks you not to chase, do not chase; some teams mean it and following up anyway is the one way this genuinely counts against you. Write the follow-up date down while you still care, because motivation about a company decays faster than the hiring process moves.
Day 5 to 10. Send the first and only real nudge.
One business week is the comfortable middle. Earlier than five business days and you look like someone who has not worked in a company; later than two weeks and the pipeline may already have moved without you. Send it in the morning, midweek, addressed to a named person if you can find one. Keep it short enough to read on a phone without scrolling, and end with a question rather than a hope, because a question is something a busy person can answer in nine seconds.
Day 12 to 17. The second note, and it is the last.
If the first one drew nothing, send a single short close-out about a week later. This is not the same email again in a different jumper. It restates your interest in one line, adds a concrete reason you would be useful, and explicitly makes it easy to say no or say nothing. Then it lets go. Two messages is a professional following a process. Four is a person the recruiter now associates with a slight sinking feeling.
After that. Change the channel, not the volume.
Stop emailing the same address. If you still want the role, look for a different door: someone in the team you can ask a real question of, a hiring manager who posts publicly, a referral from anyone you already know inside. That is a different conversation with different rules, and it is far more likely to move than a fifth message into the same silence. Meanwhile, treat the application as closed in your own records, so your energy goes where the process is actually alive.
What to say in a follow up email after applying
Six parts. That is the whole email.
The best follow-up is boring in structure and specific in content. It should be readable in under twenty seconds and answerable in one line. Here is every component, and why each one earns its place.
Part 1
A subject line that identifies you, not your feelings
Put the role title and the date you applied in the subject. Something like: Product Designer application, submitted 2 June. It sorts, it searches, and it means the reader knows what this is before opening it. A subject line that reads "Following up" or "Checking in" tells them nothing and looks like every other unopened message in the folder.
Part 2
The first line does the identifying
Name the exact role, the exact date, and where you applied. Recruiters run several searches at once and your application is one row in a system they have to go and look up. Make that lookup take three seconds. Never make the first sentence about how excited you are; make it about which of the many people writing to them you happen to be.
Part 3
One hook that is specific to them
A single clause proving you read the posting and not a generic template. The system they named, the market they are moving into, the sentence in the job description that told you what the job actually is. This is the line that makes the email unsendable to any other company, and unsendable is the standard.
Part 4
Something new, however small
A follow-up that adds nothing is a request for unpaid attention. Add one thing they did not have: a project you shipped since applying, a piece of work that maps directly onto the problem in the posting, a link to the exact page of your portfolio that shows the thing they said they need. This is the part almost everyone skips, and it is the entire reason the email gets a reply.
Part 5
One question, easy to answer
Ask about the process, not about yourself. Whether the team is still reviewing, whether there is a timeline for first conversations, whether they need anything else from you. One question, closed-ended enough that a two-word answer is a complete answer. Do not ask for feedback on your application; that is a lot of work to ask of a stranger.
Part 6
A sign-off with an exit
Give them a graceful way to not reply. A single sentence such as: happy to leave it there if the role has moved on. It sounds like it weakens the email and it does the opposite, because it removes the awkwardness that makes people avoid answering at all. You look secure, and secure is the tone the entire message is trying to buy.
Templates
Three follow-up emails you can copy today.
Change every bracket. If you send these as-is, they will read exactly like a template, which is the one thing they cannot afford to do. Each is written to be skimmed on a phone in a corridor, because that is where they will be read.
The one-week nudge, when you have a name
Subject: [Role title] application, submitted [date]. Body: Hi [Name], I applied for the [role title] role on [date] and wanted to check in briefly. The part of the posting about [the specific problem they described] is close to what I spent the last year on at [company], where I [one concrete outcome]. Since applying I have also [the new thing: shipped, published, finished]. Is the team still reviewing for this one, or has it moved to interviews. Happy to leave it there if it has been filled. Best, [Your name], [link to your site].
The one-week nudge, when the portal ate your application
Subject: [Role title], applied [date] via [portal name]. Body: Hi, I submitted an application for [role title] on [date] through your careers site and have not heard back, so I am sending this in case it is easier to answer here. Short version of why I applied: [one sentence, the strongest match to the posting]. My work is at [your link], and the [specific project] there is the closest thing I have to what this role is asking for. Could you tell me whether the role is still open. If it is not, no reply needed and thank you for reading. Best, [Your name].
The close-out, sent about a week after the nudge
Subject: Re: [Role title] application, submitted [date]. Body: Hi [Name], last note from me on this one. I am still interested in [role title], and if it helps, [the one line of new evidence: a shipped project, a result, a relevant piece you published]. If the role has been filled or paused, that is completely fine and I would rather know than wonder. Either way, I would be glad to be considered when something similar opens up. Best, [Your name].
The part nobody writes about
You cannot follow up on an application you cannot find.
Every guide tells you what to write. Almost none of them address why the email never gets written, which is that six weeks in, you no longer know who you applied to, on what day, with which resume, or what the posting even said. Here is what that looks like in the three places people keep it.
| Capability | Folio | Your inbox and sent folder | Memory and open tabs |
|---|---|---|---|
| The date you applied | A date field on the job card. You type it when you apply, and it stays visible on the board. | Guessable from the confirmation email, if there was one and if you can find it. | Gone. You will write "a few weeks ago" in the email and sound like it. |
| The date you decided to chase | A follow-up date you type on the same card, sitting next to the applied date so the gap is obvious at a glance. | Not a thing an inbox holds. You are relying on remembering to search for it. | The date does not exist, which is why the follow-up does not either. |
| A person to write to | The notes field on the card, where you put the recruiter name the moment you find it. | Sometimes. The no-reply address that confirmed your application is not a person. | You will address it to whoever seems senior on the company page and hope. |
| The wording of the posting, weeks later | The full job description is stored on the card, so the hook line in your email quotes the real thing. | Only if you emailed it to yourself. Most people saved a link that now 404s. | You will paraphrase from memory, and it will be generic, and they will feel it. |
| Something specific to add in the note | The card scores the posting against your profile from 0 to 100 and names the terms it leans on that your profile never uses. Those terms are your new line. | You reread the posting and trust your judgement, which is optimistic at 11pm. | You write that you are very excited about the opportunity. |
| What it costs | Nothing. The board, the stages, the stored job description and the match score carry no plan gate, and the resume exports to PDF or DOCX with no watermark on Free. | Free, and it fails quietly rather than loudly, which is worse. | Free until the week you apply to the same company twice. |
Be clear about what this is: a record, not a robot. Folio does not send the follow-up email, does not notify you when a date arrives, and does not know whether anyone opened anything. You type the applied date, you type the follow-up date, and you look at the board. The tool removes the excuse, not the work.
When nobody ever replies
Silence, ghost jobs, and what you can actually conclude.
The most common outcome of a job application is nothing. Not a rejection, not a maybe. Nothing. This is unpleasant and it is also almost never a verdict on you, so it is worth understanding the machinery that produces it before you take it personally.
A posting can stay live long after the role is gone. Headcount gets frozen mid-process and nobody goes back to unpublish the ad. A role gets filled internally by a person who was always going to get it, and the external search was a formality someone in compliance asked for. A team keeps an evergreen posting up to gather a pipeline for a role they hope to open next quarter. In every one of these cases you sent a considered application into a process that had already ended or had never really begun, and nobody on the other side thinks to tell you.
You cannot reliably tell these apart from outside, and the effort spent trying is effort you could spend applying somewhere the process is alive. A few weak signals are worth noticing: a posting that has been reposted repeatedly over months, a job description so vague it could describe four different roles, a company that is publicly not hiring. None of them are proof. Treat them as reasons to lower your investment, not as reasons to skip applying if the role genuinely fits.
What you can control is your own accounting. Two messages, then the application is closed in your records, whatever the employer does or does not do. Closing it yourself is the point. It is what stops a search turning into a long list of open loops that you carry around all day and never quite resolve.
Where Folio fits, and where it does not
The honest version of the product pitch.
Folio has a job tracker with five stages: saved, applied, interview, offer, rejected. Each card holds the company, the role title, the link, the location, a salary note, your private notes, the full text of the job description, an applied date and a follow-up date. The two dates are the reason this page mentions it at all. You type them, and from then on the card knows what you did and what you owe, which is exactly the information that goes missing in the sixth week of a search.
Being precise about the limits, because the internet is full of tools that are vague about theirs. Folio sends no email on your behalf. It raises no notification when a follow-up date arrives. It does not derive that date from your applied date and it will not nag you. There is no open tracking, no reply rate, no auto-apply, and no browser extension. Anything that looks like a response metric would just be the statuses you typed in yourself, played back to you as insight, and you already know what you typed.
What it does do that a sheet cannot is read the posting. Paste the job description onto the card and Folio scores it against your Folio profile, from 0 to 100, and lists the terms the posting depends on that your profile never uses. That computation runs on Folio, deterministically, and the same inputs always produce the same number. It reads the profile you wrote, not a PDF you uploaded. Practically, that missing-terms list is the fourth part of the email above: the new thing you have to say.
And the money, stated straight. The tracker, the stages, the stored job description, the match score and the resume export to PDF and DOCX all cost nothing, with no watermark on the export. What the Free plan does not give you is a domain of your own; you get a portfolio.wrxstack.com address, a Made with Folio credit on the site, 10 AI drafting generations a month, and the core designs rather than the full theme gallery. Nobody gives away a domain, and a page that tells you otherwise is selling you something later.
Frequently asked questions
How long after applying should I follow up on a job application?
One business week is the safe opening move, and anything between five and ten business days reads as normal to the person receiving it. If the posting named a review window or a decision date, that overrides the rule and you wait for it to pass. Under five days you look like you have never worked inside a hiring process; past two weeks the shortlist may already exist without you on it.
Should I follow up after applying for a job, or does it annoy recruiters?
Follow up once. A short, specific note that adds a fact and asks one clear question is a normal professional courtesy and very few people mind receiving it. What actually irritates the reader is volume and vagueness: the fourth message in three weeks, or a message that says nothing except that you are still there. The exception is a posting that explicitly asks for no calls or no follow-ups, and in that case respect it, because ignoring a stated instruction is the one version of this that reliably counts against you.
What should I say in a follow up email after applying?
Six things, in this order: a subject line carrying the role and the date you applied, an opening sentence that identifies which application this is, one clause proving you read the posting rather than a template, one piece of evidence they did not already have, a single easy question about where the process stands, and a sign-off that lets them off the hook if the role has moved on. Keep the whole thing under about a hundred and fifty words. If it cannot be read on a phone without scrolling, it will not be read at all.
Should I call to follow up on a job application, and what do I say?
Only if the posting invites it or you already have a working relationship with the person. A cold call reaches someone mid-task and forces an answer they are not prepared to give, which is a bad trade for both of you. If you do call, say who you are, name the role and the day you applied, ask one question about the timeline, and offer to get off the line inside a minute. Then send the same content as an email anyway, because the phone leaves no record and the recruiter will forget the call by the afternoon.
Who do I follow up with if I applied through a portal and have no contact?
Write to whichever named human is closest to the role: the recruiter on the posting, the hiring manager it reports to, or the team lead who is visible publicly. Failing all three, the company careers address is still worth one message, because a real human tends to sit behind it. Say in the first line that you applied through the portal on a given date, so the reader can find the record, and never resubmit the application itself as a way of getting noticed. A duplicate application is noise in their system and it does not read as keenness.
What do I do if I never hear back after following up twice?
Close it out on your own side and move the energy. A posting can outlive the role, a headcount can freeze mid-process, and an internal candidate can win without anyone updating the ad, and in every one of those cases the silence was never a message to you. Mark the application dead in whatever you track it in, stop rereading the job description, and put the next hour into a role where the process is still moving. The one thing worth keeping is the connection: if a named person was decent to you, they are a reasonable person to write to when the next role opens.