The interview process in it's entirely was very long between phases, and particularly unfriendly to people with anxiety problems due to the limited time available in the panel coding interview setup, and misleading instructions on how to prep. They also seemed confused as to what position I was even applying for, which felt very odd to me as I was forwarded by their internal recruiter. Interviewing for a full stack position, was given a completely reasonable tech screening (Simple Hackerrank web call example + manipulate object, do the REST API certify test to prep as it's fairly similar) with a very good interviewer. Very enjoyable and lots of good feedback. The proceeding technical panel interview, however, was very irritating, filled with random syntax gotcha questions about irrelevant languages or cloud components that simply were listed on my resume/linkedIn but not used for the position in question (e.g. many random python syntax questions for a Javascript/C# position, or random trivia about why you would use an AWS lambda over some unspecified alternate option when AWS experience was not previously mentioned). The hour-long coding portion was also delayed about 20 minutes, leaving only 35 min + 5 min discussion to actually complete a fairly average coding challenge that was nonetheless (again) not relevant for a full stack position. Technical prep take-away: - Do not list any languages on your resume that you cannot confidently answer trivia questions for off the top of your head. Would I to do it again, I would remove any languages not specifically relevant to the position, or otherwise google common interview questions for any language on the submitted resume. - Don't focus entirely on prep for the specific role, such as API architecture and async web service demos for a full stack position, but rather the generic data structure questions you might find on most leetcode websites.