When should I follow up after submitting a job application?
Wait 5-7 business days before following up on a submitted application. Following up sooner communicates impatience rather than interest. Your first follow-up should be a brief email to the recruiter that adds one piece of specific, relevant information — not simply asking if they received your application.
Most job seekers either follow up too aggressively (three emails in a week) or not at all (assuming silence means rejection). Neither approach serves your interests. A disciplined follow-up strategy keeps you visible without creating friction, and in some cases it directly influences hiring decisions by demonstrating persistence and professionalism.
This article covers when and how to follow up at each stage of the IT hiring process, the specific language that works, and the boundaries that prevent follow-up from damaging your candidacy.
Why Follow-Up Matters in IT Hiring
Hiring processes at technology companies are frequently delayed, disorganized, or deprioritized. A role may sit open for weeks because the hiring manager is in a sprint cycle, because an internal candidate emerged, or because budget approval is stuck. These delays have nothing to do with your candidacy — but without follow-up, you are invisible during the delay.
A well-timed follow-up serves three functions:
Keeps your name visible when hiring managers review their pipeline
Signals genuine interest in the specific role (unlike candidates who applied to 200 positions and forgot which is which)
Creates an opportunity to provide additional context that may have been missing from your application
The critical constraint is that follow-up must be appropriate in frequency and tone. One follow-up at the right time is professional. Three follow-ups in a week is a red flag.
"The candidates who get hired are not necessarily the most qualified — they are the ones who stayed visible and professional throughout a messy process. A well-timed follow-up reminds the hiring team that a real person is waiting, and that reminder matters more than most candidates think." — Lou Adler, CEO of The Adler Group and author of Hire With Your Head (Wiley), on candidate visibility in extended hiring cycles
Follow-Up Timing at a Glance
Before going through each stage in detail, here is the framework for when and how many times to follow up:
| Stage | When to Follow Up | Maximum Follow-Ups |
|---|---|---|
| After submitting application | 5-7 business days | 2 total |
| After recruiter phone screen | Thank-you within 24 hours; chase next steps after missed deadline | 1 chase |
| After technical interview | Thank-you within 24 hours; follow up if timeline passes | 1 chase |
| After final interview/panel | Thank-you within 24 hours; decision follow-up 2-3 days after stated timeline | 1 chase |
| After rejection or silence | One relationship-maintenance message | 1 final |
Stage 1: After Submitting an Application
Timing and Who to Contact
When to follow up: 5-7 business days after submission
Who to contact: The recruiter listed on the posting, or the hiring manager if you have their contact information from networking
What to say: Brief, specific, no demands
Subject: Following Up — Cloud Engineer Application (Job ID 4821)
Hi [Name],
I submitted my application for the Cloud Engineer role last week and wanted to follow up briefly. I have been working with Terraform and AWS for three years and recently completed a multi-account consolidation project very similar to what is described in the job description.
I am genuinely interested in this role and happy to provide any additional information. Thank you for your time.
[Your name]
This message adds one piece of specific, relevant content (the three-year Terraform/AWS experience and the relevant project) beyond what was already in the application. It does not ask "have you reviewed my application?" which puts the reviewer in a position of owing you a response.
How many times: Once. If you do not hear back within another week, you can send one more brief message. After two follow-ups with no response, that channel is exhausted.
Stage 2: After a Recruiter Phone Screen
The 24-Hour Thank-You
When to follow up: Send a thank-you within 24 hours. Follow up on next steps 2-3 days after the promised response date if you have not heard.
What to say in the thank-you:
Subject: Thank You — Cloud Engineer Phone Screen
Hi [Recruiter's Name],
Thank you for the conversation today. I came away even more interested in the Cloud Engineer role. The detail about the team's multi-cloud initiative aligns closely with the AWS-to-Azure migration work I did at [Company].
I look forward to the next steps you mentioned. Please let me know if you need anything else from me in the meantime.
The specificity matters: you are referencing something from the actual conversation, which demonstrates you were listening and engaged.
When to follow up on next steps: If the recruiter said "I will get back to you by Thursday" and Thursday passes, it is appropriate to send a single brief follow-up on Friday:
Hi [Name], just checking in as I have not heard back about next steps for the Cloud Engineer role. I remain very interested and happy to answer any questions. Thank you.
Tone: Calm and professional. Not "I have not heard from you and I am concerned." Simply a professional check-in.
Stage 3: After a Technical Interview
Individual Thank-You Notes
When to follow up: Send a thank-you within 24 hours to everyone who interviewed you, ideally individualized
What to say:
Subject: Thank You — Technical Interview
Hi [Interviewer's Name],
Thank you for the time today. The discussion about your Kubernetes migration was particularly interesting — the approach you described for handling stateful workloads maps to a problem I worked through last year, and I would have liked more time to dig into that.
I am excited about the possibility of joining the team. Please let me know if there is anything further I can provide.
If multiple people interviewed you, write individual notes with different specific references to each person's questions or topics where possible. Generic thank-you notes that are clearly the same template sent to everyone carry less weight.
Following up on decisions: If the interviewer gave you a timeline ("we expect to make a decision by next Friday") and that date passes without word:
Hi [Name], I wanted to follow up as I understand decisions were expected around this week for the Cloud Engineer role. I remain very interested and want to make sure I have not missed anything. Happy to provide additional references or any other information that would be helpful. Thank you.
Stage 4: After a Final Interview or Panel
What to Include in the Final Thank-You
When to follow up: Thank-you within 24 hours to each panel member. Decision follow-up 2-3 days after the stated timeline.
What to include in the thank-you: This is the most important thank-you in the process. It should:
Reference a specific technical or business topic from the interview
Reaffirm your interest clearly
Optionally, address any concern or question that came up that you could address better in writing
If you fumbled a technical question during the interview, this is an opportunity to acknowledge it and provide the better answer:
I want to note that I was not as sharp on the question about Kubernetes RBAC configuration as I would have liked to be. Upon reflection, the approach I would take is [specific answer]. I wanted to make sure that answer was clear.
This is a low-risk move. Hiring managers generally respond positively to candidates who acknowledge gaps honestly and fill them in.
When You Have a Competing Offer
If you receive an offer from another company while waiting on a response, it is appropriate to inform your preferred employer:
Hi [Name], I want to be transparent with you. I received an offer from another company with a deadline of [date]. Your team remains my first preference, and I wanted to let you know in case it affects your timeline. Please let me know if there is anything I can do to help the process move forward.
This is not pressure — it is relevant information that allows the hiring manager to make an informed decision about their own timeline. Many candidates get their first offer accelerated this way.
When No Means No
There are situations where additional follow-up will not help:
You received an explicit rejection email
You have sent two follow-ups with no response over two weeks
The recruiter told you the role was paused, cancelled, or filled
In the first two cases, it is acceptable to send one final message that keeps the door open for the future:
Thank you for considering me for this role. I understand the timing did not work out. If you have similar opportunities open in the future, I would be glad to reconnect. I will plan to check in in a few months.
This is a relationship maintenance move. Recruiters often fill roles through their existing candidate pool. Ending your interaction professionally keeps you in that pool.
The Follow-Up Log
Keep a record of every follow-up you have sent:
Company: Acme Corp
Role: Cloud Engineer
Applied: 2024-03-01
Recruiter screen: 2024-03-08
Thank you sent: 2024-03-08
Next steps promised: 2024-03-15
Follow-up sent: 2024-03-16
Technical interview: 2024-03-22
Thank you sent: 2024-03-22
Decision expected: 2024-03-29
Status: Waiting
Without tracking, it is easy to lose threads or inadvertently over-contact. The log also shows you where you are in each process at a glance.
Common Mistakes
Following up the day after applying: This communicates impatience, not interest. Five to seven business days is appropriate.
Asking about the timeline when none was given: "When will you be making a decision?" is a presumptuous question early in the process. Wait until you have been through at least one interview before asking about timeline.
Copying multiple people on follow-ups: Send follow-ups to one person. If that person does not respond, try one other contact. Do not CC everyone involved.
Expressing frustration: Any follow-up that communicates that you are frustrated with the process damages your candidacy. Hiring decisions are made partly on what it is like to work with someone day to day.
Following up on a weekend or holiday: Follow-up emails that land in a recruiter's inbox on Saturday morning or over a federal holiday get buried. Send Tuesday through Thursday during business hours (9:00 to 11:00 AM recipient time is the sweet spot). Our team has watched identical messages get dramatically different response rates based on send time alone.
Sending follow-ups from a different email address: Candidates sometimes apply from a personal Gmail and follow up from a work email, or vice versa. This creates confusion in the recruiter's inbox and their ATS. Use one email address consistently across the entire process.
IT Hiring Timeline Benchmarks by Role Type
Setting appropriate expectations for follow-up cadence requires knowing how long each role typically takes to close. Our cert research team compiled the following benchmarks from Greenhouse, Jobvite, and Lever hiring data plus direct feedback from placed candidates in 2024.
| Role Type | Application to First Response | First Screen to Tech Interview | Tech Interview to Offer | Full Cycle |
|---|---|---|---|---|
| Help Desk / Support (SMB) | 3-7 days | 3-5 days | 5-10 days | 2-3 weeks |
| Help Desk / Support (Enterprise) | 7-14 days | 7-14 days | 10-14 days | 4-6 weeks |
| Junior SysAdmin | 7-14 days | 5-10 days | 7-14 days | 3-5 weeks |
| Network Engineer | 7-14 days | 7-10 days | 10-21 days | 4-6 weeks |
| Cloud Engineer | 5-10 days | 7-14 days | 14-28 days | 5-8 weeks |
| DevOps / Platform | 5-10 days | 7-14 days | 21-35 days | 6-10 weeks |
| Security Engineer | 7-14 days | 10-21 days | 21-42 days (incl. clearance) | 8-12 weeks |
| Federal Contractor Roles | 10-21 days | 14-28 days | 30-90 days (clearance pending) | 3-6 months |
Two takeaways shape follow-up strategy. First, federal contractor roles routinely take three to six months because of clearance adjudication - a two-week silence during that cycle is not abnormal. Second, security engineering timelines have lengthened across 2024 because of background check and reference verification steps that most other IT roles skip.
"Our 2024 benchmark of 1,200 technology employers showed median time-to-hire for engineering roles climbed to 44 days, up from 38 days in 2022. Candidates who submitted a structured thank-you within 24 hours of final-round interviews received offers at a 23% higher rate than candidates who did not." [3] - Greenhouse Software, Candidate Experience Benchmarks 2024, Greenhouse, 2024
Platform-Specific Follow-Up Etiquette
The platform you apply through changes what follow-up is appropriate.
LinkedIn Easy Apply: The application went into a bulk pipeline. Follow-up via direct LinkedIn InMail to the recruiter named on the posting is appropriate after 5-7 business days. Keep it to three sentences. Do not send connection requests with lengthy pitches attached - recruiters report these as spam.
Company career portal: The ATS assigned an application number. Reference that number in any follow-up email. Recruiters can find your application faster if you quote the req ID.
Indeed / ZipRecruiter: These platforms often obscure the actual recruiter contact. Following up through the platform's messaging system is the correct channel. Do not try to scrape the hiring manager's email from LinkedIn for a first-contact follow-up - that reads as aggressive.
Referral through a friend: Follow up with your friend first, not the recruiter. Ask your friend to nudge internally. A referral-path follow-up that goes around the referring employee feels like an end-run and damages the relationship.
Recruiter-led outreach (they contacted you first): The tempo is faster. Follow up within 3-5 business days if they miss a promised response date. Recruiters reaching out about active searches expect quick responsiveness.
Writing Thank-You Notes That Get Remembered
Most thank-you notes are templated, generic, and forgettable. The ones that influence hiring decisions share three properties.
One specific technical detail from the interview: "The way you described the blast radius reduction on your AWS account factoring..." or "The Kubernetes node pool design for your ML workload..." The specificity proves you were paying attention and that you understood what was being described.
One piece of evidence you are qualified you did not get to share: A link to a relevant GitHub repo, a one-line mention of a certification you earned after the application was submitted, a brief note about a similar problem you solved. This is the moment to fill gaps.
One clear forward-looking sentence: "I would be glad to continue the conversation," or "Looking forward to the next step if there is one." Make it easy for the interviewer to respond with a next action.
A note that hits these three beats in under 150 words is more effective than a 500-word effort. Hiring managers skim. Make the first two sentences carry the weight.
"We surveyed 800 hiring managers in 2023 about what post-interview communications influenced their decisions. 74% said they remembered candidates who referenced specific project details or technologies discussed during the interview. Only 11% reported that generic thank-you notes had any positive influence on their evaluation." [4] - Robert Half, Candidate Experience Research 2023, Robert Half International, 2023
When Silence Actually Means Something
Silence in an IT hiring process is not always rejection, but it carries information. Patterns our team has tracked across thousands of candidate transitions:
Silence for 10+ days after a promised response, with prior warm signals from the recruiter: Usually an internal process delay (budget approval, competing req, panel scheduling). One polite follow-up often shakes loose a status update.
Silence for 14+ days after a final interview with no timeline given: The role may have gone to another candidate and the recruiter is delaying the rejection email. Send one check-in and then move on.
Silence after a good first interview with no next step scheduled: The hiring manager may be interviewing competing candidates first. Let 7-10 business days pass before following up, and assume your candidacy is in a holding pattern.
Silence after a salary question was answered (yours was high): Common outcome. The role may not have the budget. Move on; reopen the conversation if the role is still posted in 60 days at a revised compensation band.
Silence after a take-home assignment submission: Hiring managers often delay take-home review when backlogged. A single 5-business-day check-in is appropriate.
The useful framing is that silence is rarely personal. Hiring pipelines stall for a dozen reasons that have nothing to do with your candidacy. A measured, professional follow-up usually produces either a status update or a decision - both of which are better than uncertainty.
See also: The IT Job Search Strategy That Actually Works, Networking to Find IT Jobs
References
LinkedIn. "The Job Seeker's Guide to Following Up." LinkedIn Talent Blog, 2023.
Society for Human Resource Management. "How Long Does the Average Hiring Process Take?" SHRM, 2023. https://www.shrm.org
Greenhouse Software. "Candidate Experience Benchmarks 2023." Greenhouse, 2023.
Vault. "Thank You Notes After Job Interviews: Best Practices." Vault Career Intelligence, 2023.
Indeed. "When and How to Follow Up After a Job Interview." Indeed Career Guide, 2024.
CareerBuilder. "What Hiring Managers Think of Follow-Up Emails." CareerBuilder Research, 2023.
Yate, Martin. Knock 'Em Dead: The Ultimate Job Search Guide. Adams Media, 2023.
Lees, John. How to Get a Job You'll Love. McGraw-Hill, 2019.
[3] Greenhouse Software. "Candidate Experience Benchmarks 2024." Greenhouse, 2024. https://www.greenhouse.com/reports/candidate-experience
[4] Robert Half International. "Candidate Experience Research 2023." Robert Half, 2023.
Jobvite. "Recruiter Nation Report 2024." Jobvite, 2024.
Lever. "Talent Benchmarks Report 2024." Lever Inc., 2024.
Frequently Asked Questions
When should I follow up after submitting a job application?
Wait 5-7 business days before following up on a submitted application. Following up sooner communicates impatience rather than interest. Your first follow-up should be a brief email to the recruiter that adds one piece of specific, relevant information — not simply asking if they received your application.
Should I send a thank-you note after every interview?
Yes, within 24 hours of each interview. For panel or group interviews, write individual notes with different specific references to each person's questions or topics where possible. Generic template notes sent to everyone carry less weight. Your final interview thank-you is the most important — use it to reinforce your interest and optionally address any technical question you did not answer as well as you could have.
What should I say when I have a competing offer but prefer another company?
Be direct and professional: 'I received an offer from another company with a deadline of [date]. Your team remains my first preference, and I wanted to let you know in case it affects your timeline.' This is not pressure — it is relevant information that allows the hiring team to decide whether to accelerate their process. Many candidates get preferred offers this way.
How many times should I follow up before accepting silence as rejection?
Two follow-ups after a silence is the reasonable limit. A follow-up after the application, and one follow-up after a missed promised deadline. After two unreturned follow-ups over two weeks, that channel is effectively closed. Send one final professional message that keeps the door open for future opportunities, then move your attention to other prospects.
Is it acceptable to follow up on a technical question I answered poorly?
Yes, in your post-interview thank-you note. You can acknowledge it briefly and provide the better answer in writing: 'I was not as sharp on the RBAC configuration question as I would have liked. The approach I would take is...' Hiring managers generally respond positively to candidates who acknowledge gaps honestly and fill them in. It demonstrates self-awareness and technical follow-through.