This one felt like a seriously academic process from the beginning. The first phase was a HackerEarth test that lasted about an hour. It wasn’t “hard” in the usual sense, but it cared about code efficiency, not just getting the logic right. I scored around 62.5% and moved forward.
The next phase was a live interview-style coding session with engineers that also lasted about an hour. I did live coding with questions that leaned into core Java details—strings, exception handling—plus a logic or math problem. I also got an analysis task where the point was to reason about algorithm efficiency rather than just produce an answer.
> 1 year
Average Positive Germany
I experienced Sixt’s process as something that mixed systems and fundamentals in a fairly direct way. I first started with a short intro and then moved into a coding challenge. After that, the discussion shifted into architecture and platform topics—microservices and broader design—while still staying anchored in technologies like Kubernetes, Kafka, and Redis.
The later technical portion leaned more classic than that architecture talk: I had three technical interviews that blended DSA with DBMS and OS. Those rounds included “standard” styles of DSA questions, plus common DBMS and OS fundamentals. The difficulty range felt moderate to tough, and I could tell the managerial round would be harder for a lot of people because it was the part where most students got stuck.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
