Reached out to by a recruiter. Talked through the role and moved to the interview stage 1st round was a CV deep dive. In reality, this was a chat about the current project I was working in, the architecture and reasons why it was designed a particular way 2nd round had 3 interviews 1. A code review problem. Review a bit of code that filters a search 2. An architect design session. Design a reviews api (CRUD). How you would scale it , what db would you use , auto scaling , caching , what code language would you use etc. 3. It's called a white board exercise but it's just a hackerrank question. I was asked how to move a knight on a chessboard to a goal position. To solve it , you use breath first search. It is something I could have googled and implemented but ultimately not something I prepared for. Overall the experience was ok. I am not a fan of interview questions to implement data structures that are not really used everyday. Especially when the answers can be googled. If I can provide any advice, it would be to tell the recruiter to give you more time and don't feel pressured to go straight to interview. For an interview process like indeeds, you will need to study your college data structures and then forget them again after.