The initial interview process consisted of a quick phone screen then a ~3-hour programming challenge. It was set up differently than a typical code sample- it was an API related project that was reflective of what type of work you might do at HubSpot. The project was fun to solve, but the most weight was put on how fast you could submit the correct solution, rather than on the elegance of the solution or the quality of code that was submitted. The emphasis on speed highlighted a strong difference in values between HubSpot and myself, and I wasn't selected for a follow-up interview. My recruiter was timely and polite, but the coding challenge was a bit long for being the company's initial technical screen. It doesn't make sense to let participants work for 3+ hours on the challenge if they are only moving the fastest people forward. If you think the problem is solvable in 1-2 hours and won't consider participants who take longer- cut people off after two hours and save them the extra time.