Rainforest loop Experience - Frontend, L5, 12 YOE, Rejected

Big tech interview q's are valuable information so i'll do my share and do a knowledge dump here. I wrote a post 2 years ago [https://www.reddit.com/r/learnprogramming/comments/ycr64a/amazon_intervie

Big tech interview q's are valuable information so i'll do my share and do a knowledge dump here. I wrote a post 2 years ago <a href="https://www.reddit.com/r/learnprogramming/comments/ycr64a/amazon_interview_experience_frontend_l4_10_yoe/ returns an array of elements that would include <div color='blue'> --first time seeing this Q. was thrown off but i tried a recursion strat similar to above. i ran out of time to get nice code so it was rough. i got the logic and overall concept but interviewer prob expected better code. -System Design - Game app. Two workflows. 1st- word plus 4 pictures, pick the correct picture that matches the word. 2nd- picture with text box, type correct word in text box. after submit will show correct or incorrect screen. --I followed the standard outline for sys design like Functional reqs, non-func, API... etc. Odd experience, as i was starting the Functional reqs, i was interrupted and asked about architecture. As i was going thru API, i was interrupted and told me 'ur repeating the same thing in functional reqs' and i said i was going thru a detailed implementation. We talked about CDN (s3 vs locally hosted) and i missed marks on those questions (Pros and cons). Sucks, i did what i could i felt i did ok but i could tell it wasn't good enough, at least i learned something. --(lol) i started mentioning db and he was like "no. forget db. this is frontend. i dont care" Behaviorals, questions included: -tell me bout a time when you disagree with rest of team and how you resolve -Customer wanted something, but, what he wanted wouldn't have solved his issue -Took a big risk -Fresh perspective on a topic that was opposite of teams and you were right -Challenging problem that took a long ass time to solve Not going in full detail, but my stories were vastly improved from 2 years ago, interviewers seemed pleased with them. My best stories were: - troubleshooting sister npm package subdependencies and having to go to github and collab with the authors. -Pushing for elimination of a 996-1198px breakpoint because it's a limbo breakpoint nobody uses. desktops are all 1280px+ ---- Overall i felt i did pretty well, much better than last time, but, i was not confident i passed since i had some hiccups. And the result was i didn't. The rejection message was an automated email, no recruiter call. it's so efficient and minimal human interaction. Welp it is what it is, i'll try again next time but i'm feeling fine! Any discussions feel free to comment and hope this helps. PS- I asked the interviewers their opinion on 5 day RTO and ALL 5 OF THEM SAID I love it I sometimes went 5 days in office anyway! (... lol)