RTTS Hardware Test / Validation Engineer Interview Questions
& Process

We started with an on-campus interview, which was pretty much like a phone interview. Questions were: introduce yourself, tell me about RTTS, and any questions for them. Overall it was a pleasant initial interview. Then we got a follow-up email about whether we were chosen to head to their mid-town office for another interview. We had to fill out an application before we arrived.

I met the RTTS recruiter at a career fair at Rutgers University. They asked me which programming languages I was most familiar with. About six weeks later, I got a call for a 15-20 minute phone interview. It was pretty easy and they asked some basic programming and IT questions. The expected salary is $40-45k. The next week, I was invited for a 90-minute on-site interview at their office. I had to answer 25 questions in 40 minutes with a pencil. It's a good idea to read their website's Careers section beforehand. I also had to bring contact info for three references. IMPORTANT: RTTS requires new Test Engineers to sign a two-year employment contract because of the training they provide. Make sure you're sure before signing, as you might have to travel anywhere for long periods.

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.