Thomson Reuters Software Engineer Interview Experience: HackerRank, design, and uneven interview day

The process took about a month. Scheduling was generally smooth despite several availability reschedules, but one hour-long technical day felt one-sided because the interviewer did not seem to be listening and appeared to steer toward preselected answers.

I started with a HackerRank programming assessment and later had coding, system design, and job-fit discussions. The design prompt extended a project I had built by adding functionality. I expected a LeetCode-style coding problem but got something closer to competitive programming: I reached the logic but struggled to implement it. I could discuss my experience in the job-fit part but did not pass the final round. HR was cooperative, yet the live interactions made the important moments feel harder than the structure suggested.

Location: Bengaluru. Overall feedback: neutral. Offer status: no offer.