RWS Group logo

RWS Group Software Engineer Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
58.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at RWS Group.

Showing 3 of 12
RWS Group logo
RWS Group

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Recruiter call
Interview formats
Technical Coding

The interview process had a total of 4 rounds. The first round was a written aptitude test with some coding questions. The second round was a technical interview where they asked basic questions about Java, Python, and databases, and also tested some database queries. The third round focused more on major and minor projects and also included some coding questions. The final round was with HR.

Confirmed questions5 questions
  • Could you answer a basic Python question about strings and lists?
  • Do you have any questions about Pandas and Numpy?
  • Were there some basic questions about Java, Python, and databases asked?
RWS Group logo
RWS Group

Associate Software Engineer

Engineering · more than a year ago

Entry Average Neutral experience Decline offer 1 round
Interview process
Technical screen
Interview formats
Coding Technical

Interview was conducted on MS Teams. The interviewer asked me to join from my laptop, not my phone. It started with introductions, then questions on DSA, programming, and DBMS. The interviewer then asked me to open an IDE, and they sent a question in the comment box, which was from GFG. I solved it on my Eclipse IDE. After that, they asked me questions on other topics.

Confirmed questions4 questions
  • What is the difference between Final, finally, and Finalize?
  • Can you explain the String Pool?
  • Tell me about data types.
RWS Group logo
RWS Group

Software Developer

Engineering

Mid Difficult Positive experience No offer 5 rounds
Interview process
Take home Technical screen Technical screen Recruiter call Offer
Interview formats
Coding Technical System Design Behavioral

The hiring process was pretty smooth and professional. It started with submitting my application online. After that, I had to do a technical test that was all about coding, algorithms, and data structures. Then, I went through two technical interviews with senior engineers where we talked about problem-solving, did some coding exercises, and discussed system design. The people interviewing me knew their stuff and were easy to talk to. After the technical parts, there was an HR interview to see if I'd be a good fit for the team and talk about my career goals, which felt pretty casual and direct. Lastly, I had a quick chat with some higher-ups about the offer. The whole thing took about three weeks and it felt like a good balance between testing my technical skills and seeing if I'd fit in with the company culture.

Confirmed questions2 questions
  • Could you walk me through a difficult project you were involved in, detailing your problem-solving approach?
  • Tell me about a challenging project you worked on and how you approached solving the problems that arose during the project.

RWS Group Software Engineer Interview Questions

Quoted word for word from RWS Group interview reports.

What is the difference between Go routines and channels compared to an OS thread?

Read reports

What is the difference between Final, finally, and Finalize?

Read reports

Could you answer a basic Python question about strings and lists?

Read reports

Can you differentiate between goroutines/channels and OS threads?

Read reports

Could you explain what goroutines and channels are and how they differ from OS threads?

Read report

Can you solve the Three Sum problem without employing a greedy approach?

Read report

Formats, difficulty and experience

Across all 12 RWS Group interview reports.

Interview formats

Technical 41.4%
Coding 27.6%
Behavioral 24.1%
System Design 6.9%

Interview difficulty

Easy 8.3%
Average 58.3%
Difficult 33.3%

Candidate experience

Positive 58.3%
Neutral 16.7%
Negative 25%