Esurance is now known as Allstate. Esurance has joined forces with Allstate and will no longer be posting updates or responses on this page. For continued news and info, please follow Allstate on Glassdoor..
I applied through an employee referral. The process took 1 week. I interviewed at Esurance (San Francisco, CA) in Jan 2013
Interview
1. Telephonic interview
2. In person interview
3. HR round
Interview questions [1]
Question 1
There was really not anything difficult as such. There were 3 round of techinical interview by different team members and Team lead/Project Manager. All techinical questions were pretty stateforward and there was discussion about the work I have done in past, architecture for my current project, design patterns i used. Project Manager also asked me one puzzle that I couldn't answer :P...
It was more about my past work and technical questions coming out of that.
I applied through a recruiter. The process took 5 days. I interviewed at Esurance (San Francisco, CA) in Jun 2019
Interview
I was interviewed previous by 100 different companies over the last 5 years but never seen a recruiter who is so impatient.
I was communicating with a recruiter at Esurance and I have shared my availability with the recruiter along with my phone number.
However, I had a typo on my phone number shared with recruiter with one digit going off and also I have misspelt his name while writing a message.
I sincerely apologized the recruiter for the mistake. However, the recruiter seemed to be pissed off seriously just due to this typo two mistakes made by the candidate.
I have shared the right phone number with the same recruiter in 3 other messages and the recruiter did not pay attention to the right phone number shared but kept calling at wrong phone number.
He has rejected to continue the interview process with very harsh words on my behavior when he called me.
Here are his words "You had a typo in your phone number and you had a typo in my name, we do not accept such negligent candidates and so I want to let this go..gud luck in your job search.""
Notes for the interviewer:
1. Mistakes do happen with people and if you havent done any mistakes in your life (you are super human). if recruiter cannot accept the apologies from the candidate for typos then this shows a lot of negativity in the work culture at Esurance or specifically the recruiter.
2. When the recruiter tried to call on my wrong number, he could not connect to me since its a wrong number, instead of reaching out to the candidate or messaging to the candidate to find whats wrong, recruiter just did not follow up or tried messaging the candidate. This shows me that there is really no open role to fill at Esurance or they are not really serious in hiring .
My respoce to recruiter: "Thank you for taking your time to respond to my message and considering me for this position. I do ackowledge that there were a couple of typos in my messages and I sincerely apologize for the same. I wish you a very good luck in finding the right candidate to interview and I will surely let this opportunity go based on the culture exposed in your conversation. I coulod not imagine working in an environment so perfect with no mistakes ever made by people and may be I am not a right fit. Good luck to you as well."
Recommendation to Other Candidates:
1. I might have a bad interview experience and I wish this was only with that specific recruiter. Please continue to apply for Esurance but please think twice before you apply for a position here.
2. Make sure you avoid typos, it doesn't show professionalism and might show lack of interest while working with immature recruiters.
I applied through an employee referral. The process took 2 weeks. I interviewed at Esurance (San Francisco, CA) in Aug 2012
Interview
brief call with recruiter then in person interview. I met around 5 people. First with one software developer who asked question about current project. My development process and environment. Second round with 2 software developers. That asked me some standard programming questions (No algos) about OOPS, C# etc. Last round was with Manager and Technical Architect. They just discussed different technologies i have used in past. Manager asked one simple puzzle.
Interview questions [1]
Question 1
Standard OOPs and C# questions.
Design Patterns
SQL Queries