Video summary

I Finally Got Placed | My Placement Journey in This Job Market

Main summary

Key takeaways

Educational

Main ideas, concepts, and lessons

  • Placement anxiety + perseverance: The speaker begins placement season optimistically, then repeatedly faces rejections while struggling with DSA/aptitude and interview preparation. They keep going until securing a final full-time offer.

  • Key early mistake (preparation timing): They believe they started DSA too late—around the beginning of 6th semester—and weren’t serious enough earlier.

  • Core subjects are crucial (not optional): They admit neglecting OS, SQL practice/DBMS, and even OOPs—and emphasize that many companies test these topics in interviews.

  • OA (Online Assessment) structure and what matters: They explain that their OA was divided into sections and highlight what they were strong/weak in.

  • Interview rounds are different skills:

    • GD checks communication/confidence and debate skills—not just correctness.
    • Technical interviews check how deeply you understand your resume/projects—people get rejected when they can’t explain their own work.
    • HR interviews evaluate motivation, logistics, communication style, and alignment (e.g., why the company/engineering, willingness to switch, availability, etc.).

  • Offer acceptance + market reality: Even after accepting, they remained aware the market is unpredictable and that friends were still unplaced—promoting a realistic mindset.

  • Career strategy after joining: Their immediate focus is growth and skills; switching can be considered later based on opportunities and experience.

  • Mindset + luck + consistency: They argue placement success is partly luck-based, so you shouldn’t quit—pair consistent preparation with resilience and a “manifesting” mindset.

  • Advice for juniors (3rd/4th years): Use a practical checklist approach covering: DSA + contests, SQL/DBMS (with specific topics), core subjects (OS/Networks/OOPs), and communication skills.

Detailed methodology / instruction-style bullet points (as taught in the video)

A) Preparation timeline / approach (especially for 3rd-year students)

  • Start DSA early

    • If you’re weak in DSA, “lock in” and begin immediately.
    • Do 3–4 daily questions.
    • Practice on LeetCode.
    • Participate in coding contests regularly (even if ranks aren’t great).

  • Use contests to build real problem-solving speed

    • Don’t skip contests out of fear.
    • Competitions help even with imperfect performance.

  • Cover arrays, strings, and hashmaps

    • Focus on these via repeated practice and contest participation.

B) Syllabus focus for OA/placement (what companies test)

  • DSA / programming fundamentals

    • Continue consistent practice instead of binge learning.

  • SQL / DBMS

    • Practice writing SQL fluently.
    • Be ready for common SQL interview tasks:
      • Joins
      • Window functions
        • Understand basics and popular functions conceptually, including:
          • DENSE_RANK / RANK / ROW_NUMBER
          • aggregate-style functions (described generally)
    • Practice 50 LeetCode SQL problems as a baseline approach.

  • Core subjects (do not neglect)

    • Pay attention to:
      • OS
      • DBMS
      • Computer Networks
      • OOPs

  • Don’t leave OOPs to the last minute

    • They warn that LLD/interview questions can be based on OOPs and won’t be mastered “in two weeks” without sustained effort.

C) Communication skills (interview performance multiplier)

  • Work on English speaking

    • Interviewers expect clear communication in English.

  • Methods to improve communication

    • Use mock interviews
    • Record/talk to yourself
    • Use YouTube practice (and similar self-training)
    • Engage in gradual daily speaking practice

D) Resume/project strategy (technical interview survival)

  • Know every item you put on your resume

    • If you can’t explain a project/topic deeply, you may be rejected.

  • Prepare for “where and why” questions

    • If your resume mentions advanced topics (e.g., RAG), you must explain:
      • what it is
      • where you used it
      • how it works in your project

  • Bring proof/implementation

    • Live links/tools/demos can impress interviewers.

E) Placement execution mindset (how to behave during the season)

  • Keep applying daily

    • Don’t stop at one rejection.

  • Pick a niche and still cover fundamentals

    • Stay focused, but don’t neglect basics.

  • Accept that success includes luck

    • Even strong candidates can fail due to “dirty luck” or mismatched interview conditions.

  • Don’t give up

    • Maintain the belief that you can still be selected.

  • Manifesting (mindset practice)

    • They mention “manifesting” during June and believe mindset helped them stay persistent.

Speakers / sources featured

  • Speaker (primary): Nivedanpati Student; recently placed Software Engineer; interning at We Technology; Information Technology, 4th year at Bhagwan Parshuram Institute of Technology, New Delhi.

  • Organizations / companies mentioned:

    • RTDS
    • Gemna Sessions (as mentioned in subtitles; exact company name may be imperfect due to auto-captioning)
    • Josh Technology
    • Virsa (used as a placement/training context; exact spelling may be off)
    • We Technology (the job offer/employer; full-time conversion)
    • LeadCode / LeetCode (practice platform mentioned)
    • CodeChef (contests mentioned)
    • HackerEarth / Hackerata (practice mentioned; likely HackerRank/Hackerrank-like naming is imperfect in subtitles)
    • LinkedIn, Instagram, X (social platforms mentioned for contact)

Original video