[jxcole]

I've been to a lot of interviews and this seems like terrible advice. Besides a few behavioral questions the vast majority of interviews are algorithm and data structures questions. Memorizing a bunch of obscure, unpopular object oriented jargon seems like a waste of time. Is this a php thing?

[jordanab]

To be fair stuff like Design Patterns, SOLID, Domain-Driven Design etc. come up in a lot of interviews for "business application development" roles in other languages as well, especially C# and Java. What's ironic is that often on your first day on the job, you'll be put to work on a codebase which violates those principles in a lot of ways.

[that_guy_iain]

> To be fair stuff like Design Patterns, SOLID, Domain-Driven Design etc. come up in a lot of interviews for "business application development" roles in other languages as well, especially C# and Java.

Yea. I think there are basically two style of techincal interviews. One is FAANG where they ask you university level stuff. And the other is they ask you a bunch of stuff that they want to have implemented but haven't.

I think it's also why there is a massive culture difference in say Agile in FAANG and everywhere else. FAANG has people that don't know these things as well because to get their jobs they had to learn and study univeristiy level problems.

I think a lot of FAANG devs would get blown out of the water at some mid-level companies. FAANG has the reputation but the reputation is built on a very small subset of their actual engineers.

[the_only_law]

> Is this a php thing?

More like a certain subset of company. I've seen this sort of "trivia/jargon" interview primarily at non-tech or non-tech adjacent companies. think like F500's far away from the tech industry.