Most 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…
Ask HN: How to prepare for a Front-end Developer interview?
111–120 of 146 posts
Re: Ask HN: How to prepare for a Front-end Developer interview?
#112Understand Big O notation [1] and how to use more technical JavaScript features like .map [2] and .reduce [3]. I get asked these frequently, and it was never mentioned to me when I asked for advice on how to prepare. This may be specific to senior developer positions. [1] https://en.wikipedia.org/wiki/Big_O [2] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... [3] https://developer.mozilla.org/en-US/doc…
Re: Ask HN: How to prepare for a Front-end Developer interview?
#113Most 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?
#114Generally, I start by getting an idea of how well a candidate understands JavaScript with a problem like this: Write a function that enables the following API... createOlympian() .name('Katie Ledecky') .sport('Swimming') .country('USA') .log() // Katie Ledecky, Swimming, USA Next, if things are going well, I have the candidate transform a JSON collection response to match some arbitrary requirements using Lodash/Unde…
Re: Ask HN: How to prepare for a Front-end Developer interview?
#115Earlier quoted context omitted.
Who vets those libraries? And who writes them in the first place?
People knowing about algorithm+implementation details? Definitely not front-end developers. (Not trying to implicate that front-end devs can't do it... you get the point)
Re: Ask HN: How to prepare for a Front-end Developer interview?
#116Earlier quoted context omitted.
Who vets those libraries? And who writes them in the first place?
Not sure I understand the question... are you suggesting the concept of using vetted libraries is somehow faulty? Anyway, the answer is generally "a large community" or "some big company like google or facebook."
Re: Ask HN: How to prepare for a Front-end Developer interview?
#117HTML, Android, iOS, UWP, WPF, UWP, Qt
General design questions how a specific design would be implemented using the stack best practices.
Things not according to your opinion should have been designed better.
How to create an UI component in a specific stack.
How to avoid freezing UI effects and the best practices to have a responsive (in speed) UI.
How to use the framework features to adapt to several screens.
In the specific case of HTML, some additional general questions about JavaScript, with the typical this trap.
Re: Ask HN: How to prepare for a Front-end Developer interview?
#118Most 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…
Honest question: People always joke about this, but is it really so widespread? I only had one job interview in my life until now, and that did not have any tech questions because my CV and open-source portfolio made it reasonably clear that I can, in fact, write working programs.
Most business do ask for technical questions, but more like how do the UML diagram of some architecture, how to write SQL queries, implement some code to make their unit tests green, describe what is virtual method dispatch and so on.
Re: Ask HN: How to prepare for a Front-end Developer interview?
#119Generally, I start by getting an idea of how well a candidate understands JavaScript with a problem like this: Write a function that enables the following API... createOlympian() .name('Katie Ledecky') .sport('Swimming') .country('USA') .log() // Katie Ledecky, Swimming, USA Next, if things are going well, I have the candidate transform a JSON collection response to match some arbitrary requirements using Lodash/Unde…
var createOlympian = function() { return (function() { var attrs = []; // private variable for our olympian attributes
var olympian = {
name: function(name){
attrs['name'] = name;
return this;
},
sport: function(sport) {
attrs['sport'] = sport;
return this;
},
country: function(country) {
attrs['country'] = country;
return this;
},
log: function() {
console.log(attrs['name'] + ", " + attrs['sport'] + "; " + attrs['country']);
}
};
return olympian;
})();
};Re: Ask HN: How to prepare for a Front-end Developer interview?
#120Most 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…
See the other side: a significant number of applicants can't implement fizzbuzz, Fibonacci sequences or anything, but ask for ridiculous salaries and their portfolios appear to be mostly borrowed plumes. We need a process that isn't too time-consuming to id the chaff, allowing for false negatives (people who are good at Fibonacci numbers and interview questions, but not much else), but keeping the false positives low (I explain the Fibonacci sequence first so it doesn't become a math riddle rather than a programming task).