The interviewing process was not bad, but it did take some time. In hindsight, I wish some things had been done differently.

First, I had a phone call with HR to discuss what I was looking for and to get to know the company better.

After that, I received a coding exercise that needed to be solved in two hours, and it was quite simple.

Once that was done, I had four interviews: one for JS knowledge, one for algorithms, one for HTML/CSS skills, and a call with the hiring manager.

Everyone was very helpful and friendly, which helped a lot.

However, no one, not once, mentioned that Software Engineers at HubSpot are expected to do on-call duty. I found this out three weeks after starting.

This is not a small detail and should have been called out during the interview, especially because it's not standard practice in most European companies, and it's a very important point.

The other significant miss, in my opinion, is that even though I was interviewed by around eight different people, I am not working with any of them.

I had a call with the hiring manager, but he is far above my position as the head of a department, and I have very little contact with him.

Therefore, no one on my team met me before I started. I personally believe it's important to talk to the people you will be working with during the interview process.

• Fetch data from an API, transform it, and send it back.

• Standard JS coding questions, covering scopes, binding, currying, memoization, etc.

• Some algorithmic questions; nothing super complicated, refer to LeetCode page 1.