TrustArc Interview Questions
& Process

The interview process was pretty standard, and I made it to the final round but didn't get an offer. It involved a screening, a hiring manager interview, a take-home assignment, an interview with a marketing executive, a teammate interview, and then the offer stage. I was hoping to get the offer, but they decided to move forward with other candidates.

I applied for this role and a recruiter reached out to me for a screening interview. When she sent me the link, the options were in Philippines time zone, so when translated to Eastern time zone, the only options were either 2am/3am, or 10pm/11pm at night. When I followed up with the recruiter to ask if these were the only times available, she responded with "you can pick a time that works for you", and resent me the link with the same time options. For a company based in the US, it is unacceptable to expect a candidate to hop on a call late at night or in the middle of the night, and provide them with NO other options.

The interview process kicked off with a recruiter call, followed by a chat with the Hiring Manager. They asked me about HTML, CSS, and JavaScript, and I had to do a simple task to move a div. Then, I had a third round with three TAMs. The first part was a technical interview with a TAM, focusing on technical understanding and a small debugging task. The second part was a behavioral interview with a Senior TAM, and the third was another behavioral interview with a lead TAM. The final round was with the Chief Customer Officer, who was quite unfriendly. I think I might have upset her somehow, as she ended the interview abruptly and said the recruiter would contact me. I emailed the recruiter after about 4-5 business days and received a rejection email. The CCO was the only hiccup; she might be good at her job but not great at interviews.

I went through 4 interviews in about 10 days. Two calls were on the phone, and two were in person. It started with a recruiter call for a basic tech screen where they asked about core Java concepts like inheritance vs composition and collections. Then, a senior engineer did a more in-depth phone interview covering Java concurrency, MapReduce, and database interaction. The onsite part had two interviews: one was a whiteboard session focused on advanced Java topics, some of which were obscure knowledge-based questions. They also gave me a 90-minute coding challenge to simulate an elevator. Finally, I spoke with the VP of Engineering about general topics, not technical ones. No offer was extended. The process was efficient and professional, likely because they're expanding their team and may not have defined projects yet.