"Write a function that reverses letter order of words in a string.".split('').reverse().join('').split(' ').reverse().join(' ');
cant read code tho, ill show myself out.
In all seriousness, I like the idea. No one seems to know how to get interviews right. I kinda liked giving the applicant a real task but on second thought reading existing code might be the realest task on a new job.
> No one seems to know how to get interviews right.
Plenty of people do, but good interview processes are highly context-dependent and not trivially transferable.
And most companies just cargo-cult something associated with a name brand, then tweak it to something they're personally comfortable conducting.
I'll quote myself from an old comment:
> Every time one of these interviewing posts bubbles up I skim it to see if the author mentions things like: company size, team composition, the nature of the work the team is doing, the nature of the industry the company exists in, the way hiring decisions are made, the desired properties of their hiring process, their offer rate, acceptance rate, turnover rate, the amount of time positions tend to stay open for, or really just anything that would offer some context on what, specifically, their interview process is optimized for or achieving.
> Nine times out of ten that stuff is absent and the post is just a bunch of opinion and conjecture.
I had an interview with LINE that I really enjoyed. I prefer take home assignments, but their homework wasn't to code, it was an intentionally bad project. You could fix the problems and they would review your code or you could just state your findings.
I feel like it was the best of both styles of interviewing. People who hate in interviewing whiteboarding can show their skills on their own time, but if you're optimizing for packing in as many interviews in as possible you haven't written any unnecessary code.
>Write a function that reverses letter order of words in a string.".split('').reverse().join('').split(' ').reverse().join(' ');
Oooo. Sorry. Hard pass. Those symbols are redefined as something else in the context in question.
I don't give a shit if you can write in your favorite lang. I give a shit you can mentally my context and ask the right questions to get productive quickly, or build up your own from scratch while trying to mesh with something already there.
cant read code tho, ill show myself out.
In all seriousness, I like the idea. No one seems to know how to get interviews right. I kinda liked giving the applicant a real task but on second thought reading existing code might be the realest task on a new job.