
Tide Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 32 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Tide.
Software Engineer
I was referred for the role and started with a 30-minute recruiter call where we discussed my current job and reasons for seeking a new opportunity. Following that, the recruiter set up a code review session with two engineers. During this round, I was presented with a Python script for a bill payment function and asked to add comments as if it were a real code review. I appreciated their interview style, even though there was no feedback. The recruiter did send an automated-sounding email about feedback, but I never received a response.
- Can you explain the purpose of this Python script, which simulates making a bill payment from an account?
Senior Software Engineer
So after the initial recruiter screen, there are two main rounds. First is a code review. You’ll get a merge request, like, medium-sized, and you need to review it for improvements. They’ll share the code in a Google Doc, and you need to post your review comments there. They give you about 40 minutes to go through the code and write your comments. Then, for the next 20 minutes, they’ll chat with you about the comments you made and ask you questions about them. The second round is a manager interview. It's a chat with a manager at Tide, and it's pretty focused on technical skills. The first 40 minutes are for introductions and talking about tech stuff. In the last 20 minutes, you get to ask the manager any questions you have about Tide.
- Can you tell me about your experience with event-driven design, given your background with this architecture?
Software Engineer
The interviews were all really nice. First, there was an HR call, which went well, Genadi was polite and professional and helped me out. Then, I did a code review exercise, the interviewers were friendly and positive, and we discussed everything. After that, there were in-depth talks about my past experiences, system designs, and times I failed or succeeded. Everyone was positive again, and we had a great chat. They offered me a salary close to my current one, plus some equity, though I'm not sure how quickly I could cash that out.
- Review the provided code and find any logic errors.
- Review the provided code and find any security vulnerabilities.
- Review the provided code and find any design flaws.
Tide Software Engineer Interview Questions
Quoted word for word from Tide interview reports.
“What is the time complexity associated with a binary tree?”
Read reports →“Can you explain the purpose of this Python script, which simulates making a bill payment from an account?”
Read reports →“Can you define what a composite index is?”
Read reports →“Can you determine if it's possible to complete a circuit on a road with gas stations at fixed intervals, given the car's fuel efficiency and the amount of fuel available at each station, and if so, from which station should one begin the journey?”
Read reports →“What is Flutter and what is the importance of tests in Flutter?”
Read report →“What security should be followed for internal microservices communication versus external calls?”
Read report →“Can you explain the distinction between PUT and PATCH methods?”
Read report →“Could you explain what idempotency is and why it matters?”
Read report →“Could you explain the various REST HTTP methods?”
Read report →Formats, difficulty and experience
Across all 32 Tide interview reports.