Video summary

How to Crack Amazon as a Fresher in 2026? | SDE Interview Roadmap | Rohit Sharma | Kartikhustles

Main summary

Key takeaways

Educational

Main ideas / lessons (condensed)

  • Amazon hiring expectations for 2026 (freshers) have shifted: beyond classic DSA/system design, interview tasks increasingly include AI fluency and fast, practical building.
  • Internship is a pathway: the speaker describes using internships (including an Amazon hackathon route to hiring interest, then assessments/interviews) to reach a PPO (pre-placement offer) and then full-time conversion.
  • Hackathons are a major advantage: they provide visibility, prototypes, recognition, and sometimes direct access to internship opportunities.
  • Preparation needs to be practical and continuous: build projects, keep refining DSA/CS fundamentals, revise structured materials, and don’t treat learning as “only watching courses.”
  • Visibility drives opportunities: maintaining presence on LinkedIn with project updates and outreach increases chances of being noticed/referred.
  • AI is a tool, not a replacement: companies want you to use AI to accelerate development, but you must still understand the system end-to-end and be able to justify your code.
  • Conversion isn’t purely guaranteed: internship-to-full-time depends on team needs, performance, leadership principles alignment, and availability/open roles.

Methodology / step-by-step guidance mentioned

A) How to crack Amazon as a fresher (preparation focus)

  • Master DSA (two DSA-style questions are mentioned in the interview process).
  • Learn system design basics early enough to handle “freshers-level” system design questions (speaker notes system design questions have become more common for freshers).
  • Add AI readiness
    • Be able to explain how you use AI in daily work.
    • In assessments, expect an AI/build component (not only DSA).
    • Understand AI-assisted vs AI-native development:
      • AI-assisted: use AI/code snippets to help modify parts.
      • AI-native: delegate more end-to-end tasks to AI, but you must still verify, understand, and review output.
  • Be fast and end-to-end
    • Amazon culture (as described) values shipping, iteration, and completing work through testing and delivery.

B) How to get internships (especially first/second)

  • Use hackathons strategically
    • Participate in frequent hackathons and aim to reach finalist/prototype stages when possible.
    • After hackathons, watch for hiring interest forms and the follow-up pipeline.
  • Build a resume with proof
    • “First internship” often requires relevant work already—start building early (projects + hackathons).
  • Use LinkedIn for visibility
    • Post projects regularly (even if small prototypes).
    • Connect and keep activity high so recruiters can spot you.
    • Cold outreach to founders/recruiters is referenced indirectly as a strategy that worked.
  • Apply continuously
    • The speaker’s story emphasizes long waiting cycles and multiple applications/interactions.

C) Amazon internship conversion process (as described)

  • Hackathon → Hiring interest → Online assessment → Online interview(s).
  • Timing matters
    • The pipeline can have long delays and “waitlist” phases.
    • Offers/next steps may roll out in batches later (Nov–Dec in the story; an example release on Oct 4).
  • Internship work phases
    • January–June internship period (as described).
    • Mid-review and final review with presentations.
    • Final decision includes manager + mentor + “bar raiser” influence.
  • What gets evaluated
    • Leadership/behavioral + delivery
      • Leadership principles-style behaviors: ownership, customer obsession, high standards, end-to-end delivery.
      • Proactivity: asking for help when blocked, staying visible in standups, aligning with team work.
      • Productivity and feedback quality from the team.
  • Conversion is not 100%
    • Even strong candidates can depend on team openings and organizational needs.
    • The speaker suggests a conceptual conversion-rate view (example “75–80 out of 100” under good conditions), but stresses it varies with hiring freeze/budget.

D) “How to behave as an intern” to maximize PPO chances

  • Don’t get stuck alone
    • If blocked, ask your mentor/team promptly with genuine doubts.
  • Maintain visibility
    • Participate actively in team updates/standups.
    • Know what other team members are working on and be able to report yours.
  • Schedule recurring 1:1s
    • One-on-ones with manager (bi-weekly or monthly).
    • 1:1s with mentor to discuss growth areas, blockers, next steps.
  • Be proactive about expectations
    • Ask what the team needs and what success looks like for conversion.
  • Code review discipline
    • Even if AI writes code, you must:
      • Review comments and logic.
      • Understand what the code does.
      • Be ready to explain your implementation during review/interviews.
  • Deliver work end-to-end
    • Don’t just write code—ensure it meets goals, is reusable if applicable, and gets delivered.

E) Resources / learning plan the speaker recommends (DSA + fundamentals)

  • Language order
    • Start with C/C++ (speaker says C++ first), then move to Java.
  • DSA learning sequence
    • Mentioned resource creators:
      • Sandeep Jain (speaker tried him first; concept-focused)
      • Love Babbar (long lectures; speaker later switched)
      • Striver “A to Z” sheet as the main structured plan (topic-wise tracking)
  • Revision strategy
    • Watch at faster speed (1.5x–2x).
    • Revise after a week; repeat key topics (DP example mentioned as revised multiple times).
  • CS fundamentals topics
    • Cover alongside DSA: OOP, DBMS, computer networks, etc. (grouped as “CS fundamentals” buckets).

F) Mental health / consistency advice

  • Expect self-doubt during rejection
    • Use a coping routine (gym, mindful breaks, sport/activity) to reset.
  • Stay consistent rather than sporadic
    • “Small daily” beats gaps (example suggested routine: 2–3 hours/day coding/projects).
  • Keep academics stable
    • Maintain CGPA/CPI above a minimum threshold (speaker mentions avoiding falling too low, roughly around 8 CPI in their context).
  • Don’t skip physical activity / hobbies
    • Sports/workouts/hobbies help maintain motivation and focus.

Speaker and sources featured (as best as possible from subtitles)

Speaker(s)

  • Rohit Sharma (main speaker; also the person being interviewed/featured)

Other people referenced (not necessarily speaking on-camera)

  • Rajiv Gandhi Institute of Petroleum Technology (college mentioned as Rohit’s institute)
  • IIT Jodhpur (internship location; also where his first internship happened)
  • Smart India Hackathon
  • Flipkart (startup/company mention; internship story)
  • Microsoft (internship mention)
  • JP Morgan (mentioned hypothetically/alternate possibilities)
  • SDE / AWS / Amazon (role references; not separate speakers)
  • Striver (resource)
  • Sandeep Jain (resource/creator)
  • Love Babbar (resource/creator)
  • Gaurav Sen / Gaurav Sinha (system design/LLD/HLD resource referenced; subtitles mention “Gaurav Sen” and later “Gaurav Sinha”)

No other distinct named on-screen speakers are clearly identified from the provided subtitles.

Original video