RiskVal Financial Solutions Software Engineer Interview Questions
& Process

My interview process started with an engineer for the first round. We covered some Java and database technical questions, followed by an easy LeetCode problem. It felt like a very straightforward first step. The second round was a conversational chat with HR, focusing on behavioral questions. The interviewer was great, making it a really pleasant experience. The final round was a marathon session, about 3 hours long, with two engineers. We delved into programming and database concepts, discussed my past work, and went through more behavioral questions. This was followed by a medium and a hard LeetCode problem. The interviewers in this round were also really nice, and the whole thing was quite enjoyable. However, despite the positive experience, I never heard back after the final round. They had promised an update on the hiring decision within 1-2 weeks, regardless of the outcome, but I was left in silence. After two weeks, they said they were still deciding and I'd be notified soon. It's now been two full months, and I still haven't heard anything. If it wasn't for this lack of communication, I'd say the interview process was pretty good overall.

For the software engineer role, the interview included questions about Java threads, the difference between final and finalize, design patterns like singleton and observer, when to use abstract classes versus inheritance, abstract classes versus interfaces, and also finally, final, and finalize. We touched on design patterns in Eclipse and SVN versions. They asked about Swing, functions versus stored procedures, views, XML parsing, and libraries. Additionally, there was a question about whether interfaces have constants and a multithreading question about what happens in run() when a class implements Runnable.

Applied online through their careers portal. The process involved three rounds: first a recruiter call, then a technical phone interview, and finally an onsite interview. The interviewers were friendly, making for a quick process.