Standard product, technical, analytical questions. They aren't hard if you (a) know your stuff and (b) know what they are looking for. You you are good with above then the issues usually to do with subjectivity in the process/person you get the day of interview.
What happens in Linux Shell when trying to run ls command, Describe TCP protocol, how is TCP different from UDP and when to use each one, DNS uses UDP or TCP protocol, What is the size of UDP packet, Describe what is a struct, enum and union in C, describe the memory structure on the operating system (heap,data and stack)
Round 6: • Tell me a project I which you did the technical contribution • About youtube data design
Cant disclose due to NDA - but the questions were very basic level to the point that I didn't even remember them correctly as had prepared for advanced topics.
Decision to choose either an off-the-shelf product or in-house development of the product. How do you choose? In 4 slides explain how will you present it to the top management.
Lots of PC technician questions
No brain teasers but deep technical knowledge required
What is Young's modulus?
Be prepared to dig deep into your skillset for the program manager position this included 3 skillset interviews.
What hardware I used in the last 6 month that I think needs improvement.
Viewing 1981 - 1990 interview questions