Global Relay Lead Software Development Engineer In Test (SDET) interview questions

The initial HR call was followed by scheduling two technical interviews. HR communication was helpful in preparing for challenge. Quick introduction, followed by a coding task that lasted for about 30 minutes. The coding challenge was shared via zoom call, no much explanation. It was a screen sharing session with IDE installed on my machine. My solution worked only for limited input but did not match their expectations for a lead role. The interviewer made a few suggestions such as what data types they want to see certain fields etc. in the middle of coding which kind of felt like disturbance in completing the solution.

Introductions, a bit about the company and then some questions, followed by a coding task. The process was not one that can identify candidate skills rather one that points out their flaws and tests their recall of text book questions. It is a very negative way in which to conduct interviews and it is no surprise why it takes this company so long to hire and retain roles of this nature. The white board section is random and not very well thought out. Literally a few squares on what looked like MS Paint, with letters representing API, DB and UI. The questions are vague and don’t really make any sense. The coding task is reasonable but, you will be ‘marked’ incredibly harshly. My advice would be to implement it as if it was going live however, you will only have 30 minutes to complete it with literally no help. It is not a pairing exercise. Also, learn Java Streams, this is what they want to see. The interviewer was arrogant, inconsiderate and unprofessional. As a representative for the company, they did a poor job and displayed none of the cultural values they talked about.