Front End Developer – Interview Questions
1–10 of 152 posts
Re: Front End Developer – Interview Questions
#2Not a bad list of questions. I think I will use some of these.
Re: Front End Developer – Interview Questions
#3Not a bad list of questions. I think I will use some of these.
just avoid the fizzbuzz questions, they aren't a good benchmark for good developers.
Re: Front End Developer – Interview Questions
#4This looks like a giant list of trivia that has almost no bearing on the day-to-day effectiveness of the candidate.
For example, I don't have the slightest clue what the answer is to probably half of these and a lot of my job is to write javascript that gets run millions to billions of times a day. The "code questions", by contrast, were all ridiculously easy.
So, would it really matter if you are hiring someone who doesn't remember the difference between .call and .apply off the top of their head?
Re: Front End Developer – Interview Questions
#5I really like this js question (whiteboarding):
Implement function foo which takes an integer size, and returns an array of that size where each element in that array is a function that returns the index of that function in the array. Testcase: 42 === foo(1000)[42]()
There are 3 different correct solutions. Discuss which solution is better, worse... etc (if they get there)
(could probably be worded better, I'm not an english major)
Re: Front End Developer – Interview Questions
#6Re: Front End Developer – Interview Questions
#7This has been around for a few years and it's due for some major updates. The CSS questions are becoming very, very dated.
> Have you played around with the new CSS Flexbox or Grid specs?
Flexbox is well past the point where you should be "playing around" with it. It's time to straight-up learn it, if not start using it in production. It's ready. And if that leads you to the question of "well what about crappy old versions of IE?", well there's another interview question for you.
Only one question about preprocessors—and a vague one at that? Not even a mention of things like Grunt and Gulp, pattern libraries, style guides, or even the terminal?
This stuff is integral, not optional, these days.
I interviewed a lot of people last year for a senior front-end position that we never ended up hiring for. We made a few offers that fell through but for the rest, I would have ended up teaching them how to do the bulk of the job had we hired them.
Re: Front End Developer – Interview Questions
#8Anyone else feel like there is a lot of esoteric information here? For instance:
> Are there any problems with serving pages as application/xhtml+xml?
I've never had to or considered serving pages as application/xhtml+xml, there's no reason for me to know the answer to this question and I've been working on the front end for ages. If I ever had reason to serve a page application/xhtml+xml I would thoroughly research it. Although I would say the JS questions look decent.
Re: Front End Developer – Interview Questions
#9This looks like a giant list of trivia that has almost no bearing on the day-to-day effectiveness of the candidate. For example, I don't have the slightest clue what the answer is to probably half of these and a lot of my job is to write javascript that gets run millions to billions of times a day. The "code questions", by contrast, were all ridiculously easy. So, would it really matter if you are hiring someone who…
I was thinking the same thing. I've built manys a website in pretty much every front-end language imaginable and I would struggle to answer many of these. Yet I feel little shame in saying that I believe myself to be a very competent programmer. What is the significance of having memorized a bunch of arbitrary terms? If you don't know what the difference is between and that doesn't mean you aren't a competent developer. It means you've never needed to know that to this point to successfully build a web app to meet a business need. If I'm hiring somebody I'm much more interested in whether they can actually build shit in a smart way when asked to do so, and with minimal guidance. We live in an age with ample internet access and a plethora of on-demand information resources. Why must we pretend that we don't?
As Colonel Frank Slade says in Scent of a Woman when asked by his nephew why he always gets his job title wrong- "Because it's not important for me to get it right."
Re: Front End Developer – Interview Questions
#10This has been around for a few years and it's due for some major updates. The CSS questions are becoming very, very dated. > Have you played around with the new CSS Flexbox or Grid specs? Flexbox is well past the point where you should be "playing around" with it. It's time to straight-up learn it, if not start using it in production. It's ready. And if that leads you to the question of "well what about crappy old ve…
>Flexbox is well past the point where you should be "playing around" with it. It's time to straight-up learn it, if not start using it in production.
I dont think that is 100% true quite yet. IE9 for example is still quite popular, not to mention the bugs in modern browsers.
http://philipwalton.com/articles/normalizing-cross-browser-f...