Verisk Software Engineer Interview Questions
& Process

I applied online via LinkedIn and the recruiter reached out for a resume screen. After about a week, I had a 30-min chat with the Team Lead and Hiring Manager about my resume, how I think, and my skills. They said I'd move to an onsite interview. But then the recruiter went quiet for two weeks, even after I followed up a few times, before finally setting up the onsite. The onsite loop had a coding round with a Senior Manager focusing on C#, threading, and multitasking. Then, a technical interview with two developers where we talked Docker, AWS, SQL, and did a coding exercise. After that, a behavioral chat with the Team Lead. A fourth interview with the Director was planned but got canceled because they were busy. The recruiter said I'd get an update soon, but again, ghosted until more follow-ups led to being told they were still wrapping up with others. The next day, I was told they picked someone else. Funny thing is, the job is still up on their site, and I've had other recruiters reach out about it. I thought the interviews went pretty well, I answered most questions, except one from the Senior Manager. The lack of communication and transparency in the hiring process was really disappointing.

So, it was a campus placement thing. The first round was like 30 mins of Aptitude and then 30 mins of CS Fundamentals. After that, they interviewed the shortlisted people with 2 Technical Rounds. The questions were mostly about OOPs, Data Structures, and some puzzles. The Aptitude had 10 questions each for English, Analytical, and Quantitative aptitude, like Time & Distance and Directions. The CS Fundamentals had questions on DBMS (7Q), DSA (6Q), OS (3Q), Pseudocodes (4Q), Computer Networks (5Q), COA (2Q), OOPS (1Q), and C++ (2Q). Some questions were tough, others were super basic. They asked about Paging, CPU Cycles and scheduling, and Time complexities of Sorting. TECHNICAL INTERVIEW SUGGESTION: You really need to get better at Data Structures, learn them inside out, including how they're implemented. They expect you to focus a lot on OOPs and Fundamentals.

The process kicked off with an aptitude and computer science (CS) round, which was in an MCQ format. The aptitude part was moderately difficult, and the CS portion heavily focused on areas like Database Management Systems (DBMS), Operating Systems (OS), Computer Organization, and C++. Later, for the interview phase, the emphasis moved to Object-Oriented Programming (OOPs), Data Structures and Algorithms (DSA), SQL, and Logical Thinking. The interviewers really dug deep, making sure you understood the core concepts thoroughly. It was a tough but fair process overall, testing both technical knowledge and analytical skills in a comprehensive way.