Quiz style interviews are the WORST! They feel like the interviewer is trying to make me look bad. They don't bring out the best in candidates and only really show you who has memorized the text book. Idk about you but I don't want to work with people like that.
The majority of the company/ "interviewer" is looking for the correct answer, looking for the finish line, even though you do show good progress.... Sad but true
This is such a shit take! Quiz questions have no place in an interview, FULL STOP! Ask questions to find out how a person thinks and breaks down an issue. Ask questions about things that you have actually experienced either in that environment, ideally, or from a previous related role!
Once I was doing whiteboard coding at interview, I changed it mid way thru and described why, then when solution was done, interviewer ask me, what if this would be input and I say, well I would have to change this, so both works, we did few more of these type of question. Few days later I got a email that I have 0 skill
Thanks for this video. I'm interviewing tomorrow in-person. It's only going to be 30 minutes, so there may not be a technical interview question at all, but your advice had some good principles when navigating a technical interview question: 1. Reiterate the question with the interviewer to clarify what you're trying to solve. 2. Focus on the problem-solving process, not on the "correct" solution. 3. Talk out loud explaining the what and why of your coding process.
It's easy to ace that stupid " technical interviews", for Java for example, just memorize All the javadocs and the judge, sorry, interviewer, says "wow, he is a great programmer". For spring interview, the same, just memorize all annotations and you are done.
This pandemic is making tech interview horrible. Many interviewers are simply nit-picking. Or looking for Olympians. Their attitude is just annoying. Why do they have to look like an ass... lol. Tech ppl dont have to be like this. Put some effort into your looks and talk in more ppl friendly. No one is here to kill u. lol
Having done many coding interviews, I can assure you that it is the correctness that matters at the end and not the process. They say they care about the process, but what they ultimately care about is whether you solved the puzzle.
Lol no. Correctness is also super subjective. I *conduct* interviews to hire for our team at Zillow, and it's not pass/fail based on whether they "solved the puzzle".
@@David-we5nr Well that has been my experience. And I have done 20+ interviews in the past three years. In coding interviews correctness is not subjective; your code either works or it doesn't.
@@siarez there's so much more to it. You can have solutions with different runtime complexities, variable naming/code structure/code composition all matter, producing test cases, discussing code scaling. Explaining your reasoning matters. Handling edge cases. None of these are directly tied to code running or not. In fact I've failed candidates who had a working solution and passed ones that had partially working code. There's so so so much more to interviewing
@@siarez I'm offering this as unsolicited advice. Maybe you passed 20/20 of those interviews, in which case, keep doing what you're doing. But if you're looking for ways to improve, accepting that code correctness is only a small piece of the puzzle will help a lot in prioritization
@@David-we5nr All good advice. I'm seasoned developer and I'm pretty good in all those fronts. The only thing I wasn't not good at was solving Leetcode puzzles. Maybe you are different, but the 20+ people who interviewed me seemed to mostly care about whether I found the lowest time/space complexity solution.
spot on - if you are strong in a particular area or have some past experience that displays your abiility to adapt including how you learned new technologies and skillsets, look for logical avenues to draw parallels to what you know or how you performed. The goal is to in part provide the interviewer a positive impression on how a past experience can predict how you will adapt to the new environment/technology. IE....I may not have worked with HIVE or Impala, but I taught myself mySQL and in my last job I worked on....and this is why I can use that to be successful in learning XYZ in the new position.... Also - Focus on things you have done at some point and avoid the 'I was part of a team that worked on....' answers. What did you do and how can you help us?
Very true so far for myself and hopefully inspiring to someone enough to get them past the nervous freeze at not having a clue about a solution when asked at first. I almost never have a direct solution without talking it out a bit first. Get them talking, ask questions. I hate dead air, have had that experience. Great video to remind me as enter the interviewing process again!
This interview does not show any variability in the application process. There is no differentiation in the situation people are in when they are trying to get a job. Most people searching for help are not in a position to show off.
This had absolutely no relationship to 'technical' and everything to do with how to handle soft skills and false certainty in a common interview process for a programmer.
Have you checked for firms in your area where you would like to work....then searched LinkedIn for folks that work there? I once had a cool conversation years ago with someone on linkedIn by asking questions about how they got the positions in their career...Granted I didn't get an interview from that contact, but it helped me network and eventually make useful connections. Good Luck!
I'm about to get shredded in my first technical interview tomorrow. Say a prayer for ya boy
How did it go?
@@abdallamosa7079 Got the job :D
@@alexbraatz1431 Congrats!
Quiz style interviews are the WORST! They feel like the interviewer is trying to make me look bad. They don't bring out the best in candidates and only really show you who has memorized the text book. Idk about you but I don't want to work with people like that.
I know I'm going to do great in my interview tomorrow
How’d it go
@@darensmith6444 I didn't get it LMAO
@@Sean-tv5od damn why not?
same
You'll get one eventually! Keep up with the hard work
The guy is hard at work on Facebook at the back
🤣 LOL..
I want to work here! You get to wear shorts, and flips to work. ;)
lol
The majority of the company/ "interviewer" is looking for the correct answer, looking for the finish line, even though you do show good progress.... Sad but true
This is such a shit take! Quiz questions have no place in an interview, FULL STOP! Ask questions to find out how a person thinks and breaks down an issue. Ask questions about things that you have actually experienced either in that environment, ideally, or from a previous related role!
Once I was doing whiteboard coding at interview, I changed it mid way thru and described why, then when solution was done, interviewer ask me, what if this would be input and I say, well I would have to change this, so both works, we did few more of these type of question. Few days later I got a email that I have 0 skill
oh wow........ man....
lol doubthfull
Same lol people are easily threatened to creative thinking
Thanks for this video. I'm interviewing tomorrow in-person. It's only going to be 30 minutes, so there may not be a technical interview question at all, but your advice had some good principles when navigating a technical interview question:
1. Reiterate the question with the interviewer to clarify what you're trying to solve.
2. Focus on the problem-solving process, not on the "correct" solution.
3. Talk out loud explaining the what and why of your coding process.
It's easy to ace that stupid " technical interviews", for Java for example, just memorize All the javadocs and the judge, sorry, interviewer, says "wow, he is a great programmer". For spring interview, the same, just memorize all annotations and you are done.
great tips, the technical interview can be very hard to master
Scared of the interview. Have one next week!
When the time comes for my interviews for jobs, I know I'm going to fail.
This pandemic is making tech interview horrible. Many interviewers are simply nit-picking. Or looking for Olympians. Their attitude is just annoying. Why do they have to look like an ass... lol. Tech ppl dont have to be like this. Put some effort into your looks and talk in more ppl friendly. No one is here to kill u. lol
That guy looks like Virat Kohli
ha ha right
The guy on the left looks and sounds like a bully straight out of a British Simon Pegg movie
Ok, thats it! Pause right there! We are going to play battleship!
OMG your accent is more complex than the Spring framework. Is that Welsh or NY? (The interviewer)
Having done many coding interviews, I can assure you that it is the correctness that matters at the end and not the process.
They say they care about the process, but what they ultimately care about is whether you solved the puzzle.
Lol no. Correctness is also super subjective.
I *conduct* interviews to hire for our team at Zillow, and it's not pass/fail based on whether they "solved the puzzle".
@@David-we5nr Well that has been my experience. And I have done 20+ interviews in the past three years. In coding interviews correctness is not subjective; your code either works or it doesn't.
@@siarez there's so much more to it.
You can have solutions with different runtime complexities, variable naming/code structure/code composition all matter, producing test cases, discussing code scaling. Explaining your reasoning matters. Handling edge cases.
None of these are directly tied to code running or not. In fact I've failed candidates who had a working solution and passed ones that had partially working code.
There's so so so much more to interviewing
@@siarez I'm offering this as unsolicited advice. Maybe you passed 20/20 of those interviews, in which case, keep doing what you're doing. But if you're looking for ways to improve, accepting that code correctness is only a small piece of the puzzle will help a lot in prioritization
@@David-we5nr All good advice. I'm seasoned developer and I'm pretty good in all those fronts. The only thing I wasn't not good at was solving Leetcode puzzles.
Maybe you are different, but the 20+ people who interviewed me seemed to mostly care about whether I found the lowest time/space complexity solution.
Summary of the video:
Be honest.
Review and research the project you have done.
If you dont know the topic,actively mentioned relevant topic.
spot on - if you are strong in a particular area or have some past experience that displays your abiility to adapt including how you learned new technologies and skillsets, look for logical avenues to draw parallels to what you know or how you performed. The goal is to in part provide the interviewer a positive impression on how a past experience can predict how you will adapt to the new environment/technology. IE....I may not have worked with HIVE or Impala, but I taught myself mySQL and in my last job I worked on....and this is why I can use that to be successful in learning XYZ in the new position.... Also - Focus on things you have done at some point and avoid the 'I was part of a team that worked on....' answers. What did you do and how can you help us?
Very true so far for myself and hopefully inspiring to someone enough to get them past the nervous freeze at not having a clue about a solution when asked at first.
I almost never have a direct solution without talking it out a bit first.
Get them talking, ask questions. I hate dead air, have had that experience. Great video to remind me as enter the interviewing process again!
Can you recommend how much time would be needed to prepare for technical interviews?
no samples given, cant learn much!
This guy in the shorts looks like Virat Kohli.
This interview does not show any variability in the application process. There is no differentiation in the situation people are in when they are trying to get a job. Most people searching for help are not in a position to show off.
Damn! The day after i have a technical interview and I'm freaking nervous. Hope i clear it.
I like that guy's shirt!
Same!
Same! (2)
wait, isn't that your shirt? hahaha
same
yeah
Great content. Louder audio next time please
This had absolutely no relationship to 'technical' and everything to do with how to handle soft skills and false certainty in a common interview process for a programmer.
Test your preparation with mock technical interviews: getamock.com
process is much more important.
Does he go to interviews dressed like that?
There’s a lot out there about acing a tech interview, but I wish there was content on how to actually land an interview first
I’ve been applying to jobs since graduation from bootcamp and I’m having trouble getting an interview
Have you checked for firms in your area where you would like to work....then searched LinkedIn for folks that work there? I once had a cool conversation years ago with someone on linkedIn by asking questions about how they got the positions in their career...Granted I didn't get an interview from that contact, but it helped me network and eventually make useful connections. Good Luck!
He has my shirt.
Thanks for the info gentlemen
Wanted to let yall know that I found this very helpful.
Thanks! helpful talk
Es una lata este video
He bit looks like virat kohli..do anyone else think the same??
Yes he is Virat Kohli
Good Overview! Hmmm...This guy looks familiar 👋
Indian H1B crowd dont let others get a job!!
shut up racist
Don’t blame the Indians. They are humans just like you.