Real, anonymous reports from people who interviewed for Software Engineer at Fivetran, newest first and distilled into what to expect across the loop.
My process was genuinely hard and stretched across multiple stages, and live coding was central to it. I completed the first live coding task and all the tests passed, which made me feel like I was on track. Even so, I didn’t go through to the next round.
The process started like it was going to be a straightforward multi-step journey: a recruiter call, then a very thorough hiring manager interview packed with technical questions. After that, I was moved into a project stage that was different from pure coding interviews. I had to create a presentation that addressed specific questions across multiple related datasets, with the expectation it would be shown to a panel that would then ask questions.
The interview process typically starts with a recruiter call, followed by a hiring manager discussion and multiple technical rounds, often spanning several weeks. Candidates reported a mix of coding, design, and behavioral interviews, with some experiencing delays and rescheduling issues.
Candidates faced various technical assessments, including live coding sessions and HackerRank-style problems, often focusing on Java, data structures, and algorithms. The difficulty level ranged from medium to hard, requiring candidates to demonstrate problem-solving skills under time pressure.
Some candidates encountered a project presentation stage, where they had to analyze datasets and present findings to a panel within a tight deadline. This round was noted for its abrupt cancellations and perceived lack of respect for candidates' time.
Behavioral interviews were included to assess candidates' soft skills and cultural fit, often focusing on past experiences and problem-solving approaches. The atmosphere during these interviews was generally described as friendly and respectful.
Candidates reported mixed experiences regarding communication throughout the process, with some feeling well-informed while others experienced vague updates or a lack of feedback after interviews. This inconsistency affected overall candidate satisfaction.
The overall difficulty of the interview process was perceived as challenging but fair, with candidates suggesting that thorough preparation, particularly in coding and system design, was essential. Many reflected on the importance of practicing coding problems in advance.
