The Art of Ruby Technical Interviews

From RubyConf 2015 in San Antonio Texas.

So, you want to be a Ruby developer? You've attended a bootcamp, read the books, and completed online courses. You're ready to start building great things. But the technical interview process can be a challenge for new Ruby developers. I'll teach you how to prepare, practice and give you techniques to answer tough questions.

Transcript

1. THE ART OF RUBY TECHNICAL INTERVIEWS
2. CHRIS MAR SOFTWARE ENGINEER CUSTOMINK @CMAR
3. YOU HAVE BEEN LEARNING RUBY
4. EXPERIENCE
5. BUILD
 SOMETHING
6. PASSION IS
 INTERESTING
7. USE
 MULTIPLE
 GEMS
8. PUSH IT
 TO GITHUB
9. DEPLOY IT
 TO HEROKU
10. FORK ME
11. CLEAN CODE
12. DESCRIBE WHAT YOU HAVE BUILT
13. CONTRIBUTE
14. EVERY PROJECT NEEDS DOCUMENTATION
16. em-dash: — en-dash: – 2000 – 2015
17. RESUME
18. PRACTICE
21. Start in the Middle
22. RUBY IS THE COMMUNITY
23. MATZ, TENDERLOVE AVDI, SANDI
24. RUBY ROGUES
 RUBY 5
25. RUBY 2.3.0 RAILS 5
26. TOOLS OF
 THE CRAFT
27. YOU ARE NOT
 AN EXPERT
28. THE INTERVIEW
29. WHAT ARE YOU
 LOOKING FOR?
30. CURIOUS
 MINDS
31. COACHABLE
32. PASSION
33. ENTHUSIASM
34. WHO CONDUCTS THE INTERVIEW?
35. ENGINEER
36. SOLVE PROBLEMS
37. BUILD
 THINGS
38. LOVE
 RUBY
39. WE WANT TO
 HIRE YOU
40. WILL YOU HELP
 ME SOLVE PROBLEMS?
41. WILL IT BE
 FUN BUILDING
 THINGS WITH YOU?
42. YOU & ME FOR 5 YEARS?
43. DO YOU KNOW RUBY?
44. ENUMERABLE
45. .EACH .MAP .INJECT
47. ACTIVE::RECORD ASSOCIATIONS
48. HAS_MANY BELONGS_T0 HAS_MANY :THROUGH
49. ALGORITHMS
50. NOT ABOUT CORRECTNESS
51. SOLVE IT BRUTE FORCE
52. •Bottlenecks •Unnecessary work •Duplicated Work
53. KNOW
 HOW THE WEB WORKS
54. HARD
55. I HAVE NEVER THOUGHT ABOUT THIS
56. BUT I WOULD
 START WITH…
57. COULD WE
 PAIR ON A SOLUTION?
59. DO NOT
 SAY I COULD
 GOOGLE IT
60. ASK A QUESTION
61. THERE IS A
 PLACE FOR YOU
62. WE WANT TO
 HIRE YOU
63. @CMAR THANK YOU