Upgrade to Pro — share decks privately, control downloads, hide ads and more …

DevOpsDays Boston 2020 - Passing the Technical Interview

Ben Edmunds
September 29, 2020

DevOpsDays Boston 2020 - Passing the Technical Interview

In this talk we’ll discuss the main aspects of handling the large tech company interview process. We’ll cover topics like prepping for interviews, coding interview questions, large scale system design, behavioral questions, how to interview your interviewers, and negotiation.

First we’ll cover how to prep for interviews, resources, and time allocation. Along with what you should expect throughout the process.

Next we’ll walk through how to prep for each step of the interview process.

We’ll finish up by discussing what to do once you receive an offer and how to negotiate.

Ben Edmunds

September 29, 2020
Tweet

More Decks by Ben Edmunds

Other Decks in Technology

Transcript

  1. Who is this guy? Ben Edmunds Open Source Author PHP

    Town Hall Podcast
 More Than Code Podcast Staff Eng @ Wayfair
  2. Stages 1. Phone Screen • High level • Why are

    you looking • What are you looking for • Pitch on company/role
  3. Stages • High level but deeper tech • Experience with

    specific technologies • Pitch on Company/Role 2. Manager Screen
  4. Stages 3. Coding Test - Take Home • Small project

    • Designing architecture • Designing APIs • Solving algorithms
  5. Stages 3. Coding Test - Online • Small problem(s) •

    Algorithmic problem • Time complexity • Space complexity
  6. Stages 3. Coding Test • Lite version of Coding and

    Sys Design on-site evals • Real world experience PREP
  7. Stages 3. Coding Test • Sys Design & Architecture •

    Based on role 
 interviewing for PREP
  8. Stages 3. Coding Test • Algos • Common Problems PREP

    + FizzBuzz, 8 Queens, Boggle, Subset Sum, etc
  9. Stages 4. Onsite Evals • 9-9:30 - arrival / meet

    recruiter • 9:30-10:20 - meet hiring manager • 10:30-11:20 - coding w/ 2 sr engineers • 11:30-12:20 - sys design w/ sr architect • 12:30-1:30 - lunch w/engineer on team • 1:30-2:20 - coding w/ 1 staff engineer • 2:30-3:20 - debrief w/ recruiter
  10. Stages 4. Onsite Evals • 9-9:30 - arrival / meet

    recruiter • 9:30-10:20 - meet hiring manager • 10:30-11:20 - coding w/ 2 sr engineers • 11:30-12:30 - sys design w/ sr architect • 12:30-1:30 - lunch w/engineer on team • 1:30-2:20 - coding w/ 1 staff engineer • 2:30-3:20 - debrief w/ recruiter
  11. Stages 4. Onsite Evals • 9-9:30 - arrival / meet

    recruiter • 9:30-10:20 - meet hiring manager • 10:30-11:20 - coding w/ 2 sr engineers • 11:30-12:30 - sys design w/ sr architect • 12:30-1:30 - lunch w/engineer on team • 1:30-2:20 - coding w/ 1 staff engineer • 2:30-3:20 - debrief w/ recruiter
  12. Stages 4. Onsite Evals • 9-9:30 - arrival / meet

    recruiter • 9:30-10:20 - meet hiring manager • 10:30-11:20 - coding w/ 2 sr engineers • 11:30-12:30 - sys design w/ sr architect • 12:30-1:30 - lunch w/engineer on team • 1:30-2:20 - coding w/ 1 staff engineer • 2:30-3:20 - debrief w/ recruiter
  13. Stages 4. Onsite Evals • 9-9:30 - arrival / meet

    recruiter • 9:30-10:20 - meet hiring manager • 10:30-11:20 - coding w/ 2 sr engineers • 11:30-12:30 - sys design w/ sr architect • 12:30-1:30 - lunch w/engineer on team • 1:30-2:20 - coding w/ 1 staff engineer • 2:30-3:20 - debrief w/ recruiter
  14. Stages 4. Onsite Evals • 9-9:30 - arrival / meet

    recruiter • 9:30-10:20 - meet hiring manager • 10:30-11:20 - coding w/ 2 sr engineers • 11:30-12:30 - sys design w/ sr architect • 12:30-1:30 - lunch w/engineer on team • 1:30-2:20 - coding w/ 1 staff engineer • 2:30-3:20 - debrief w/ recruiter
  15. Stages 4. Onsite Evals • 9-9:30 - arrival / meet

    recruiter • 9:30-10:20 - meet hiring manager • 10:30-11:20 - coding w/ 2 sr engineers • 11:30-12:30 - sys design w/ sr architect • 12:30-1:30 - lunch w/engineer on team • 1:30-2:20 - coding w/ 1 staff engineer • 3:30-4 - debrief w/ recruiter
  16. Stages 4. Onsite Evals • 9-9:30 - arrival / meet

    recruiter • 9:30-10:20 - meet hiring manager • 10:30-11:20 - coding w/ 2 sr engineers • 11:30-12:30 - sys design w/ sr architect • 12:30-1:30 - lunch w/engineer on team • 1:30-2:20 - coding w/ 1 staff engineer • 3:30-4 - debrief w/ recruiter
  17. Examples “Given an array of the 100 most common child

    names in 2020, sort them alphabetically” “List the top 10 products sold alphabetically on the sidebar of a site. Given an array of the top 1,000 products where the key is their popularity and the value is the product name. Return an array.” Quicksort
  18. Examples “Given an array of the 100 most common child

    names in 2020, sort them alphabetically” const childNames = […]; return childNames.quicksort(); Quicksort
  19. Examples const products = […]; return products.quicksort() .slice(0, 10) .quicksort();

    “List the top 10 products sold alphabetically on the sidebar of a site. Given an array of the top 1,000 products where the key is their popularity and the value is the product name. Return an array.” Quicksort