To add up to this, I've seen companies not telling candidates exactly when the results for the interview will be out. This can be very disturbing since every day you'll just be thinking about the results.
Also, I've been in the interview where the interviewer referred to a particular problem as "Easy", 10 minutes in and this made me extremely anxious thinking that I can't even solve the easy problem.
Why don't we give people the choice in technical test?
I am a creative, passionate, full stack web developer. I love technology! Currently I'm really into Node & React but I am very experienced in PHP, Drupal 8, accessibility, CI/CD #WomenWhoCode
Hi, I'm a developer with three year of experience. I am trained in Java/J2e but I am mostly a Javascript/Typescript lover <3 currently working in GIS, with ReactJS and LeafletJS
Indeed I have the same critics. I had to search intensively for a job last year, and I remember getting really stressed and depressed by the end of the month.
Nearly every interviews were algorithms supposedly "easy" to do in a few minutes... I panicked and got stressed and unable to do anything.
But I also experienced a great process once, mostly involving pair programming with three differents developers with framework and languages of my choice. They were really helpful and ready to let the candidates feel more relaxed. Even if eventually I didn't get the job, I learned a lot and I felt great after this time. I keep a great feeling from this afternoon.
I am a creative, passionate, full stack web developer. I love technology! Currently I'm really into Node & React but I am very experienced in PHP, Drupal 8, accessibility, CI/CD #WomenWhoCode
Hi, I'm a developer with three year of experience. I am trained in Java/J2e but I am mostly a Javascript/Typescript lover <3 currently working in GIS, with ReactJS and LeafletJS
Hi, Great post! I've noticed this as well.
To add up to this, I've seen companies not telling candidates exactly when the results for the interview will be out. This can be very disturbing since every day you'll just be thinking about the results.
Also, I've been in the interview where the interviewer referred to a particular problem as "Easy", 10 minutes in and this made me extremely anxious thinking that I can't even solve the easy problem.
I loved this point and great post 🦄
Thank you so much :)
Oh yes, very good points! That second point is very bad interviewer behaviour, very belittling!
Indeed I have the same critics. I had to search intensively for a job last year, and I remember getting really stressed and depressed by the end of the month.
Nearly every interviews were algorithms supposedly "easy" to do in a few minutes... I panicked and got stressed and unable to do anything.
But I also experienced a great process once, mostly involving pair programming with three differents developers with framework and languages of my choice. They were really helpful and ready to let the candidates feel more relaxed. Even if eventually I didn't get the job, I learned a lot and I felt great after this time. I keep a great feeling from this afternoon.
Yes, that's how I feel great interview processes should be. Even if you weren't a fit for the role, you're left with a positive feeling.
And it is a great way to insure that the candidates, even if they fail, will feel great about the company and want to learn and to their best