The questions themselves deserve a separate paragraph. The interview was split to several quizzes: hardware design, rtos-related, c, c++, linux, security. Majority of the questions was single-answer test questions. Few open questions to write some snippet. The hardware and security part was quite ok. The rest was not. The C/C++ questions were based on a code snippets prepared exactly for interview purpose. So, there were some crazy-looking constructs like 3[arr] + (arr+1)[1], !!!arr, &(*(&arr[1]+1)+2). Things that you should never see on production. I don't see a point of asking such questions. This kind of questions doesn't check if you're good engineer or not. There were no good coding practices questions, no software design-related. All C++ questions were pre-C++11.
Embedded C Interview Questions
58 embedded c interview questions shared by candidates
The written test pattern covers all the system programming basics as well as C programming concepts. networking, files, disks, linked lists, pointers, structures, enums, unions.
There were very little technical questions. The focus of the interview was the nature of my background and what I could bring to the company.
Shallow copy and deep copy threads
What is the importance of using IEEE standard protocols?
Make a C code that changes the 4th bit of the value stored in address 0x8000.
Siemens: 1) Inheritance using private, protected, public for child class what is the scope for all. 2) can private parent class be accessible by child class. Yes/No. If yes then how. If no then why? 3) c program on double linked list to find minimum of all list using double pointer. 4) pointer to pointer what is the output 5) Socket programming any idea? 6) What is context switching 7) communication protocol. 8) oops concepts
What is the difference between struct and union keywords in C ?
Viewing 51 - 60 interview questions