Susco Interview Questions
& Process

I filled out the online application which had 16 technical questions. Then I got invited to do an online assessment. After that, I got my assessment results. Next, the org reviewed my application and the assessment results. Finally, the org told me their decision.

So, there were 2 interviews for me. First one was with a recruiting company, and then the second one was with Susco employees, like the Director of Projects, Chief Architect, and Director of Support. They also sent me 2 assessments with general questions. The last interview was a bit over an hour, where the team talked about who they're looking for and shared info about the company, its culture and mission. They were more focused on my background and expertise rather than just theoretical QA questions.

So, they hit me with a few questions and then this interactive test. It was like a command line thing for a few languages. The interviewer would drop some code and ask me to finish it, or tell them what would happen if it ran. The stuff they used was never gonna be in a real app, all designed to mess with you. It wasn't really about if you could solve problems, more like a gotcha. The questions got simpler towards the end once I figured out their trick with the examples. It was kinda like a take-home test, but done live.

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.