think-cell Software Engineer Interview Questions
& Process

I spent over 5 hours on the take-home task, which I actually enjoyed solving. Even though I successfully ran and tested my submission locally, there was a small mistake in my code that made it incorrect. The issue is that besides the error log, I received no feedback on my submission, which I think is really important when asking someone to spend their evening on it. I emailed to ask for feedback, and their response explained common mistakes applicants make, none of which applied to my situation, leaving me confused. After some research, I figured out the problem myself, but I was really annoyed that companies ask candidates to dedicate a lot of time to assessments but aren't willing to give back the minimal time needed for valuable feedback. If someone is really interested, they might figure it out on their own if they save the page before submitting and keep a snapshot of the error, like I did. However, I don't like being treated as a number in someone's database and want my time to be respected. I won't re-apply, at least not without hesitation. I'm sure this company does good work, but I believe mutual respect is the foundation for collaboration, which Think-cell failed to establish with me.

The first stage was an online C++ test that you could submit over a generous time period. The second stage was an in-person interview. Unfortunately, I didn't make it to the second round. The submission process for the first round was confusing because the submission page appears after the compile page, leading one to believe multiple submissions are allowed when only two are permitted. It felt like the test was just a quick filter for a company with a vast number of applicants, suggesting they don't invest much effort into each candidate. Automated accept/reject systems indicate a lack of concern for human error on the candidate's part, as if candidates have no agency in choosing the company. I won't be reapplying or giving this company another chance.

The interview process involves a few stages. Initially, there's an automated test focusing on algorithms, data structures, and some C++ knowledge. Following that, candidates undergo 2-3 technical interviews with software engineers. The company has specific requirements for its engineers, which can make it challenging to pass all the stages. Despite the difficulty, the experience was positive and offered insights into working with C++ on a mature product. A drawback was the interview duration, approximately 2 hours, and limited scheduling flexibility, which could be inconvenient for those with existing work or other commitments.