It's fair. you do the way it's most convenient, less anxiety inducing and what works best for you. do you like pair programming? or you prefer taking your time on a project thinking through things yourself? or a mix of both? prefer backend or frontend? wanna talk some folks in your prospective team? i liked that instead of boxing the process a single way they were flexible on letting me choose what would works best for me.

The interview process at Brightside for engineers is incredibly pleasant. It's not as high-stress as other engineering interviews but I still believe they're able to assess the right qualities that they're looking for in engineers. My process was: - Initial call with an internal recruiter - Technical conversation with the CTO - Choice of a take-home exercise or a live pair programming interview (I love when companies provide options to best suit the candidate's availability/preferences) - Final chat with HR to receive and discuss the offer Everyone that I met and spoke to (including meeting a couple of other members of the team when an offer was anticipated to find team fit) was amazingly kind I was incredibly excited for the opportunity to work with this team. At the end of the day I had a different opportunity come up that I couldn't pass up but I think I'll have a permanent "what if" question in my mind because the experience with these folks was that great. Out of respect for their process I won't dive too deeply into what's discussed but this is a company who cares deeply about finding mission-driven engineers who care about working in a team-setting to build an amazing product. I've marked the interview difficulty as "easy" mostly because if the right fit is there, I think you'll feel it and know and I think that's mutual. I don't think people will pass this process who don't meet the bar that Brightside is setting, but I also don't think they're going to overly quiz you or make you feel dumb along the way.