Regarding the coding challenges- As someone who can write Java Selenium web automation, even architect a CI/CD test solution from scratch, I can say without question these are not the correct questions to even ask. Yes I know this is to be expected in a 'coding challenge' interview but that is in itself the problem. If someone can solve these scratch coding problems they are in the mindset of a developer. If I am confident AND competent to succeed in this interview I am a developer. Full stop. If I can perform even these basic scratch coding functions I'm not pursuing QA. FAR more relevant is a simple webdriver test against any live public domain. As many elements or pages as time allows or some specifically difficult to find elements or something of this nature. Alternatively, automate an API test using whatever solution you are comfortable with. The reason is these tests completely ignore the value of the QA mindset. The QA mindset has always been the bridge between the dev and the end user. If you make this the test you eliminate the QA mindset from the role and you end up with junior devs testing senior devs code. That will just make the junior devs into better devs. You need to allow for coding NOT being the candidate's primary mindset. Any time you ask the candidate to solve a coding problem instead of testing an existing coded solution you are missing the whole point.
Question to hiring managers: Question to managers: what is the point of forcing a person to write a work code in an interview? It seems to me that if a person can write at least some code which is logically right, that is enough. It takes a lot of time to find syntactic errors, but instead you can ask a question like, how would you improve this code ? thank you! P.S. you are doing a great job! Regards, Alex
Alex Ov fair enough. I’ll bring this to the next sessions. However the main point was not about to make code working, but breaking down the approach of solving problem.
Just to mention that she needed to indent the sout statement inside the class that’s why it was throwing the exception. But overall she did a good job on that.
Looks like guy from Tinder came to show how smart he is. Interrupting and giving stupid jokes (and several questions) is the order of the day for him...
@@Mike606S That is a lot of 'should' to go around. I don't feel shame because I'm not a code monkey like most here do. If you get that out of the way and get down to it this is about finding bugs, and most devs couldn't fight their way out of a paper bag to do that.
Join our FREE mock interviews: www.evgenykim.com/
Regarding the coding challenges- As someone who can write Java Selenium web automation, even architect a CI/CD test solution from scratch, I can say without question these are not the correct questions to even ask. Yes I know this is to be expected in a 'coding challenge' interview but that is in itself the problem.
If someone can solve these scratch coding problems they are in the mindset of a developer. If I am confident AND competent to succeed in this interview I am a developer. Full stop. If I can perform even these basic scratch coding functions I'm not pursuing QA.
FAR more relevant is a simple webdriver test against any live public domain. As many elements or pages as time allows or some specifically difficult to find elements or something of this nature.
Alternatively, automate an API test using whatever solution you are comfortable with.
The reason is these tests completely ignore the value of the QA mindset. The QA mindset has always been the bridge between the dev and the end user. If you make this the test you eliminate the QA mindset from the role and you end up with junior devs testing senior devs code. That will just make the junior devs into better devs.
You need to allow for coding NOT being the candidate's primary mindset. Any time you ask the candidate to solve a coding problem instead of testing an existing coded solution you are missing the whole point.
Many thanks to everyone doing this! Very helpful. Appreciate your time and hard work!
you are very welcome! hang on, we will post more!
she is very confident ..Love the the whole interview
Question to hiring managers:
Question to managers:
what is the point of forcing a person to write a work code in an interview?
It seems to me that if a person can write at least some code which is logically right, that is enough. It takes a lot of time to find syntactic errors, but instead you can ask a question like, how would you improve this code ?
thank you!
P.S. you are doing a great job!
Regards,
Alex
Alex Ov fair enough. I’ll bring this to the next sessions. However the main point was not about to make code working, but breaking down the approach of solving problem.
I appreciate all interviewers and interviewees. Very helpful to me. Thanks again~~
Im searching for qa automation job in APAC or USA living in EU. Youre awesome guys
Just to mention that she needed to indent the sout statement inside the class that’s why it was throwing the exception. But overall she did a good job on that.
On 1:49:58 Igor was mentioning about his RUclips videos on how to prepare for interviews,can anybody pls share the link for it? Thanks
Thanks for this! :)
I can surely say the difficulty level of programs asked for SDET interviews are much complex than this atleast in India . But this is amazing. Cheers
Thanks. But the tasks are too easy...
Alexander Radchenko yep, these are warm up questions.
I want to join the slack group, however the link is not working
Please check that link again, we updated it
@@EvgenyKim1 I got it. Thank you
Candidate 2 is for sure coming from a Bootcamp without any experience.
I liked the 3rd guy
Good interview. For the coding challenge, you are providing a platform that you are not sure about how's working. It's confusing.
yeah, you right. it wasn't good prepared on our side. even it was the first time
Nice!
Check our another Mock Interviews in the playlist here: ruclips.net/p/PLk-V_MWpOixvauvscsMeKNqZ91AI7si9f
How can I join this live interview
skillsjump.com/mockinterviews
Looks like guy from Tinder came to show how smart he is. Interrupting and giving stupid jokes (and several questions) is the order of the day for him...
but he was the only one who clearly explained to the first two candidates that in order to apply for the coding position you need to be able to code
@@Mike606S Sure, but it's not a 'coding position', it's SWQA automation. BIG difference.
@@jameshisself9324 ok, at least it's a `you should know how to code` position
@@Mike606S That is a lot of 'should' to go around. I don't feel shame because I'm not a code monkey like most here do. If you get that out of the way and get down to it this is about finding bugs, and most devs couldn't fight their way out of a paper bag to do that.