T. Rowe Price Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 33 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at T. Rowe Price.
T. Rowe Price
Software Engineer Intern
Intern Easy Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical
It was all behavioral questions, nothing technical except talking about my personal projects. Mostly about how I fit the company values and experiences I've had in teams. Like, tell me about a time you had to work in a team or a time you had to problem solve or change your approach to a problem.
Confirmed questions1 question
- Can you share a time when you had to solve a problem or adjust your strategy for tackling an issue?
T. Rowe Price
Software Engineer
Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral System Design
4 stage interview process with a 30 min screening, 90 min coding exercise, 1 hr team fit, and 1 hr architecture discussion. It was a decent mix of challenges, but overall the interviewing process lacked structure, with a mix of people from different abilities and roles interviewing me. The coding exercise was high-pressure 'pair' programming where they constantly pointed out mistakes. They seemed uninterested in me as a person, only caring if I could code. I unfortunately failed the coding interview, only to discover this after completing all other interviews. It's unreasonable to ask candidates to commit more than an hour of their time; I'll let you draw your own conclusions about the company and their interview style from this.
Confirmed questions1 question
- Can you share an instance where you failed?
T. Rowe Price
Software Engineer
Mid Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Coding Behavioral
The interview process was disorganized. The recruiter reached out for my availability and I provided it. Usually, recruiters confirm before scheduling, but this one sent me a confirmation for an interview the very next day without checking with me first, and only after 10 days. She didn't even call to explain the hiring process. When I asked what to expect in the interview, like if it would be technical, white-boarding, behavioral, or resume-based, she replied, 'I don't know.' During the interviews with two individuals, there was no human interaction; they just asked questions robotically. One interviewer, who was a team lead, sounded quite rude. By the end, I was certain I didn't want to work there due to the lack of teamwork and poor interaction, which I felt reflected the company culture.
Confirmed questions4 questions
- Can you explain Merge Sort?
- Regarding hash maps, how do you prevent collisions?
- What's your estimate for the number of balls that can fit inside a bus?
T. Rowe Price Software Engineer Interview Questions
Quoted word for word from T. Rowe Price interview reports.
“What distinguishes an abstract class from an interface? Is it possible to instantiate an abstract class, and if so, why?”
Read reports →“What's your estimate for the number of balls that can fit inside a bus?”
Read reports →“Regarding hash maps, how do you prevent collisions?”
Read reports →“Can you describe the main characteristics of RESTful APIs?”
Read reports →“What are your thoughts on RESTful services?”
Read report →“Which programming languages do you like to use the most?”
Read report →“What's your strategy for writing easily testable code?”
Read report →“What was the most difficult course you took?”
Read report →“What are your thoughts on unit testing?”
Read report →Formats, difficulty and experience
Across all 33 T. Rowe Price interview reports.