This document summarizes tips and advice for front-end developer interviews. It covers 7 key areas: 1) algorithms and data structures, 2) JavaScript language skills, 3) layout and styling, 4) technologies, 5) types of interviews, 6) considering different companies and jobs, and 7) dealing with rejections. The document provides specific resources on each topic like websites, courses, code snippets, and advice from other engineers on how to prepare for and succeed in interviews.

1. @jcemer
what I
learned
interviewing
for front-end
developer roles

2. http://
jcemer.com
@jcemer

5. but wait!
which companies
have you had
interviews with?

6. facebook, work&co,
uber, klarna, catawiki,
thoughtworks, toptal,
codeminer, globo.com,
stickermule, toggl,
booking.com…

7. http://
crackingthecoding
interview.com/
a behind the
scenes look at
how google and
facebook hire
developers.

8. this is not just about
interviews. it has
tips to improve you
as a developer and
a person.

9. 1. algorithms
and logic

10. https://
hiredintech.com/
courses/
algorithm-design/

11. https://
projecteuler.net/
archives

12. https://
hackerrank.com/
domains/tutorials/
cracking-the-coding-
interview

13. https://
123test.com/
logical-reasoning-test/

14. Big O Notation
in JavaScript
https://medium.com/cesars-tech-insights/
big-o-notation-javascript-25c79f50b19b

15. O(n)

16. O(n^2)

17. http://bigocheatsheet.com/

18. Array sorting

19. 2. javascript
language

20. function methods:
the difference
between fn.call,
fn.apply, and fn.bind.

21. inheritance: how the
Constructor.prototype
and Object.create
work.

22. vectors:
arr.slice or
arr.splice?

23. memorize some
code snippets

24. clojures: how to
code a function
with the signature
add(x)(y).

25. math: return the
time overlap
between flights with
given departure and
arrival times.

26. you don’t need
to memorize this

27. 3. layout

28. left and right float
things on the screen
will never go out
of style.

29. flexbox is the new
kid on the block.

30. it is good to know
how to properly
style a dropdown
menu or a colored
table.

31. mind the tradeoffs
of using canvas
or svg.

32. 4. technology

33. https://
github.com/
alex/
what-happens-when/

34. learn the basics of
http, dns, ip, git,
command line.

35. understand the
concepts behind
the most popular
frameworks and libs.

36. 5. kind of
interviews

37. https://
youtube.com/watch?
v=N233T0epWTs

40. don’t be afraid of
the white board,
or skip it.

41. https://
github.com/
poteto/
hiring-without-
whiteboards

42. in coding interviews
it’s better to explain
your decisions
before writing
it out.

43. don’t keep your
assumptions to
yourself. say
them out loud.

44. be ready to talk
about what you
learned from related
previous companies
and projects.

45. improve your
teaching skills.
the interviewer
should learn
from you.

46. 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.”

47. 6. companies
and jobs

48. 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”

49. small or
big company.

50. startup or
agency or
software house or
mature company.

51. feeling or
data driven.

52. remote or
face-to-face
work.

53. Rafael Silva
Full-stack
developer at
@gofooji
“read articles and
tweets from
people that work
there, search for
the company on
Glassdoor.”

54. use the interviews
to understand if
that company is a
good fit for you.

55. cultural fit

56. 7. the reject

58. Christoph
Nakazawa
Engineering
Manager at
Facebook
“don't give up!
also interview with
other companies
and get a lot of
interview
experience.”

59. ask for feedback
and evaluate it
slowly: be mindful.

60. “it’s just a job”
better to focus on
your happiness.

61. last but not
least…

62. https://
en.wikipedia.org/wiki/
Mongrel_complex

63. brazilian
devs rock!

64. we
rock!

65. @jcemer
thank
you.
I hope you
had fun!