RDA Corporation Interview Questions
& Process

The interview process was people focused and organized in a timely manner, with a professional approach. The people and hiring manager were kind. It was no longer than 1 hour and had 4 stages. We had discussions about expertise, teams, project management phases, collaboration aspects, and project portfolios and programs.

What a wild ride! Started with a chat with a super nice internal recruiter about my past work - I thought I nailed it, and boom, got links for online multiple-choice tests right after. Got good feedback super fast, and was set up for round two within 2 hours. Round two was two days later - a full hour of tech questions from a really cool Principal Architect. He focused on concepts and real-world scenarios, not just code syntax. And again, lightning fast feedback - within 10 minutes, they said I'd have a final interview with a VP soon. But then, the next morning, the recruiter called with a curveball. Apparently, the job description was misleading. They actually wanted React experience, not Angular as advertised, and serious Azure/cloud architect level skills, none of which was mentioned initially. To top it off, the VP wasn't cool with my remote location, even though it's a remote job! I was confused for a bit, then just found it hilarious. Talk about a colossal waste of time for everyone involved, especially asking about Angular when they needed React! This whole thing was just bizarre, but hey, what do you expect from a .NET consultancy shop? Makes sense why I never bothered with them.

The interview process was thorough and very professional. I went through several rounds, including a presentation of my Business Analyst artifacts to a panel. Everyone I spoke with — from the recruiter to the leadership team — was kind, engaged, and clearly passionate about their work. The questions were thoughtful and focused on real-world BA practices, collaboration, and communication. The final panel interview was structured but conversational, which made it a great experience overall. While I wasn’t selected in the end, it felt like there may have been a strong candidate identified early in the process. Still, I appreciated the opportunity and the respect shown throughout. I’d recommend future candidates come prepared to discuss real project examples and how they approach stakeholder collaboration.

There are multiple phases. First is a phone screen with the hiring manager about your personal experience/interests. Then an email with a link to a quick programming quiz. After that, in-person meetings with higher-ups, including a difficult/in-depth technical interview. Then an in-house coding exercise. Finally, a meeting with an executive to discuss the role.