Embedded Software Engineers entwickeln und warten Embedded Systems. Hierfür sind ggf. fortgeschrittene Software- und Problemlösungskompetenzen erforderlich. In einem Vorstellungsgespräch für Embedded Software Engineers wird der Gesprächspartner wahrscheinlich Fragen stellen, mit denen Ihre Programmierkenntnisse und -erfahrungen geprüft werden sollen. Sie werden auch über Ihre Teamfähigkeit sprechen müssen, da die Stelle möglicherweise in einer Gruppe ausgeübt wird.
Interview started with my introduction and the interviewer was a senior employee in the company.He asked to coding questions on arrays,bit manipulation,strings.He asked me to write the code in C language without using inbuilt functions for all the questions.I confidently answered all the questions but i didn't get shortlisted unfortunately.
Lot of questions about pointers in C
Name a time when (majority of questions)
how does a packet travel between two hosts connected in same network?what is subnet mask?
phone interview operating systems- priority inversion, ISR & interrupt vector table, order of complexity of sorting algorithms
Brain Teasers: questions are not hard if you are calm. Engineers are not familiar with your resume, so one of the engineer asked me what do you think I should question you (like what do you believe is your strength and where should he start this interview.)
How to code kernel accessible by multi-tasks without wait.
How post increment works.
about mutex and semaphore.
Phone Screen- Basic new grad level Embedded questions on C, memory, components of a microcontroller, bit manipulation, etc. and some general high-level questions on experience. No interactive coding. Onsite - HR - several (unnecessary) behavioral questions and discussion about company and benefits. HR didn't seem to care about my responses or my salary expectation (which he had asked for). And then four technical rounds(Engineers and one with hiring manager) plus an additional round at the end (was not in the schedule) with a director. Questions included - Lot of finding the bug or output of C code snippet questions (questions repeated by some interviewers). Some of these were good (and easy) but many of these questions required you to be familiar with some C peculiarities that you would never use in real life. Find an issue with how mutex is used in a C code snippet Write a given C function in Assembly (you can come up with your own instructions) A debugging question related to DMA and cache coherency How would you debug a memory leak? RTOS vs General-purpose OS. How to implement a mutex? Mutex vs Semaphore How would you assign task priorities to a producer and consumer task in your system? Add two numbers whose individual digits are represented in two distinct linked lists (function heading was in C++) Implement cache-alligned version of malloc Knowledge based questions of Interrupt vector table, interrupt priorities and ISR. In-depth questions on how SPI and I2C bus works (since on my resume) Some interviewers (the experienced ones) and their questions were good and emphasized on thought process and gave feedback to my responses but some were condescending. One interviewer was scrolling on his phone while asking me to write output of C functions he chose randomly and one after the other from a list of questions he had printed out in a bunch of papers.
Viewing 1431 - 1440 interview questions