J'ai postulé via un recruteur. J'ai passé un entretien chez Twingate
Entretien
Enjoyed the first round where you got to talk to a prospective teammate and determine fit.
Second round was a 2-4 hour take home. The problem was fun though I’m not sure how it applied to the job as the first round I thought the job required python Django experience and not something you’d write in your C class for a class assignment. The problem was fine though I’m not sure why I didn’t pass as I implemented all the expected functions and added plenty of tests. For a longer take home, it would have been nice to get specific feedback on it like “you didn’t write up these specific test cases” or your class design lacked “x”. Even if I didn’t pass the round, I still wanted to learn something from it to apply to future interviews since I spent a decent chunk of time on it compared to probably how long they took to review my work.
All in all it was fun, though I was disappointed to not have gotten actionable feedback to learn for the future. I say it was a difficult take home if you hadn’t learned the concept they wanted you to implement more recently as the first portion I had to refresh my memory of it to follow how certain algorithms were built. ;)!
Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer chez Twingate
J'ai postulé via un recruteur. J'ai passé un entretien chez Twingate en mai 2026
Entretien
Terrible experience.
First round went great, I met with a manager who was very friendly, we discussed the industry Twingate is operating in and what life at Twingate was like.
Second round was a coding challenge, you get about three hours to implement a faux memory allocator. Before the round began, I asked if I could use AI (Claude Code) to implement a solution, and that was approved. Early the next week I received an interview request for the "next round" which would be a code review of this project and an additional coding exercise.
Third round is where the process turned sour. It was supposed to be a "code review" but in actuality the "interviewer" just had me share screen while directing me to various parts of the code where there were bugs or inconsistencies, for example where Claude had hallucinated something into the README that actually wasn't present in the codebase, without actually asking me about my own contributions or prompting approach. It felt like the interviewer had already made up his mind before the interview started, and just wanted to embarrass me.
Would recommend staying far away from this company if this is representative of the culture here.