After a rejection: ask for feedback and keep a review log

The feedback request

Generic requests ("any feedback would be appreciated") are easy to ignore. Ask one narrow question that a busy interviewer can answer in a sentence.

Subject: Data Scientist interview - thank you - [Your Name]

Hi Aditi,

Thank you for letting me know, and for arranging the interviews. I understand
the decision.

If it is possible to share, I would find it useful to know whether the main gap
was in the modelling case discussion or in the SQL round. One line would help me
prepare better.

Regards,
[Name]

Why this works:

• It accepts the decision up front, so there is no risk of an argument.
• It names the two rounds, so the recruiter can forward it to the panel with a simple question.
• "One line" sets a small expectation.

Send it to the recruiter who informed you, not to interviewers directly, unless you had direct contact with them during the process.

What to expect back

Many companies have policies against detailed feedback, and many recruiters simply do not have it. Common replies, and what they mean:

The review log

Add a second sheet to your job application tracker, with one row per rejection.

Fill in the self-rating and "what went wrong" on the day, before any feedback arrives. It stops the recruiter's reply from overwriting your own memory of the interview.

Reading the log after ten rows

Sort by round reached. A fictional example after ten rejections:

Round reached       Count
Resume screen       4
Online test         0
Technical 1         1
Technical 2 (case)  4
Manager round       1

This candidate's problems are in two places: the resume is not getting through for some roles, and case rounds are failing. The test and first technical round are fine. So the plan is not "study everything"; it is:

1. 1For the four screen rejections, compare the resume against those JDs using the method in testing your resume against job description keywords.
2. 2For the four case rejections, collect the questions from the log and practise answering each with the business metric first, then the method.

Protecting your morale

Rejections in a job search are normal. A few habits help:

• Limit how often you check email for results. Once in the morning and once in the evening is enough.
• Count activity, not outcomes, in your weekly review: applications sent, practice sessions done, projects improved.
• Talk to someone who has hired, not only to other candidates. One conversation with a hiring manager about what they look for can reframe several rejections.

When to reapply

If the feedback was "close decision", a polite note to the recruiter three to six months later, with one concrete thing you have improved, is reasonable:

Hi Aditi, we spoke in October about the Data Scientist role. Since then I have
completed a pricing elasticity project and published it on GitHub. If a similar
role opens, I would be glad to be considered.

If the log keeps pointing to the same technical gap in modelling rounds, a structured course can close it faster than practice alone. The Data Science programme runs for six months with live online sessions and recordings; the free skill check is a quicker first step.