How many rounds is the T. Rowe Price Quantitative Analyst interview process?

Candidates report 3 stages: Recruiter Screening, Technical Assessments, and Panel Interactions. The interview process section above breaks down what each stage covers.

How much does a Quantitative Analyst at T. Rowe Price make?

Reported compensation for Quantitative Analyst roles at T. Rowe Price ranges from roughly $150k base to $225k total per year, varying by level, team, and location.

What topics come up in the T. Rowe Price Quantitative Analyst interview?

T. Rowe Price Quantitative Analyst interviews most often cover Quantitative Analysis, Investment Research (Retirement Research), System Design (Interview Round), Problem Solving, and Coding Assessments, based on topics extracted from real candidate reports.

What questions does T. Rowe Price ask Quantitative Analyst candidates?

Recent candidates report questions like "Moving Average for Time Series" and "Handling Missing and Noisy Data". The question bank above tracks 20 questions for this role, ranked by how often they come up in T. Rowe Price interviews.

T. Rowe PriceQuantitative Analyst

Updated Mar 23, 2021

T. Rowe Price Quantitative Analyst Interview Experiences 2026

Real, anonymous reports from people who interviewed for Quantitative Analyst at T. Rowe Price, newest first and distilled into what to expect across the loop.

Get your personalized T. Rowe Price Quantitative Analyst prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

> 1 year

Easy Negative Baltimore, MD

The process started with an online coding assessment from a third party, and it felt pretty easy overall. After I completed that, I moved into a technical Zoom interview with a senior quant developer where we talked about data structure and my work experience.

Next came two separate Zoom meetings with four team members total. The first of those focused on realtime coding and felt fairly simple. The second meeting was about experience and system design, and it threw me off because the interaction felt uncomfortable and tense—one interviewer came across as extremely disengaged and rude, and there were awkward pauses where it felt like we were just staring at each other.

> 1 year

Difficult Positive Baltimore, MD

My process stretched across several days and ended up being quite long. It included a panel interview, followed by a series of one-on-one discussions, and it blended technical and behavioral questions throughout.

For the technical parts, I did whiteboarding for coding questions and also case analysis, which made it feel more like problem solving in context rather than just algorithm memorization. I also spoke with team members from both the immediate group and an adjacent one, so I got a sense of how different parts of the organization thought about work.

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.