1 / 11

Nailing Your Technical Interview

#GHC13. Nailing Your Technical Interview. Sabrina Williams 10/4/2013. 2013. Sabrina Williams. Software Engineer in Test @ Google Conducted a wide variety of interviews Software Engineer Software Engineer in Test Test Engineer Interns (all levels in college) We want you to succeed!!

casta
Download Presentation

Nailing Your Technical 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. #GHC13 Nailing Your Technical Interview Sabrina Williams 10/4/2013 2013

  2. Sabrina Williams • Software Engineer in Test @ Google • Conducted a wide variety of interviews • Software Engineer • Software Engineer in Test • Test Engineer • Interns (all levels in college) • We want you to succeed!! • Disclaimer: advice not necessarily universal but generally applicable

  3. Interviewer’s Goal: Sabrina’s 6 ‘C’s • Would I want you on my team? Evidence! • Character • Coding • Cognition • Communication • Creativity • Culture • Missing C’s (confidence, charisma, etc.) • Difference: fatality of negative signals

  4. Interview Format • Non-coding question(s) • Experience based on résumé • Best practices and processes • Coding and/or design question(s) • Show proficiency in programming language • Choose appropriate data structure/algorithm • May involve diagramming (for design) • May include doing a code review • Time to ask the interviewer questions

  5. Do’s and Don’ts: Do’s • Think out loud • Understand the question (clarify & repeat) • Explicitly state assumptions • Give a simple solution first • Mention optimizations • Let interviewer decide importance • Test your code • Pay attention to hints

  6. Do’s and Don’ts: Don’ts • Disrespect the interviewer • Argue, but don’t fight • Don’t insult the interviewer’s intelligence • Try too hard to reproduce previously-seen solutions • Ask inappropriate questions • Salary (directly) • Complain about company decisions • Play on underrepresented status

  7. Preparation: Non-Technical • Writing on a white board • Speaking out loud while you code • Coding without an IDE • Implementing simple solutions • Explaining the items on your résumé • Research the company (just a little bit) • Products • Key people (CEO, Chairman, founders) • Headquarters, # employees, etc.

  8. Preparation: Technical • Programming Language • Data Structures • Stacks, queues, trees, tries, graphs, hashmaps • Understand operations on the structures • Algorithms • Provide Big-O for any code you write • Iterative vs. recursive solutions, DFS vs. BFS • System Design • Testing

  9. Preparation: Resources • Practice problems • Project Euler • TopCoder • HackerRank • Google Code Jam • Glassdoor • CLRS “Introduction to Algorithms” • Open source • Other engineers (mock interviews)

  10. Contact Information • Sabrina Williams • Google+: https://goo.gl/sGyQvg • Twitter: @barkimedes • Blog post: http://goo.gl/VWVO7O • Blog at https://barkimedes.blogspot.com • Will contain more details than the slides

  11. Got Feedback? Rate and Review the session using the GHC Mobile App To download visit www.gracehopper.org

More Related