J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Cozero (Germany) en avr. 2024
Entretien
I applied from Linkedin, got the first email after 2 weeks, and the first available slot i could schedule was the week after.
The interview was with CTO/founder. He was late then started rushing with questions i could not finish. He would interrupt constantly, usually after barely one sentence. almost as if being fluent in english is a mistake and you are only supposed to answer with verbs and nouns to keep it "optimal". The communication was poor and it was clear they had lots of candidates, otherwise they wouldn't adopt this speed dating approach. Too bad i had to wait one week for the call(the initial 2 weeks are fine as a response, but then there were no free slots for a week)
I asked some questions at the end, and i could tell they were bothering him, questions like how you do you handle on call or do you use this or that technology. Very awkward and forced, interaction and i got the the generic reject email the same day with obviously no context behind the decision.
I am a fullstack typescript developer and i work on the same tech stack as in the job description, hence i assumed the issue was my non technical area, but i can only guess, since this was not the technical interview, just the screening one basically.
J'ai postulé en ligne. J'ai passé un entretien chez Cozero (Germany) (Berlin) en avr. 2026
Entretien
Interviewed for a Senior Software Engineer role at Cozero. Overall, a frustrating and poorly structured process.
The interview loop was long: recruiter call, Head of Engineering, then three back-to-back interviews on the same day lasting over three hours. A final stage with the co-founder was already scheduled and then cancelled after the previous round.
The first two technical interviews were actually good. The code review and system design were relevant, well scoped, and clearly aligned with the role. No issues there.
The Product & Data interview is where the process completely breaks down. There was no clear structure, no consistent line of questioning, and no obvious evaluation criteria. It felt unfocused and disorganised. After already passing two strong technical rounds, this stage came across as unnecessary and poorly designed. It was not clear what was being assessed or how a backend engineer was being evaluated in that setting.
The rejection was generic and provided no meaningful feedback. However, since the process is sequential and you only move forward if you pass each stage, it’s clear the decision came from that Product & Data round.
The biggest issue is the mismatch between the strong technical stages and a final decision being made based on an interview that doesn’t seem well defined or consistently run.
In the end, this meant spending over 3 hours in interviews in a single stretch, essentially half a working day, only to be rejected based on a stage that lacked clarity and direction. That level of time investment simply isn’t justified by how the process is structured.
Overall, the process feels inconsistent and overcomplicated for a company for a company that’s only been around for about 6 years and still relatively small.
Would not recommend unless you’re willing to invest significant time into a process that may not be well aligned or fairly assessed end to end.