INTERVIEWING AT TIDE
Senior Backend Engineer
At Tide, we strive for a best-in-class candidate experience. We are super excited to be moving forward on
the path to become a Tidean Engineer. We believe preparation is key to successfully navigating interviews.
We want to set you up for success! This guide is a roadmap and support for your upcoming interviews.
FUNCTIONAL SCREEN
The Functional Screen is an essential part of getting to know Tideans and the day-to-day work life in the Engineering
Team. The technical conversation will focus on topics around microservices, architecture, REST APIs, testing practices,
and databases. This is also a great opportunity for you to learn more about Tide and get some of your questions
answered.
This interview is about engineering practices and your experience. Consider having a few project examples that you can
describe, including your involvement, contribution, challenges encountered, solutions provided and technologies used.
Make sure you are in a space where you are comfortable discussing a career opportunity.
CODE REVIEW
The Code Review is a deep dive into your approach to a real world problem. We believe that code is read more often
than it is written and hence decided to incorporate it into our core assessment. As a FinTeach product company, we rely
on exceptionally well-written, testable, scalable and maintainable code to ensure a flawless user experience.
At this step, you will be meeting with your potential peers. The actual Code Review takes ~40 mins, the remaining time is
for Q&As.
You will be given a piece of code of about 80 lines written in Python. This code is written by a very junior developer,
hence, there will be a lot of areas for improvement. You will be doing the code review in a Google Doc, where you will
add comments just like you would on a PR. You can of course ask questions, suggest improvements and alternative
ways to write the code, add links to specs, guidelines, blog, document, add just about anything.
INTERVIEWERS’ ADVICE
● Read the best practices to follow while reviewing a PR, like this stack overflow post on how to do code reviews
better. You can also go through an extensive resource by Google on how to do code reviews.
● Take your time to look at the code. For the code review itself, you can even stop sharing your screen, mute
yourself and stop your camera. We want this to feel as natural and private as you would be doing a regular CR. If
you have questions, interviewers are there to help.
● Extra context: the REST API Controller will be written in Flask or FastAPI.
[Link]