DP World Test Automation Engineer Interview Questions
& Process

The interview process had 4 technical rounds. A couple of the interviewers seemed from a non-technical background. The interviewer was asking very theoretical questions like 'list top 5 exceptions'. Also, they were more interested in talking than listening to my answers. The person kept interrupting me mid-sentence. If you're hiring for a senior SDET role, you should have an interviewer with basic technical knowledge and good communication skills.

The entire interview process was really great! It felt more like a chat where we could discuss our ideas about the problems. They weren't focused on just the right answer, but more on how we approached things. Even the senior folks on the panel were super friendly and helpful.

My interview experience was really bad. The interviewer was rude. They gave me one medium and one easy coding question from GeeksforGeeks. The copy-paste in Teams wasn't working, so they spoke the question, and I had to write it down. They only told me half the question and expected me to code, but I copied the full question from chat. I took 3-5 mins to think about the logic, and they started yelling, saying I'd already taken 7 mins and should finish in 15 mins. I politely told them I don't just jump into coding and explained the logic. They said it was correct and I could start coding. I coded my logic but didn't get the desired output because it was incomplete. They seemed scared to do a dry run with me and only cared about the final output. They kept reminding me about time, and I kept suggesting we move to the next question. They then asked very detailed questions about implicit and explicit waits, which I answered partially correctly. I told them I don't go that deep into Selenium concepts because I don't find it necessary and prefer to spend time learning cloud technologies like AWS/Azure. They advised me to switch to cloud jobs instead. I politely disagreed, saying I believe in upskilling and learning. Maybe they wanted a confident answer on implicit/explicit waits, which they themselves weren't confident about and ultimately gave a wrong answer. They had an attitude throughout the interview, which I mirrored. The interview lasted 1.30 hours, and I was exhausted. There was a screening round before this technical interview. I received an email saying they'll get back to me when they find a suitable opening. The whole hiring team and the interviewer seemed unprepared. I'm sharing this experience so that someone can take notice and it doesn't happen to anyone else.