
RDI Software Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 75 interview experiences · FREE TO READ
Which role are you interviewing for?
20 roles · 75 reportsCandidate interview experiences
First-hand accounts from people who interviewed at RDI Software.
Junior Developer
The process was a bit lengthy and even tiring. I was called for an interview for another position, and I had already submitted the test. After being approved, I was informed there would be another stage, and it was scheduled for the very next day, leaving me no time to prepare. During the Live code interview, the prompt was read only once, and there was no way to refer back to it; I could only ask the recruiter, who would then re-read it. This made me extremely nervous and caused me to forget the entire prompt.
- Tell me about your experiences.
- What new things have you been learning in the market?
- How do you stay updated?
Senior Software Developer
The interview process took over a month to get started due to rescheduling, which I found to be one of the worst I've experienced. Initially, they asked for a complex solution, which felt more like solving a real problem from their backlog than a technical skill assessment. Despite applying for a senior developer role, the interview engaged more like an architect position, requiring a full system design including infrastructure, security, and communication. While developers should have these understandings, asking for a system design and then architecture exercises felt excessive for the role offered.
- Besides developing a system using SOLID and Abstract Factory with a full txt of instructions, we did a pair program to draw the end-to-end communication flow involving infrastructure, servers, and services using a flowchart.
Software Test Automation Engineer
One of the best recruitment and selection experiences. A process that was humanized, empathetic towards the candidate, and very responsible. There were 3 stages in total between interviews and assessment tests, and feedback was always received within a few days. From the first contact, I felt welcomed and seen, and the interviewer was very well-prepared and attentive. Even though it was an internship position, it was clear to me all the care and interest in making the selection process very calm and fluid.
- Could you share some details about your previous work experiences?
- What's your current academic standing?
- What do you consider to be your main strengths?
Test Automation Engineer
The interview process was quite lengthy, starting with a one-month C# bootcamp in collaboration with a tech school. At the end of the bootcamp, I completed a project. A few days later, I received a technical test from RDI to complete. Following that, I had interviews with HR and area managers, all of whom were very attentive. I felt comfortable throughout the entire process, even though it took around 4 months from the start of the bootcamp to get hired.
- The first interview asked about personal life, English level, and future aspirations (5-year plan).
- In the second interview, after the technical test, they asked about English speaking ability, posed some questions in English to be answered in English, inquired about the reasons for a career change into technology, asked about the biggest difficulty faced during the technical test, and the rationale behind tool selection for the test.
RDI Software Interview Questions
Quoted word for word from RDI Software interview reports.
“What's a way to find an odd number without using modulo?”
Read reports →“Could you implement a C function that converts a string to an integer (atoi)?”
Read reports →“Could you rotate an int array A, N times, right for positive N and left for negative N?”
Read reports →“Can you estimate the number of Taxis in the city?”
Read reports →“What are the main causes of memory leaks in C++ and how can they be identified?”
Read report →“Could you explain the YOLO architecture/algorithm and its loss function?”
Read report →“Can you explain what a collision is in a hash table?”
Read report →“In C#, do developers need to worry about memory leaks?”
Read report →“What are the differences between a stack and a queue?”
Read report →Formats, difficulty and experience
Across all 75 RDI Software interview reports.