Before I start, I do want to say that you can clear Hubspot interview easy if you read the interview questions on here and do research even on leetcode or elsewhere. I have a feeling they know interviewers know what technical questions are coming, and yet have not changed the interview questions since... forever, and for a reason too: Will the person be a good "Hubspotter". As long as you know your basic data structure and algorithms, you can clear technical interview easy. I really believe the behavioral parts are the most important part, basically they want to see if you're a cultural fit. And I have a feeling this is how most interviews at most places go. Yes even FAANG. Ok now: Upon application, you'll receive an online assessment. The assessment can be hard depending on your background. It has to do with getting info from a rest endpoint, modifying it, and then sending it back. You have to sort some data in between getting and sending. If you do your "research" you can easily solve this. Hint: Check leetcode or github, but try to understand and don't copy! (in case you're asked about your solution). Once you successfully finish the OA, a recruiter will request to talk to you, ask you some general questions, and give you the next steps. Be nice, polite and friendly. People do not like monotone, nonchalant voices. Speak like you want to be there. Your recruiter will describe the interview process, which is one 1hr behavioral + technical, then another 1hr behavioral + system design. Again, the behavioral is probably the most important here, because if you managed to do the OA successfully, and do your research, you will clear the interview. A common misconception people have is that they think they gave the exact right solution, either from researching and knowing exactly what the solution is, or actually knowing the solutions. You have to be able to articulate and talk through your solution, and actually know what you're talking about. Take the interviewer's suggestion, idc if you read grokking the system design. Do not be pompous, do not be a know-it-all, but show knowledge at the same time! If your interviewer says "for now lets go with a relational database and not a nosql database", but you know the best way is to go with a nosql database, tell them why you were going to go with a nosql database politely, then go with the freaking relational database for now. It's not about being right, it's about finding solutions to the problems the interviewers are throwing at you! Furthermore, learn the STAR technique for answering your behavioral questions. This is VERY important. Show humility and for the love of gosh do not sh*t talk previous coworkers/people you collaborated with when answering these questions. Don't blame people and don't make yourself out to seem like you can do no wrong. Your recruiter should tell you what questions to expect on the behavioral. PRACTICE THEM WITH THE STAR TECHNIQUE. Again, the behavioral is really the only barrier between you and an offer, assuming you have decent DS and Algo knowledge and have read the interview questions on here, and have practiced them. My interviewers and recruiter were very nice and friendly. If you manage to clear these coding + system design + behaviorals, AND they deem you are a cultural fit, polite and not an a**hole, you will get an offer. This should be one of the easiest new grad interview, because there's so much of the process out there on the internet, and on here on glassdoor! Put the time in if you want that easy 6-figure straight out of college job. Making it average difficulty because comp sci majors/SWE are notorious for not knowing how to behave. But technical is extremely easy. And lastly, it wouldn't hurt to research the company to actually know what they do with their product.