A good decision to join Tide.
A good decision to join Tide.
-
The company has a good work-life balance.
-
There are work-from-home benefits.
-
There is good growth.
-
The process includes 360-degree feedback.
-
There is a 6-month review.
Nothing I can think of. There can be some issues but those are negligible.
Additional Ratings
Was this helpful?
Tide Interview Experiences
Senior Software Engineer
I applied online. The process took 3 weeks. - First round: An intro call with a recruiter to discuss brief details about the role and the process. - Second round: A technical discussion focusing on web services, REST, databases, and some CS fundamen
Senior Software Engineer
I applied through a recruiter. The process took four weeks. The interview process consists of two main rounds, post recruiter screening: - Code Review: In this round, you're expected to review a medium-sized merge request for improvements. The code
Senior Software Engineer
I applied through a recruiter. I was given code to review and forty minutes to review about fifty lines of code in a Spring Boot controller class. There was one PUT API which takes input parameters. The topics covered included PUT vs. PATCH vs. POST
Senior Software Engineer
April 20, 2023I applied online. The process took 3 weeks. - First round: An intro call with a recruiter to discuss brief details about the role and the process. - Second round: A technical discussion focusing on web services, REST, databases, and some CS fundamen
Senior Software Engineer
Bengaluru, Karnataka, IndiaJuly 28, 2025I applied through a recruiter. The process took four weeks. The interview process consists of two main rounds, post recruiter screening: - Code Review: In this round, you're expected to review a medium-sized merge request for improvements. The code
Senior Software Engineer
Bengaluru, Karnataka, IndiaMarch 20, 2024I applied through a recruiter. I was given code to review and forty minutes to review about fifty lines of code in a Spring Boot controller class. There was one PUT API which takes input parameters. The topics covered included PUT vs. PATCH vs. POST
