First off, you didn’t “fail.” Honestly it sounds like that interview was crap if they failed you because you forgot some curly braces. Interviews or companies that care that much about small things or even getting the exact answer that they are looking for are more than likely companies you are glad you aren’t at. Especially when you’re a junior.
A technical interview isn’t about getting things exactly right. It’s about just seeing what someone’s thought process is like. Does it fit with the company and the people there? The best interviews are when a conversation happens between both parties. Always remember you’re interviewing the company as much as they are interviewing you.
But some general advice: don’t worry about it. I have been in an interview before where I felt like I did really good. I walked out feeling good and didn’t get hired. It happens to everyone. The more interviews you do the more comfortable you become. Just keep gaining your confidence. Confidence is a big thing in interviews. Be confident in how you describe your solution to a problem.
Just keep going and learning more. One interview that didn’t go the way you wanted it to go doesn’t define and change anything.
Yeah, I mean that's where I was confused. I thought in interviews they mostly check the logical abilities of the candidate, coz if the candidates logic is clear then programming won't be difficult. Same happened while writing an SQL query, I gave him my idea on how I would approach for the desired result, but he wanted the query and when I checked it on Google after the interview, I was absolutely right. But I learnt a lot too from this interview! Hey btw can I ask for a suggestion? I usually prefer writing a pseudo code before coding as it later becomes easier, but during interviews they don't have much time. So how should I approach?
Write out the pseudo code first if that makes you feel comfortable. Write it out using comments. If this is a live coding interview and they are putting you on a strict time limit then in my opinion that is a huge red flag.
In live coding interviews take your time. Don’t feel like they are rushing you. Write out the pseudo code and show how you would solve it then start writing out the code. Also talk everything out outloud with them. As someone who is an interviewer for interns and junior developers, I love it when the person I’m interviewing talk out what they are currently doing out loud with me.
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.
First off, you didn’t “fail.” Honestly it sounds like that interview was crap if they failed you because you forgot some curly braces. Interviews or companies that care that much about small things or even getting the exact answer that they are looking for are more than likely companies you are glad you aren’t at. Especially when you’re a junior.
A technical interview isn’t about getting things exactly right. It’s about just seeing what someone’s thought process is like. Does it fit with the company and the people there? The best interviews are when a conversation happens between both parties. Always remember you’re interviewing the company as much as they are interviewing you.
But some general advice: don’t worry about it. I have been in an interview before where I felt like I did really good. I walked out feeling good and didn’t get hired. It happens to everyone. The more interviews you do the more comfortable you become. Just keep gaining your confidence. Confidence is a big thing in interviews. Be confident in how you describe your solution to a problem.
Just keep going and learning more. One interview that didn’t go the way you wanted it to go doesn’t define and change anything.
This is 100% right on. (Speaking as an interviewer myself.)
Yeah, I mean that's where I was confused. I thought in interviews they mostly check the logical abilities of the candidate, coz if the candidates logic is clear then programming won't be difficult. Same happened while writing an SQL query, I gave him my idea on how I would approach for the desired result, but he wanted the query and when I checked it on Google after the interview, I was absolutely right. But I learnt a lot too from this interview! Hey btw can I ask for a suggestion? I usually prefer writing a pseudo code before coding as it later becomes easier, but during interviews they don't have much time. So how should I approach?
Write out the pseudo code first if that makes you feel comfortable. Write it out using comments. If this is a live coding interview and they are putting you on a strict time limit then in my opinion that is a huge red flag.
In live coding interviews take your time. Don’t feel like they are rushing you. Write out the pseudo code and show how you would solve it then start writing out the code. Also talk everything out outloud with them. As someone who is an interviewer for interns and junior developers, I love it when the person I’m interviewing talk out what they are currently doing out loud with me.