Trax Interview Questions
& Process

The hiring process was clear, well-structured, and efficient. Everyone involved was polite, approachable, and supportive throughout all stages. Communication was timely, and I appreciated receiving constructive feedback promptly after each step.

I had 4 interviews with them and was ghosted by HR. After a week and a half, I asked for a follow-up and received a reply that they needed 2 more weeks to make a decision. Of course, nobody reached out to me. I contacted HR again and never got an answer. Gosting your candidates is not normal. After having 4 (!) interviews, I expect at least a follow-up email that you chose to proceed with another candidate.

So this was a really weird interview process. It started with a phone screening that felt more like a sales pitch, especially when I asked about recent layoffs. Then there was an on-site where HR first asked me to ask them questions, which was odd so early on. After that, two developers interviewed me; they seemed more nervous than I was and weren't really prepared with questions, so I ended up asking them most of the questions. They might have been caught off guard. We then did a tour, and I had to fill out a two-page questionnaire with my bio info, most of which was already on my resume. I overheard the HR person telling others that she likes it when candidates ask her questions because it shows genuine interest. My take is that this is better for later in the process, not before actual technical interviews. Nobody cares about the PTO if they don't know if they have a shot at the job or if they even like the company. Next, I had to take three online tests: aptitude, minicog, and a personality test. Later, I met a VP of app development at a coffee shop. He mentioned the tests indicated my logical thinking wasn't the best and asked for code samples. Funny enough, this VP was supposed to be at my on-site interview. They also wanted to start a background check. Since I didn't get clear information on the next steps, I sent some code samples, which they confirmed receiving. And that was it. No further communication, and the job ad was reposted two weeks later. For someone who got that far, a simple 'no offer' would have been professional courtesy, especially for a company of this size. Compared to other companies in the area and California, this place felt like a startup with no established processes, not a serious enterprise. I'd advise developers not to waste their time here. In today's job market, this is unacceptable. There are much better companies that know how to interview candidates. I wish the company good luck.

So, Trax's interview process usually has a few steps. First, there's an initial chat with the recruiters to look over your resume and talk about your experience. If that goes well, you'll have some technical interviews, where they'll check how you solve problems and your skills, maybe with some coding or case studies for the job. You might also have behavioral interviews to see if you're a good fit with the team and how you communicate. Then, possibly a final chat with leaders to make sure you're on the same page with the company's goals.