I was selected through a campus interview. I had solved some previous year interview questions, mostly based on state machines and timing violations. There was one aptitude test, which was easy, and an interview. Perceptions: People: Very friendly,
Questions on linked lists, queues, and arrays were asked. Questions on computer architecture were asked. The HR round was conducted by one of the hiring managers. Questions on cache handling were asked.
I went through a GPU compiler loop last year. For me it was two technical screens then an onsite with a few deep dives, but it varied by team. I barely saw LeetCode style questions. Most coding was C or C++ plus compiler flavored graphs and systems t
I was selected through a campus interview. I had solved some previous year interview questions, mostly based on state machines and timing violations. There was one aptitude test, which was easy, and an interview. Perceptions: People: Very friendly,
Questions on linked lists, queues, and arrays were asked. Questions on computer architecture were asked. The HR round was conducted by one of the hiring managers. Questions on cache handling were asked.
I went through a GPU compiler loop last year. For me it was two technical screens then an onsite with a few deep dives, but it varied by team. I barely saw LeetCode style questions. Most coding was C or C++ plus compiler flavored graphs and systems t