R Systems logo

R Systems Interview Questions
& Process

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

Based on 224 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
61.3% Positive experience

Which role are you interviewing for?

30 roles · 224 reports

Candidate interview experiences

First-hand accounts from people who interviewed at R Systems.

Showing 4 of 224
R Systems logo
R Systems

Node JS and AWS Developer

Engineering · nearly a year ago

Mid Difficult Neutral experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical

I went through one virtual technical round for the Node JS and AWS Developer position. The interviewer was on time, and we kicked off the interview as scheduled. After some initial introductions, I was asked around 10 to 15 questions about AWS services like SRS, S3, CloudWatch, CloudTrail, RDS, DynamoDB, EC2, Serverless architecture, and SQS. Then, there were about 5 to 6 questions on Node.js, covering topics such as encryption, microservices architecture, thread pooling, and service workers. The main focus was on cloud architecture ideas and backend basics.

Confirmed questions6 questions
  • Could you explain how Lambda integrates with SQS?
  • What is AWS X-Ray, and what is its function when used with Lambda?
  • Can you define the Serverless Framework?
R Systems logo
R Systems

Android Lead

Engineering · a year ago

Lead Average Negative experience No offer 4 rounds
Interview process
Take home Technical screen Technical screen Technical screen
Interview formats
Technical Coding

Started with an online assessment (ChatGPT was useful). Then went through the L1 Android interview, which covered basic Android and Kotlin Coroutine questions. The L2 coding round was on Kotlin playground, where they focused more on code syntax than logic. No other technical questions were asked, which was unusual. The next round might be a client round with more technical questions. These are the rounds I know about.

Confirmed questions2 questions
  • Questions about Android fundamentals, Kotlin Coroutines, and SOLID principles.
  • A question about string manipulation, specifically finding the maximum character in a given string, to be written on Kotlin playground.
R Systems logo
R Systems

IOS Developer

Engineering · a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Technical screen Recruiter call Background check Offer
Interview formats
Technical Coding Behavioral

The interview process at R Systems was horrible, disorganized, and unprofessional. It was a complete waste of time. I went through multiple rounds, including technical assessments and HR discussions, but each round was delayed, uncoordinated, and poorly managed. The interviewers seemed disinterested and unprepared, asking repetitive questions that showed they hadn't even reviewed my resume. After clearing all rounds, HR confirmed my selection via email and assured me an offer letter would be sent soon, but it never happened. Despite follow-ups, I received only excuses, false promises, and silence. This is highly unprofessional and disrespectful. They ghosted me without explanation, which is unethical. I strongly advise job seekers to stay away from R Systems.

Confirmed questions2 questions
  • What are the basics of Swift?
  • Can you provide some Swift UI coding examples?
R Systems logo
R Systems

Azure DevOps Engineer

Engineering · more than a year ago

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

So, the first round was all about questions from my resume, the interviewer was super chill and nice. They asked about Jenkinsfile, Ansible playbook, and basics of Kubernetes, Docker, and my career stuff. Then, the second round was an advanced technical one with 2 interviewers, also very calm and professional. They hit me with tough questions on Azure, and scenario-based questions on Kubernetes, Docker, Ansible, Terraform, and some shell scripting. I got dinged there. But, I asked for another shot after a few weeks, saying I'd studied up. They gave me another chance to redo the second round with a different team. They really grilled me for an hour, even though it was supposed to be only half an hour. They asked stuff like how to build app infra, how a standard Kubernetes infra works, and how I'd build a pipeline considering both on-prem and cloud. Overall, it was a good experience.

Confirmed questions8 questions
  • Could you please write a Jenkinsfile from the beginning to deploy a Java application?
  • How would you write an Ansible playbook to deploy Nginx on 10000 servers?
  • What is the method you would use to copy a file to all these 10000 servers?

R Systems Interview Questions

Quoted word for word from R Systems interview reports.

How can I determine the IP address of my current machine using Linux commands?

Read reports

What are the different HTTP status codes and when are they used?

Read reports

What is AWS X-Ray, and what is its function when used with Lambda?

Read reports

For the string 'Sehdev', can you write code to count the occurrences of each character?

Read reports

What steps would you take to recover Jenkins if you forgot the Admin password?

Read report

Can you write a Java program to replace all the leading and trailing zeros in a number, but without using the Replace function? For instance, if the input is 0001120380.0000, the output should be 1120380, and for the input 00012.001200, the output should be 12.0012.

Read report

Can you provide a sample Kubernetes configuration file that includes 10 replicas of a pod?

Read report

What is the difference between a lookup and a joiner transformation, and which is faster?

Read report

What is POM (Page Object Model) and why is it used in Selenium?

Read report

Formats, difficulty and experience

Across all 224 R Systems interview reports.

Interview formats

Technical 45.8%
Behavioral 32.5%
Coding 14.4%
Other 2.2%
Group 2%

Interview difficulty

Easy 16.5%
Average 70.5%
Difficult 12.9%

Candidate experience

Neutral 12.2%
Positive 61.3%
Negative 26.6%

Reports by job function

Engineering 187
Analytics 13
Operations 10
Sales 6
Other 3
Marketing 2