The first interview mainly asked various Linux questions: what happens behind the scenes when I run ls in a shell, the differences between containers and virtual machines, and other knowledge questions like those. I wasn't asked to write code.
After passing the first interview, I had a virtual onsite with three interviews. Beforehand, I asked the recruiter what each one would cover, but they absolutely refused to say, beyond saying there would be both technical and behavioral questions. Afterward, I found that it was basically one conversation round with technical questions like the first interview and behavioral questions, one conversation-plus-system-design round, and one coding-only round. The system-design portion was only 30 minutes; everything before it was conversation.
I mainly failed on the coding. I had always prepared data-structure-and-algorithm questions, the LeetCode kind, mostly in Java. But the interview was entirely Python file-parsing problems, several of them. I spent ages trying to write them with Java's buffered reader and kept running into compilation problems. I'm not sure whether coding interviews at finance companies are all like this or whether it was because this wasn't a traditional SDE role.
Overall, there was a lot of conversation in their interviews. Apart from the coding round, each one started with at least half an hour of it.
Discussion
Loading comments…