From Hindi Medium to ₹16 LPA | Keshav's Inspiring Journey | AccioJob Placement | AccioJob Review

Main ideas / concepts conveyed

• Keshav’s background and path to a high package

  • Started from a Hindi/Sanskrit-medium, tier-3 college background in Ghaziabad (UP), with limited early exposure to coding.
  • Transitioned through multiple interests:
    • DSA + competitive programming (early college)
    • Web development (attempted multiple times; later found better teaching in the 3rd year)
    • ML/AI (eventually became the focus; led to internships and project building)
  • Ultimately landed an Implementation Engineer role through a job drive, with salary negotiation.

• What really helped more than background

  • He repeatedly emphasizes that background matters less than people think.
  • The strongest differentiators were:
    • Experimenting across domains until he found what he enjoyed
    • Building proof of work (projects + internship experience)
    • Preparing for interviews strategically (especially how to “drive” the conversation)

• College placements vs off-campus (and why it’s hard)

  • On-campus placement outcomes can be distorted by strict eligibility filters (e.g., 10th/12th percentage cutoffs), which may exclude otherwise strong candidates.
  • Off-campus hiring is difficult largely due to:
    • High supply of candidates with similar skills
    • Limited number of hires
    • Low shortlisting probability unless you have an interview source/referral

---

Methodology / actionable instruction lists

A) “How to land interviews” (till-interview focus)

Keshav’s implied approach:

• Don’t rely on luck alone; improve controllable factors (acknowledging luck exists):

  • Keep strong DSA fundamentals (DSA is still required)
  • Build outstanding projects (especially in more modern-sounding domains like ML/AI)
  • Be ready to clearly explain:
    • What you built
    • Why you built it
    • Problems/difficulties you faced

• Target internships/experience

  • Having around ~1.5 years of experience by end of college significantly strengthened his placement/interview performance.

---

B) Interview “driving” tactic (how he managed question flow)

• Don’t just answer questions—shape the discussion.

• His method:

  • Identify topics you expect interviewers to probe.
  • During the interview, drop a curated one-liner about a relevant project at the right time.
  • This makes the interviewer curious, increasing the chance they ask follow-ups.

• Key condition (explicitly stated):

  • Only “drive” if you have genuine proof of work behind it.
  • Don’t push a topic you can’t deeply explain (e.g., not a shallow clone).

• Topics used as discussion anchors:

  • Final-year project: DSA recommender system
  • Internship leverage: enterprise/startup work (cloud cost optimization system)

---

C) Skill strategy evolution (what companies ask now)

• Progression described:

  • Earlier: DSA + aptitude
  • Then: DSA (medium/advanced)
  • Now: DSA + web/ML/AI + strong projects
  • Near-term expectation (from the video): more system design / architecture / “AI-native” projects

• Core takeaway:

  • “DSA-only era is over” doesn’t mean DSA is unnecessary.
  • The direction is DSA + something else (projects and domain depth).

---

D) Beyond-college job strategy (off-campus / referrals / community)

He suggests steps to increase interview probability:

• Build connections outside college

  • Use LinkedIn referrals
  • Join clubs (avoid distraction from your own path)
  • Leverage relatives or existing industry connections

• Create a “proof of work” profile

  • Post and maintain visible artifacts:
    • CodeChef / Codeforces participation
    • Contest participation
    • Projects (posted publicly)

• Goal:

  • Convert “connections” into interview calls, because cold applications have poor probabilistic outcomes.

---

Key lessons / takeaways

• Try multiple domains early; don’t lock into what most classmates are doing (even if it’s “web dev everywhere”).
• Get teaching quality / the right guidance when stuck (better web development teachers in 3rd year unlocked enjoyment for him).
• Internships matter:
  • They can provide enterprise-like exposure
  • They can lead to PPO / cushion for campus placement scenarios
• Eligibility cutoffs (like 10th/12th %) can block you even with strong CGPA—so candidates must consider criteria strategically.
• Interview performance isn’t only technical:
  • Story structure and the ability to drive the conversation matter.
• Community/referrals increase off-campus chances far more than raw skill alone.

---

Speakers / sources featured

1. Keshav (video guest; implementation engineer at Tener/“NR” in subtitles; job via AccioJob drives)
2. Host / interviewer (AccioJob interviewer) (speaks multiple times; mentions AccioJob, job drives, and asks questions)
3. AccioJob / Tanner / “AQ Job” (company/source mentioned throughout; conducts job drives and assessments with partner companies)
4. Partner hiring company behind the drive (named indirectly in subtitles as “NR” for Keshav’s final role; full company name not clearly provided in captions)