There were phone calls with the recruiter at every stage, before and after the interviews. The first phone coding interview was conducted on Google Docs, followed by an onsite interview. The interview scheduling process was inefficient and slow, but the recruiter was nice.

The phone interview involved a relatively simple coding question to be completed in a Google Doc. Afterwards, I was asked follow-up questions about generalizing the solution to a more complex problem. The interviewer had a very difficult-to-understand Indian accent and did not provide helpful responses to my clarifying questions, which resulted in me solving the wrong problem. However, either the bar for the phone interview is quite low, or the interviewer reviewed the GDoc later (I corrected the code afterward) and noticed my revisions.

To my surprise, I was invited for an onsite interview, which consisted of five 45-minute sessions. As I am quite junior, all the interviews focused on algorithms, coding, and data structures, with no systems design questions. Frankly, I found the questions to be easy and quickly devised efficient algorithms for all of them. I wrote down code that should have been correct, with the exception of one minor syntax error on the board and another small mistake that I caught and corrected.

I had practiced many coding questions beforehand and encountered variants of all the problems presented during the interview.

Afterward, the recruiter informed me that I would not be moving forward, stating "coding ability not strong enough." She did, however, mention that some interviewers provided very positive feedback. Having researched the applicant scoring process, I'm finding it difficult to pinpoint what went wrong. It's possible that several interviewers had negative impressions and gave me low scores.

Oh well. I had assumed that the absence of behavioral questions meant that strong coding performance would be sufficient for passing. It seems there is more to the evaluation process.

A bunch of fairly simple questions with string manipulations you can probably find on LeetCode and such, some tree questions, etc.

If you do a bunch of review questions covering the usual data structures, that should be good enough.