Tide logo

Tide Backend Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 5 interview experiences · FREE TO READ

2 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Tide.

Showing 3 of 5
Tide logo
Tide

Backend Engineer

Engineering · nearly a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Coding Technical

The initial HR interview was fine, pretty standard. Then I had a code review test that took about 60 minutes, which was also okay and pretty typical. However, after that, they didn't bother to let me know they weren't moving forward with my application. Getting rejected is totally fine, but it's super unprofessional to not inform someone about the hiring decision. It's been 3 months now and still no word.

Confirmed questions2 questions
  • Reviewed a simple code snippet.
  • Regarding the order of updating databases, should the internal database be updated before the third-party one, or the other way around, given that changes must be reflected in both?
Tide logo
Tide

Backend Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Technical Coding Behavioral

I had a quick chat with the recruiter first to go over the basics. Then, there were two technical interviews. One involved reviewing a short piece of code (40-50 lines) in Google Docs. They discussed what I missed and asked for more details on my suggestions, alternative approaches, and related topics. The other technical interview covered my experience with different technologies and architecture styles, plus some questions about working with people. The whole thing moved pretty fast, and I got some helpful feedback at the end.

Confirmed questions3 questions
  • What distinguishes PUT from PATCH, and in what scenarios is each appropriate?
  • Can you describe a type of individual you'd prefer not to collaborate with or have on your team?
  • If your manager happened to be that specific type of person, what would be your course of action?
Tide logo
Tide

Backend Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding

I was invited for a code review round. The interviewers seemed uninterested from the start. They asked for introductions just for formality and didn't even properly explain my question about their company. I spent 40 minutes commenting on a Google Doc they shared while they remained silent. We only had about 3 minutes for discussion at the end. Their question was why I didn't consider concurrency. It was a very abrupt end to the interview. Even though I wasn't rejected, I knew I didn't want to work with them due to their attitude. The HR person also seemed out of touch, asking how often I do code reviews. When I said I only did peer reviews every sprint, they told me there's no point if I can't pass their coding round, implying it would be a waste of their time. I should have realized then. Folks, just go home, you aren't fit for the role. No one smiled or sounded enthusiastic.

Confirmed questions1 question
  • Code review of sample code in Google Docs

Tide Backend Engineer Interview Questions

Quoted word for word from Tide interview reports.

What distinguishes PUT from PATCH, and in what scenarios is each appropriate?

Read reports

Regarding the order of updating databases, should the internal database be updated before the third-party one, or the other way around, given that changes must be reflected in both?

Read reports

Can you describe a type of individual you'd prefer not to collaborate with or have on your team?

Read report

If your manager happened to be that specific type of person, what would be your course of action?

Read report

Formats, difficulty and experience

Across all 5 Tide interview reports.

Interview formats

Coding 45.5%
Technical 36.4%
Behavioral 9.1%
System Design 9.1%

Interview difficulty

Easy 0%
Average 100%
Difficult 0%

Candidate experience

Positive 40%
Negative 60%