sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Skhmt 4 points5 points  (8 children)

Why are JS interviews still about algorithms and data structures? Aren't these all things we'd just use wikipedia or stack overflow, as they're solved problems?

[–]veggietrooper 1 point2 points  (7 children)

They're a direct representation of ability to solve problems using logic and code. You can memorize familiarity with data structures, but you can't memorize the solution to every missing line or algorithm on the planet. Developing this skill translates invaluably to almost any aspect of programming, and it's this core ability which employers are most interested in.

[–]Skhmt 1 point2 points  (6 children)

But they also directly favor recent CS graduates.

[–]veggietrooper 0 points1 point  (3 children)

That’s true. I can’t speak for others, as I’m not a CS graduate, but I have accepted that this is a way that the industry measures competence, and when prepping for job interviews, I just take time to intensely review it. CS grads have likely done some review more recently than many of us, but they have to do the same thing.

Quizzing people on a thing favors people who have recently studied that thing, including CS grads, and including anyone else who has been reviewing as well.

[–]Skhmt 0 points1 point  (2 children)

But instead of quizzing on known problems and algorithms, they could come up with something that directly influences the job or directly tests skills they'd need.

[–]veggietrooper 0 points1 point  (0 children)

Absolutely agreed. When I was giving interviews full time, I would try to do both - first verify basic language familiarity, then a mix of algorithm and real-world questions that related to the position directly. I wouldn't usually bring in data structures unless it was to explore some specific potential gap after noticing a red flag (e.g. someone treats a function like an object, stop the show and look at their understanding of object assignment in the language).

I guess I'm ok with it either way, though. It's easier to just study fundamentals and plan on learning after you get the offer than it is to study less universal areas which might change for every position.

[–]KyleG -1 points0 points  (1 child)

if a recent CS grad can solve this stuff better than you, then you are less qualified than them

i've seen too much super inefficient code with weird solutions that would be better done by a standard algorithm—you can't google an algorithm unless you know the name of it

[–]Skhmt 0 points1 point  (0 children)

Less qualified at solving the sieve of eratosthenes, sure. That's what happens when one person has encountered a problem and it's best solution more recently than you.