Overall the interview process was a positive, but challenging experience.
I first talked with a recruiter.
He gave me some background on the company and asked a few questions about my background.
I then had a more technical interview with the manager of the one Automation group.
There was a brief introduction and then some technical questions, felt like this one was thrown right into the technical weeds from the beginning.
After I asked some clarification questions regarding the problem he asked about my background.
I have good experience with Test automation but not necessarily the hardware side of testing which made it a little more difficult to answer the questions properly.
I did then get the Python coding interview, this was definitely more focused on Hardware than it was software.
Essentially, the interviewer pasted a large amount of empty Python code and asked for me to write a test using the code.
I made sure to explain my process, receive feedback and apply it, etc.
It was just more hardware oriented than I was expecting, so I felt like I asked more questions than wrote code, only because I wanted to make sure I fully understood the problem before just trying things.
I got my rejection letter a few days later.
Again, overall not a bad experience, I felt like I wasn't prepared for the type of questions being asked.
How to verify and test a hardware component has the right voltage?
How would you test the firmware is behaving as expected?
The following metrics were computed from 1 interview experience for the Aurora Software Engineer Test Automation role in Pittsburgh, Pennsylvania.
Aurora's interview process for their Software Engineer Test Automation roles in Pittsburgh, Pennsylvania is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Aurora's Software Engineer Test Automation interview process in Pittsburgh, Pennsylvania.