RDI Software logo

RDI Software Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 27 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
77.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at RDI Software.

Showing 3 of 27
RDI Software logo
RDI Software

Software Developer

Engineering · nearly a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Behavioral Technical

I applied through the job link. It took a while for them to call me for an initial chat. However, I found everyone I spoke with to be very helpful and pleasant. There was more than one technical interview, which was not a problem.

Confirmed questions1 question
  • Por que você estava procurando sair da empresa que estava anteriormente para entrar na RDI?
RDI Software logo
RDI Software

Senior Software Developer

Engineering · a year ago

Senior Difficult Negative experience No offer 3 rounds
Interview process
Take home Technical screen Presentation
Interview formats
Coding System Design Presentation

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.

Confirmed questions1 question
  • 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.
RDI Software logo
RDI Software

Software Developer

Engineering

Entry Difficult Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Technical screen
Interview formats
Behavioral Technical Coding Other

First, there's a meeting with the interviewer to check your fit with the company. Then, a call with the manager, where they ask about your development experience, your knowledge regarding the job requirements, and have a short chat in English to assess your speaking skills. After that, you're given a crazy technical test, requiring production-quality code with tests and full documentation in just 48 hours. The process itself is good, it's just a shame the technical test's difficulty level was totally mismatched with the role.

Confirmed questions1 question
  • How much experience do you have with the technologies required for the position?

RDI Software Software Engineer Interview Questions

Quoted word for word from RDI Software interview reports.

Could you implement a C function that converts a string to an integer (atoi)?

Read reports

What are the main causes of memory leaks in C++ and how can they be identified?

Read reports

Could you explain what Dependency Injection is and how it works, and provide an example of when it would be appropriate to use?

Read report

What qualities do you think a good boss should possess?

Read report

What's your self-assessment of your English proficiency?

Read report

Formats, difficulty and experience

Across all 27 RDI Software interview reports.

Interview formats

Technical 38.8%
Behavioral 31.3%
Coding 20.9%
Presentation 4.5%
System Design 3%

Interview difficulty

Easy 11.1%
Average 63%
Difficult 25.9%

Candidate experience

Positive 77.8%
Negative 18.5%
Neutral 3.7%