Tech Recruiter EXPOSES Why You’re Still Unemployed | Lakshay Sakhuja | DSA Roadmap | Kartikhustles

Summary of the video content

The video is a podcast-style discussion where a tech recruiter (Lakshay Sakhuja) offers candid explanations of why many candidates remain unemployed despite applying for jobs. The core message is that hiring is limited by market demand, recruiter/manager workflows, and candidate quality (especially resume and interview integrity)—not by claims like “AI taking jobs” or recruiters “not responding.”

1) Hiring realities: market demand is changing, not disappearing

• The recruiter argues the market is still hiring, but expectations have shifted.
• A major change is that many software roles (especially Java) now expect AI-related familiarity, such as:
  • understanding AI tools/models,
  • using coding copilots,
  • adapting workflows with AI assistance.
• Candidates should expect higher or modified tooling/skill requirements compared to a few years ago.

2) What “HR” actually does in the hiring pipeline

The recruiter clarifies that “HR” is not a single role:

• Talent acquisition / recruiters handle sourcing and end-to-end coordination:
  • screening → interviews → offer follow-up.
• There are also specialized HR functions (e.g., operations, payroll, finance, etc.).
• In large companies, work is often split into stages:
  • some recruiters focus only on sourcing profiles,
  • others handle calling, scheduling, assessments, and offer coordination.
• Recruiters face heavy throughput—often reviewing dozens to ~100 CVs per day—so they must prioritize quickly.

3) Why candidates get rejected: resume quality and keyword specificity

The recruiter emphasizes that many applicants fail at basics:

• Project details must be specific:
  • what technology was used,
  • what the project actually was,
  • what responsibilities you owned,
  • which company/team it was for.
• Resumes should include relevant keywords for Java/IT and related tech (as applicable), such as:
  • Spring Boot,
  • Microservices,
  • CICD/DevOps.
• “ATS-friendly” formatting matters, but:
  • trying to game ATS (e.g., hidden/white text keywords) is unreliable and can harm correctness.
• Resume length: a short, focused resume is preferred (often ~1–1.5 pages).
  • Overly long resumes reduce the chance recruiters will read thoroughly.

4) Recruitment volume and speed: easy apply and timing matter

• Using platforms like LinkedIn Easy Apply can increase visibility and feed data into tracking systems (spreadsheets/ATS links).
• However, even with large volumes:
  • recruiters still can’t review everything,
  • if thousands apply quickly, only a fraction get attention.
• A practical suggestion is to apply when a role is fresh:
  • use time-based filters like “posted within the last 24 hours/days.”

5) Interview integrity: widespread cheating and how it changes the process

A major part of the discussion covers how cheating is detected during coding/technical rounds:

• Reported methods include:
  • second devices / hidden communication,
  • AI-assisted answers in real time,
  • screen-reading or piped-in answers,
  • even lip-syncing or audio manipulation in virtual calls.
• Because cheating is common, interview processes may evolve:
  • more face-to-face rounds later,
  • more aggressive questioning to verify genuine knowledge.
• The recruiter states they use experience, behavior signals, and follow-up questions to detect inconsistencies.

6) Lying / fake documentation: BGV failures and “abscond/notice period” issues

The recruiter highlights that verification is stricter than before:

• Fake experience, fake education documents, and PF-related discrepancies are reported.
• Candidates may lie about:
  • notice period / last working day,
  • whether they are on bench,
  • abscond reasons,
  • PF deductions and employment proof.
• Such issues can invalidate offers even after interviews.

7) Referrals and LinkedIn presence: referrals help, but aren’t magic

• Referrals still add value because they can improve priority, but:
  • they do not override technical fit,
  • a referral cannot compensate for weak project evidence or insufficient skills.
• LinkedIn optimization matters:
  • keep skills and role details updated,
  • use relevant keywords in the headline/bio,
  • activity can help recruiters find you (daily posting isn’t strictly necessary).

8) Closing advice: focus on real skills, honest proof, and persistence

• The recruiter discourages “shortcut” strategies:
  • resume gaming,
  • mass spamming,
  • fake documents,
  • exaggerated claims.
• Instead:
  • build correct skills (e.g., DSA practice, Java and its stack),
  • tailor resumes to job requirements,
  • apply strategically and keep going.
• The message is motivational but grounded in real hiring process constraints: persistence + fit beats tactics.

---

Presenters / Contributors

• Lakshay Sakhuja — main presenter; tech recruiter / HR–talent acquisition perspective
• Kartik — host / co-presenter introducing and engaging (mentioned frequently)