Coding interview with code signal. Required to have camera, microphone, screen sharing and government ID. Not sure what the other steps would have been in the process. Typical leet code style questions.
The phone screen was surprisingly in-depth, focusing heavily on algorithms and data structures. After that, I faced two technical rounds, which included implementing a trie-based tokenizer and an in-memory key-value database with TTL expiry. The DSA questions were tough, but I felt prepared after working through the PracHub interview experience archive the week before. Even when I struggled, I found the questions familiar, which gave me a little boost. I ultimately received an offer, but I decided to decline after some consideration.
Questions d'entretien [2]
Question 1
Implement a trie-based tokenizer that splits raw text into subword tokens
Technical interview, mid to hard. I faced a problem related to simulate rocket movement, in a game fashion. It was doable, but not in the time I had, at least not for me.
Questions d'entretien [1]
Question 1
Write an algorithm that simulates a game of rockets.
The process is incredibly fast-paced and skip the HR fluff. Expect a heavy focus on raw engineering talent and low-level system understanding. After the initial screen, I had to jump into a deep-dive session involving real-world infrastructure challenges at a massive scale. They want to see if you can actually build things from scratch under pressure without relying on any "Magic" internal tools.