Divination by code at the interview. How are candidates screened?

Question

Programming

Quite common in job interviews: send or show sample code... Mmm... That you're "proud" of or like.
This moment should kind of tell a lot about the specialist, and also say a lot about the company. But what exactly does he say?
What are recruiters trying to check in this case? Check the level of knowledge or the degree of sophistication in the construction and naming of classes? Benefit, dedication of a person to a profession? Or is it only about the desire of developers to find ideal solutions despite the functionality of the product?
And what would you send if you were asked to send such an example?

Answer 1

I would show Bogosort https://ru.wikipedia.org/wiki/Bogosort - a very interesting algorithm.

Answer 2

I have always considered such a requirement to be idiotic. What can be understood from a small piece of code? Never mind!
It would be nice to be asked to send the entire source code, or a large solid module, but after all, they usually ask to send the "most elegant class" or similar nonsense. You won’t see architecture from it, the ability to solve complex problems, too. Is it possible to look at the code style and reveal a completely Hindu shit code, but this is also nonsense.

Answer 3

They check for shit, check thinking, check knowledge of the language, the level of perfectionism, etc.
As a java programmer, they checked me for all sorts of crap like knowledge and use of OOP, whether I use certain features and why, how I optimize the code, whether there is noodles, whether the JCC code and other bullshit comply.
Often they don’t check shit, they just require a code because an acquaintance of Ichar said that it’s so fashionable now.
When I was asked to send code or give a link to github, I sent spherical code in a vacuum. As a rule, it did not affect anything, a kind of fashionable ritual.

Answer 4

Some companies require you to send code from an open source project in which you participated. The company believes that if you do not spend time developing free projects, then you are a bad programmer. In my personal opinion, a crazy criterion.

Answer 5

What are recruiters trying to check in this case?

Yes, they do not try to check anything ... except perhaps the hardness of the candidate's memory for knowledge of all language specification tasks.
In fact, this is one of the most idiotic requirements in the selection of candidates.

Answer 6

The requirement to show the code or the github profile with the code has become standard.
Recruiters themselves only check whether you have a code or not, and pass the links to the client / PM / team leader. And those look at their purely subjective opinion, how high quality it is, and it will be convenient for them to work. At the same time, if a future employee wants to first study the project code (so as not to run into something inadequate), they can safely refuse him.
As for the code that you are "proud of" - this is generally HR nonsense, in my opinion, from the category of "who you will be in 5 years", "would you shake hands with Lenin" ...

Answer 7

It's all nonsense in essence. Normally name the main variables and functions with classes, i.e. so that there is not one letter, but a normal word that expresses the essence of what is happening - that's all.
Those. instead of

a = 170
b = 70 
c = a*b

need something like

height = 170 
mass = 70 
mass_coefficient = height*mass

It’s easier to understand each other this way, because it’s quite difficult to understand what variables from the same letter do with each other.