The document outlines strategies for succeeding in technical interviews, authored by Gayle Laakmann, who has substantial experience working at top tech companies and creating a resource hub for interview prep. It emphasizes the structure of interviews, what companies evaluate (technical skills, experience, communication), and strategies for both soft skills and technical question preparation. Key advice includes thorough research on companies, practicing coding without a computer, and the importance of demonstrating problem-solving approaches during coding interviews.

1. Cracking the Technical InterviewCracking the Technical InterviewGayle LaakmannFounder / CEO, CareerCup.com

2. My BackgroundUPenn BSE / MSE ‘05 in CSEx-Engineer at Google, Microsoft and Apple + Offers from Amazon, IBM and others3 Years on Google Hiring CommitteeInterviewed 120+ candidatesPreviously taught 2 courses at UW(Now MBA Student at Wharton / UPenn)

3. CareerCupFounded 2005Largest source for technical interview questions (3000+ FREE questions)Services:Book (E-Book and Paper)VideoMock interviews

5. How are interviews structured?How are you evaluated?Process

6. Technical Interview ProcessInitial Screen (Phone / Campus)4 - 5 on site interviews10 min General40 min Technical10 min Closing

7. What do companies look for?Are you smart?Algorithmic skillsCan you code?OOO, Cleanness, bug free (sort of), etcWhat are you like?Communication, friendliness, etcWhat have you done?Relevant experience, passion, etc

8. What do companies look for?Applying

9. Resume SelectionProject experience!Course workOpen sourceIndependent studiesMaster C++ or JavaSkills PassionWork Ethic

10. Resume Advice:One Page. (Seriously.)3 Sections: Education, Employment, ProjectsPet Peeve: Save file with your name

11. Why do you want to work here? What was your favorite project?Interview prep – SOFT SKILLS

12. Research the company / teamPrepare 10 – 15 questions:Genuine QuestionsHow much time do you spend coding each day?Insightful QuestionsI noticed that Google uses Standard X. How do you solve problem Y?Passion QuestionsWhat are the opportunities to learn about scalability at Google?Soft Prep – The Company / Team

13. Create Preparation Grid for Projects+ (maybe) Behavioral GridSoft Prep – Yourself

14. Strengths vs. WeaknessesMediocre answer: “it was hard because I had to learn new languages / technologies”Not just answering Q’s – show who you are!Soft Prep – Yourself

15. How do you prep for coding questions?What do you prep?Interview prep – Tech SKILLS

16. Data structuresAlgorithmsConceptsWhat to study

17. How to implementWhen to use (pros / cons)Data Structures

18. ImplementationSpace vs Time ComplexityAlgorithms

19. ConceptsNot just a concept – know how to code!

20. Don’t practice on computer!

21. What do companies look for?Interview – soft SKILLS

22. The Interview: Chit Chat - TipsBe specific – not arrogant “Yeah, I did all the hard work for the team” “I implemented the file system, which was considered one of the hardest components.”Limited details (else too hard to follow)Ask good questions!

23. ituationctionesponseThe Interview: Chit Chat - TipsSstructure your responsesAR

24. How do you tackle hard tech questions?Interview – tech SKILLS

25. General Advice for Technical QuestionsTalk out loud – show us how you think!Good interviews = hard questionsDon’t be nervous if you can’t solve something!You’re not done untilthey say you’re done.

26. The Coding Interview: 5 Steps

27. Asking QuestionsWhat are the data types?How much data?What assumptions do you need?Who is the user?NOTE: Especially important at Microsoft.

28. OMG! I have no idea how to solve this problem!Algorithm Discovery Approaches

29. Algorithm Discovery ApproachesPattern Matching

30. What problem is this similar to?

31. Simplify / Generalize

32. What if the data was a different type?

33. Base Case & Build

34. Can you do this just for element 1? 1 and 2? …

35. Data Structure Brainstorm

36. Go through all data structures – can they help?Algorithm Discovery ApproachesPattern MatchingA sorted array has been rotated, so that the elements might appear in the order 3 4 5 1 2. How would you find the minimum element?

37. Algorithm Discovery ApproachesSimplify / GeneralizeA ransom note can be formed by cutting words out of a magazine to form a new sentence. How would you figure out if a ransom note (string) can be formed from a given magazine (string)?

38. Algorithm Discovery ApproachesBase Case & BuildDesign an algorithm to print all subsets of a set.

39. Algorithm Discovery ApproachesData Structures BrainstormNumbers are randomly generated and sorted into an (expanding) array. How would you keep track of the median?

40. Find Problems with Your AlgorithmWhat’s the space / time complexity?What if there’s lots of data?Does your design cause other issues?If there are other issues, did you make the right trade offs?

41. Pseudo Code & CodePseudo code first – but tell your interviewerUse data structures generouslyWhat are the right ones?Define your own = shows good styleDon’t crowd your codingStart in the upper left corner of board, not bottom

42. TestingTest your code!Extreme casesCheck for user errorTest general casesCAREFULLY FIX MISTAKES

43. What about non-algorithm problems?System DesignDesign for small system, then scale.Object Oriented DesignWhat are the major objects?How do they interact?Trace It!

44. (eg, things that wouldn’t fit in elsewhere)FINAL THOUGHTS

45. The Interview: Ending ItSmile, be positiveIf you think you bombed, don’t worryFollow up with your recruiters (sometimes they forget)

46. The OfferIt’s always negotiableHelps if you have competing offerDon’t lie – companies know what competitors offerIs it really what you want?Money, career options, etc

47. My Red Flags: People who…… wrote code and didn’t test it… found mistakes and would make random fixes… jammed things messily into an existing data structure… didn’t consider the impact of their algorithms… were scared to try

48. Take Aways – Getting ReadyGet Project ExperienceShow project experience on resumeS. A. R. (Situation Action Result)Prepare Project / Behavioral Grids

49. Technical Interview PrepThings to know (data structures, algorithms, concepts)Simple  Know ImplementationComplex  Know ConceptsPractice interview questions!

50. At The Interview Be niceInterviews are supposed to be hardApproachesPattern matchingSimplify / GeneralizeBase Case & BuildData Structure Brainstorm

51. Other ResourcesE-BookVideoPaperMock InterviewsSlides posted at CareerCup.com/lectures20% Discount Code:[removed from online posting – email support@careercup.com to get it]I have removed the discount code from online posting because, well, things are Google-able and the code is intended for penn students. Please email gayle@careercup.com from your UW email address to get the code.