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 Software Engineer Interview Questions
4,669 embedded software engineer interview questions shared by candidates
Everything about C language, Hardware related questions, Generic Code writing, Pseudo Code I2C, SPI & Uart Reception, Power Supply design, Relay Interfacing with uC, Past Projects
What is the difference between TCP and UDP ?
1. One math trick question, about algebra 2. Write a class for something.
C library functions, C++ background, building a counter
All C programming. Lots of bit manipulation, some systems programming questions, and a "code coverage" question about testing
Thread synchronization, scheduling. Inter process communication.
How to detect a cycle in a linked list? How to know at which node the cycle begins?
Questions related to your projects and work experiences.
Look for basic leetcode exercises to practice. Get some basic knowledge about GNSS.
Viewing 3821 - 3830 interview questions