Real, anonymous reports from people who interviewed for Software Engineer at Tide, newest first and distilled into what to expect across the loop.
I applied through a referral and started with a short recruiter call that lasted about 30 minutes. We talked about my current role and why I wanted to switch, and then the recruiter lined up a code review round with two engineers.
I interviewed for an SDE-4 position and was genuinely surprised by how familiar the questions felt. When I got into the rounds, the same questions I’d already seen posted elsewhere showed up again.
The interview process typically spans about two to three weeks and consists of multiple rounds, including an initial recruiter call, a code review, and interviews with managers or peers. The timeline is generally tightly scheduled, with 1-2 days between each step, creating a brisk pace that minimizes overthinking.
A key component of the interview is the code review round, where candidates are asked to review a code snippet and provide comments. This round often involves discussing the candidate's observations and reasoning, which can be intense and requires clear articulation of thoughts.
The interviews emphasize technical evaluation, including coding challenges, system design discussions, and practical engineering tasks. Candidates should expect to demonstrate their problem-solving skills and technical knowledge in a hands-on manner.
Interviews often blend technical discussions with behavioral questions, focusing on past experiences and cultural fit. Candidates should be prepared to discuss their work history, successes, and failures in a way that aligns with the company's values.
Candidates frequently report a lack of feedback or communication after interviews, which can lead to uncertainty about their performance. It's advisable to follow up with the recruiter for clarity on outcomes and next steps.
The overall difficulty of the interview process is generally perceived as average, but candidates should be prepared for specific challenges, such as time constraints during coding tasks and the need to articulate design decisions under pressure.