Real, anonymous reports from people who interviewed for Software Engineer at T. Rowe Price, newest first and distilled into what to expect across the loop.
I started with interviews that felt pretty low-ceremony—friendly, professional, and not especially rigid about a script. The conversations ran anywhere from about 30 minutes to an hour, and there wasn’t much in the way of formal structure to the process.
After an initial stage, I reached a technical round where I was given the question ahead of time. I had about a week to prepare a solution, which made the process feel less like a timed test and more like a take-home that I could work through at my own pace.
The interview process typically consists of multiple stages, starting with a screening call, followed by technical interviews, and concluding with behavioral assessments or team fit discussions. Candidates should expect a mix of formats, including coding exercises, one-on-one conversations, and possibly an assessment center.
Technical interviews often include coding exercises, with some candidates experiencing live coding or pair programming sessions. Questions can range from basic coding tasks to more complex system design challenges, and candidates may be given prompts in advance to prepare.
Many interviews emphasize behavioral questions, exploring candidates' past experiences, problem-solving approaches, and alignment with company values. Candidates should prepare to discuss their work history and how they handle challenges in a team setting.
The overall tone of interviews can be described as friendly and professional, with some candidates noting a casual atmosphere. However, experiences vary, with some reporting a more rigid or mechanical interaction style during technical assessments.
Candidates often experience delays in communication throughout the process, with some reporting a lack of feedback after interviews. It's important to remain patient and proactive in following up with recruiters for updates.
Candidates suggest preparing for a variety of technical topics, including coding challenges and system design, while also being ready to discuss personal experiences and behavioral questions. Familiarity with the company's values and projects can also be beneficial.
