Most unexpected interview questions?

Question

PHP

Probably boiled up. I recently had several interviews.
This time, one question is more sophisticated than the other.
One requires you to name all the tables when generating an RBAC model in yii2 (I didn’t name everything, because for the last 4 months I have been working on projects that are simple in this direction and this model is not needed there. Well, I don’t remember right away).
Today, the question is completely out of my mind. It was necessary to define the programming paradigm and name all directions.
I asked a programming teacher from a friend, she replied that this is not an easy question and it does not come up so often at the university.
In short, after such questions, I did not see the point of working in this office. This is not Google or Yandex to really sit and cram.
Or maybe I don’t understand something and new trends have gone? And like you need to sit down and re-learn all the basics of programming? (I have not sat at a desk for 8 years).
And it was a middle interview.
And they didn’t care that I have a code on github and that I use some kind of technology there. We are talking purely theoretically.
By the way, there was no story about themselves and what they do there. Or maybe they did not suit me according to their projects. Because there was such a case. Passed at the beginning of those. interview, and then they began to talk about what they would have to do, but such work did not suit me.
I'm very interested in what other questions I get in interviews?
PS About OOP and patterns it's all set.

Answer 1

It was necessary to define the programming paradigm and name all directions.

I would also set the definition of the word abstraction
people really lost from simple definitions ... no one forces you to give an exact definition, but you can do it in your own words ... there is a head, connect your thoughts and voice,
please give a definition - a primitive way to identify the ability to express thought/thinking

Answer 2

You need to be able to conduct an interview, this is not such an easy thing as it seems. You were most likely interviewed by a purely techie, in such cases, often the interview rolls into an exam on his favorite toys. If you have a great eye, then there is no chance, all alternatives and suggestions will be ignored, and he will continue to load with what he prays for. There are no interviews at such "interviews", they will not listen to you and will not tell you anything, their time is too expensive, and you are just an applicant who claims to play in their sandbox.
The ideal option is a techie-manager, a person who understands the technical part, but at the same time knows how to communicate with people (this is not easy, the techie from 1 paragraph also thinks he can). Thanks to this skill, he will not consider himself a god and will be able to look at the issue from the outside, or even admit that there are different solutions.
Another option is a purely manager. But it's more when you apply for a managerial or part-management position. Here the spread is very wide, the saddest option is when the manager considers himself a techie, then problems from 1 paragraph are still layered on top. Basically, these are quite normal interviews, but there may be many questions "for life". There are also peculiar ones, so there is a technique of "aggressive interview" - the interviewer is late for 10-15 minutes (this should make the candidate nervous), then without any conversation he falls asleep with questions, in every possible way showing that this candidate is interested, not they. Sometimes it can work, but when this is used in IT, the candidate gets the feeling that he was talking to an incompetent cattle. Although all this is just what I saw.
It seems to me that if a person is really needed, then they will take him. But not all interviewing companies actually recruit people.

Answer 3

Or maybe I don’t understand something and new trends have gone? And like you need to sit down and re-learn all the basics of programming?

The basics of software development and computer science need to be understood, as well as PC architecture, operating systems, networks, basic programming paradigms, algorithms, and the like. It's just basic knowledge. Depending on the specialization, it is necessary to understand the above at a different level.
Regarding new trends, a programmer studies all his life ... Or he sits in some research institute, state. enterprise, another web studio that rivets the same type of craft sites, etc. and only called a programmer. Those. it’s not possible to do interesting things and get relatively a lot of money, but at the same time not constantly improve yourself.
And yes, you need to prepare for interviews. The fact that you have 5-7-10-15 years of formal experience does not mean anything at all. Only knowledge, skills, and the level of tasks to be solved / the ability to solve problems of a certain level play a role here.
This is a very vague question. Anything from what I wrote in the first paragraph + specific knowledge, for example, on the specialized technology stack that you own. Often social skills are also tested, but this is mainly at positions above the middle.

Answer 4

Often they want to hear at least something coherent, if not an exact answer to such questions. To understand that a person can communicate coherently and logically (which is useful when communicating with colleagues at work, not only code is supposed to be written)

Answer 5

How to enter the house