If the anecdotes I read here are correct, you should be prepared to implement a red-black tree in C, followed by an A* pathfinding algorithm on the whiteboard. I think the best preparation you can do is to spend several hours reviewing your old projects. For each project, recall and be prepared to explain in depth: - The biggest technical challenge you faced and how your team solved it - The technical tradeoffs your…
Asking a front-end developer to write a red-black tree is insane. Is anyone actually doing that?
Ask HN: How to prepare for a Front-end Developer interview?
11–20 of 146 posts
Re: Ask HN: How to prepare for a Front-end Developer interview?
#12You should at least be familiar with the major front-end libraries and frameworks - React, Angular and Ember. You don't necessarily need to "know" them, but at least know about them. You should be familiar with what ES6 is and what Babel does. These technologies probably won't be specific questions per se but if they come up and you can't speak about them, it'd be a red flag. Even for a front-end developer you should…
I would never care about these if I was specifically hiring a front-end dev. I've never once seen any of them come up in the context of front-end work in my entire career. And in fact an interviewer asking questions about them would be a huge red flag for someone who prioritizes nerd-cred over actual business needs, and is therefore likely to make poor decisions.
Re: Ask HN: How to prepare for a Front-end Developer interview?
#13Re: Ask HN: How to prepare for a Front-end Developer interview?
#14If the anecdotes I read here are correct, you should be prepared to implement a red-black tree in C, followed by an A* pathfinding algorithm on the whiteboard. I think the best preparation you can do is to spend several hours reviewing your old projects. For each project, recall and be prepared to explain in depth: - The biggest technical challenge you faced and how your team solved it - The technical tradeoffs your…
I don't know about that, but you should at least know the algorithms necessary to traverse the DOM.
Re: Ask HN: How to prepare for a Front-end Developer interview?
#15You should at least be familiar with the major front-end libraries and frameworks - React, Angular and Ember. You don't necessarily need to "know" them, but at least know about them. You should be familiar with what ES6 is and what Babel does. These technologies probably won't be specific questions per se but if they come up and you can't speak about them, it'd be a red flag. Even for a front-end developer you should…
Re: Ask HN: How to prepare for a Front-end Developer interview?
#16Re: Ask HN: How to prepare for a Front-end Developer interview?
#17Re: Ask HN: How to prepare for a Front-end Developer interview?
#18Re: Ask HN: How to prepare for a Front-end Developer interview?
#19You should at least be familiar with the major front-end libraries and frameworks - React, Angular and Ember. You don't necessarily need to "know" them, but at least know about them. You should be familiar with what ES6 is and what Babel does. These technologies probably won't be specific questions per se but if they come up and you can't speak about them, it'd be a red flag. Even for a front-end developer you should…
> Even for a front-end developer you should have a basic knowledge of data structures like linked lists, binary trees, min/max heaps, depth/breadth first search, tries, recursion, hash tables, etc. I would never care about these if I was specifically hiring a front-end dev. I've never once seen any of them come up in the context of front-end work in my entire career. And in fact an interviewer asking questions about…
Re: Ask HN: How to prepare for a Front-end Developer interview?
#20Having gone through this situation before, my biggest mistake while performing this type of interview was not actually having candidates build something with the team. Frontend development is usually very visual and UX-oriented, so it's important to see what they can build and their attention to that type of detail. There's plenty of knowledge questions that can filter candidates down by experience, but until you get…
To add to your answer, having them build a clone of a simple game in 1-3 hours, especially when they have to balance a bare bones look with more features versus a slicker look with fewer features, and deciding which to cut and what's important to them and how they think about it -- all that can be revealing.