I recently attended an interview with Accenture. At the beginning, the interviewer introduced herself and mentioned that she has 16 years of experience. The interview started normally, and she asked me a few technical questions. While answering, I usually take a few moments to think before responding. Because of this, she repeatedly assumed that I was looking at another screen for answers. Even after I clearly said that I was not doing so, she asked me the same thing multiple times, which made me feel uncomfortable during the interview. At certain points, when I answered questions, she commented that my answers sounded “bookish.” I understand that I may not have been able to answer every question perfectly, and I completely accept that there is always room for improvement. However, towards the end, she said that I should come prepared and not waste the interviewer’s time. I personally felt that this statement was discouraging and could have been communicated in a more respectful manner. In the industry, there are also many situations where candidates complete multiple interview rounds, receive positive feedback, or even get offer-related communication, and later are informed that the position has been closed. In such cases, the candidate’s time and effort are also impacted. Experience and seniority are valuable, but I believe interviews should remain professional, respectful, and comfortable for both sides. A candidate may be nervous or may need some time to think before answering, but that should not make them feel small or disrespected.

Straight forward and purely technical . Two rounds of interview.one technical and one hr with manager round Coding assessment was also there but not that much tough.Application level questions including use cases.

I had a 1-hour interview for the Salesforce Developer role. The discussion mainly focused on my understanding of Lightning Web Components (LWC) and Apex development. Most of the questions were scenario-based, testing practical knowledge and real-time problem-solving skills. The interviewer covered key concepts like component communication in LWC, use of @wire and imperative Apex calls, and handling Apex triggers and classes. There were also questions on governor limits and best practices in Salesforce development. Overall, the interview was technical and focused more on hands-on experience rather than theoretical knowledge. It was a good experience to showcase practical skills in Salesforce