Alarm Software Engineer interview: scripted questions that missed the project context

I had a multi-stage process that felt more about vibe than deep technical evaluation. It began with a recruiter conversation about my resume and work history, plus a brief sense of what the role required. The technical interview did not match my background well. It felt rigid and disconnected, and the interviewer repeatedly asked about things already clear on my resume.

The behavioral questions in that technical round felt scripted and generic. When I tried to follow up about projects or team context, the interviewer seemed confused about where I was going. They did pivot to the company's project work, which was relevant to my experience, but time ran out before I could fully explain it. The people were nice, but I did not get a clear reason for not receiving an offer. The process felt inefficient and short on feedback.

It took longer than I expected to hear anything definitive. Despite the friendly tone, the structure and communication mismatch left me feeling that the interview did not show my strengths. I came away thinking they could consolidate stages and make standards and expectations more consistent with the level they were hiring for.

Location: United States. Overall feedback: positive. Offer status: no offer.