4 ms·

That is fascinating. I wouldn't even show up for an interview if they told me to prepare for that kind of exam. What kinds of companies are these and where are

That is fascinating. I wouldn't even show up for an interview if they told me to prepare for that kind of exam. What kinds of companies are these and where are they located? Sounds like an interview designed by an omega nerd nightmare boss.

formulathree 3y ago
Have you been interviewing recently? The qualitative interviews that test design are actually the ones that are unreasonably challenging now. You have to cater to the interviewers design philosophy. For example I tend not to prefer putting data into a class if it's not needed, but we had one interviewer who wanted all my logic as methods on a class even though it's fine to have functions operating on a data structure. Not a big deal either way right? But there it is... With the influx of candidates they measure this bs.
WinLychee 3y ago
If you view the list here: https://leetcode.com/problemset/all/ https://leetcode.com/problemset/all/ you will see the questions tagged by company (there is a paid option as well). If they have a name you know, they probably do this style of interview.
- evantbyrne 3y ago
  I don't understand what I'm looking at. Who is tagging companies? Why would leetcode know the specific questions people are being asked to whiteboard?
  - jselysianeagle 3y ago
    People who interview at these companies report on their interview experience. It's true, these leetcode style questions do get asked and not just by the FAANG companies but lots of much smaller, no-name companies as well. Yes, you can certainly find companies out there that don't interview in this way, but leetcode interviews are extremely common.
    - evantbyrne 3y ago
      Strange. Not something I've seen, but I'm also very picky about the companies that I have applied to in the past–to the point of picking specific people I want to work with–and never ever go after mega orgs (I've contracted with some of them, and that's enough to know to stay away). Seems like a practice that would actually bias in favor of more junior developers, because of the emphasis on speed and familiarity to CS classwork. Obviously some programming jobs are heavy on algorithms, but that's neither the case for most roles nor what typically sets apart senior developers from juniors.

formulathree 3y ago

Have you been interviewing recently? The qualitative interviews that test design are actually the ones that are unreasonably challenging now. You have to cater to the interviewers design philosophy. For example I tend not to prefer putting data into a class if it's not needed, but we had one interviewer who wanted all my logic as methods on a class even though it's fine to have functions operating on a data structure. Not a big deal either way right? But there it is... With the influx of candidates they measure this bs.

WinLychee 3y ago

If you view the list here: https://leetcode.com/problemset/all/ https://leetcode.com/problemset/all/ you will see the questions tagged by company (there is a paid option as well). If they have a name you know, they probably do this style of interview.

evantbyrne 3y ago
I don't understand what I'm looking at. Who is tagging companies? Why would leetcode know the specific questions people are being asked to whiteboard?
- jselysianeagle 3y ago
  People who interview at these companies report on their interview experience. It's true, these leetcode style questions do get asked and not just by the FAANG companies but lots of much smaller, no-name companies as well. Yes, you can certainly find companies out there that don't interview in this way, but leetcode interviews are extremely common.
  - evantbyrne 3y ago
    Strange. Not something I've seen, but I'm also very picky about the companies that I have applied to in the past–to the point of picking specific people I want to work with–and never ever go after mega orgs (I've contracted with some of them, and that's enough to know to stay away). Seems like a practice that would actually bias in favor of more junior developers, because of the emphasis on speed and familiarity to CS classwork. Obviously some programming jobs are heavy on algorithms, but that's neither the case for most roles nor what typically sets apart senior developers from juniors.