The process was very fast and the in-house recruiter is very responsive and communicative.
The interview process starts with a phone screen with the recruiter. Next is an interview with the CTO. We discussed my experience, the overall architecture at Gro, and what I'm most interested in. Be aware that they are currently growing, so there are quite a lot of opportunities.
After the CTO come the technical interviews. 2 separate coding interviews. One was basic algorithm leetcode-type stuff, the other build a very simple text-based game. Not really sure why needed two as one seems like it would have sufficed. After getting past the coding interviews, there were system design and troubleshooting interviews. System design was to build a feature into an application with global reach. Troubleshooting was basics of memory, threading, caches, and latency (think p99). There's probably an additional one or two interviews beyond these, but this is where I stopped.
Generally, interviewers seemed more interested in the types of problems that can be studied/prepared for rather than my actual experience. If you grind leetcode for a few weeks and watch some practice design interviews on youtube, that should more make up for any lack of real-world experience.