Quantitative Risk Management logo

Quantitative Risk Management Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 22 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
40.9% Positive experience

Which role are you interviewing for?

7 roles · 22 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Quantitative Risk Management.

Showing 4 of 22
Quantitative Risk Management logo
Quantitative Risk Management

Actuarial Financial Analyst

Finance · more than a year ago

Entry Difficult Neutral experience No offer 3 rounds
Interview process
Recruiter call Onsite Background check Offer
Interview formats
Behavioral Technical Case

I sent my resume and cover letter in, and heard back from HR about a week later about having a casual lunch with someone in the role I applied for. We met up for lunch and they asked about my background, skills, and interest in the company. They invited me back a couple of weeks later for an in-person interview, where I had 4 1-on-1s. A few weeks after that, I met two more people who were out of town during the first interview. It's been a few weeks since then and I haven't heard back, so I'm not expecting an offer. They seem to be looking for someone entrepreneurial, a self-starter, and someone they can get along with.

Confirmed questions8 questions
  • Regarding your consulting background, can you detail your client interaction experience, especially since this position requires providing actuarial customer support for our risk management product?
  • Please prepare to discuss every single bullet point on your resume in detail, as we will be covering it thoroughly.
  • We noticed a poorly worded statement regarding one of your internships; could you elaborate on that?
Quantitative Risk Management logo
Quantitative Risk Management

Software Developer

Engineering · more than a year ago

Entry Difficult Neutral experience No offer 5 rounds
Interview process
Technical screen Recruiter call Group Presentation Technical screen
Interview formats
Coding Behavioral Group Presentation Technical

It was a really organized in-person interview. First, they reviewed the code I wrote for a given problem. The reviewer really dug into parts of the code where they thought I didn't fully grasp the technical details, focusing on very minor things. This was to gauge how I react to criticism and how quickly I can learn. Next, I met with the company owners who were just there to give their final approval on new hires, and they didn't know much about me or the role. I had a question ready for them about the topic, which got them talking and sharing ideas. Then, I had an interview with two developers who would be my colleagues, to see if we'd get along. After that, two project managers asked me to present my design at a high level, to check if I could step back from the details and discuss it from a business perspective. Finally, I interviewed with the architect. This was the opposite of the code review. Instead of focusing on what I didn't know, they asked about my strongest language and we went deep on that, even though it wasn't the primary language for the job. I felt good after the interviews, but didn't get the offer because I had expressed interest in roles beyond the one I applied for, which I also communicated during the process. My advice for others is: they aren't looking to help you grow your career. They want to hire you for a specific job and keep you there as long as possible. So, if you're applying for something like a receptionist, emphasize that answering phones is your passion and you can't imagine doing anything more fulfilling.

Confirmed questions2 questions
  • Can you provide a single line of C++ code to reverse a given string?
  • Can you reverse a string using a single line of C++ code?
Quantitative Risk Management logo
Quantitative Risk Management

Financial Risk Analyst

Finance

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Panel
Interview formats
Behavioral Technical Case

Someone from the company introduced me to the role, and then I had 3 interviews. The first interview was with VPs and manager-level people, where we had a lot of behavioral questions and casual chats. The second interview was with the team I'd be working with, and they asked a lot about fixed income knowledge, derivative pricing, and my programming experience, mainly about databases and basic programming concepts. The third interview was with the Executive VP and a technology manager.

Confirmed questions1 question
  • How would the yield curve change given a specific economic condition, or conversely, what economic condition would cause a given change in the yield curve?
Quantitative Risk Management logo
Quantitative Risk Management

Product Analyst

Analytics

Entry Average Neutral experience No offer 3 rounds
Interview process
Onsite Background check Offer
Interview formats
Technical Behavioral

The interview process took too long. I had to make 3 distinct trips to the company (they didn't pay for any of them). In total I was interview by over 8 different people. Interviewers were very kind and nice people but I think some of my interviews were entirely redundant. Basically repeated the same thing. After the final interview, they asked for my SAT exam result, which I never took.

Confirmed questions1 question
  • If you were given a triangle, what would be your verification method?

Quantitative Risk Management Interview Questions

Quoted word for word from Quantitative Risk Management interview reports.

Can you provide a single line of C++ code to reverse a given string?

Read reports

How would the yield curve change given a specific economic condition, or conversely, what economic condition would cause a given change in the yield curve?

Read reports

What are the various types of risks that insurance companies encounter?

Read report

Explain how a bank generates revenue and its operational framework.

Read report

Formats, difficulty and experience

Across all 22 Quantitative Risk Management interview reports.

Interview formats

Technical 40.4%
Behavioral 34.6%
Coding 7.7%
Case 7.7%
Presentation 5.8%

Interview difficulty

Easy 9.1%
Average 50%
Difficult 40.9%

Candidate experience

Negative 18.2%
Positive 40.9%
Neutral 40.9%

Reports by job function

Finance 9
Engineering 6
Analytics 4
Consulting 2
Other 1