It was an on campus interview. The interviewer is very nice. Although the interviewer said I've done a very good job, I didn't make it to the onsite interview. By the way, before this on campus interview, there was an online coding, it contains 5 easy JavaScript questions to be finished in 60 minutes.

It was an interesting experience. A recruiter reached out to me asking if I was thinking of leaving my current place. I was given the choice of a take home challenge or a 45 minute onsite interview. I chose the take home which was a classic snake game written in vanilla js. I submitted it and didn't hear back for almost 2 weeks - I honestly thought I'd been ghosted. I did follow up of course, but after a week of radio silence I let it go. When they got back to me, they said I did great and wanted me to come in for an onsite. The onsite went okay - 3 panels with two people each and lunch with another employee. First panel was Language Specifics which was to make an image carousel in vanilla JS. it was confusing because the css/html was structured already so you waste time trying to figure out how it was coded and picking up from where someone else left off. Normal in a day to day job of course but jarring under a time crunch. I did passable on this, I definitely could have done better. Second panel was System Design which was a discussion on a logging company's apis. How would you structure a page in terms of components, api requests and responses, etc. This, I thought, went really well. There was a brief break for lunch Third panel was Data Structures and Algorithms which was the hardest by far. Despite it being a "collaborative interview with no right or wrong answers" the interviewer I was with wouldn't really engage as I tried to work out the problem. Overall I'd say it was fair. My only two gripes are my take home was never talked about which gives you a real 'well why bother' kind of feel. Second is they lean so much on live coding which really just weeds out people who can't code in front of a live audience. which is not really illustrative of a typical day in tech imo.