SRT Group Interview Questions
& Process

Applied online for one of about a dozen postings on LinkedIn, some with lots of activity and some without. Had a phone interview first, then an in-person interview that was scheduled, then cancelled, then rescheduled, making me think they don't do this often. HR asked canned questions. When I asked HR for the benefits package, they said it's not shown until an offer is accepted. A technical interviewer described the benefits. The technical interview went well, but then I was told the job posting was on hold due to a business issue. A couple weeks later, they called with a low offer for a different job title. I clarified that it wasn't the title I interviewed for, and they said they'd check. They called back with an offer for the job I interviewed for, but due to the delays, I had already accepted another local company's offer for 10% more. I asked if they could match, and they said no.

The interview process started with an introductory call. Scheduling the next interview was complicated by court duty. I was upfront about the summons, and 'Amanda' promised to reschedule around it. After my court duty ended, Amanda asked if I could meet on February 9th at either 12 PM or 2 PM, and I agreed. I was available at both times on the scheduled Friday, but no one from the company showed up or contacted me. They completely ghosted me, which, as a military veteran, I found incredibly disrespectful and a waste of my time.

I went through a few interview stages for this role. First, there was a 30-minute phone screen with HR. Then, a 45-minute tech test over screen share. Finally, a 1-hour onsite interview. Honestly, I was pretty unimpressed. The office felt more like a warehouse than a proper workspace. The technical interview focused too much on coding a specific thing in a specific language, instead of assessing software design and building skills. During the interview, the HR person actually said they needed to hold my phone so I wouldn't cheat, which I found amusing because a good tech test shouldn't rely on that, and in the real world, you use the internet when you forget specific details. The biggest issue for me was the heavy HR involvement, which felt like a lot of unnecessary fluff based on my 20+ years as a consultant. I didn't feel like I'd want to work there. Despite the HR focus, I never heard back after the interview, so I assume no offer was made. I had given a high salary expectation, which they likely wouldn't meet given their office situation. Some of the tech folks seemed decent, and in a different setting, I might have learned from them. But the strong HR push, the phone confiscation, and the dismal office environment made it a bad fit.

Had a quick behavioral chat with the recruiter, then interviewed with the manager and three software engineers. They wanted to hear about my projects on my resume, my coursework, and if I had any knowledge about the company and wifi/bluetooth. They also asked me to explain OOP.