Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Fetch
Colloquio
I was given a coding challenge while the recruiters were looking at my resume. A majority of people would ignore this type of question without already having done an interview, so I was hoping to to spend a few hours on the challenge, polish it, and submit it to stand out. I was rejected a few days later. What a waste of time.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Fetch
Colloquio
1. Take home project (took a few hours in a day to do)
First red flag - the project had SDET in the title. QA Automation Egineers and SDETs are 2 different positions. Nevertheless, I did the project.
2. Recruiter interview - went well, if selected for the next interview, you will meet someone from the team to "discuss submitted project and your experience"
3. Technical Interview
In the confirmation email this interview it says "Please be prepared to discuss your submitted exercise". This was the expectation, but what they don't tell you is that apart from doing a take home coding exercise, you'll need to do a live coding extension of your project. So if your project is done in a way that doesn't acomodate this extension, then you're done. Interviewer mentions that QA Automation Engineers and SDETs are synonymous in the QA dept (red flag).
Overall -Expectations are not set for candidate's success. They make you research about the company and everything for you to not even discuss that research. Also, they need to familiarize themselves with what role they are really looking for. The salary range for the role is very wide, that's another red flag. Beware for QA's that are considering applying and to Fetch, best of luck.
Domande di colloquio [1]
Domanda 1
Your take home project had 9 coins, now modify your project to find the fake out of 20 coins
