📜 ⬆️ ⬇️

Interview eyes interviewee


I jot out a few thoughts on how I see the right job interview for software developer.


At the interview the employer must offer the candidate a cup of coffee / tea. It is necessary! And you need to start with this. Coffee has to talk. The candidate feels more comfortable, the brain begins to work better. For one cup, you can offer another, third, depending on how the conversation goes. Surprisingly, due to the underdevelopment of the culture of the interview, the employer ignores this elementary action ... I’m not talking about what would ideally be like to have a glass of wine. =). And further, respectively, how it goes). Thus, from a boring routine, we turn the process into an exciting action. This is the first scenario.

  • Do not need a candidate to blow the brain with cunning puzzles. At the interview, his brain is vulnerable and frankly sucked from the finger of the task only harm.
  • Idiotic questions, such as what a stack is, how many bits are in a byte, marasmic - can you write a demon under Linux - keep it for yourself. This may offend the candidate.
  • If this is a C + + vacancy - leave all the spruce plus with you. You spoil the impression about the office by asking whether you can call a purely virtual function and saying that this happens with us often, various warning asserts pop up.
  • All questions on COM - keep to yourself. You are outdated. The candidate will be uncomfortable to realize this.
  • Hardcore things like how to know if a number is a power of two for O (1) is certainly cool, but who is able to immediately, not knowing, to have a solution? Why ask it?

Ok, what then to ask? Elementary. No blanks, test tasks, tasks on paper for the allotted time. You need to ask about what the candidate has done in previous work. Specifically. No abstract tasks for finding a path (although you can =), but simply, close to reality, what and how and why they did it.

Create a context and be inside that context. It's complicated? Not. So why only a few understand this? (one! =).
')
And only on the basis of the prerequisites - the work done by the candidate - you can ask things connected on the subject.

Something like this. Inspired by).

Your job as an employer is to find and understand what the candidate is interested in. Is it interesting to you? And look at whether your interests intersect, in what areas and to what extent.

Source: https://habr.com/ru/post/285316/


All Articles