Interview with the recruiter, with the usual questions. Very pleasant to talk to.

The coding interview started with brief introductions and went straight into the problem statement, which was hosted on Hackerrank.

It seems the problem statement always changes per interview. Some problems seem to be relevant to what you'd be doing in production (e.g., call APIs and do something with the data), and some are reminiscent of the early days of learning programming (e.g., create a tic-tac-toe game).

The challenge wasn't particularly hard but did throw me off, thus I got flustered and couldn't even recall the simplest things.

Questions asked to the interviewers were about whether they get involved or know much about their AWS infrastructure. It seems that they only focus on building code, so if you're looking to just code, this is the right place for you. If you're handling more than just code, e.g., cloud infrastructures, pipelines, or overall system design as a software engineer, then this probably isn't the place for you.

Code a dynamic tic-tac-toe game.