The interview process was not organized properly. My interview was scheduled for 3:00 PM, but I was interviewed only at 5:30 PM.
My resume was sent through a consultancy and was shortlisted by the interviewing manager for further processing. The requirement was for Selenium/Coded UI using C#, but I had not worked on either of those tools, though I had proficient knowledge of C#. I had informed the consultancy of this, and they were told that learning a new tool would not be difficult and I could learn quickly. This was also relayed to the manager, which is why I was shortlisted for the interview.
However, after a long wait of 2.5 hours, I was called for the interview. An additional 15-20 minutes were spent arranging the panel and calling the manager on a conference call.
After that, I was not asked anything related to C#. Instead, I was asked to explain the pillars of OOPS and processes in agile methodologies. That was all. My interview concluded in 10 minutes. I inquired about the job opportunity and received a very brief description.
If the requirement for Selenium/Coded UI was so strict, I should not have been called. Alternatively, they could have made an attempt to assess my C# programming skills, as any automation engineer knows that learning a new tool does not take long.
Explain pillars of OOPS.
Differences between Agile and Waterfall.
Explain bug life cycle.
Explain differences between severity and priority while logging a defect.
The following metrics were computed from 1 interview experience for the Dell Software Development Engineer In Test role in Bengaluru, Karnataka.
Dell's interview process for their Software Development Engineer In Test roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Dell's Software Development Engineer In Test interview process in Bengaluru, Karnataka.