Interview Review – Python Developer / Tutor Role!
I would advise candidates to think carefully before committing to the interview process for this role. While the opportunity initially appeared legitimate, the overall experience was extremely time-intensive, poorly communicated, and ultimately not proportional to the compensation or outcome.
I applied through LinkedIn and was contacted by the company regarding a Python Developer/Tutor position. The interview process took a little over two weeks, during which I spent several full working days on unpaid technical work.
Company Presentation vs Interview Expectations!
The company’s public-facing materials contain noticeable inconsistencies, missing content, and language issues. While the tools used to build a website are not important on their own, this became relevant given how strict and detail-oriented the interview expectations were. There was a clear mismatch between how polished candidates were expected to be and how the company itself presented information.
Interview Process Structure!
The process consisted of multiple stages, starting with a lengthy reasoning-based assessment, followed by a substantial technical coding challenge. The initial assessment alone required several hours to complete. Despite performing well, the feedback I received at this stage was vague and somewhat contradictory.
The next phase involved implementing a fairly complex TCP server based on a very detailed specification. Candidates are expected to dedicate full working days over several consecutive days, submit daily progress updates, and track time spent on the task. This amounted to what felt like a full-time workload for close to a week, without compensation or any guarantee of advancement.
Submission and Review Concerns!
Although the process initially suggested multiple allowed submissions, this changed during the course of the challenge. Feedback on submissions was inconsistent, often generic, and did not clearly reference specific parts of the implementation. In several cases, feedback pointed out issues that had already been addressed.
Communication during this stage was particularly weak. Questions and clarification requests often went unanswered, and feedback emails did not always come from official company domains, which reduced confidence in the process.
After being informed that I had reached what appeared to be my final allowed submission, I sent a professional message acknowledging the situation and thanking them for the opportunity. I did not receive a response.
Shortly afterward, I noticed the same role being advertised again, despite having been closed while I was actively interviewing.
Conclusion!
It took me over 2 months to interview. With multiple return requests on the project and asking me to make changes on the project that were already made. Did 2 rounds of live interview. Then got a generic response a week later telling me that I have not qualified. In essense, for the compensation and the amount of work they put you through for this interview, it is not worth it.
Compensation vs Effort!
What made this experience especially difficult to justify was the compensation range advertised for the role. Given the depth of the technical work, the time commitment required, and the level of scrutiny applied, the offered pay did not align with the effort expected from candidates.
Overall Impression!
To be fair, the technical challenge itself was interesting, and I did gain personal value from completing it by adding a solid project to my github portfolio. Early communication during the process was also polite and encouraging. Unfortunately, the lack of transparency, shifting expectations, and poor communication during later stages overshadowed those positives.
Overall, the process felt disorganized and dismissive of candidates’ time. Anyone considering this interview should be aware that it is highly demanding, unpaid, and may not result in an offer or even clear closure.