Waste of time + terrible interviewing skills (for the most part). Honestly it was shocking how untrained the interviewers were at interviewing. Overall they framed the on-site as being a front-end, back-end and system design interview. Based on that description you'd assume you would be tested on something front-end related, something back-end related and maybe a component of a system. The technical interviews weren't related to anything you would have to code in an actual position of front-end, back-end or fullstack. Basically if you study the most popular leetcode problems for a month you'll do amazing. Will you end up using those same techniques or seeing those same problems in your actual job? Never. I'll give credit to one of the interviewers. This person was friendly, well spoken, understood it was an interviewer and gave a good sense of what it would be like working under them and on the team. The problem was obscure, but everything else aside was reasonable and gave me a sense of the culture. The second technical interviewer was unprofessional, awkward (sorry, but it's true) and couldn't properly explain the purpose of the session, question. The question, again, was just a standard tricky leet code problem. The interviewer, when asked, failed to explain the purpose of the question and how it gives any sense of the candidates technical ability to do the job. I'm not just assuming this, I asked. And the response was "it doesn't." Once I tried to engage with the interviewer about what he actually did in his position I was able to find some overlap in what I do and what he does that could create a dialogue and give him a better sense of my qualification. But he didn't really care to have a conversation about that and instead just said time's up. Also, he was definitely just lying on his bed the entire time which was awkward. Lastly, the system design interview. SDI questions are meant to be vague. They are so they give the interviewer a sense of how you'd better scope the system you're building and its requirements. Well, this person said random things the entire interview that conflicted with what he previously said. Once completely a portion of the question, he would say it couldn't do X if it were Y product until I reminded him that he asked me to do something entirely opposite. At the end of the interview I asked a basic question about culture and he mumbled something incoherently for 20-second then admitted he didn't answer the question and said it was a better one for HR. I have no clue how you would fit someone into a position and experience level based on how they conduct interviews. If you believe technical aptitude to build a scalable, maintainable system is correlated with string manipulation leetcode problems you're mistake . But as an interviewer it's easy to gauge a culture and the people in it by their ability to communicate and make decisions and this was a good example of one that is dropping the ball. I felt like I wasted an entire day with a company that has give zero effort into its interview process/strategy. Get your stuff together.