
RTTS Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Which role are you interviewing for?
4 roles · 14 reportsCandidate interview experiences
First-hand accounts from people who interviewed at RTTS.
Software Engineer
I applied online and heard back about a month later. The whole thing took about two weeks, from a phone chat to a second in-person meeting with the founder. The phone call was pretty basic, covering coding questions and general programming stuff. Then, for the first in-person interview, there was a quick 30-minute quiz. It was mostly about coding syntax (C++ and SQL) and some logic problems at the end. The last interview really focused on whether I knew about the company. They got back to me within a week after that final interview.
- Could you tell me about the services RTTS offers?
- If we got a new client, what's a new service you'd suggest we offer them?
- Can you whiteboard a program that reads a file called MYFILE.txt, pulls out just the company name from each line, and then writes those names to a file called YOURFILE.txt? Assume the file can have any number of lines.
QA Automation Engineer
First, there was a phone screening, then a coding aptitude test. After that, an in-person interview. Then a background check. Finally, I met with management for a final interview where they asked me questions about my behavioral habits and also gave me a coding test to solve on a whiteboard in the language of my choice. The whole process was pleasant, professional, and the people were kind.
- Are you passionate about this industry?
Java Developer
The interview process was pretty standard. It began with a phone interview, which then led to an in-person interview where I was asked several technical questions. The entire process took approximately 2-3 weeks.
- For an array with 11 elements, what's the address of the final element?
Test Engineer
After applying online, I had an initial phone screening. This call was unannounced and conducted by an executive, not a recruiter, which made me think they lacked a proper HR department. The call focused on technical questions like C++ and web protocols, instead of assessing mutual fit. The executive said it would take 5 minutes, but it lasted 10-15 minutes. Then came the first in-person interview. The office seemed quiet and sparsely populated. I didn't see any female employees, which raised concerns about the company culture. I was given a written technical assessment with multiple-choice and handwritten coding questions. One multiple-choice question asked what RTTS stands for, with the answer in the footer. Many questions seemed pointless, like asking the meaning of the company's acronym. Next, I had a second in-person interview where I had to live code a problem on a whiteboard. A few days to a week later, they offered me the job. I declined due to concerns about the company and sketchy details in the offer letter, suggesting high turnover and a poor work environment. This company is not recommended, especially for a first job.
- Could you tell me what RTTS stands for?
RTTS Interview Questions
Quoted word for word from RTTS interview reports.
“For an array with 11 elements, what's the address of the final element?”
Read reports →“In C/C++, how do you declare a whole number?”
Read reports →“What is a for loop?”
Read reports →“What's the difference between a do loop and a while loop?”
Read reports →“Can you explain how to declare an integer variable in Java?”
Read report →“What are two tiers in a two-tier web-based architecture?”
Read report →“Can you tell me what XML stands for?”
Read report →“Can you explain the difference between a while loop and a do-while loop?”
Read report →“Could you write some code that takes integers from a user and gives back their total?”
Read report →Formats, difficulty and experience
Across all 14 RTTS interview reports.