Real, anonymous reports from people who interviewed for QA Automation Engineer at Wolters Kluwer, newest first and distilled into what to expect across the loop.
Get your personalized Wolters Kluwer QA Automation Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I got referred by a friend for a Senior Automation Test Engineer role, and right away the process stood out to me as slow. I went through all the rounds, and once everything was completed, they confirmed an offer by email and asked me to commit to my joining.
The part that made it feel unprofessional was what happened shortly before my start date. A week before I was supposed to join, they backed out and cited organizational changes and budget restrictions. It left a sour feeling because it wasn’t just a “no” at the beginning—it came after I’d already been told to commit. In the end, there was no offer, and the way it was handled made the experience feel like it could disrupt someone’s real employment plans.
> 1 year
Average Negative India
My interview started with a clear plan: HR told me I’d have two technical rounds and one HR round. Both technical rounds ended up being pretty basic but still technical, and after I cleared the first two, HR told me my feedback was positive and that I was selected. They even discussed salary and confirmed everything seemed aligned.
Then the process shifted in a way that threw me off. HR said another informal round would be scheduled with a country head, but last-minute that was changed into a technical round led by a manager. During that manager-led discussion, the pace felt rushed, and it really came across like they were trying to “cut” me with questions—some were about technology I hadn’t applied for or discussed. I walked out with the feeling it was more formality than fair evaluation.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
