Performance Software Interview Questions
& Process

It was okay, but it felt rushed because it was short. I met a few different people and they asked me the same thing multiple times. I wasn't able to tour the facility or anything.

I applied online and got a call from HR about a week later. Had a short phone screen, and then another call a few days later to set up an in-person interview. They gave me a design problem to do before the interview: an automatic door opener. You get some vague system requirements and need to figure out SW requirements, design, pseudo code, and tests. It took a few hours. Since I'm near Clearwater, my interview panel was one person from Clearwater and two from Phoenix via Skype. We talked about my experiences and some general stuff, then went over the design problem. They mostly want to know why you made certain assumptions to judge your problem-solving skills. Then there was a round of behavioral questions, and I asked my questions. The interview lasted about an hour and a half. I got the offer about a week later.

I was contacted by a recruiter in Arizona, and after a good conversation, we scheduled an in-person interview. The recruiter mentioned I'd have an assignment beforehand, which involved documenting an embedded system design with IEEE-format requirements. This took several hours. On the interview day, I was asked general background questions and had a discussion. They also asked a couple of string manipulation questions involving pointers and one bit shifting question. Towards the end, they elaborated on the position, and I realized it wasn't for me. It seemed to be primarily a documentation role with minimal programming, more aligned with traditional engineering principles rather than modern software development. They didn't even ask about the 4-hour document I prepared, which felt like a waste of time. Despite my disinterest, they never followed up, which speaks volumes about their regard for candidates.

I interviewed at my college. The process was pretty simple. Main focus was on Basic computer science knowledge. Some experience with embedded systems and c / c++ is needed. There was a test involving the creation of basic requirements and analysis. The test is meant to gauge a persons thought process and not much coding was involved.