Fabric Insurance Agency Senior Software Engineer interview questions

The initial step was a conversation with the hiring manager, which included a few behavioral questions — things like how I handle difficult situations or how I respond when I’ve broken something in production. The technical portion was straightforward and definitely not LeetCode-style. It involved reading data and included a small logic challenge, like converting time from 24-hour to 12-hour format. The interviewers were all very nice, professional, and easy to talk to. Even though I didn’t get the job, I genuinely enjoyed the experience and appreciated how respectful and organized the process was.

The interviewers were professional and friendly. There are some great people at this company. The interview process was fair and comprehensive for both interviewer and interviewee. However, I felt the company is strongly overweighting coding interview success (pass rate less than 100% is an auto-fail) vs. evaluating the candidate as a whole. The interview process consists of several stages: recruiter screen, manager screen, technical challenge, virtual onsite, and after, probably references + C-suite interview, but I did not make it this far. The virtual onsite consists of a debugging challenge (involves coding, be prepared), system design interview revolving around APIs, and a hiring manager screen. You have to score a 100% on all coding portions or you're done regardless of how well you know everything else. The debugging interview was ok, but I was unable to provide a coded solution within the allotted amount of time. With that said, I felt my answers + tradeoffs for a long-term fix were within reason. I checked online following the onsite, and I was unable to come up with anything I had not said other than a con I had missed in one alternative. I felt the debugging interview was the biggest reason I was rejected after reviewing my interview process retrospectively. Know Typescript well and review basic DSA to get past the initial screen. The debugging interview is going to be a bit of luck, intelligence, and prior experience. For system design, you don't need FAANG prep, but make sure that you understand the fundamental backend architecture of your own system. Caution: they may say your system is complicated even if you only add a few tables and use basic tools to schedule tasks/cronjobs which I found surprising (so be "simpler than simple"). For the hiring manager screen, bring your proudest moments/projects and rehearse basic behavioral questions.