GetInsured Interview Questions
& Process

It was a good experience, with one video interview round where about 10-12 standard questions were asked. I was offered a basic salary to work remotely for the insurance process. The management was cooperative and professional throughout my time with the company. Management is really understanding and supportive. It worked out great for me. It's a good company to work for, with average pay but a good organization. I'd recommend it to people looking for remote customer service or insurance customer service roles.

The budget for this APM role is way too low for Pune market standards, especially since it needs some technical knowledge of APIs and databases. The interview process is super inefficient and lacks transparency, leading to endless waiting times. It seems they have just one HR person juggling recruitment, onboarding, employee lifecycle management, event planning, and more, which explains why interviews get delayed by weeks. Follow-ups are either ignored or too vague to understand the status or next steps. The HR didn't even know who the hiring manager was or what happens after clearing the interview. The interviewer's questions, like asking how I stay technically updated for an APM role that doesn't require development experience, felt off. When I asked how this position would benefit the interviewer and their team, they had no clear answer, suggesting the role might not be essential and could be cut. The whole 2.5-month process shows this position isn't a company priority. Plus, one of the interviews felt unnecessary to have video on, which made me uncomfortable. They really need a more efficient and transparent process to build candidate trust, even if they don't get the job. After 2.5 months of back-and-forth, calls, messages, emails, a long write-up for HR's queries, and two interviews, I got a generic rejection. Other companies usually give detailed reasons. When I asked for feedback, HR said they didn't know but would try to find out, making me wonder if they even have a debriefing process.

It went pretty well. They asked me some questions about my past roles and work experience with previous companies, and about my SQL and Python knowledge. They also asked about some SQL projects I've done.

It was a very rushed onsite interview, and I didn't get a chance to ask any questions. In one of the interviews, the interviewer didn't give me enough time to clarify their questions and even left the room while I was trying to answer one. They asked me a specific question about Hibernate twice, which suggests it's a high priority for them. If you haven't encountered that specific issue before, even if you understand general Hibernate behavior, it would be difficult to answer as they expected. The interview wasn't overly difficult, but it felt like they were looking for very particular answers rather than focusing on problem-solving. It seemed more like a test of specific topic experience.