After an initial phone screen, was asked to build a basic application against an API they provided. The API was designed to be inconsistent and throw different sorts of errors (as mentioned by other interviewers), with the aim being to build a UI that was durable against unexpected responses that could result from upstream issues. I thought the test was a breath of fresh air from the typical coding assessments I've had in other interviews, which typically either focus on abstract topics unrelated to the core job requirements or else are too surface level to accurately assess a candidate's skill. The particular focus on how to make a UI durable when APIs provide inconsistent or invalid responses was a practical thing to test when the development environment is as API-centered as it is now, and showed me that the company is focused on the end-user experience. After I'd submitted my response, I had a follow-up call with one of the teams engineers to review my submission. We discussed the solution I'd implemented and pair-programmed some changes. After that call I had an on-site during a sprint kickoff, and was offered the position shortly after. From when I submitted the assessment to my first day the process took roughly 3-4 weeks.