4 ms·

I recently learned that job interviews are great at showing what’s wrong with the company you are applying for. For instance, I recently had an interview where

I recently learned that job interviews are great at showing what’s wrong with the company you are applying for. For instance, I recently had an interview where I got hammered with questions regarding design patterns. My daily work doesn’t consist of figuring out why I should prefer the Observer pattern or Mediator pattern over one another. As such, I failed to give a satisfying answer in 2 minutes. How it would normally work for me: I see that I would need to apply one or the other, and would start researching the pros and cons. I've used both of them. This is a substantial decision, and as such needs some time and thoughts. Or maybe I'm the fool and I’m just "doing it wrong".

dmichulke 4y ago
Sounds like they're filtering out functional programmers. Bold move.
- boywitharupee 4y ago
  Is it assumed that these engineers lack knowledge of design patterns? Can you clarify the definition of function programmers here.
lonelyasacloud 4y ago
Fwiw, I've asked candidates seemingly meaningless questions that don't directly relate to the day-to-day activities of the job. The questions - and how a candidate responds - can be helpful to both sides (as observed) wrt figuring out how individuals might fit into the prospective organisations. For instance, from the employer's pov, if the organisation is already filled with academic Computer Scientists, and the interviewee comes across as dismissive of the importance of design patterns, it's a red flag about fitting in. However, if they go over the top the other way, then that might be a red flag about how practical they might be. If they don't know where to start with the question or are perhaps tongue-tied, then that's also information. While from the interviewee's pov, if they prefer a more practical environment, then those questions may be, as observed, a red flag about a role that wouldn't be a good fit for the candidate. A good interview process maximises the flow of information in both directions in a short space of time and increases the chances of a good fit. It's a process to which these type of questions can be helpful when properly applied.
- nemetroid 4y ago
  This isn't central to the point you're making, but I would place design pattern knowledge squarely in the realm of software engineering and not computer science.
- gardenhedge 4y ago
  How do you know you're doing a "good interview process"?
  - lonelyasacloud 4y ago
    > How do you know you're doing a "good interview process"? Monitor in some way, shape or form how often the process ends with happy, productive teams and thriving new hires that stay with the organisation for a decent amount of time beyond the point where they become productive. Seek to get better.

dmichulke 4y ago

Sounds like they're filtering out functional programmers. Bold move.

boywitharupee 4y ago
Is it assumed that these engineers lack knowledge of design patterns? Can you clarify the definition of function programmers here.

lonelyasacloud 4y ago

Fwiw, I've asked candidates seemingly meaningless questions that don't directly relate to the day-to-day activities of the job. The questions - and how a candidate responds - can be helpful to both sides (as observed) wrt figuring out how individuals might fit into the prospective organisations. For instance, from the employer's pov, if the organisation is already filled with academic Computer Scientists, and the interviewee comes across as dismissive of the importance of design patterns, it's a red flag about fitting in. However, if they go over the top the other way, then that might be a red flag about how practical they might be. If they don't know where to start with the question or are perhaps tongue-tied, then that's also information. While from the interviewee's pov, if they prefer a more practical environment, then those questions may be, as observed, a red flag about a role that wouldn't be a good fit for the candidate. A good interview process maximises the flow of information in both directions in a short space of time and increases the chances of a good fit. It's a process to which these type of questions can be helpful when properly applied.

nemetroid 4y ago
This isn't central to the point you're making, but I would place design pattern knowledge squarely in the realm of software engineering and not computer science.
gardenhedge 4y ago
How do you know you're doing a "good interview process"?
- lonelyasacloud 4y ago
  > How do you know you're doing a "good interview process"? Monitor in some way, shape or form how often the process ends with happy, productive teams and thriving new hires that stay with the organisation for a decent amount of time beyond the point where they become productive. Seek to get better.