Real, anonymous reports from people who interviewed for Data Engineer at Tredence, newest first and distilled into what to expect across the loop.
After an initial recruiter-style scheduling step, my process ended up being pretty straightforward: two technical rounds and then an HR-focused round. Each of my calls was about half an hour, and the interviewers were friendly and supportive overall.
I made it through two rounds and was genuinely hoping things would convert, but the third interview changed the tone fast. The interviewer was unusually rude and the communication felt off—he seemed to ask questions unclearly and then expected answers, with long stretches where he barely spoke. I ended up having to repeat my explanations twice just to get the conversation going.
The interview process typically includes an initial recruiter call, followed by two technical rounds and an HR round, with some candidates experiencing delays and lack of communication that can stretch the timeline significantly.
Technical interviews primarily assess SQL skills, data engineering fundamentals, and practical application through project discussions, with some candidates also facing questions on Python and analytics concepts.
The HR round often focuses on cultural fit, collaboration, and problem-solving, with candidates encouraged to discuss their motivations and career goals in relation to the company.
Candidate experiences vary widely, with some reporting friendly and supportive interviewers, while others encountered rudeness or a lack of clarity, impacting their overall impression of the process.
Some candidates faced case-style scenarios requiring them to reason through data problems, emphasizing the importance of structured thinking and practical application over theoretical knowledge.
Several candidates noted issues with follow-up communication, including delays in receiving updates or lack of closure after the interview process, which left a negative impression despite completing all steps.