Video Summary - Non-CS to Amazon, Samsung & Google 🔥 | DSA Roadmap That Works

Summary of the video/subtitles (DSA → Amazon/Samsung → Google; roadmap for placements)

Satyam is a 2024 NIT Patna graduate, now a Google software engineer (he switched to Google around Jan 2025).
He previously did internships at Amazon and Samsung, then later moved to Google.
The host shares that he was rejected by Google in the final round, framing the discussion around “how to reach Google.”

Google work schedule is described as flexible, not a strict daily office requirement.
He says you must come to the office only two days a week; the rest can be work from home (with team-to-team differences).
He pushes back on “reels lifestyle” stereotypes:
- Yes, there are plenty of campus amenities (gym, games like pickleball / table tennis / basketball),
- but workload and “chill-ness” vary significantly by team.
He mentions weight gain (~10 kg in 6 months) after joining, then later added the gym and balanced it with games.

In college, his early approach was heavily focused on Competitive Programming (CP) and DSA.
He recommends starting before interview prep, building strong problem-solving through platforms like:
- Codeforces / LeetCode / CodeChef
He credits this for:
- improved problem-solving skill
- building a competitive mindset (aiming for high ratings and titles like Candidate Master/Guardian)
- learning time management through regular contests and practice

Since first-year at NIT Patna was online (Covid), he had more time for coding.
He created/maintained study/coding groups and held live contests/discussions for peer learning.
For exams, he sometimes relied on topper guidance shortly before exams, leading to a CGPA around 8.4.
He emphasizes that CGPA was not his primary selection factor for top tech roles.

He says in college he mostly pursued coding and didn’t build a deep development/project habit.
He attributes part of it to starting from basic web topics and losing interest.
During internships:
- Amazon internship pushed him into more development work, which was hard initially because he lacked fundamentals.
- He later learned to do projects end-to-end, understanding the full flow (backend → API → UI rendering).
Strong advice:
- Don’t build just for “show”—build for understanding
- Avoid “copy-paste/build only when interview needs it”
- If you can’t explain the why behind tech choices (e.g., specific HTML tags), interviews will reveal it

Amazon internship
- Did well technically
- Worked on a project related to video series navigation / season & episode formatting
- Didn’t get PPO due to higher expectations and recession
Oracle attempt
- Got stuck when they asked CS fundamentals, not just DSA
- Admits he memorized definitions without understanding deeper mechanisms
Samsung
- Selected via a process where online assessments were more structured
- Offline interviews emphasized relative factors like coding performance/rank and interview rounds
- He felt relieved after the placement

After Samsung full-time, he started preparing again to switch.
When the Google opportunity came via LinkedIn HR outreach, he had about one month to prepare.
He used his leave time for focused preparation:
- reviewing Google interview experiences
- doing LeetCode / DSA end-to-end preparation
- building notes earlier so they stayed useful closer to interviews

He argues own notes work better than others’ notes because:
- they reflect what you understood at the time
- they help you reconstruct reasoning later
- writing in his own language (Hindi) improved comprehension and recall

He claims big tech (Google/Amazon/Microsoft) typically doesn’t use CGPA as a strict filter; minimum thresholds may exist, but the emphasis is problem-solving.
For smaller companies, CGPA may matter more as an elimination filter.
Practical advice:
- Keep a decent CGPA (he suggests 8+ as a safe baseline)
- but don’t over-optimize it at the expense of DSA

Amazon
- Mostly DSA-focused, plus a behavioral round
- Behavioral topics include time management, team communication, and handling disagreements
Google
- Emphasizes problem-solving using unique questions and follow-ups
- Also focuses on code readability/clarity, not just “famous memorized LeetCode patterns”
- He says Google tests how you think and iterate, not only whether you can reproduce known solutions

Pick a language (he recommends C++ mainly because many resources/examples assume it, and STL knowledge transfers well).
Understand core STL basics (e.g., vector/map/queue).
Create accounts on CP platforms and start from lower difficulty, gradually increasing.
Use contests not only for ratings, but to learn:
- time management
- why you missed: topic gap vs misunderstanding vs speed issue
Suggested resources mentioned:
- Codeforces explanations for DSA/CP
- Aadit Verma for DP (as remembered in the subtitles)
He stresses achieving goals like:
- Guardian on LeetCode
- Expert on Codeforces to build confidence

He observes increased suspicion that some contestants use AI/copy-paste to inflate ratings.
His advice:
- Don’t let others’ cheating derail you—contests are for your own learning.
- “Inflated” skills won’t hold up in real interviews where you must solve without assistance.
- Real interviews expose lack of understanding.

Don’t panic about placements; he claims most students eventually get offers (either on-campus or later).
Maintain a group with peers, discuss topics, and keep coding enjoyable.
Balance matters: there were nights studying late, but it was sustainable through preparation and peer learning.