Initial phone call with the recruiter, who I thought was good at describing the job and communication in general. The next steps he described were a little different than what I understood as not being a pure leetcode round, but that could have been my fault. I unfortunately couldn't find my notes to verify. Either way, you should be prepared for tech rounds if you're interviewing! The second round is the tech round with one of the engineers on the team. Forewarning that I'm a bit biased when it comes to these types of tech interviews, so take that into consideration with what I'm saying. I have done a few hundred leetcode questions in the past (still definitely not an expert), but I don't feel performance on these types of questions is always a good indicator of a good engineer, and I definitely don't think asking leetcode mediums or hards is useful for such a small non-tech company. But everyone has their own idea of how to interview, so to each their own. My experience was somewhat similar to the other software engineer interview listed in Glassdoor, but I wouldn't go as far as to say the guy was rude/uninterested! I would mostly attribute it to the stereotypical social awkwardness some software engineers have; don't take it personal! The engineer didn't really describe the question, but he had it written out in a coderpad page. So you're going to have to sit in silence for a while trying to read through the problem and understand the skeleton code that's already written. I definitely struggled with this question, even after asking my own questions. But I was a little rusty on leetcode, so maybe someone who prepared more than me could have fared better. I tried to find this question on leetcode.com and found two that were similar. One was a hard and the other a medium, but I think the question I was asked was a variation of one or the other, or both. I'd probably lean more towards a medium, but who knows. Since I am biased (sorry!) as I mentioned above and was expecting a little bit of an easier interview, I just marked my experience as neutral. Definitely brush up on your leetcode if you want to interview and work here!

Had a lunch with the recruiter, and met with the Director of Engineering for a casual chat. Both very personable, smart, and fun people. I quickly felt that it'd be the right environment for me. I broke my interview into two days due to time constraints and spent about 2-2.5 hours both times. Each interviewer was clearly an expert in their field. Met with mostly engineers and 1 PM.