I applied online and the interview was done over Google Meet. It was split in to Technical and Behavioural parts, technical part involved a small coding challenge. Interviewers were very friendly, conversation was nice and casual.
Preguntas de entrevista [1]
Pregunta 1
Standard behavioural questions, tell me a time you.. etc etc. Coding was leetcode easy/medium. Interviewers are there to help you through.
Everyone on the team was very nice and respectful. Seems the company is run pretty well and the recruiters got back to me promptly with respect to scheduling. However, I wish the company was more transparent in regards to the selection process and gave adequate feedback. The interview process was time consuming between online assessment, speaking with the recruiter, emailing times to coordinate, an interview with an engineer and then a five hour zoom onsite. I felt as though I answered the questions optimally but did not receive an offer. After the time you invest with going through the process, I wish they would give a feedback sheet to help better the onsite candidates who did not receive the position in the future.
Preguntas de entrevista [1]
Pregunta 1
Data structure and algorithms questions. Leetcode easy. Maybe leetcode medium depending on the way you look at it.
Envié una solicitud electrónica. Acudí a una entrevista en EverQuote (Boston, MA) en nov 2020
Entrevista
Online assessment -> Phone interview -> Final round that lasted 5 hours
Honestly they think they're the next big thing when all they do is build a platform that send data to insurance companies. The last interview with one of the founding engineers was so bland. Another engineer, a team lead for one of the teams there, sat in the interview. He looked extremely uninterested, did not say anything after introducing himself.
The founding engineer asked me, the new grad, to design an architecture similar to what they did to send data in JSON format to an insurance company so the user didn't have to fill out Everquote's form and the insurance company's form twice.
Instead of focusing on the design, the founding engineer asked: "What technologies do you think would best fit our scenario?" Huh? What does this question even mean? Do I think a specific programming language will be better for this design? Why would the programming language matter? He continued to ask some stupid questions like "What do we need to worry about when implementing the API?" I talked about scale, but that wasn't what he was looking for. He said we needed the API authentication key from Geico to make sure Geico knew that it was Everquote calling their API.
Unfortunately, this company thinks that they're the next big thing because they're scamming users out of their information and selling it to insurance companies.
I'm glad I got rejected, because I had a terrible experience talking to members of their team. They are all white. They lack diversity. I wouldn't be surprised if they only hired white candidates out of everyone that interviewed that day.