Some notes to my personal experience in interviewing processes and how it should be like

I must to say directly that I really doesn't like a toxic interviewing processes, that are really stressful, especially such technical interviews, with online coding and stupid obvious questions ("what's the difference between abstract class and interface?") or otherwise with really advanced questions ("show me in code how we could optimize and which optimizing strategies we could use for upward and downward funarg problem in cactus-stack, which consist of call-stacks, for storing the context of suspended stackful coroutines? could you please show me your abilities and write a "simple" state machine (state automata) right here and right now for stackful coroutines suspension?" - and this ones is a real example of questions for Rust, C++ and Go interviews in which I had experience of participation!) — 'cause I experienced a lot of such interviews, and had failed on hundreds of them, despite I really confident with my knowledge on each interview! And this always was really stressful, not only on an interview itself, but mostly after, because I started to doubt in myself, my knowledge, experience, skills, abilities, and so on. This was isn't right, because when we experiencing stress we couldn't thinking right and make a right decisions. This is also a very thin psychological and physiological phenomenon, especially for creative minds and specialties.

I was a team lead (raised/growed up to this position mostly) in three companies in my career - at a fin-tech project of mobile payment system in a banking industry (where I started as a team-lead immediately at the beginning), and in two companies who targeting their products for cloud managed networking infrastructure for last mile mesh networks and cell operators - and in a team lead position I was managing teams (also working as a product owner in scrum agile task processing), hiring and examining new developers by myself, and had a deep knowledge of what exactly the interviewing process should be like, how it should be arranged and built, to give a confidence and calm conveniences for the interviewee, candidates to developers in a team, to be confident in their knowledge, and show themselves in a right way, 'cause they are just couldn't make a good impression to an interviewer twice!

Here is the good article about this subject - https://danluu.com/algorithms-interviews/

And I completely agree with every word of Dan Luu!

Most of the questions, tasks and coding samples on most of my interviews doesn't have any relevance to the further real work!

Most of the interviews are completely wrong and for me personally most of them shows the wrong arrangement processes that built in a teamwork and shows a bad toxic corporate culture in a companies. And I happy that I didn't got a work in and with such companies!

And that's why not only the candidates failed at the interviews, but also most of the companies, startups and products are failed in further - 'cause they choose a wrong approaches and started to build processes in a team relying on these wrong approaches. And they doesn't even have a clue about it! (And that's why such specialties as scrum-master existing!)

Me personally really appreciate the work of this project, its values, and the movement it have started - https://compassionatecoding.com

First of all - developers must be involved to the product development, and good approaches, practices and processes in a teamwork must to help them to reach the goals. So as a team-lead I always prefer to give to candidates a one week (probation test period) to show themselves, their skills on real work, on real tasks, to get involve and to give them a chance to feel themselves a part of a team, and to give them feel deeply of how do they could fit into the teamwork processes, how the corporate culture suits to them, rather than get involved to toxic and stressful interviews processes. And this approach just works fine for the most of candidates - they've been a good part of a team, integrated in a team fast, and growing up fast as a developers!

#thinkingoutloud #sundaythoughts

#Rust #Kotlin #CPP #Go #Golang

#interview #interviews

#processes #culture

#work #team

#teamwork

Published in @technologique channel:

@technologique/1458

@technologique/1459

@technologique/1461

@technologique/1449