eSimplicity Interview Questions
& Process

Went through a few rounds of interviews and made it to the final stage, but they ended up choosing another candidate. The first couple of interviews were about 45-60 mins each and mostly about my experience and background. I thought those were good conversations and the interviewers seemed interested. The early parts were good, but the last round felt a bit off.

The interview process involved an initial tech screen, followed by a HackerRank or Coderbyte assessment with about 3 questions. Then, there was a 1-hour whiteboarding session with an engineer, which was half listening to them ramble. After that, I was ghosted – no follow-up emails, calls, or anything. Just a complete waste of time. They seem to be funded by government contracts, so expect them to waste your tax money and your time too. Best to skip this one.

There were two interviews. The first one involved questions about my resume, a request to talk about myself, and how I saw the company benefiting me. The second interview was with an electrical engineer who asked about my technical knowledge in the field, and also about my strengths and weaknesses.

The interview scheduling was a bit disorganized. The first interview, I expected a coding exercise, but it turned out to be a conversation with a QA team member about their automation framework and how they utilize the drobotic framework, which involved minimal coding. The subsequent interview involved my interviewer presenting me with a logic or algorithm problem, which felt more suited for someone early in their career than a seasoned test automation engineer. I struggled with these types of problems, as they aren't typically part of my work. My own approach for hiring test automation engineers usually focuses on testing methodologies, automation strategies, and analytical skills, but this interviewer had a different perspective and wasn't very helpful when I sought clarification.