Technical Interviewing

Technical Interview slides for bootcamp workshop

Transcript

1. Technical Interviews rj zaworski · @rjzaworski · github.com/rjz
2. Write a program to shuffle a deck of cards.
3. How did you do?
4. Ineffective interviewing ★ Vague, open-ended questions ★ No introduction or context
5. Ineffective interviewing ★ Vague, open-ended questions ★ No introduction or context ★ No communication!
6. Before we begin 1. Software is collaborative 2. Teams aren’t just tech 3. Interviews are conversations
7. Before we begin ★ Every team is different ★ Every company is different ★ Every hiring process is different
8. Before we begin ★ Every team is different ★ Every company is different ★ Every hiring process is different ★ Your mileage may vary
9. Setting the stage First impressions matter!
10. Setting the stage ★ Get to know the company ★ Introduce yourself
11. Setting the stage ★ Get to know the company ◦ Industry? ◦ Major products or projects? ◦ Team / management structure? ◦ Technologies? ★ Introduce yourself
12. Setting the stage ★ Get to know the company ★ Introduce yourself ◦ Cover letter ◦ Current github ◦ Focus technologies / projects for role ◦ Demos?
13. Show up Technical interviews are still interviews
14. Show up ★ Get a good night’s sleep ★ Arrive early (but not too early) ★ Dress one notch above ★ Bring what you need
15. Show up Q: What to expect? What to bring? A: Ask recruiter / hiring manager in advance!
16. Whiteboarding ★ Knowledge, thinking, and communication ★ Text editor ~ physical whiteboard ★ Format may vary ◦ pair programming ◦ take-home ◦ one thing about spec work..
17. Whiteboarding 1. Write the spec 2. Propose a naive solution 3. Implement it 4. Validate against the spec
18. Whiteboarding In other words, “TDD”
19. 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
20. 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
21. 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
22. 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?
23. Whiteboarding Remember: it’s a communication exercise!
24. Any questions?
25. Wrapping up ★ Ask company / team questions in person ★ Thank interviewers for their time ★ Follow up afterwards
26. 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
27. Follow up ★ Ask company / team questions in person ★ Thank interviewers for their time ★ Follow up afterwards
28. 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)
29. Further Reading ★ Grad’s guide to team coding (Atlassian) ★ Practice problems (Codewars) ★ Even more practice problems (Hackerrank) ★ The whiteboarding exercise
30. Thank you! rj zaworski · @rjzaworski · github.com/rjz