From Tier-3 College to Top Tech Companies 🚀 | DSA, Projects, Resume & Placement Roadmap

Main ideas / concepts / lessons

1) How to ask questions in the session (and what the session is for)

The host frames the sessions as:

• No stories, no lectures
• Q&A format
• Participants ask questions one by one (raised hand)

The host also explains confusion around “tier” (1/2/3/4):

• You don’t need to validate your question before asking.
• The platform exists to express what’s on your mind, not to seek validation elsewhere (e.g., Instagram).
• The session is meant for people who previously booked sessions elsewhere (e.g., “Top Meets”) but didn’t get outcomes.

2) Resume strategy: don’t “overstuff” unrelated tech; be truthful but targeted

A participant describes an AI engineer who applied broadly with many technologies on the resume, which led to:

• Interview calls outside their real fit
• Rejections later

Host’s principle:

• You can write technologies, but only write what you can answer, because interviews will probe those areas.
• Otherwise you’ll fail on deep/edge questions tied to those keywords.

Resume structuring recommendation:

• Make the resume centric around one core area (example: Java/Spring Boot for software development).
• Add AI/ML basics only as supportive knowledge—not as the main claim, unless you genuinely can do that work.

For AI/ML roles, the host argues software dev + deep AIML are different “plates,” and combining everything indiscriminately doesn’t work.

3) Choose a career “plate”: Software development vs AIML/Agentic AI roles

Guest (Jatin) emphasizes separating roles for Agentic AI (AgentKI/AgentKI):

• User perspective roles: build/integrate LLM-based software products (engineer/business-facing building)
• Builder perspective roles: model training/testing (becoming ML engineer / data scientist)

Key takeaway:

• You can’t realistically become expert in both development and deep AIML at the same time just by listing everything.
• Choose where you want to be, and target roles accordingly.

4) DSA progression: intuition develops through repeated practice, not shortcuts

Host’s explanation of DSA “levels”:

• Start with easy problems → then medium → later hard.
• There is no shortcut for the hard approach—you progress by not giving up when stuck.

Rejection handling in practice:

• Failures on some test cases are often edge cases used for follow-ups/interviews.
• Learning from those failures builds intuition.

5) Learning methodology for DSA: one resource end-to-end + lectures only for concepts, practice for intuition

The host repeatedly advises:

• Stop bouncing between many roadmaps/resources.
• Pick one master course/playlist and complete it end-to-end.

Suggested pattern per concept:

• Watch a few videos to understand the concept (not a lecture marathon).
• Immediately practice on LeetCode:
  • Solve multiple questions using that pattern.
  • Build the approach using your own reasoning.

Intuition develops when you apply the pattern to a new question and try yourself.

6) Topic learning: use the easy→medium→hard progression; catch edge cases via doing

For topics like DP and graphs:

• Learn basics first (DP has many edge cases; graphs have extra considerations).
• Watch a limited number of topic explanation videos (e.g., 10–15).
• Then solve:
  • Start easy
  • Move to medium
  • Gradually handle complexity

DP-specific advice from Jatin:

• Understand DP structure such as:
  • Top-down vs bottom-up memorization
• Then create/solve problems to see when to apply each concept.

7) Revision is essential (contradicting “don’t revise” advice)

Host’s stance:

• Revision is the main source of retention.

Practical revision method:

• Do a batch of problems (example: 5 questions).
• Revise that set (example: revise the same 5 repeatedly).
• Repeat on an alternating-day or weekly cadence.

Why:

• Without revision, knowledge fades.
• “Mastering 500/1000” without iterative revision isn’t enough.

8) Application strategy: don’t wait for “perfect timing,” keep applying during hiring peaks

Hiring is peak at multiple times:

• 15 Jan to April
  • Freshers: April to July
  • Experience: 15 Jan to April (as described)
• Another peak: Aug to late Sept / early October

Rule of thumb:

• Apply continuously rather than “start applying tomorrow.”
• Target multiple companies (example: 5–7).
• Apply often as openings appear (every alternate day / every few days).

9) Referrals: helpful but not required; optimize resume and LinkedIn first

Host’s view:

• They personally got jobs (Amazon/Goldman/Google mentioned) without referral.
• If your LinkedIn + resume are optimized, referrals become less necessary.

Referral benefit:

• If two candidates are similar, referral can improve call likelihood.
• But referrals won’t replace a weak resume.

10) Non-IT background: still possible—use startups/internal moves + tool roadmap

A participant asks about non-IT background and learning with C++.

Host’s response:

• Field doesn’t matter; skill matters.
• Big-company calls may be harder initially without an IT degree, but:
  • Start via startups
  • Then move internally later

Example internal movement:

• Moved from data visualization tools → data science team, then started Python gradually.

Roadmap for non-tech to tech:

1. Master Microsoft Office tools, especially Excel
2. Learn data visualization tools: SQL, Power BI, Tableau
3. Then learn Python
4. Leverage internal opportunities to strengthen resume with real experience

11) Language choice: use the language you’re already working with (Java recommended for dev track)

Host advice:

• Don’t learn a new language just for DSA.
• Stick to the language you’re already strong in (example context: Java in Salesforce).
• If starting software dev fresh:
  • Java is recommended as a base language—it helps with other resources/books and building projects.

12) Paid courses: not necessary if free resources are mastered

Host strongly advises:

• Don’t buy paid courses initially.
• Use free playlists/courses fully (one end-to-end).

Free Python suggestion mentioned:

• “Harshit Vashisht” YouTube course (start-to-pro style; libraries + syntax; also DSA/data science oriented)

Overall message:

• Paid courses may exist, but free content + practice is enough.

13) Education/certificates (B.Tech vs B.Sc vs IIT online-style courses): degree alone doesn’t guarantee jobs

A participant asks about leaving B.Tech and considering an IIT Patna BS/B.Sc-type path.

Host’s general position:

• A degree doesn’t automatically get you a job.
• You must:
  • remove backlogs
  • develop skills
  • build projects

Criticism of “IIT-wrapped” online/hybrid courses:

• Often:
  • marketing/credential-focused
  • uneven outcomes (few “heroes,” many others get weaker value)
  • produce certificates rather than real learning pathways

Practical guidance:

• Choose a course that gives you real skills/work.
• Don’t jump blindly between courses because it becomes complicated.

14) Interview readiness: define “when to apply” based on approach-finding under time

Host’s readiness indicator:

• If you can find approaches for easy/medium/hard within about 1 hour, you’re ready to apply.

Also:

• Don’t expect instant calls—keep applying while preparing.

15) Placement season timing: apply even after it slows

Host explains:

• October hiring slows (festivals/holidays).
• Still apply in November/December (December mentioned as still active for big-company hiring).
• Don’t stop applying after a peak window.

---

Methodology / instruction lists

A) Resume / interview targeting (to avoid mismatched calls)

• Identify your true core track:
  • Software development OR AI/ML/Agentic AI
• Resume:
  • Make it centric to the core (e.g., Java/Spring Boot for dev).
  • Add only related AI/ML basics if you can answer questions from them.
• Avoid:
  • Listing every technology from job descriptions if you can’t go deep.
• Rule:
  • If you include a tech keyword, expect interview questions on it.

B) DSA learning loop (concept → practice → intuition)

• Pick one master DSA resource/course playlist.
• For each topic:
  • Watch only a few concept videos needed to understand the pattern.
  • Immediately practice on LeetCode:
    • easy → medium → hard
• During practice:
  • Try solving first with your own reasoning.
  • If you fail, review and identify the missing pattern/edge case.
• Continue until you can solve unseen questions using the pattern.

C) DSA revision plan

• After solving a set:
  • Revise it (example given: Solve 5 → revise 5; repeat with next batch).
• Cadence:
  • revise every alternate day or weekly
• Goal:
  • prevent forgetting; revision is treated as the main source.

D) Topic ramp-up (DP / graphs specifically)

• DP:
  • understand DP mechanisms (e.g., top-down vs bottom-up memorization)
  • then solve in increasing difficulty using easy→medium progression
• Graphs:
  • expect additional edge cases
  • learn traversal/technique first, then solve for edge-case awareness
• General:
  • cover early guidance from ~10–15 concept videos
  • then rely on repeated self-practice for intuition and edge cases

E) Job application strategy while preparing

• Choose target companies (example: 5–7).
• Apply consistently:
  • during peaks and after (don’t stop after October)
  • check openings frequently (alternate days/every few days)
• Apply alongside preparation:
  • don’t wait for “tomorrow”
• Referrals:
  • use as a secondary boost; they help more when resumes/skills are already comparable.

F) Non-IT-to-tech roadmap (as described)

• Master:
  • Excel and Microsoft Office fundamentals
• Learn:
  • SQL, Power BI, Tableau
• Then:
  • Python
• Then:
  • enter via startups and/or internal team movement
  • build resume with practical projects and internal experience

---

Speakers / sources featured (mentioned in subtitles)

Speakers (people)

• Manish (host; addressed multiple times as “Manish Bhai” / “sir”)
• Jatin (guest; works in AIML; also mentions making videos)
• Divya (guest who provides roadmap advice)
• Ayush (mentioned as someone whose advice aligns with focusing on practice over lectures)
• Ashish Mishra (mentioned as someone who previously struggled and later improved)
• Rahul Singh (asked questions)
• Hrithik Sharma (asked about Google CGPA myth)
• Anupriya (asked/raised an opportunity-related point)
• Abhishek (asked from where to start / channel guidance)
• Papaya (participant’s name mentioned; asked about B.Tech vs IIT Patna course confusion—context suggests “Papaya” responded to a host prompt)
• Rahul Bhai / Rahul (distinct from Rahul Singh sometimes implied; subtitles include “Rahul” multiple times)
• Nagraj Dharamdas (mentioned as someone who took a similar course type)
• Ashish Harshit Vashisht / Harshit Vashisht (YouTube course creator recommended for Python)

Sources / platforms / courses (non-person)

• LeetCode
• Striver (DSA course/channel)
• Luv Babbar
• Code / “Love Babbar” (referred to as a DSA teacher; likely “Luv Babbar”)
• Abdul Bari (Time Complexity mention)
• Cyber / Coding Ninja-like reference: “Cyber” mentioned as a resource channel/course (exact platform ambiguous due to subtitles)
• Tech U Forward Plus (mentioned as a paid course, said to be unnecessary)
• Wellfound (mentioned as a common place to apply)
• LinkedIn
• Microsoft Office / Excel
• Power BI, Tableau
• SQL
• Python
• C++, C, Java (programming languages discussed)
• Amazon / Google / Microsoft / Goldman Sachs (company targets mentioned)
• Oracle (employment mentioned by host in personal example)
• Salesforce (employment/language context mentioned by host)