I applied in-person.
It was a very negative experience. Eighty percent of the questions were asked from the one Postman screen. The questions weren't any deep and tested more of my memory rather than intelligence. Status codes were asked repeatedly, like what is 400, 401, 402, 500, 501, 502, rather than any deeper knowledge. There was constant grilling on what else comes along with status codes, message, and description. I managed to say response time, and he just wanted data size too as the answer. Another time, he asked what else is there apart from API endpoints and method, and he was expecting headers as an answer. It was a no-brainer at all.
The interviewer seemed inexperienced and stubborn to his own experience and failed to explore my skillset and aptitude. It seems like I wasted a lot of time visiting their office twice and writing their overly lengthy assignments.
Just learn the Postman page by heart. You should know all status codes, every single detail, and the parameters passed. It is a no-brainer.
The following metrics were computed from 2 interview experiences for the Zeta Software QA Engineer role in Bengaluru, Karnataka.
Zeta's interview process for their Software QA Engineer roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Zeta's Software QA Engineer interview process in Bengaluru, Karnataka.