Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

What I learned interviewing for front-end developer roles


Published on

Tips to improve you as a developer and a person.

Published in: Technology
  • Hello! Get Your Professional Job-Winning Resume Here - Check our website!
    Are you sure you want to  Yes  No
    Your message goes here

What I learned interviewing for front-end developer roles

  1. 1. @jcemer what I learned interviewing for front-end developer roles
  2. 2. http:// @jcemer
  3. 3. but wait! 
 which companies have you had interviews with?
  4. 4. facebook, work&co, uber, klarna, catawiki, thoughtworks, toptal, codeminer,, 
 stickermule, toggl,…
  5. 5. http://
 crackingthecoding a behind the scenes look at how google and facebook hire developers.
  6. 6. this is not just about interviews. it has tips to improve you as a developer and a person.
  7. 7. 1. algorithms and logic
  8. 8. https:// courses/
  9. 9. https://
  10. 10. https:// domains/tutorials/ cracking-the-coding- interview
  11. 11. https://
  12. 12. Big O Notation in JavaScript big-o-notation-javascript-25c79f50b19b
  13. 13. O(n)
  14. 14. O(n^2)
  15. 15.
  16. 16. Array sorting
  17. 17. 2. javascript 
  18. 18. function methods: the difference between, fn.apply, and fn.bind.
  19. 19. inheritance: how the Constructor.prototype and Object.create work.
  20. 20. vectors: arr.slice or arr.splice?
  21. 21. memorize some code snippets
  22. 22. clojures: how to code a function with the signature add(x)(y).
  23. 23. math: return the time overlap between flights with given departure and arrival times.
  24. 24. you don’t need to memorize this
  25. 25. 3. layout
  26. 26. left and right float things on the screen will never go out 
 of style.
  27. 27. flexbox is the new kid on the block.
  28. 28. it is good to know how to properly style a dropdown menu or a colored table.
  29. 29. mind the tradeoffs of using canvas 
 or svg.
  30. 30. 4. technology
  31. 31. https://
  32. 32. learn the basics of http, dns, ip, git, command line.
  33. 33. understand the concepts behind 
 the most popular frameworks and libs.
  34. 34. 5. kind of
  35. 35. https:// v=N233T0epWTs
  36. 36. don’t be afraid of the white board, or skip it.
  37. 37. https://
 hiring-without- whiteboards
  38. 38. in coding interviews it’s better to explain your decisions before writing 
 it out.
  39. 39. don’t keep your assumptions to yourself. say them out loud.
  40. 40. be ready to talk about what you learned from related previous companies 
 and projects.
  41. 41. improve your teaching skills. 
 the interviewer should learn from you.
  42. 42. Juarez da Silva Bochi
 Software Engineer at The New York Times “don't pretend to know what you 
 do not. what you know should be enough. ask questions.”
  43. 43. 6. companies 
 and jobs
  44. 44. Rafael Silva
 Full-stack developer at @gofooji “in most cases companies are hiring you to help them to grow a business so learn everything that you can about it”
  45. 45. small or 
 big company.
  46. 46. startup or 
 agency or software house or
 mature company.
  47. 47. feeling or data driven.
  48. 48. remote or face-to-face work.
  49. 49. Rafael Silva
 Full-stack developer at @gofooji “read articles and tweets from people that work there, search for the company on Glassdoor.”
  50. 50. use the interviews to understand if 
 that company is a good fit for you.
  51. 51. cultural fit
  52. 52. 7. the reject
  53. 53. Christoph Nakazawa
 Engineering Manager at Facebook “don't give up! also interview with other companies and get a lot of interview experience.”
  54. 54. ask for feedback and evaluate it slowly: be mindful.
  55. 55. “it’s just a job” better to focus on your happiness.
  56. 56. last but not least…
  57. 57. https:// Mongrel_complex
  58. 58. brazilian devs rock!
  59. 59. we rock!
  60. 60. @jcemer thank 
 you. I hope you 
 had fun!