Susco Software Engineer Interview Questions
& Process

I had an initial phone interview and then I was asked to take an aptitude test and personality assessment. They sent me the results and I was in range on both tests. They did not explain why I was not selected. To get the top score, the most number of questions questions have to be answered correctly in the allowed time.

After applying, there's an HR screen which involves online tests from criteriacorp.com. First, you'll take the CCAT cognitive assessment (like an intelligence test), which is pretty important to prep for, maybe using iprep.online. After that, there's a personality test - just be yourself. The CCAT seems to have a high cutoff, but they don't share scores. ============================================================================== The next step is a one-hour interview with a technical manager. This involves general questions mixed with coding exercises using code snippets pasted into an online platform. The snippets were in older Javascript with jQuery, focusing on function references, higher-order functions, and specifically variable scope like closures, no modern ES6 features. He'll also ask which frontend framework you'd prefer for the next interview. ============================================================================== They usually schedule the second interview, which lasts two hours, within a day or two. It's similar to the first, with questions and technical exercises. There was a React exercise using class components and a weird directory structure. They also had two exercises on StackBlitz involving modifications to Telerik jQuery Kendo grids. Then, the lead interviewer shared his desktop showing Visual Studio and MS SQL Management Studio. He had a Kendo grid in the frontend connected to a REST API backend, pulling data from a 'Products' table. The task was to add a 'Category' column to the grid, enable filtering by it, add the column to the database (with a code table?), populate it, wire it through the backend, and display it. They used a PetaPoco ORM in a recent .NET Core Web API. He didn't expect prior Kendo or PetaPoco knowledge and provided hints.

The interview was in-person at their offices. We talked about my experience and then started the technical part. I answered some questions on paper and talked through my answers (how and why I arrived at that answer). Most of them were about JavaScript and some about other languages. Then, I had to complete a small coding problem on the computer in the interview room and we talked about some different frameworks. It gave me a good idea of how many different kinds of projects I would be working on and what the pace of the office is like. It was more of a technical interview than others I'd experienced.