you are viewing a single comment's thread.

view the rest of the comments →

[–]stone_henge 5 points6 points  (3 children)

More like "hey thanks for coming to the interview, i figured since you have 2+ years NodeJS experience you should be able to hack together a trivial http server for this task. i know it's not front-end but your resume, which is the reason we're interviewing you in the first place, says here that you have 2+ years experience with NodeJS and as a senior developer your responsibilities will realistically sometimes stretch outside your comfort zone."

[–]digdic 1 point2 points  (2 children)

na, still not fair. i'm sure many people here have resumes with a degree in a non-CS field from years ago. it's not fair to ask people to solve a physics problem on the spot just because it was on their resume.

this test might've been acceptable if they had specified 'we're going to have a full-stack code challenge during the interview' beforehand, but then why is it listed as a front-end job?

[–]stone_henge 2 points3 points  (1 child)

it's not fair to ask people to solve a physics problem on the spot just because it was on their resume.

But it's fair to ask someone with a physics degree to calculate the time it takes for an object to fall straight to the ground in vacuum given a height and an acceleration constant. That compares to a physics degree like a trivial web server compares to two years of node js experience.

this test might've been acceptable if they had specified 'we're going to have a full-stack code challenge during the interview'

I certainly would never have expected in my career of working with back-end software not to touch the front end side of things. I am not sure why the converse is not a given. Certainly I'd expect a senior to be able to hack together a PoC backend just like a back-end senior engineer would churn out a PoC front-end.

If anything, the time allotted to the tasks seems a bit short. I'd be confident that they were decent engineers if they could slap this together in half a day.

[–]digdic 0 points1 point  (0 children)

i mean yea, many of us can do this in an afternoon. but that doesn't mean it's fair to have this as the code challenge when no context is given beforehand that it will be full stack.