The first step is a take-home React challenge after speaking with the recruiter. It was nothing complicated and took less than an hour.

Next, there was a live coding screen with an engineer. I did not feel this was a good assessment of a candidate's abilities. They wanted me to implement a lot of relatively simple functionality in approximately 50 minutes, which felt like it would require cutting many corners. Even then, I wasn't able to achieve a working implementation. They didn't focus much on edge cases, React best practices, or implementing good UX, and instead just wanted to see working code quickly. All in all, it was relatively simple functionality, but a lot for a one-hour interview. In my opinion, it's not a great indicator of whether a candidate can succeed in the role by writing good, modular, clean code.

The specifications were relatively clear, and there wasn't much need or opportunity for collaboration with the interviewer. There was a lot of silence throughout the interview.

Implement functionality for creating, editing, and deleting elements in a list-based system (i.e., similar to a to-do list).

Requires multiple components, state management, and input handling.