↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Offers from Amazon, Apple, and Facebook: Things I Wish I Knew

The article argues that there is no single path into big tech companies. The author says she did not follow the usual “LeetCode grind” approach, instead studying like a class, practicing interview problems, and relying on mock interviews and community support. She also stresses that communication, feedback, and nerves are part of the interview itself.

Reading notes
#

  • The author says big tech felt inaccessible to her for several reasons, including limited LeetCode practice, anxiety, and feeling late to the process.
  • She prepared by treating interview prep like coursework, using books, notes, memorization, and conceptual study.
  • Her main syllabus was complexity analysis, data structures, and algorithms.
  • For data structures, she focused on linked lists, arrays, strings, stacks, queues, graphs, maps, sets, trees, tries, and heaps.
  • For algorithms, she studied sorting, binary search, traversals, recursion, backtracking, and some OOP concepts.
  • She says she did not fully get to dynamic programming, bit manipulation, system design, or greedy algorithms before getting offers.
  • She used Cracking the Coding Interview, university notes, GeeksforGeeks, a friend’s CodePath notes, and MIT OpenCourseWare.
  • She kept interviewing while learning and failed many interviews along the way.
  • Her practice included easy LeetCode problems for comfort and medium problems for interview-style practice.
  • She recommends spending real time on each question, revisiting it, discussing it with others, and practicing under time constraints.
  • She used Pramp for mock interviews and also practiced with friends and student communities.
  • She says interviewers evaluate communication and whether they want to work with you, not only technical skill.
  • She recommends small talk, a polite introduction, and staying attentive and pleasant throughout the interview.
  • During the problem, she advises clarifying assumptions, edge cases, and expected behavior before coding.
  • She treats interviewer feedback as part of the process and says responding well to corrections matters.
  • She says nerves were one of her hardest problems and that practice, flashcards, and repeated exposure helped reduce anxiety.
  • She emphasizes that it is okay not to know everything and that failure is only final if you stop trying.
  • She says taking care of health matters during long interview prep because the process can be exhausting.
  • She believes interviews measure persistence, learning ability, study habits, willingness to face challenges, response to feedback, and communication under pressure.
  • She lists helpful resources: Facebook Above and Beyond CS, LinkedIn, Rewriting the Code, CUNY Tech Prep, Pramp, Cracking the Coding Interview, LeetCode, community support, and Back to Back SWE.
  • She says a concentrated month of studying during January was what most strongly carried her to the offers.
  • Her conclusion is that different people can reach big tech through different paths, and that persistence matters.