When I go into an interview and it's a live coding session that involves algorithms when the job is a backend engineer dealing with APIs, I simply just kindly apologize to them that I'm going to have to end this interview prematurely... and then just walk away. I hate these interviews and will not subject myself to humiliation and will certainly NOT spend weeks learning algorithms that I am not even going to be using on the job.
@@balu.92 Really depends on the level of the role. Take home coding challenges are the best to see any persons coding style and level no matter how long they've been in the industry. If they can't or won't do that then I'd just have them describe to me how they would implement a recent feature that you or maybe someone else in the team has done. If it's api eccentric maybe ask them how they would design an API for say getting users and other entities related to that. Also see what ways you can secure your APIs (auths, rate limits, IP whitelist?). Can also go over with some problems your team recently encountered and have them walk through how to debug?
The worst is when you're interviewing for a technical role at a higher level than the person giving the interview. Then they're sitting there sneering at you doing an interrogation.
This is a brilliant video and topic. The field of software engineering is as vast as an ocean. How in the world can you prepare for a coding interview or assessment test when they can hit you with a ton of topics that you do not use or even come across? It seems that companies are just ignorant about reality, too lazy to put together their own assessment plan or they are using interviews as a lazy filtering tool. They know if they set the bar a mile high for Jr. positions they will wind up hiring a mid level on the cheap. How can you fight that?
People hate coding interviews because it is very abnormal and uncomfortable when strange person is staring at you while you are in the middle of your thought process. I always freeze in such circumstances. I definitely prefer to be alone when I need to analyze a problem and find a solution.
I'm dreading the day I have to do this... I'm still learning to code.. From what I've seen online with the interviews... I think these interviews are more for getting an idea of how the potential candidate can think through a problem (of course you should know how to code as well) and observer the way they think. What do I know... Just my thought on it.
When I go into an interview and it's a live coding session that involves algorithms when the job is a backend engineer dealing with APIs, I simply just kindly apologize to them that I'm going to have to end this interview prematurely... and then just walk away. I hate these interviews and will not subject myself to humiliation and will certainly NOT spend weeks learning algorithms that I am not even going to be using on the job.
Can you suggest a few Qs that would better assess a person's back-end skills? Just off the top of your head. Thanks
@@balu.92 Really depends on the level of the role. Take home coding challenges are the best to see any persons coding style and level no matter how long they've been in the industry. If they can't or won't do that then I'd just have them describe to me how they would implement a recent feature that you or maybe someone else in the team has done. If it's api eccentric maybe ask them how they would design an API for say getting users and other entities related to that. Also see what ways you can secure your APIs (auths, rate limits, IP whitelist?). Can also go over with some problems your team recently encountered and have them walk through how to debug?
@@Xaero324 Thanks for answering!
think twice if you are thinking of a software development career - the interviews are brutal - and they keep getting worse.
Yeah it gets seriously worse…. Two phone screens and two online assessments and three on-site interviews for internships … WTF
Coding interviews don't test your problem solving abilities. They just test if you googled that problem beforehand or not.
The worst is when you're interviewing for a technical role at a higher level than the person giving the interview. Then they're sitting there sneering at you doing an interrogation.
This is a brilliant video and topic. The field of software engineering is as vast as an ocean. How in the world can you prepare for a coding interview or assessment test when they can hit you with a ton of topics that you do not use or even come across? It seems that companies are just ignorant about reality, too lazy to put together their own assessment plan or they are using interviews as a lazy filtering tool. They know if they set the bar a mile high for Jr. positions they will wind up hiring a mid level on the cheap. How can you fight that?
You deserve more subscribers bro. This vid was very insightful compared to a lot of other RUclips vids on this topic. Keep it up
Thanks man, i appreciate the kind words. Super glad you found the vid insightful!
People hate coding interviews because it is very abnormal and uncomfortable when strange person is staring at you while you are in the middle of your thought process. I always freeze in such circumstances. I definitely prefer to be alone when I need to analyze a problem and find a solution.
I'm dreading the day I have to do this... I'm still learning to code.. From what I've seen online with the interviews... I think these interviews are more for getting an idea of how the potential candidate can think through a problem (of course you should know how to code as well) and observer the way they think. What do I know... Just my thought on it.
Just say no to coding interviews.
Yeah, software engineering requires so much more than just the coding tests of the algorithms. Well said. :)
"Talk is cheap, So me the code"