A recruiter from the company reached out. Initial call was about what I was looking for, possible salary and comp range, and what they were looking for in the position they were trying to fill. Got into their tech stack and how it lined up with mine, nothing deeper than that. We agreed it felt like a good fit, and recruiter said they would set up a call with the engr manager. Engr manager and I had a call a few days later. Got much deeper into tech stack questions, no coding exercises though. Just trying to feel out your experience level and asking some get-to-know you questions based on your resume. Then they described the position and the team composition. The call went well, and the recruiter reached out the next day to say they wanted to set up the technical portion of the interview. The technical interview was split into 3 meetings of 1 hour each on the same day. 1. Talk with a tech team lead engineer, go over culture at the company, questions about your prior experiences and how they contributed to where you're at in your career development. Portion will be give to ask any questions you have. 2. Talk with an engineer on the team you're interviewing for, go over high-level API design for a common use case, in this case it was design Twitter API with basic functionality (create tweet, follow user, fetch tweets in chronological order to display in UI) 3. Coderpad session with engineer on team you're interviewing for, question was selected to be relevant to the work you're going to expect. This question was sorting maps of strings based on a timestamp, nothing crazy that needed DP or backtracking. You can ask questions to anyone. The recruiter was very forthcoming and responsive.

Great technical team members and pleasant conversations all around. Recruiter gave verbal commitment with offer details, then rescinded a few days later. Get a written offer first., don’t trust what they tell you.