State Farm Software Engineer Interview Questions
& Process

I got invited to do an online interview. It was all automated, no human interaction at all. It had about 5 questions that I had to record myself answering, plus an online coding test. The interview questions were behavioral and not that hard. The coding assessment had a simple practice area. The real coding challenge was really old and weird, like a LeetCode problem but without debugging. It was some string compression question that's not used anymore. With 10 years of experience writing APIs, that's not the kind of coding I do. It felt unfair that no human was involved. I got a generic rejection email about a week later. It was super disappointing because I've been a customer for years. Maybe I should switch insurance companies and maybe that's why their website is so bad. They should use AI better, like for customer experience, not to screen out experienced engineers with fake interviews.

So first, I had to do this HireVue thing where you just record yourself answering behavioral questions. You get two chances for each question if you mess up the first time. After that, I talked to a lead and a manager. We started with more behavioral questions, then they asked me about software stuff, and finally, they showed me some code and asked what the output would be. That was it for me.

The interview process started with a HireVue round. Following that, there was a technical interview with the manager. In this round, you can expect manager-level questions such as how you would handle an increased workload, how you would prioritize tasks, your motivation for joining State Farm, and what makes you unique for the role. There were also technical questions, including one about Guidewire transactions that cannot be done Out of Scope (OOS) – Sub, renewal, or Final audit. Additionally, I was asked some questions about a Java code sample. I believe I answered everything, but I'm not entirely sure about the correctness of my answers.