The interview process with HubSpot was very transparent. The technical recruiter I had was great and conducted a thorough initial call with me, which lasted about 30 minutes. He explained HubSpot's structure, their products, and their near-future goals. They also provide links to excellent blog posts that offer insight into the process and the company.

After a screening call with the recruiter, you are given a take-home test. You have 3 hours to achieve a successful 200 status code from the API endpoint they provide. Without going into extensive detail (to avoid giving away the test specifics for HubSpot), it involves handling HTTP requests and some data manipulation and parsing (sorting, structuring, etc.). Once you receive the 200 status from the server, you have as much time as you need to clean up your code, make it more idiomatic and functional, and then submit it via a link provided by the recruiter upon success.

My advice for this part is to focus on getting the correct payload to the API first, before creating elaborate algorithms and data structures, as the 200 success is the primary scenario they prioritize at this stage.

After successfully completing the take-home test within the time limit, I was invited for a 4-hour interview. This comprised of meeting the recruiter, an interview with the Director of Engineering, three Software Engineers, and concluded with the recruiter again.

The initial questions with the first software engineer were not difficult; however, the questions increased slightly in difficulty with each subsequent interview.

My second software engineer interview involved a small coding challenge. They assess the data structures you use and how you employ them, so be mindful of writing throwaway code. It's not about necessarily employing complex paradigms, but simply being aware of what you are using and why.

Despite getting the method to work during the interview, my code could have been more thoughtful and efficient (based on feedback). Listen carefully for tips, as interviewers often provide them; I simply lacked the foresight to apply them at the time.

My last software engineer interview was with a predominantly front-end engineer. You have the option of using either vanilla JS or jQuery; I chose vanilla JS. This involved connecting small functions to the DOM via event listeners. Some HTML and CSS are involved, but if you have a professional grasp of these, you will do fine.

All members of HubSpot allow for chat at the start and questions at the end of each of their allotted time, and I had the privilege of being interviewed by some very pleasant individuals.

After completing the on-site interview, you receive a tour of the office. The recruiter generally contacts you within about 3-4 days. In my case, he called with feedback. Although I was not offered the position, which was disappointing, it was a nice personal touch. Many companies would inform you via an automated email, but the feedback provided was detailed and well worth considering.

Create a memoization method for caching.