EPAM Systems Senior QA Automation Engineer interview questions

The overall experience was a major disappointment and one of the weakest recruitment processes I have experienced. The initial recruiter call went well, but communication afterwards was extremely slow. After waiting for around two weeks without any update, I sent a follow-up email and later a LinkedIn message. Another week passed before I finally received a response saying that the recruiter was still waiting for feedback from the hiring team. After another follow-up in a week, I was eventually informed that the process would continue, and the technical interview was scheduled almost one month after the initial recruiter call. The technical interview itself covered a broad range of topics, including Java, Selenium, REST Assured, API testing, testing strategy, Cypress, Git, SQL, SOLID principles, TestNG, Cucumber, and two practical coding exercises. The interviewer was professional, but it was surprising that the interview focused heavily on advanced Java topics even though my CV clearly stated that my practical Java experience dated back more than five years. One week after the interview I sent another follow-up email. More than three weeks after the interview, and over two weeks after my follow-up, I still had not received any feedback or final decision. The technical interview itself was worthwhile, but the overall candidate experience was overshadowed by very slow communication, repeated periods of silence, and the need to repeatedly chase updates. Overall, this was one of the most disappointing recruitment processes I have experienced.