Here’s our alumni, Sneha Padhi, who made it to her dream job at Microsoft!

Main ideas, concepts, and lessons

• Long-term dream + role modeling

  • Sneha’s father worked at Microsoft, which made the company a long-standing goal from childhood.
  • She was influenced by Microsoft’s work culture and wanted to work there (or at least in a similar organization).

• Early exposure to the company

  • As a child, she attended a “Take Your Child to Work”-style event at Microsoft.
  • She gained hands-on exposure to equipment and learned how Microsoft works, which increased her interest in engineering.

• College choice shaped by entrance constraints

  • During JEE prep, she didn’t score high enough for CSE at her preferred colleges.
  • She entered through MSET, selected a college via that route (GRIET), and committed to working hard there.

• Academic strategy for non-IIT/NIT backgrounds

  • She emphasized maintaining a very high GPA (9+) to offset the lack of an IIT/NIT “brand.”
  • Her mindset: strong academics + good work can still strengthen a resume.

• Career timeline: internship/interview attempts and setbacks

  • A key moment came when JP Morgan approached her at Microsoft for an internship opportunity.
  • She passed an online test but was eliminated during the next stage due to behavioral questions (a HireVue-like process described later).
  • Later, she applied for Microsoft-related opportunities and Goldman Sachs and experienced:
    • Passing technical screening but getting rejected afterward.
    • A belief that the weakness was in the HR/management phase, especially around explaining/positioning her projects under pressure.

• Interview learning through repeated experience

  • She compares multiple setbacks (including an Amazon interview in 2012) to show a pattern:
    • Not remembering a project well enough during clarifying questions can hurt performance.
    • Sometimes, interviews still progress unexpectedly (e.g., she proceeded despite thinking she would fail).
  • She highlights that introspection after rejection often reveals the most actionable issue (e.g., being rushed, project clarity, or confidence).

• HireVue / HireVue-style rejection: what she concluded

  • Communication is critical:
    • Even if the interviewer isn’t fully focused on content, clear communication can help keep attention.
  • She felt her thoughts were scattered during HireVue.

• Preparation philosophy: persistence + understanding over copying

  • Consistency problems happen (she mentions the common loop of starting/stopping arrays).
  • She overcame a specific barrier (“stuck on arrays”) through structured learning (Smart Interview course).
  • For hard topics like dynamic programming and graphs:
    • Persistence matters—don’t give up just because it doesn’t “click” immediately.
    • Repeated exposure eventually makes concepts feel natural.

• Use of resources (including “GPT”) as a learning tool

  • When stuck on a LeetCode hard problem, she recommends:
    • Look up the solution briefly (even via GPT or similar).
    • Spend only ~30 seconds scanning for keywords/categories (e.g., DP, backtracking, graphs, prefix sums).
    • Return to the problem and try again.
    • Repeat the cycle multiple times (about 2–4 reads/iterations).
  • She argues GPT helps because it provides an approach/decision-making train of thought, not just code.
  • She warns against jumping straight to code, copying, and missing underlying logic—especially in DP.

• Mindset during ranked competitions

  • In competitive programming/screening-style challenges (Smart Address program mentioned):
    • She wasn’t top on the leaderboard.
    • She doubted herself because others seemed naturally strong in DSA.
  • Lesson: development is personal; you can’t measure your growth solely against others’ pace.
  • Progress comes from consistent effort, even if it’s slower for you.

• Company-focused strategy

  • For companies like Microsoft, Google, and Amazon, she concluded DSA/algorithms are the main emphasis.
  • She prioritized based on needs:
    • If she struggled with a topic, she focused there instead of trying to do everything.
  • For Microsoft specifically:
    • She used Microsoft-specific questions and popular prep sheets (e.g., Striver sheet).
    • She targeted weak topics and worked through them systematically.

• Time management: how she prepared with limited scheduling

  • Microsoft took 1–2 months to respond after resume selection to OA (online assessment).
  • There was also about 1–2 months between OA and the interview, giving her time to prepare.
  • After the invite, she used Reddit and adjusted plans based on community guidance.
  • She had a tight gap: about one week between receiving the invite and the final interview date.
  • Principle: if you don’t feel ready, you probably can’t become “fully ready” instantly—but you can cover as much as possible with the time you have.
  • She notes an advantage: earlier-year students may be evaluated more leniently than final-year applicants.

• Smart Interview course impact

  • She credits the Smart Interview (DSA course) and its instructor:
    • Structure helped her avoid getting stuck on the same topic.
    • Better explanations increased her interest in DSA.
  • A memorable moment:
    • A “follow-up” question was taught as commonly asked by big companies.
    • In her actual Microsoft interview, she was asked that same follow-up.
    • Recognizing it boosted her confidence and helped her complete the task.

---

Methodology / instructions (detailed bullet points)

A) How to prepare when stuck on hard problems (problem-solving loop)

• If you cannot solve a LeetCode Hard problem after ~20–30 minutes:
  • Use an external resource (she mentions GPT or similar).
  • Spend about 30 seconds reading the explanation/solution to extract:
    • The topic category (e.g., backtracking, dynamic programming, graphs, prefix sums).
  • Stop using the resource and return to attempt the problem again.
• Repeat the cycle:
  • Watch/read again for 1–2 minutes,
  • Try again,
  • Do this 2–3 times (or more if needed).
• Goal:
  • Build understanding through repeated exposure until it “clicks,” rather than memorizing code.

B) Learning approach for complex concepts (DP/graphs)

• Study multiple explanations until the concept becomes understandable.
• Treat “not understanding the first time” as normal.
• Practice persistence:
  • Don’t give up just because the problem feels incomprehensible.
  • Keep trying until the concept becomes natural.

C) Interview preparation prioritization strategy

• Identify what each target company emphasizes:
  • For Microsoft/Google/Amazon: focus primarily on algorithms/DSA.
• Don’t try to do everything:
  • Prioritize based on your weakest areas.
• When an interview chance appears:
  • Work through company-specific question sets plus standard lists (e.g., Striver sheet).
  • Double down on topics you previously found difficult to avoid getting stuck again.

D) Communication strategy for video/HR-style stages (HireVue-like)

• Recognize that communication can heavily affect interviewer perception.
• During HireVue/self-recorded stages:
  • Prevent scattered thinking.
  • Communicate clearly so the interviewer can stay engaged even if they aren’t fully focused on every detail.

---

Speakers / sources featured (as mentioned)

• Sneha Padhi (main interviewee/alumna)
• Sneha’s father (source of Microsoft inspiration; employer mentioned)
• JP Morgan (approached her regarding an internship opportunity at Microsoft)
• Microsoft (target employer; interview/OA context)
• Goldman Sachs (internship/interview experience context)
• Amazon (2012 interview experience context)
• Reddit (community source Sneha used for interview timing/insights)
• Striver sheet (study list mentioned)
• Smart Interview / Smart Interviews course and its instructor (DSA course credited for her progress)