Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Front End Developer – Interview Questions

github.com

Post reply on HN
Print view View original

71–80 of 152 posts

Re: Front End Developer – Interview Questions

#71

Post by nkangoh »

EC1 wrote: post #60
cozuya wrote: post #41

Earlier quoted context omitted.

Without asking technical questions, how would an interviewer weed out the people who say the former but can't actually back it up? Because if the above is the entire hiring process, your junior developers aren't going to have to be concerned about their imposter syndromes, because they'll be working along side actual imposters.

Employment probation. We fired a few people right off the bat within 3 months because they very clearly bullshitted us. One guy fucking used notepad to code. I'm not joking.

What exactly is wrong with using notepad to code? No syntax highlighting?

Re: Front End Developer – Interview Questions

#72

Post by driverdan »

cozuya wrote: post #17
steakejjs wrote: post #4

This 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…

Call and apply are core concepts to writing good javascript. I would not hire someone (at least for any sort of senior role) that could not tell you exactly how both of them work. Many of the other things on this page are certainly "trivia" that could be addressed by google when they come up, but not those.

How often do you use call and apply? I've been a JS developer for a long time, have written a lot of JS code, and rarely need to use call and apply.

Unless you're writing all your code from scratch and not using any frameworks / util libs (which you should) you won't need them very often.

Re: Front End Developer – Interview Questions

#73

Post by thesimon »

cozuya wrote: post #41
forrestthewoods wrote: post #30

As an interviewee: "This is what I've in my career. If you'd like to give me money then I can do those things for you." As an interviewer: "Tell me what you've done in your career. We'd like to give you money to do those things for us." That's all I really want or need for either side of the table.

Without asking technical questions, how would an interviewer weed out the people who say the former but can't actually back it up? Because if the above is the entire hiring process, your junior developers aren't going to have to be concerned about their imposter syndromes, because they'll be working along side actual imposters.

A startup I worked for made the applicants do pair programming for two days. Needless to say, the people getting hired were very good.

Of course, if you are in a big company this is too much time and work (Recently had 6 interviews at big corps, not a single line of code written for a junior position)

Re: Front End Developer – Interview Questions

#74

Post by Daiz »

bbotond wrote: post #62
mkoryak wrote: post #5

I 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…

The only solution I could think of is this: function foo(n) { var result = []; for (var i = 0; i What are the two others?

You could use Function.prototype.bind in a couple ways, or even Array.prototype.map (though sadly you can't really do new Array(n).map, if that was true you could make this a one-liner).

    // new Array(n) could just be [] in all examples
    //
    // using Array.prototype.map
    // sadly you can't do new Array(n).map
    // because it doesn't iterate over undefined functions
    function foo(n) {
      for (var ret = new Array(n), i = 0; i

Re: Front End Developer – Interview Questions

#75

Post by jnbiche »

serve_yay wrote: post #64
bbotond wrote: post #62

Earlier quoted context omitted.

The only solution I could think of is this: function foo(n) { var result = []; for (var i = 0; i What are the two others?

That's using a closure, another would be to use Function.prototype.bind (but really that's still using a closure, just putting it out of sight), can't think of any others.

>Function.prototype.bind (but really that's still using a closure, just putting it out of sight),

How is `bind` still using a closure? `bind` just allows users to alter a function's execution context. However, the implementation varies according to the JS engine. Some of them may use a closure internally as a part of the process, but I don't think V8 does.

Re: Front End Developer – Interview Questions

#76

Post by shawndumas »

mkoryak wrote: post #5

I 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…

    var foo = function (len) {
      return Array(len)
        .join(0)
        .split(0)
        .map(function (e, i) {
          return function () {
            return i;
          };
        });
    };

Re: Front End Developer – Interview Questions

#77

Post by drinchev »

I know this repo. I've used it a lot of times while interviewing front-end developers.

I would give anyone using it a tip of advice :

Use this list not as a TOC or a check list. Use it to remind yourself what you could actually talk with the person that is applying for a job.

I usually start with the questions and present them not as a real question, but as a more of a "topic of conversation". Like for example :

Question => Transformed into topic

"Which version control systems are you familiar with?" => "Have you used VCS on your previous job? Which VCS is your favourite?"

"Name 3 ways to decrease page load (perceived or actual load time)." => "Have you ever tried to improve google page speed index or your page speed at all?"

Next I will ask in a similar ways questions about HTML, CSS and so on. I could go deeper if I see a person is interested in what we are talking about.

Anyway I've been interviewing more than 10 persons with this list in front of me. I highly recommend it as a base of your interview.

Re: Front End Developer – Interview Questions

#78

Post by frandroid »

danielweber wrote: post #70
EC1 wrote: post #60

Earlier quoted context omitted.

Employment probation. We fired a few people right off the bat within 3 months because they very clearly bullshitted us. One guy fucking used notepad to code. I'm not joking.

How do you get an employee to leave a permanent position for your temporary position?

Most full-time, permanent jobs have a 3 month probation period at the start of the contract where the employer can fire the new employee easily.

Re: Front End Developer – Interview Questions

#79

Post by danielweber »

frandroid wrote: post #78
danielweber wrote: post #70

Earlier quoted context omitted.

How do you get an employee to leave a permanent position for your temporary position?

Most full-time, permanent jobs have a 3 month probation period at the start of the contract where the employer can fire the new employee easily.

What's your source for "most"?

Also, why would I leave my job where I'm not on probation for a new job where I am on probation?

Re: Front End Developer – Interview Questions

#80

Post by tall »

I don't really care for this style of interviewing. A technique that really works is to take a problem the company is currently facing, slim it down and present it to the candidate pre-interview. Then when he comes in you ask him to explain his solution, and the choices he made.

It allows the candidate to be far more relaxed and puts him in a situation a lot more akin to the work that he will be doing for your company.

Post reply on HN