First off I was contacted by the recruiter that said that my salary range was too high for the position and I should have gone with my gut feeling and say no thanks. But I decided to continue the process so then there was a secondary interview where I was asked behavior type questions, everything went well with that round and then there was a take home project which was okay. I then got to review my project with other QA Engineers and the questions that were asked were not well prepared at all and then at the end of the interview they also said that I should have gotten an email for the second half of the interview which I did not receive. So the feedback that I received was that I answered the questions using technology jargon, but I answered the questions that were asked, and if they needed clarity because I was speaking over their heads then they should have said so and not just acted like they understood what I was saying. Also I asked if what I was saying was making sense and they said yes. So that is not my fault. All in all my take is that this company is too young for anyone with more than 10 years of Technology experience in any discipline. Also go with your gut feeling it will save you a lot of wasted time. And the pay range they are willing to pay for the level of work they are expecting does not equal out. I also reviewed other reviews for this company and I was definitely spared!
Domande di colloquio [1]
Domanda 1
They asked how did I reduce the Production bug rate. I answered the question and it went right over their heads!!!!!
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Hudl nel mese di lug 2024
Colloquio
The recruiters seem like nice people, but the Tech/Engineering team has no clue on what they are doing / hiring for. It is being marketed as a ONE YEAR CONTRACT role (which mean you can be out of a job in a year) and at the same time its 5 days WFO.
Initially a recruiter reached out on LinkedIn which then converted into a 30 minute call. Basic 2way introduction.
Next was the interview with the hiring manager where all questions were asked around everything except the actual testing stuff. I even confirmed if I was being interviewed for a TECH/QA role or something else. The questions mostly were wayward and unrelated to the role.
This then was followed up by a take home assignment. This is where they dropped the ball.
The assignment was mailed by the recruiter with just 2-3 lines of guidance and no specifics on how they wanted it to be designed (TDD vs BDD; POM vs PageFactory; etc)
What's even weird is the assignment was to test the LIVE login page for HUDL's website.
Yes you heard it right - LIVE LOGIN PAGE- of their website.
I did complete the assignment before the deadline and submitted it and 2 days after my submission I see that the login page has been completely changed/ revamped!!
Imagine the horror and shock to see my tests failing due to a change in the system under test which was NOT communicated at all.
The login page must have had a major change that was pushed to production after I submitted my tests.
Imagine you are asked to practice playing for a football team and you do that but when you turn up, the company asks you to play for a tennis team!!!
In all the companies I have interviewed previously, the ASSIGNMENT is usually based on a different ENVIRONMENT where the SYSTEM IS UNTOUCHED and DOES NOT CHANGE!
If the engineering leaders at HUDL cannot even comprehend this basic caveat and are unwise enough to give a production level, frequently changing system to the interviewees as an assignment; I thing we are better off not working under them!
My assignment was rejected due to "code not working" and other ridiculous comments which should've been informed in the guidelines of the assignment to begin with.
Dear recruiters, pls ask for feedback from the candidates too. A lot of time and efforts are invested into the assignment and it feels terrible too see it rejected for juvenile and preposterous reasons.
To anyone interviewing for HUDL - make sure you get clarity on the 1yr contract role + the take home assignment
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Hudl (Lincoln, NE) nel mese di gen 2023
Colloquio
1. I was contacted by a Technical Recruiter on Linked In 2. After having initial screening with Tech Recruiter, I was scheduled to have an interview with the hiring manager. Through the process, another technical recruiter would manage all the contact and process. 3. After meeting with the hiring manager, I was given a technical project to complete. 4. After completion of the technical project, I met with two members of a QA department, a Senior QA Manager and a Senior QA Engineer to review the technical project 5. After passing the technical project interview, I met with some members of the team/squad I'd be joining so they could see if I would be a good fit. 6. Immediately after that meeting, I met with the Director of QA for the division I would be hired for. 7. A few hours after that meeting, I received an offer for the position. The entire process took about 3 weeks from the first phone call with the tech recruiter to receiving an offer.
Domande di colloquio [1]
Domanda 1
If company decided to sunset the support of a brower, and then the following week clients raised issues that they couldn't access a feature in that browser, how would you handle it as QA?
