1 / 46

How to prepare a Tech Interview

How to prepare a Tech Interview. Last Survivor guide to code interviewing. Speakers : Alberto Lorente Leal, alorlea@ieee.org Diego Lucas Jiménez, diego.lucas.jimenez@ieee.org. Backgrounds. Education : Ingeniero de Telecomunicación, ETSIT UPM

nan
Download Presentation

How to prepare a Tech Interview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Howto prepare a Tech Interview LastSurvivor guide tocodeinterviewing Speakers: Alberto Lorente Leal, alorlea@ieee.org Diego Lucas Jiménez, diego.lucas.jimenez@ieee.org

  2. Backgrounds • Education: • Ingeniero de Telecomunicación, ETSIT UPM • Civilingenjörutbildning data teknik, KTH • M.Sc. Software Engineer of DistributedSystems, KTH • Software Engineer, ~1 year • Presidente IEEEsb, año 2010-11

  3. Backgrounds • Education: • SystemsAdministrator, ComputerScience • Software Engineer, 2 years • SystemsAdministrator, 2 years • ETSIT UPM IEEEsbValuateMember (6 years)

  4. Outline • Introduction • What do they look for? • What do they expect? • Preparing a CV • The process. • Getting the interview • Preparation • The Tech Interview!

  5. Introduction • Whatthehellisthis? • Wherediditcamefrom? • Knowing a language vs. Proficient in language • Hiringpeople (cheap vs. Expensivelawsuits) • Software isnotaneasybusiness... • Whyisit so popular? • Doesitdifferfrom a normal Interview? • Isit so hard?

  6. What do they look for? Testing aptitude, not knowledge

  7. What do theyexpect? The most important interview question is not covered any place probably. In fact, it’s often the single most important question in your interviewers' minds as they grill you in that little room. Despite the questions on polymorphism and heaps and virtual machines, the question they really want an answer to is ... Would I have a beer with this guy?

  8. Preparingthe CV

  9. Preparingthe CV

  10. Preparingthe CV

  11. Preparingthe CV • Build a powerful resume • Goal: HIRE ME!! • Includerelevantinformation • Gettothepoint, keepit simple (2 pages) • Checkyourgrammar!! • Easyto do, isn’tit?

  12. Preparingthe CV • Sixmilestonestobuild a powerful CV: • AccomplishmentOriented • QuantifiableResults • WellTargeted • UniversallyMeaningful • Clean, Professional, Concise • WellStructured and Clear

  13. Clear CV WTF!!? WTF!!? WTF!!?

  14. No, seriously

  15. Preparingthe CV • Nowyou are askingyourself: • Make use of your time! • Make a kick-ass resume How I can make myself special? It’s really not that hard. Ok, no, itis.

  16. Theprocess

  17. Gettingthe interview • Applythrough Job sites. • Internship • GraduateEntryLevel • Waitforanswer. • Alternatives? • Referal • Job fairs • Recruiters • LinkedIn • Social Networking

  18. Overview Interview Process

  19. Preparation • Hopefully, youreceive a response of yourdreamcompany. • Reaction? Hello xxxx, Thanksforyourinterest in Google, I am fromthetechnicalrecruitingteam and I wouldfurtherdiscussyourjobopportunitieswithus. Whenisitokaytotalk? Regards,

  20. Preparation Whatpeopleseewhenyougetthe interview Whatyoureallysee

  21. Preparation • Yourbiggestexamis at yourdoorstep. • Up tothechallenge? • Remember: Testing aptitude, not knowledge Looking for doers

  22. Preparation • Do notonlyfocusontechnicalaspects • Theywanttoknow YOU! • i.e: Yourpersonality. • Addchemistrytotheteam. • Definitely NOT mindlesscoding machine • Expect Behavioralquestions

  23. BehavioralQuestions • Personality • Communicatewell • Answerwell • Watchfor red flags Arrogant, non teamplayer • Strategies: • NuggetFirst • S.A.R: Situation, Action, Result

  24. PreparingBehavioralQuestions • Iseasierthanitseems • 1. CV islikeyourlifeexperience, refreshthesituations. • 2. PreparationGrid.

  25. Strategy 1: NuggetFirst • Startwith a goodinitiator • Goal: Graspinterviewersattention and context Q: Whatwasyourgreatestachievement in project X? A: One of mygreatestachievementswaswhenweadded a new wholefunctionality..

  26. Strategy 2: S.A.R

  27. TechnicalSkillsInterview Preparation

  28. Howtotech interview • Study and refreshconcepts! • Network Engineer Routing, OSPF, TCP/IP, etc • Software Engineer  Algorithms, threads, scalability, coding, ObjectOrientedDesign, Patterns…. • Practice! • Loads of problemson internet • Do notmemorize, useless. • Pushyourlimits! • WRITE CODE ON PAPER (or Google Docs) • AvoidIDEs

  29. Data Structures • Howtoimplement • I.E: Knowhowtocodeityourself • Pros/Cons

  30. Algorithms • Implementation • Space vs. Time Complexity • Learnthycomplexities!! http://bigocheatsheet.com/

  31. OtherFancyAlgorithms • Pathfinding: • A* • Sorts: • Comparisonwithothersorts (insertion, selection) • DynamicProgramming: • Knapsack 0-1 orKnapsackwithrepeateditems • AnythingthrownonProgrammingCompetitions

  32. Concepts • And howtocodeit.

  33. Masteringthe Interview

  34. Duringthe interview • Ask Questions! • Ambiguousquestions, informationismissing • Do notstartcoding as a maniac Red flag, NO HIRE • Talkoutloud • Show yourprocessthinking • Thinkcritically • Isthisoptimal? Complexities? • Slow and cleancode • Beatifulcodewinspoints • Test yourcode! • And fixitaccordingly

  35. GoodCoding Style • Methodical, no rush and no stress. • Bug free code • Doublecheckitworks and fixit (TDD?) • Checkborder cases • Cleancode • Concise, readable • Good use of libraries and data structures • Capable of anotherprogrammerunderstandwhatyouwrite.

  36. Itsaboutstyle: GoodCode • Whycan’twe be friends?

  37. It’saboutstyle: BadCode • Desiretokill!

  38. Dafuken! Do I needtoacealltheseconcepts?

  39. Do notworry! • Evaluationis RELATIVE • Notabsolute It’s not about how quickly you solved the problem… Whatdoesthis mean? … it’s about how quickly you solved it relative to other candidates.

  40. Tell me, Mr. Anderson... • Sit position! • Handsoverthetable • Look theeyes of yourinterviewer • Stay in a relaxedactitude • You are nervous. Confessit! • Mistakes are normal. • Youhavedefects • Point them. Thenexplainhow are youtryingtocorrectthem. • Butanyway, you are thebestcandidate • Convincetheinterviewer

  41. Relax • Interviews are hards • Show thebest of yourself • And final note: EVERYONE MAKES MISTAKES. Everyone!

  42. After Interview • Follow up withrecruiter • No answer != rejection • No idea of your performance onthe interview • Do notthinkorworryaboutit. • Random factor • Interview anti-loop • Ifyoufail, get up and try again, and again.

  43. Mostimportantly • Ifyoufail, learnfromtheexperience • In my case I learned a lot in algorithmsand othertechaspects • And as a gamer: GOOD LUCK & HAVE FUN!

  44. Questions?

  45. Sources • Informationwastakenfrom: • Slides of Cracking thecoding interview, advice and strategiesfor SWE. Gayllaakmann McDowell, Founder of CareerCup. • The Google Resume, Howto prepare for a career and Land a Job on Apple, Google or Microsoft. GayllaakmannMcDowell. • Cracking thecoding interview, 150 interview problems and solutions. GayllaakmannMcDowell. • Otherinterestingsources: • Programming Interviews Exposed, 3rd Edition. • CareerCupwebsite. • Search Google

  46. End of Part 1

More Related