One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
It's hard to talk about your job when you don't have a support for it.
Something I have found very good is to propose a pull request where you intentionally wrote lots of bugs and bad practice, and ask the candidate to review it.
👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
Agreed, this is a great way to get some insight into how the candidate thinks, and it’s also arguably a better way to be sure that they understand the language than all these coding tests people do (it’s not hard to learn to write code in a language, but it’s often quite challenging to learn to recognize good code in a language and understand how to improve upon bad code to make it better).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's hard to talk about your job when you don't have a support for it.
Something I have found very good is to propose a pull request where you intentionally wrote lots of bugs and bad practice, and ask the candidate to review it.
This is a very interesting idea. I quite like it.
Agreed, this is a great way to get some insight into how the candidate thinks, and it’s also arguably a better way to be sure that they understand the language than all these coding tests people do (it’s not hard to learn to write code in a language, but it’s often quite challenging to learn to recognize good code in a language and understand how to improve upon bad code to make it better).