First round is a technical assessment sent via Coderbyte. Multiple choice questions around various AWS products (mostly serverless) followed by two Leetcode medium style coding questions. Second round consists of a coding exercise. It's fairly straightforward; you're essentially just executing a left join on two Python dictionaries. There's an emphasis on memory utilization since the company is run on a serverless stack. There's then a separate system design interview. I honestly don't know how to describe this because it's about as hand-wavy of an interview I've been in as far as system design goes. Just know how various serverless AWS products work and you should be okay here. Then after that are the CEO and CTO interviews, mostly around fit. The CEO was pretty fun to talk to and I really enjoyed the conversation. The CTO was...nice enough, but there were times where it felt like he was reading off a script or really just rattling off a bunch of buzzwords and seeing how familiar you were with them.

Passed recruiter screen, had a call with CTO where I was asked about a series of buzzwords related to data pipelines. CTO immediately showed lack of both technical and leadership skills.