Here are a few questions/problems I was asked in from-end interviews a couple months ago: Write a function that accepts an array of ints and a target number. If two of the numbers in the array can add up to the target, return their indices. (aka Two Sum) Write a function that accepts an int x and prints a spiral of "#"s so that the number of "arms" in the spiral equals x. Write a function that accepts a month and a y…
>>The good interviewers, IMO, gave me a "take-home" problem of building some mini front-end app that hit an API, and the really fun one involved reverse engineering an unpublished API - that's how I got my current job. I agree with you, but whenever this subject comes up, a lot of folks here on HN complain that they have full-time jobs and families and don't have time for "take-home" questions.
Ask HN: How to prepare for a Front-end Developer interview?
131–140 of 146 posts
Re: Ask HN: How to prepare for a Front-end Developer interview?
#132Earlier quoted context omitted.
I might have experience but that still looks totally trivial for me... is many people not passing the first test?
It's not meant to be difficult. You'd be surprised how many people don't pass this. The most important part of the interview for me is when we advance to talking about what a candidate has actually done.
Re: Ask HN: How to prepare for a Front-end Developer interview?
#133Earlier quoted context omitted.
Try writing the same thing without a computer why don't ya. As an interviewer I can see why you would want to force someone to jump through arbitrary hoops like that but if someone can show me `() => i` and explain why that works, that would be good enough for me.
No need for the snark. There is still way more ES5 code being written than ES6. The point is demonstrating knowledge of closures and variable lifecycle, the how is irrelevant. I replied specifically because he said "I don't see the problem" - if you start with ES6 I can imagine it doesn't look like a problem at all.
In fact I would argue it's important that if the candidate shows practical knowledge of ES6 you need to make sure they also grasp the actual semantics (i.e. they won't rely on implementation details of Babel and run into errors in native ES6 environments).
That said, if you are hiring for a dedicated frontend developer role, the majority of JS you write will have a build step. If it has a build step, you should use modern tooling. If you use modern tooling, you might as well include Babel to make the developers' lives less of a pain.
Re: Ask HN: How to prepare for a Front-end Developer interview?
#134Earlier quoted context omitted.
This is why SV needs to stop abusing the term "engineer" - because this is indeed work that can be done on the front end, but under no circumstances should you expect front end developers to know how to do this. If you have a specific need, or you're building something very complex, then you probably want an engineer -- most companies (including any of the big ones) typically only need developers. It's good to have e…
Right or you could have a "developer" tinker with stuff and that's how wind up with things like redux
Re: Ask HN: How to prepare for a Front-end Developer interview?
#135Most modern production quality software systems there days are implementing fibonacci algorithms as part of their core business rules, controlled via a red/black tree. Usually it's held together by a fizzbuzz architecture so as a minimum you should be able to whiteboard fizzbuzz. You should understand all these things well, and really if you are doing modern software development these things hould be day to day tasks…
Re: Ask HN: How to prepare for a Front-end Developer interview?
#136Oh yeah, I also ask them to talk about how to make an interface feel responsive even though most actions can trigger a network call that may take several seconds to respond.
Re: Ask HN: How to prepare for a Front-end Developer interview?
#137Earlier quoted context omitted.
It's not meant to be difficult. You'd be surprised how many people don't pass this. The most important part of the interview for me is when we advance to talking about what a candidate has actually done.
That's my point, I've read many times that I'd be surprised how many times people don't pass this (and I agree) but I'd love to know how many. Could you share please?
Re: Ask HN: How to prepare for a Front-end Developer interview?
#138Closures, specificity, home made getElementsBySelector, DOM traversal stuff, weird IE things, coding standards, an understanding of how jquery works, how to protect against npm poisoning/leftpad issues, lodash, semantic naming strategies, being opinionated (why is BEM shit/great?), box model, floats, flex box, centering techniques, an understanding of how plane old js works, cross origin/same origin stuff, basic desi…
For example, in a recent string of interviewing here for a couple of large SF-based companies and startups, I've encountered questions like re-implementing jQuery, doing the JS for the game Snake, palindrome checkers, longest chain of ascending numbers in an array, shortest path, matching node (given a node in one tree, find the same node in an identical tree), and basically a whole bunch of other questions where only JS skill were assessed.
Re: Ask HN: How to prepare for a Front-end Developer interview?
#139Closures, specificity, home made getElementsBySelector, DOM traversal stuff, weird IE things, coding standards, an understanding of how jquery works, how to protect against npm poisoning/leftpad issues, lodash, semantic naming strategies, being opinionated (why is BEM shit/great?), box model, floats, flex box, centering techniques, an understanding of how plane old js works, cross origin/same origin stuff, basic desi…
A couple of years ago, I would have answered the same way. Now, at least in the SF Valley area, these types of things are largely ignored and instead we're asking a lot more CS questions (algorithms, data structures, design patterns, etc). In fact, I'd say about 99% of interviews for a front-end position don't ask ANY CSS questions at all - they're all JS-based. For example, in a recent string of interviewing here fo…
Re: Ask HN: How to prepare for a Front-end Developer interview?
#140Earlier quoted context omitted.
I agree that it's far from what is needed in everyday tasks, but in defense of that process: if you are unable to implement fizzbuzz, Fibonacci numbers, etc., I am almost sure you can't understand react sagas or dependency injection properly. Mixed with more open-ended questions (why was React built? how does it compare to Angular? What's a generator function?), I believe this isn't the worst type of interview. See t…
> their portfolios appear to be mostly borrowed plumes. I don't understand this phrase. What do you mean by borrowed plumes?
edit: this is my best-fit guess. I have no idea what I'm talking about.