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

Technical Interviewing

Technical Interviewing

Technical Interview slides for bootcamp workshop

RJ Zaworski

October 01, 2015
Tweet

More Decks by RJ Zaworski

Other Decks in Programming

Transcript

  1. Before we begin 1. Software is collaborative 2. Teams aren’t

    just tech 3. Interviews are conversations
  2. Before we begin ★ Every team is different ★ Every

    company is different ★ Every hiring process is different
  3. Before we begin ★ Every team is different ★ Every

    company is different ★ Every hiring process is different ★ Your mileage may vary
  4. Setting the stage ★ Get to know the company ◦

    Industry? ◦ Major products or projects? ◦ Team / management structure? ◦ Technologies? ★ Introduce yourself
  5. Setting the stage ★ Get to know the company ★

    Introduce yourself ◦ Cover letter ◦ Current github ◦ Focus technologies / projects for role ◦ Demos?
  6. Show up ★ Get a good night’s sleep ★ Arrive

    early (but not too early) ★ Dress one notch above ★ Bring what you need
  7. Show up Q: What to expect? What to bring? A:

    Ask recruiter / hiring manager in advance!
  8. Whiteboarding ★ Knowledge, thinking, and communication ★ Text editor ~

    physical whiteboard ★ Format may vary ◦ pair programming ◦ take-home ◦ one thing about spec work..
  9. Whiteboarding 1. Write the spec 2. Propose a naive solution

    3. Implement it 4. Validate against the spec
  10. Whiteboarding 1. Write the spec a. Clarify problem, assumptions b.

    “Given a deck of cards, expect the same cards in a pseudo-random order, assuming cards are a string array” 2. Propose a naive solution 3. Implement it 4. Validate against the spec
  11. Whiteboarding 1. Write the spec 2. Propose a naive solution

    a. Talk through your approach b. Revise assumptions 3. Implement it 4. Validate against the spec
  12. Whiteboarding 1. Write the spec 2. Propose a naive solution

    3. Implement it a. Functions clarify input / output b. Define placeholders (e.g. Rand() => Number ) if needed c. Don’t worry about optimizing (yet!) 4. Validate against the spec
  13. Whiteboarding 1. Write the spec 2. Propose a naive solution

    3. Implement it 4. Validate against the spec a. Step through function, check result to spec b. It failed? Correct errors and repeat. c. Or it passed! What’s next?
  14. Wrapping up ★ Ask company / team questions in person

    ★ Thank interviewers for their time ★ Follow up afterwards
  15. Wrapping up ★ Ask company / team questions in person

    ◦ Technical interviewers have ‘been there!’ ◦ Get scoop on tech stack, teams, and roadmap ◦ Inquire about next steps! ★ Thank interviewers for their time ★ Follow up afterwards
  16. Follow up ★ Ask company / team questions in person

    ★ Thank interviewers for their time ★ Follow up afterwards
  17. Follow up ★ Ask company / team questions in person

    ★ Thank interviewers for their time ★ Follow up afterwards ◦ Build relationships with simple thank-yous ◦ Keep in touch of status changes (other offers, etc)
  18. Further Reading ★ Grad’s guide to team coding (Atlassian) ★

    Practice problems (Codewars) ★ Even more practice problems (Hackerrank) ★ The whiteboarding exercise