Intermediate
Email Writing
#interview
#follow-up
#professional-email
📧 Follow-up Email After a Job Interview
5 exercises — write a professional follow-up that leaves a positive impression: the right timing, subject line format, body structure, tone calibration, and closing phrases.
Follow-up email formula
- When: within 24 hours of the interview
- Subject: Follow-up: [Role] Interview — [Your Name], [Date]
- Body: Gratitude → specific moment from the interview → restated interest in the role
- Tone: warm, professional, interested — never desperate or demanding
- Length: 3–4 short paragraphs maximum
0 / 22 completed
1 / 22
You finished a software engineer interview at a startup on Tuesday afternoon. You felt it went well. When should you send a thank-you / follow-up email?
Send within 24 hours — the same evening or next morning is ideal. This timing shows genuine interest and professionalism while the interview is still fresh in the interviewer's mind. The thank-you email also gives you one more brief touchpoint to reinforce a positive impression.
Why within 24 hours?
① The interviewer likely met several candidates — your email arrives while they still remember specific things you said ② Hiring decisions in tech startups can move fast — sometimes within 2 days ③ It demonstrates follow-through and initiative, both valued in engineering roles
What if you wait a week? The email loses relevance — the team has moved on, and it may even look like an afterthought.
Are follow-up emails intrusive? No — a professional, concise thank-you is standard practice. The only scenario where you might skip it: if the recruiter explicitly said "no need to follow up."
Format: Email is standard; avoid LinkedIn DM or text/call unless those channels were used for the interview arrangement.
Why within 24 hours?
① The interviewer likely met several candidates — your email arrives while they still remember specific things you said ② Hiring decisions in tech startups can move fast — sometimes within 2 days ③ It demonstrates follow-through and initiative, both valued in engineering roles
What if you wait a week? The email loses relevance — the team has moved on, and it may even look like an afterthought.
Are follow-up emails intrusive? No — a professional, concise thank-you is standard practice. The only scenario where you might skip it: if the recruiter explicitly said "no need to follow up."
Format: Email is standard; avoid LinkedIn DM or text/call unless those channels were used for the interview arrangement.
2 / 22
You interviewed for a Senior Backend Engineer role. Which subject line is most appropriate for your follow-up email?
"Follow-up: Senior Backend Engineer Interview — [Your Name], date" is correct. A strong interview follow-up subject line has three elements:
① Signal word — "Follow-up:" tells the reader immediately what kind of email this is ② Role + company context — "Senior Backend Engineer Interview" — if the recruiter has multiple open roles, this disambiguates ③ Your name + date — makes the email easy to find and forward (e.g., to the hiring manager)
Why the others fail:
"Did I get the job?" — too casual, puts pressure on the reader, and may irritate a busy recruiter
"Re: My Application" — too vague; doesn't signal what stage you're at or what you want
"Following up on our meeting" — "meeting" is imprecise for an interview context; also lacks your name and date
Pattern to remember:
Some candidates add the company name too, which is helpful if they're applying to multiple places simultaneously: "Follow-up: Backend Engineer Interview — Acme Corp — [Name]"
① Signal word — "Follow-up:" tells the reader immediately what kind of email this is ② Role + company context — "Senior Backend Engineer Interview" — if the recruiter has multiple open roles, this disambiguates ③ Your name + date — makes the email easy to find and forward (e.g., to the hiring manager)
Why the others fail:
"Did I get the job?" — too casual, puts pressure on the reader, and may irritate a busy recruiter
"Re: My Application" — too vague; doesn't signal what stage you're at or what you want
"Following up on our meeting" — "meeting" is imprecise for an interview context; also lacks your name and date
Pattern to remember:
Follow-up: [Role Title] Interview — [Your Full Name], [Day DD Month]Some candidates add the company name too, which is helpful if they're applying to multiple places simultaneously: "Follow-up: Backend Engineer Interview — Acme Corp — [Name]"
3 / 22
You're drafting a follow-up email after a positive technical interview at a fintech company. Which content is most appropriate for the body of the email?
Gratitude + specific reference + restated interest — this three-part structure creates a professional, personalised follow-up that stands out from generic emails.
Why this combination works:
① Gratitude — "Thank you for taking the time to speak with me" — basic professional courtesy; never skip it ② Specific reference — "I particularly enjoyed discussing the microservices migration challenge — it made me think about [X]" — this proves you were engaged and listened, not just going through the motions. It also reminds the interviewer of a positive moment ③ Restated interest — "I'm very interested in joining the team and working on [specific project/challenge mentioned]" — signals forward motion without pressuring the interviewer
What NOT to include in this email:
• Salary negotiation — premature; wait until an offer is made
• Updated CV — implies you sent something below par originally; don't draw attention to weaknesses
• Demand for detailed feedback — this feels entitled; you can ask for brief feedback if you're rejected, but not before the decision
Length: 3–4 short paragraphs maximum. Interviewers are busy — a wall of text undermines the impact.
Why this combination works:
① Gratitude — "Thank you for taking the time to speak with me" — basic professional courtesy; never skip it ② Specific reference — "I particularly enjoyed discussing the microservices migration challenge — it made me think about [X]" — this proves you were engaged and listened, not just going through the motions. It also reminds the interviewer of a positive moment ③ Restated interest — "I'm very interested in joining the team and working on [specific project/challenge mentioned]" — signals forward motion without pressuring the interviewer
What NOT to include in this email:
• Salary negotiation — premature; wait until an offer is made
• Updated CV — implies you sent something below par originally; don't draw attention to weaknesses
• Demand for detailed feedback — this feels entitled; you can ask for brief feedback if you're rejected, but not before the decision
Length: 3–4 short paragraphs maximum. Interviewers are busy — a wall of text undermines the impact.
4 / 22
A colleague shares this draft follow-up email: "Hi Sarah, just checking if you've made any decisions yet? I'm very excited and I really need this job. I have financial obligations and really hope I'm selected. Please let me know as soon as possible."
What is the most significant problem with this email?
What is the most significant problem with this email?
Desperation and pressure are the core problem. "I really need this job," "I have financial obligations," and "please let me know as soon as possible" all shift the emotional burden onto the reader and undermine the candidate's professional positioning.
Why this damages your chances:
① It creates discomfort — interviewers are not responsible for your financial situation; making them feel that pressure creates a negative emotional association with your application ② It signals desperation — candidates who communicate from a position of need are perceived as less selective — which paradoxically makes you look less desirable ③ "Please let me know ASAP" — implies urgency that isn't yours to set; the hiring timeline belongs to the company
The professional alternative:
"Hi Sarah, thank you for the opportunity to interview for the backend role on Tuesday. I enjoyed the conversation about the data pipeline architecture challenges. I remain very interested in joining the team. I look forward to hearing about next steps at your convenience."
Tone calibration:
Professional follow-up = warm + concise + interested + patient
What to avoid = desperate + pressuring + overly personal + demanding
Why this damages your chances:
① It creates discomfort — interviewers are not responsible for your financial situation; making them feel that pressure creates a negative emotional association with your application ② It signals desperation — candidates who communicate from a position of need are perceived as less selective — which paradoxically makes you look less desirable ③ "Please let me know ASAP" — implies urgency that isn't yours to set; the hiring timeline belongs to the company
The professional alternative:
"Hi Sarah, thank you for the opportunity to interview for the backend role on Tuesday. I enjoyed the conversation about the data pipeline architecture challenges. I remain very interested in joining the team. I look forward to hearing about next steps at your convenience."
Tone calibration:
Professional follow-up = warm + concise + interested + patient
What to avoid = desperate + pressuring + overly personal + demanding
5 / 22
Which closing sentence is most appropriate for a follow-up email to a software engineering recruiter or hiring manager?
"Please do not hesitate to reach out if you need any additional information. I look forward to hearing from you." is the professional standard for a follow-up email close. It achieves three things without overstepping:
① Opens a door for the recruiter — "do not hesitate to reach out" signals availability and willingness to provide more (code samples, references, technical clarification) ② "I look forward to hearing from you" — signals interested anticipation without demanding a timeline ③ Leaves the next move with the hiring team — correct, because it belongs there
Why the others fail:
"I'll follow up again on Monday" — announces a follow-up before the original email has been read; can irritate a busy recruiter and signals impatience. If you want to follow up again, do it — but don't announce it in advance
"I expect a decision by end of week" — you don't set the hiring timeline; this reads as pushiness
"Let me know if you decided. Thanks." — grammatically awkward ("if you decided" → should be "once you've made a decision") and far too casual for a professional context
Full closing formula:
Thank you again + availability offer + forward-looking close + professional signature (name, LinkedIn, phone)
① Opens a door for the recruiter — "do not hesitate to reach out" signals availability and willingness to provide more (code samples, references, technical clarification) ② "I look forward to hearing from you" — signals interested anticipation without demanding a timeline ③ Leaves the next move with the hiring team — correct, because it belongs there
Why the others fail:
"I'll follow up again on Monday" — announces a follow-up before the original email has been read; can irritate a busy recruiter and signals impatience. If you want to follow up again, do it — but don't announce it in advance
"I expect a decision by end of week" — you don't set the hiring timeline; this reads as pushiness
"Let me know if you decided. Thanks." — grammatically awkward ("if you decided" → should be "once you've made a decision") and far too casual for a professional context
Full closing formula:
Thank you again + availability offer + forward-looking close + professional signature (name, LinkedIn, phone)
6 / 22
You spent the last week reviewing a colleague's pull request for a new microservice. The PR was initially rejected due to several minor styling inconsistencies and a lack of comprehensive unit tests. After discussing the feedback with your colleague and helping them address these issues, the PR was finally merged. Now, you're drafting a brief follow-up message to your team lead about this process. Which of the following options best describes the tone and content for your email?Option A: 'Hi [Team Lead], Just wanted to confirm that the microservice PR has been merged. It was a bit tedious, but we got there.'
Option B: 'Hi [Team Lead], Following up on the recent microservice PR (
#1234). I provided feedback and support to my colleague in addressing the styling issues and adding unit tests, leading to successful merging. I'm happy to discuss this further if needed.'Option C: 'Hey [Team Lead], Just letting you know the PR is done. Don't worry about it.'
Option D: 'Hi [Team Lead], The microservice PR was merged! I think the code quality has improved significantly thanks to my review.'
The correct answer (B) demonstrates professional communication within a development team. It acknowledges your contribution clearly and concisely while highlighting the positive outcome – successfully merging the PR through collaborative effort. Options A and C are too informal and don't convey appropriate appreciation or offer further discussion. Option D is overly assertive about code quality, which isn't always the best approach in a professional setting; it's better to focus on the process and the successful resolution.
7 / 22
You've just finished a technical interview for a DevOps Engineer role at a cloud services provider. During the interview, you discussed your experience with Kubernetes and CI/CD pipelines. The interviewer emphasized the importance of automation and monitoring within their environment. You want to send a brief follow-up email to reinforce your interest and highlight your relevant skills. Which of the following emails best achieves this goal?
Option A:
Subject: DevOps Engineer Application
Hi [Interviewer Name],
I enjoyed learning more about the DevOps role at [Company Name] and your team's focus on automation. I'm confident my skills in Kubernetes and CI/CD align well with your requirements. Please let me know if you need any further information.
Option B: Subject: Following up - DevOps Engineer Role
Just wanted to reiterate my strong interest in the DevOps position. I'm a fast learner and eager to contribute to [Company Name].
Option C: Subject: DevOps Interview Feedback
Thank you for taking the time to speak with me yesterday about the DevOps Engineer role. I appreciate the opportunity to discuss my experience with Kubernetes and CI/CD.
Option D: Subject: Interested in DevOps Role
I'm very interested in the DevOps Engineer position at [Company Name]. I think I would be a good fit for your team.This question tests understanding of professional email etiquette in a technical context. Option A is the best response as it directly references the conversation's focus on automation and monitoring – demonstrating you listened and are aligned with their priorities. Options B and D are too generic and lack specific details to showcase your skills effectively, while Option C simply expresses interest without providing any value or reinforcing key takeaways from the interview.
8 / 22
You've just finished a technical interview for a Lead Software Engineer role at a large e-commerce company. The interview focused heavily on designing scalable APIs and handling high traffic loads. During the discussion, you mentioned your experience with implementing caching strategies using Redis and optimizing database queries. The interviewer asked if you had any further questions about the project or the team's architecture. Which of the following follow-up email options best demonstrates professionalism and a continued interest while subtly reinforcing your expertise?
Option 1 correctly frames the follow-up as a thoughtful response demonstrating interest in the company's challenges and offering value (sharing resources). It avoids overly enthusiastic language and subtly highlights your expertise. Options A and B are too casual; option C is purely transactional and doesn't offer any added value, while option D sounds overly assertive and potentially intrusive. The key here is to show you were listening and have something relevant to contribute.
9 / 22
You spent the last week reviewing a colleague's pull request for a new microservice. The PR was initially rejected due to several minor styling inconsistencies and a lack of comprehensive unit tests. After discussing the feedback with your colleague and helping them address these issues, the PR was finally merged. Now, you're drafting a brief follow-up message to your team lead about this process. Which of the following options best describes the tone and content for your email?Option A: 'Hi [Team Lead], Just wanted to confirm that the microservice PR has been merged. It was a bit tedious, but we got there.'
Option B: 'Hi [Team Lead], Following up on the recent microservice PR (
#1234). I provided feedback and support to my colleague in addressing the styling issues and adding unit tests, leading to successful merging. I'm happy to discuss this further if needed.'Option C: 'Hey [Team Lead], Just letting you know the PR is done. Don't worry about it.'
Option D: 'Hi [Team Lead], The microservice PR was merged! I think the code quality has improved significantly thanks to my review.'
The correct answer (B) demonstrates professional communication within a development team. It acknowledges your contribution clearly and concisely while highlighting the positive outcome – successfully merging the PR through collaborative effort. Options A and C are too informal and don't convey appropriate appreciation or offer further discussion. Option D is overly assertive about code quality, which isn't always the best approach in a professional setting; it's better to focus on the process and the successful resolution.
10 / 22
You've just finished a technical interview for a DevOps Engineer role at a cloud services provider. During the interview, you discussed your experience with Kubernetes and CI/CD pipelines. The interviewer emphasized the importance of automation and monitoring within their environment. You want to send a brief follow-up email to reinforce your interest and highlight your relevant skills. Which of the following emails best achieves this goal?
Option A:
Subject: DevOps Engineer Application
Hi [Interviewer Name],
I enjoyed learning more about the DevOps role at [Company Name] and your team's focus on automation. I'm confident my skills in Kubernetes and CI/CD align well with your requirements. Please let me know if you need any further information.
Option B: Subject: Following up - DevOps Engineer Role
Just wanted to reiterate my strong interest in the DevOps position. I'm a fast learner and eager to contribute to [Company Name].
Option C: Subject: DevOps Interview Feedback
Thank you for taking the time to speak with me yesterday about the DevOps Engineer role. I appreciate the opportunity to discuss my experience with Kubernetes and CI/CD.
Option D: Subject: Interested in DevOps Role
I'm very interested in the DevOps Engineer position at [Company Name]. I think I would be a good fit for your team.This question tests understanding of professional email etiquette in a technical context. Option A is the best response as it directly references the conversation's focus on automation and monitoring – demonstrating you listened and are aligned with their priorities. Options B and D are too generic and lack specific details to showcase your skills effectively, while Option C simply expresses interest without providing any value or reinforcing key takeaways from the interview.
11 / 22
You've just finished a technical interview for a Lead Software Engineer role at a large e-commerce company. The interview focused heavily on designing scalable APIs and handling high traffic loads. During the discussion, you mentioned your experience with implementing caching strategies using Redis and optimizing database queries. The interviewer asked if you had any further questions about the project or the team's architecture. Which of the following follow-up email options best demonstrates professionalism and a continued interest while subtly reinforcing your expertise?
Option 1 correctly frames the follow-up as a thoughtful response demonstrating interest in the company's challenges and offering value (sharing resources). It avoids overly enthusiastic language and subtly highlights your expertise. Options A and B are too casual; option C is purely transactional and doesn't offer any added value, while option D sounds overly assertive and potentially intrusive. The key here is to show you were listening and have something relevant to contribute.
12 / 22
You spent the last week reviewing a colleague's pull request for a new microservice. The PR was initially rejected due to several minor styling inconsistencies and a lack of comprehensive unit tests. After discussing the feedback with your colleague and helping them address these issues, the PR was finally merged. Now, you're drafting a brief follow-up message to your team lead about this process. Which of the following options best describes the tone and content for your email?Option A: 'Hi [Team Lead], Just wanted to confirm that the microservice PR has been merged. It was a bit tedious, but we got there.'
Option B: 'Hi [Team Lead], Following up on the recent microservice PR (
#1234). I provided feedback and support to my colleague in addressing the styling issues and adding unit tests, leading to successful merging. I'm happy to discuss this further if needed.'Option C: 'Hey [Team Lead], Just letting you know the PR is done. Don't worry about it.'
Option D: 'Hi [Team Lead], The microservice PR was merged! I think the code quality has improved significantly thanks to my review.'
The correct answer (B) demonstrates professional communication within a development team. It acknowledges your contribution clearly and concisely while highlighting the positive outcome – successfully merging the PR through collaborative effort. Options A and C are too informal and don't convey appropriate appreciation or offer further discussion. Option D is overly assertive about code quality, which isn't always the best approach in a professional setting; it's better to focus on the process and the successful resolution.
13 / 22
You've just finished a technical interview for a DevOps Engineer role at a cloud services provider. During the interview, you discussed your experience with Kubernetes and CI/CD pipelines. The interviewer emphasized the importance of automation and monitoring within their environment. You want to send a brief follow-up email to reinforce your interest and highlight your relevant skills. Which of the following emails best achieves this goal?
Option A:
Subject: DevOps Engineer Application
Hi [Interviewer Name],
I enjoyed learning more about the DevOps role at [Company Name] and your team's focus on automation. I'm confident my skills in Kubernetes and CI/CD align well with your requirements. Please let me know if you need any further information.
Option B: Subject: Following up - DevOps Engineer Role
Just wanted to reiterate my strong interest in the DevOps position. I'm a fast learner and eager to contribute to [Company Name].
Option C: Subject: DevOps Interview Feedback
Thank you for taking the time to speak with me yesterday about the DevOps Engineer role. I appreciate the opportunity to discuss my experience with Kubernetes and CI/CD.
Option D: Subject: Interested in DevOps Role
I'm very interested in the DevOps Engineer position at [Company Name]. I think I would be a good fit for your team.This question tests understanding of professional email etiquette in a technical context. Option A is the best response as it directly references the conversation's focus on automation and monitoring – demonstrating you listened and are aligned with their priorities. Options B and D are too generic and lack specific details to showcase your skills effectively, while Option C simply expresses interest without providing any value or reinforcing key takeaways from the interview.
14 / 22
You've just finished a technical interview for a Lead Software Engineer role at a large e-commerce company. The interview focused heavily on designing scalable APIs and handling high traffic loads. During the discussion, you mentioned your experience with implementing caching strategies using Redis and optimizing database queries. The interviewer asked if you had any further questions about the project or the team's architecture. Which of the following follow-up email options best demonstrates professionalism and a continued interest while subtly reinforcing your expertise?
Option 1 correctly frames the follow-up as a thoughtful response demonstrating interest in the company's challenges and offering value (sharing resources). It avoids overly enthusiastic language and subtly highlights your expertise. Options A and B are too casual; option C is purely transactional and doesn't offer any added value, while option D sounds overly assertive and potentially intrusive. The key here is to show you were listening and have something relevant to contribute.
15 / 22
You spent the last week reviewing a colleague's pull request for a new microservice. The PR was initially rejected due to several minor styling inconsistencies and a lack of comprehensive unit tests. After discussing the feedback with your colleague and helping them address these issues, the PR was finally merged. Now, you're drafting a brief follow-up message to your team lead about this process. Which of the following options best describes the tone and content for your email?Option A: 'Hi [Team Lead], Just wanted to confirm that the microservice PR has been merged. It was a bit tedious, but we got there.'
Option B: 'Hi [Team Lead], Following up on the recent microservice PR (
#1234). I provided feedback and support to my colleague in addressing the styling issues and adding unit tests, leading to successful merging. I'm happy to discuss this further if needed.'Option C: 'Hey [Team Lead], Just letting you know the PR is done. Don't worry about it.'
Option D: 'Hi [Team Lead], The microservice PR was merged! I think the code quality has improved significantly thanks to my review.'
The correct answer (B) demonstrates professional communication within a development team. It acknowledges your contribution clearly and concisely while highlighting the positive outcome – successfully merging the PR through collaborative effort. Options A and C are too informal and don't convey appropriate appreciation or offer further discussion. Option D is overly assertive about code quality, which isn't always the best approach in a professional setting; it's better to focus on the process and the successful resolution.
16 / 22
You've just finished a technical interview for a DevOps Engineer role at a cloud services provider. During the interview, you discussed your experience with Kubernetes and CI/CD pipelines. The interviewer emphasized the importance of automation and monitoring within their environment. You want to send a brief follow-up email to reinforce your interest and highlight your relevant skills. Which of the following emails best achieves this goal?
Option A:
Subject: DevOps Engineer Application
Hi [Interviewer Name],
I enjoyed learning more about the DevOps role at [Company Name] and your team's focus on automation. I'm confident my skills in Kubernetes and CI/CD align well with your requirements. Please let me know if you need any further information.
Option B: Subject: Following up - DevOps Engineer Role
Just wanted to reiterate my strong interest in the DevOps position. I'm a fast learner and eager to contribute to [Company Name].
Option C: Subject: DevOps Interview Feedback
Thank you for taking the time to speak with me yesterday about the DevOps Engineer role. I appreciate the opportunity to discuss my experience with Kubernetes and CI/CD.
Option D: Subject: Interested in DevOps Role
I'm very interested in the DevOps Engineer position at [Company Name]. I think I would be a good fit for your team.This question tests understanding of professional email etiquette in a technical context. Option A is the best response as it directly references the conversation's focus on automation and monitoring – demonstrating you listened and are aligned with their priorities. Options B and D are too generic and lack specific details to showcase your skills effectively, while Option C simply expresses interest without providing any value or reinforcing key takeaways from the interview.
17 / 22
You've just finished a technical interview for a Lead Software Engineer role at a large e-commerce company. The interview focused heavily on designing scalable APIs and handling high traffic loads. During the discussion, you mentioned your experience with implementing caching strategies using Redis and optimizing database queries. The interviewer asked if you had any further questions about the project or the team's architecture. Which of the following follow-up email options best demonstrates professionalism and a continued interest while subtly reinforcing your expertise?
Option 1 correctly frames the follow-up as a thoughtful response demonstrating interest in the company's challenges and offering value (sharing resources). It avoids overly enthusiastic language and subtly highlights your expertise. Options A and B are too casual; option C is purely transactional and doesn't offer any added value, while option D sounds overly assertive and potentially intrusive. The key here is to show you were listening and have something relevant to contribute.
18 / 22
You've just finished a technical interview for a Frontend Engineer role at a SaaS company. During the discussion, the interviewer asked you to elaborate on your experience with React and Redux. You want to send a brief follow-up message to the hiring manager, highlighting your enthusiasm and key skills. Which of the following Slack messages is most effective?
Option A: 'Hey [Hiring Manager Name], just wanted to say thanks again for the chat! Really enjoyed learning about the team's work on the new UI.
Option B: 'Hi [Hiring Manager Name], Following up on our conversation. I'm very interested in this role and my experience with React/Redux aligns well with your needs – especially building complex state management solutions.'
Option C: 'Just checking in, did you need anything further from me regarding my technical skills?'
Option D: 'Thanks for the time! I'm still figuring out if this role is a good fit for me. Let me know when you have some time to discuss it further.'Option B is the strongest because it directly addresses the interviewer's request by highlighting relevant skills (React/Redux) and connecting them to the company's needs. It demonstrates proactive engagement and a clear understanding of what they were looking for. Options A and D are too vague, while option C could be perceived as overly inquisitive.
19 / 22
You're reviewing a pull request submitted by a junior developer for a backend API. The PR introduces a new endpoint but lacks proper input validation and error handling. You want to provide constructive feedback in the code review comment. Which of the following approaches is most professional and helpful?
Option A: 'This isn't working! Fix it!'
Option B: 'The API endpoint is missing input validation. Add checks for valid data types and handle potential errors gracefully to prevent unexpected behavior.'
Option C: 'Looks good, but maybe add a timeout?'
Option D: 'This needs more documentation. Add some comments explaining what this does.'Option B offers specific guidance on improving the code by addressing critical issues like input validation and error handling – essential for robust API design. It's constructive, actionable, and explains *why* the changes are needed, rather than simply stating what's wrong.
20 / 22
You've just finished a technical interview for a Data Engineer role. The interviewer asked you to describe your experience with data pipelines and ETL processes. You want to end your follow-up email with a strong closing statement. Which of the following is most appropriate?
Option A: 'I'm really excited about this opportunity!'
Option B: 'I'm confident that my skills and experience align well with your requirements, and I am eager to contribute to your team.'
Option C: 'Let me know if you need anything else from me.'
Option D: 'Thanks for the interview – it was good.'Option B is a professional and assertive closing statement. It reiterates confidence in your suitability while expressing enthusiasm for contributing to the team - a key element of positive communication in this context.
21 / 22
You're drafting a follow-up email after receiving feedback on your pull request. The reviewer suggested adding more tests and improving code readability. You want to acknowledge the feedback and outline your next steps. Which of the following sentences is most suitable for the end of the email?
Option A: 'I'll just do what you said.'
Option B: 'Thank you for your detailed feedback; I'm prioritizing addressing the test coverage and readability issues in my next commit.'
Option C: 'Got it. Will get to it ASAP.'
Option D: 'Thanks, that's all good.'Option B demonstrates a proactive approach by acknowledging the feedback, clearly stating your planned actions (adding tests and improving readability), and linking them to a specific commit. This shows you've understood the review and are taking ownership.
22 / 22
You're writing a short update in a team standup meeting. You spent yesterday debugging an issue with a new feature. The issue was caused by a race condition. Which of the following concise updates is most appropriate?
Option A: 'I worked on the new feature today and found some problems.'
Option B: 'Spent the day investigating a race condition in the new feature – identified and resolved it by implementing a locking mechanism.'
Option C: 'Just finished fixing something.'
Option D: 'Had a busy day.'Option B provides specific details about the problem (race condition), the resolution (locking mechanism), and demonstrates technical understanding. This is valuable information for the team and shows you've tackled a challenging issue effectively.
Continue practising:
Technical Interview Prep →
Frequently Asked Questions
What does the "Follow-up Email After a Job Interview — English for IT" exercise cover?
Practise writing professional follow-up emails after a software engineering interview. 5 exercises: timing, subject lines, body content, tone, and closing phrases.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Follow-up Email After a Job Interview — English for IT"?
This exercise has 22 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Email & Writing exercises?
Browse the full Email & Writing hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.