Nothing too difficult about the technical questions, I came from a public school in CA near the start of my JR year, and by the end of the year every type of question that was asked was covered in class. They don't look for the absolute best answer, as long as it's not overly complicated.
Initial round was a online mcq round comprising of 15 technical questions.Duration was 30 minutes. Unfortunately kicked out of first round
One or two design questions. Remaining all were on DS and algo e.g. BST, linked lists, practical implementation of these concepts. Some were on the OS basics.
Every thing was basics. I screwed it up
Design a backup system. (no requirements, no more details, and very vague)
How to build a system to sync files in two folders?
Nothing that difficult. Just know your basics about data Structures, Algorithms and Testing if interviewing for a SDET position.
Can't remember the actual questions now, but those were usual interview ones. No crazy trees or graphs, but mostly combinatorics-like, string/array manipulation, basic geometrical applications etc. No brain teasers, only technical.
nothing was like any unexpected questions. all questions were almost easy.
The most unexpected question was about how I would spread the work between my team mates and myself.
Viewing 2771 - 2780 interview questions