Real, anonymous reports from people who interviewed for Software Engineer at Tredence, newest first and distilled into what to expect across the loop.
I started with a recruiter touchpoint, and about a week later I was pulled into a technical screen. From there, the process turned into a sequence of hands-on rounds—there were three technical discussions and then, at their office, they asked me to do an additional technical round. The difficulty landed in the easy-to-medium range overall, and the topics kept circling around the same stack: React and Node.js, plus SQL.
My process was heavy right from the start. I had an aptitude plus coding round where the coding problem was honestly too hard for how it was described, and the complexity of it felt like it was tangled up enough that I couldn’t even get a clear handle on what the question was asking. I wasn’t able to crack it.
The interview process typically consists of multiple rounds, starting with an aptitude test followed by technical discussions. Candidates can expect a mix of coding challenges and project discussions, often culminating in an HR round.
Interviews heavily emphasize core technical skills, including data structures and algorithms (DSA), SQL, and web technologies like React and Node.js. Candidates should be prepared for both theoretical questions and practical problem-solving scenarios.
The overall difficulty of the interviews varies, with some candidates finding them easy to medium while others felt challenged, particularly in coding rounds. The experience can feel rushed or well-paced depending on the interviewer and format.
Candidates reported varying levels of communication quality, with some experiencing friendly and supportive interactions while others found the format impersonal or awkward due to technical issues. Clear communication is emphasized throughout the process.
Candidates often leave interviews without clear feedback or understanding of their standing, especially after technical tests. Some received offers, while others were surprised by rejections based on experience requirements or other criteria.
Candidates should prepare for a mix of coding, theoretical questions, and discussions about past projects. Familiarity with the required tech stack and practicing problem-solving under time constraints can be beneficial.