Verisk Interview Questions
& Process

A recruiter reached out on LinkedIn in late October and we booked an interview. After the screening, I got a case study the next day that I had two days to complete. Once I sent it back, I had an interview with two team managers. They said I'd hear back in a few weeks, but it's been five weeks and I still haven't heard anything. I tried to reach out to the recruiter but got no response. I'm assuming I won't hear back. I've heard similar things from others about Verisk, but I decided to try anyway because the role, company, and people seemed like a good fit. But the lack of communication and care has made this a negative experience and shows a lack of professionalism and respect. I would have preferred a rejection email to complete silence. This lack of effort from Verisk says a lot. I won't apply here again and caution others.

This interview was for an intern/fresher role. Initially, the HR on the call mentioned preparing for DevOps technologies. However, during the actual interview, after I answered questions about Git, GitHub, and Jenkins, the interviewer then asked advanced Docker questions. It made me wonder how a fresher is supposed to get hands-on experience with Docker. Right now, a fresher can develop and test applications, but DevOps is a whole culture of managing both Development and Operations teams using various tools and technologies. They really expect an intern to know about DevOps technologies.

The interview process was pretty structured and thorough. It kicked off with a chat about my background and projects. Then came the technical rounds where they really dug into object-oriented programming concepts, SQL queries, database design, and general problem-solving. They were looking for both my theoretical knowledge and how I'd apply it practically, so it felt like a well-rounded evaluation of my skills and experience.

So Verisk has this interview thing that goes on for a few stages, and it's kinda different for each job, like Software Engineer, Data Scientist, or Business Analyst. 1. First, there's a Recruiter Screen for like 30 to 45 minutes, either on the phone or video. They just wanna check out your background, why you wanna work there, and if you fit the job and company vibe. 2. Then, you might have an Online/Technical Assessment, usually on something like HackerRank. It's got coding challenges (Python, SQL, algorithms), some aptitude stuff, and basics on databases/operating systems. If you're going for a data role, they might throw in some multiple-choice questions about machine learning or statistics too. 3. After that, there are usually 1 or 2 Technical Interviews where you'll do whiteboard or live coding. Expect questions on Data Structures, OOP, SQL joins, OS, DBMS, and some brain teasers. For example, they might ask you to explain OOP with a pizza analogy or give you a puzzle like the "two ropes burn in 45 minutes" one. 4. They might use a Video/Panel Interview, sometimes a one-way video for early behavioral checks, or later on, actual live chats with managers or your potential teammates. These usually dive into your technical approach, how you handle architecture, teamwork, and if you're a good cultural fit. 5. Depending on the role, you might get a Case Study / Take-Home assignment / Presentation. Data or Analyst jobs often have these, where you'll need to present your methodology and findings to both techy and non-techy folks. 6. Lastly, there could be a Final HR / Leadership Round. This might be an HR chat about salary and fit, or for more senior roles, a final talk with directors or higher-ups. This whole process usually takes about 2 weeks, but sometimes can drag on for a month. It's generally considered medium to challenging, with the technical parts needing solid knowledge in DSA, SQL, OOP, and OS. Some people mentioned communication issues or slow responses, especially towards the end. For Software Engineers specifically, expect an aptitude + CS fundamentals test, then 2 technical rounds covering OOP, DS, SQL, puzzles, and system/OS stuff. If you're from a campus drive, that's usually the path. Remember to brush up on your DSA, OOP, SQL, and CS basics, and practice explaining things clearly, especially for more senior jobs. Be ready to back up your work if you do a take-home project or case study. And don't be afraid to follow up politely if you don't hear back!