5 Candidate Behaviours Recruiters Notice Immediately

Five recruiter-facing behaviours sit between a strong resume and an interview slot, and all five are adjustable before your next application goes out.

The original list that circulates in placement prep groups is framed as what not to do. That framing is backwards. Each of these behaviours has a concrete, low-effort alternative that takes less time than rewriting a resume section. Here is what each one looks like in practice.

Apply to One Role Per Recruitment Cycle at Each Company

When a recruiter sees three simultaneous applications from the same candidate to different business units, the immediate read is: this person does not know where they would add the most value. That is not an enthusiasm signal. It reads as an unfocused application, and it puts the recruiter in the position of deciding which role to even forward you for.

The better approach: read each job description carefully, map it against your existing skills and projects, and apply to the one role where the fit is strongest. If two roles at the same company are genuinely similar (for example, two automation testing openings in the same practice), a brief note in your cover email acknowledging both is cleaner than two parallel applications.

The exception is mass-hiring portals. TCS NQT, Infosys InfyTQ, and similar platforms route candidates to roles internally after the aptitude and coding rounds. Applying through those official portals is fine because the company manages role assignment. The single-application caution applies when you are finding roles on LinkedIn, Naukri, or the company’s careers page where a recruiter handles each listing separately.

One targeted application, written clearly, consistently outperforms three scattered ones. Recruiters remember candidates who applied twice to unrelated roles more than they remember the ones who applied once with precision.

Social Media Profiles Show Up in Recruiter Searches

LinkedIn Talent Solutions surfaces candidate profile data alongside application details in recruiter workflows. A headline, summary, or work history that contradicts the resume creates friction in shortlisting, not because recruiters are looking for reasons to pass, but because an inconsistency raises a question that takes effort to resolve.

A practical audit before your next application cycle:

• LinkedIn headline: Should reflect the role or function you are applying for, not the internship you left two years ago.
• GitHub: For software, testing, or data roles, a public repository with at least two complete projects signals that you write code beyond coursework. Private-only or empty repositories do not actively help your application.
• Glassdoor: Glassdoor’s community guidelines ask reviewers to be factual and first-hand. That standard is also, practically speaking, the register that keeps a review from becoming a liability when a recruiter at the company you reviewed is the one reading your application.
• Twitter/X and Instagram: These come up less frequently in campus hiring screens, but a public account that directly contradicts claims you made in the interview is a risk worth removing.

The practical checklist is one step: search your name before you apply. Check that what appears is factually consistent with what you have written on the resume. Update your LinkedIn work history dates to match your resume dates. Even a one-year discrepancy reads as an error at best and an inaccuracy at worst.

Rescheduling Once Is Manageable; Twice Becomes a Pattern

Rescheduling one interview slot, with a clear reason and at least 24 hours of lead time, is a normal part of campus placement coordination. Recruiters manage several dozen interview slots at the same time and understand that genuine conflicts come up.

What tends to close the slot:

• Rescheduling less than two hours before a scheduled call, with no prior notice
• Rescheduling the same role twice in the same hiring cycle
• Sending a reschedule request without offering alternate times, forcing the recruiter to initiate another scheduling exchange

The version that works: one message, a brief and specific reason, and three alternate time slots in the same message. The recruiter responds with a single word rather than managing a back-and-forth. Keep the message under five lines.

Punctuality and follow-through are the signals recruiters use to infer how a candidate will behave once hired. One reschedule handled proactively is neutral. Two, especially without alternate slots offered, raises a reliability question that is difficult to answer in the interview itself.

If a slot genuinely cannot work, withdrawing politely from that recruitment cycle is a better outcome than rescheduling three times and leaving the recruiter uncertain about whether you will show up.

Follow Up Once, Then Move Your Attention Forward

Following up after an interview is professional and expected. The standard in most campus placement contexts is one email, sent five to seven working days after the interview date, or one working day after the recruiter’s stated decision window closes if they gave you one.

What that follow-up email should contain:

• A brief, specific reference to something discussed in the interview, one that only you would know from that particular conversation
• A polite, direct reiteration of your interest in the role
• A single ask: an update on your application status

What it should not contain: urgency language, comparisons to competing offers, or a timeline ultimatum. One short paragraph is enough.

After one follow-up, the recruiter has full context. A second follow-up within the same week signals that you are not reading the situation. A third suggests anxiety rather than interest, and it tends to make the recruiter less responsive rather than more.

The more productive redirect after a single follow-up: open two or three more applications. Continuing to apply actively after an interview signals market confidence. More practically, it ensures your placement timeline does not rest on a single decision.

Resume Accuracy Is Checked Against References and Records

Background verification is routine in Indian campus placements, particularly for large IT services firms. The documents and details checked most consistently: CGPA and percentage conversions, internship start and end dates, company names, reference contact details, and skill listings that do not match interview performance.

The failure mode worth addressing is not deliberate fabrication: most candidates are aware of that risk. The common, low-intention version is a resume that is simply six months out of date: an internship that ended in December 2024 listed with a title that does not match the offer letter, or a reference phone number for a manager who has since changed roles and organisations.

A 30-minute accuracy pass before each application cycle covers most of this:

• Verify that every date is current and matches your offer letters, certificates, or marksheets
• Update the skills or tools section to reflect what you are working with now, not what you were learning 12 months ago
• Confirm that all reference contacts are reachable at the numbers and email addresses listed

One specific detail: CGPA to percentage conversions. If you list both figures, confirm that the conversion matches the formula your university publishes. A discrepancy between the two figures on your resume (even if both are technically correct by different formulas) is the kind of thing that surfaces in verification and needs to be explained in a context where you have no opportunity to explain it.

---

These five behaviours affect shortlisting conversations that happen after written rounds. If aptitude preparation is running in parallel, FACE Prep’s guides on calendar problems, clock and timing questions, and coding and decoding question types cover the common first-round patterns.

The five behaviours above address the recruiter-facing layer of campus placements. There is a sixth factor that is increasingly relevant for technical roles in 2026: project evidence. A deployed project on a public GitHub is harder to overlook in a resume screen than a listed skill: it answers the recruiter’s unstated question of whether you actually use the tools you have written down. TinkerLLM is where that project gets built. ₹499 puts real LLM API calls in your hands, and the resulting micro-project gives you something concrete to point to the next time a recruiter asks what you have actually shipped.