Trainual Software Engineer Interview Questions
& Process

I went through the whole interview process at Trainual. It started with a meeting with the Director of Engineering, then I met two engineers to discuss my values and how I give and receive feedback. After that, there was a take-home project where I had to solve a real-world problem. The process concluded with a follow-up interview and code review of the project with two engineers. From my first contact with the recruiter to meeting everyone, the experience was very kind and thoughtful. The project involved creating a full-stack solution and was quite time-consuming. The code review was enjoyable, giving me a chance to explain my choices and discuss future optimizations. Even though I didn't get an offer, I found the process very educational and enjoyed meeting everyone.

I was interviewed by Marlowe first, who was very kind and created a welcoming atmosphere. She was direct and answered my questions, noting that any she couldn't answer would be addressed later. Her enthusiasm made me feel connected to the team. Then, Arash and Steven interviewed me and addressed the more in-depth questions. They also asked a lot about why I want to join Trainual. It was enjoyable because I'm passionate about coding. I believe interviews are a two-way street where I assess them as much as they assess me. The interview process was great, with genuinely enthusiastic and energetic people who accurately represent the company culture.

A recruiter hit me up a few times, so I eventually checked out the company and got back to them. The initial call with her was fine, but then I had to talk to some engineers from the team and it was a total snooze fest – felt like they just grabbed a list of terrible interview questions and read them out, sometimes even repeating one. They rejected me a couple of hours later, which wasn't a shocker and honestly, I wouldn't have proceeded either, but wow, that was a rough hour.