Tier 3 College to Google | Palo Alto Networks | Google SDE Roadmap | DSA | Ft. Venkatesh Dhongadi

Main Ideas, Concepts, and Lessons

• Starting point doesn’t limit success

  • Venkatesh Dhongadi shared that he came from a Tier 3 college (Gokte Institute of Technology, Yara II) and still reached Google.
  • He challenges the belief that only Tier 1/Tier 2 colleges can land top-company jobs, arguing that preparation and execution matter more than college tier.

• College preparation strategy: internships + continuous skill building

  • He pursued multiple forms of work during college, including:
    • Teaching/instruction work (English and later DSA-related recorded lectures)
    • Tech internships / part-time work
  • Later, he used these experiences to build readiness for bigger roles.

• GRE/IELTS as an optional parallel path

  • While moving toward placements, he prepared for GRE and IELTS as a backup route (US Masters).

• Real-world hiring is probabilistic and time-sensitive

  • Even with strong performance, offer conversions (PPOs) may depend on factors like:
    • internship performance
    • manager/team fit
    • internal business needs
  • He described the anxiety around PPO timelines—sometimes outcomes become clear only near deadlines.

• How he handled corporate uncertainty

  • His approach during internships included:
    • do “homework” first (try solving independently)
    • if stuck, ask clearly
    • when tasks are ambiguous, request unambiguous direction
    • seek frequent feedback from managers/team leads

• Interview readiness: software engineering vs “just for interviews”

  • His view: be strong in fundamentals so you can pass interviews without turning learning into pure short-term cramming.
  • He distinguishes between:
    • learning for genuine engineering competence
    • studying only for interview formats

• DSA matters, but there’s nuance

  • Big tech uses DSA as proof of problem-solving ability.
  • Competitive programming (CP) is beneficial (“good to have”), but not strictly required—problem solving is the core requirement.
  • He reassures that LeetCode-style practice + fundamentals can work if done well.

• Resource strategy: pick one roadmap and stick to it

  • He recommends using a structured DSA sheet/roadmap (referenced in a “Striver A to Z”-type style).
  • Core advice: avoid “resource hopping”; complete one high-quality plan thoroughly (even a free version may be enough).

• Career portal applications: perseverance + sometimes unusual tactics

  • He described applying multiple times via Google’s portal and waiting months for updates.
  • He also shared an anecdote about using a secondary “fake”/secondary email account (created to avoid his real email in random signups) and later receiving a legitimate recruiter response.
  • Overall timing can be long—he mentioned roughly six months from application to progress.

• Google hiring process explained at a high level

  • He referenced a flow involving:
    • elimination rounds / interview rounds
    • team matching (a pool of candidates; managers select based on skills and team needs)
  • He clarified that team matching isn’t purely rejection—it’s about finding the right fit.

• Communication is a make-or-break skill

  • He repeatedly emphasized that strong speaking/writing (especially English) affects interview outcomes.
  • Even with technical strength, poor communication can lead to rejection.

• Networking compounds over time

  • He explained how referrals and networks work:
    • people hire friends they trust will perform
    • managers may recommend/pull people they already know when they move companies
  • He advises staying visible through consistent content and sharing work (e.g., blogs/technical posts).

• Mindset: be “the absolute best”

  • He concluded with a motivational principle: aim to be the best at whatever you do, with full effort—money and fame follow consistent excellence.

---

Methodology / Instructions Mentioned (Detailed Bullets)

A) Preparation Approach for Tier 3/Tier 4 Students Aiming for Top Companies

• Clarify your “market requirements”

  • Review job descriptions and understand the skills needed for your target roles.

• Build from basics with a plan

  • Pick one programming language and learn it deeply (common options: C++ / Java / Python).
  • Start DSA while building a development track.

• Choose a development track (full-stack or domain)

  • Examples mentioned:
    • Frontend: React / ReactJS
    • Backend: Node.js + Express, or Django/Flask (Python)
    • Database: SQL or MongoDB
    • Auth: Firebase authentication
  • Build projects connecting the stack components.

• Build projects + compete

  • Participate in as many contests as possible.
  • Maintain a strong portfolio and publish what you build.

• Use job portals aggressively once ready

  • Apply regularly for internships/full-time roles.
  • Start early enough (he suggested starting in the first semester window if possible).
  • Maintain a backup plan, not reliance solely on PPO conversion.

• Do not rely on college classes for learning

  • Attend if needed for grades, but self-learning using resources is the primary driver.

---

B) DSA Practice Methodology He Recommends

• Use a structured “DSA sheet” / roadmap

  • Prefer a trusted roadmap (referenced as a “Striver A to Z”-style plan).
  • Stick to one resource/plan instead of bouncing between many.

• Frequency-based strategy

  • Solve topics in an order based on frequency of company question trends (he mentioned internally sorting Google-related questions by frequency).

• Practice enough to pass interviews

  • Use breadth + depth: solve enough variations to handle different problem statements.

---

C) Competitive Programming (CP) Guidance

• If you can do CP, do it (no loss), but:
  • Don’t assume “no CP = no Google”.
  • The real target is problem-solving skill; CP is one tool to strengthen it.

---

D) Internship Conversion / Professional Performance Checklist

• Take initiative but avoid nonsense

  • If you don’t know something, ask—but:
    • first attempt solving independently (“homework”)
  • For ambiguous tasks:
    • ask what “done” looks like clearly

• Get frequent feedback

  • Regularly meet your manager and ask:
    • what’s going well
    • what to improve

• Maintain regular work quality

  • PPO conversion can be impacted near the end; don’t stop improving before evaluation.

---

E) Job Application Strategy for Waiting & Referrals

• Apply multiple times and persist through long silence periods.
• Ask for referral when appropriate
  • Referrals can help during the process, though he emphasized applying through the portal first.
• Don’t treat one channel as guaranteed
  • Keep applying externally while waiting.

---

F) Communication and Interview Execution

• Practice confident communication

  • Especially English fluency for interviews (or at least be understandable and direct).

• Don’t under-sell yourself technically

  • But don’t over-explain—stay clear, structured, and confident.

• Prepare explanations of trade-offs

  • For system design / LLD/HLD discussions, focus on:
    • understanding requirements/features
    • breaking down tasks
    • understanding how components interact

---

G) Using AI Tools (Warnings / Conditions)

• AI can help write code, but:
  • you must still understand what you’re building
  • break large tasks into smaller sub-tasks before using AI
  • provide enough context to avoid “rabbit hole” irrelevant codebases
• Treat AI like a “kid”:
  • clearer step-by-step instructions produce better outputs.

---

Speakers / Sources Featured

• Speakers

  • Venkatesh Dhongadi (Google Software Engineer; podcast guest)
  • Karthik (podcast host/interviewer)

• Referenced external sources (not speaking roles)

  • Google (career portals/hiring process; Google blog mentioned)
  • Virat Kohli (mentioned as inspiration for the “be the absolute best” mindset)
  • Striver-style DSA roadmap / DSA sheet (mentioned as a resource type)