Skip to contentSkip to footer

Embedded Software Engineer Interview Questions

Salaries
Interviews

Embedded Software Engineer Interview Questions

Gli Embedded software engineer si occupano di sviluppare e mantenere i sistemi integrati e devono possedere competenze avanzate in ambito di software e di problem-solving. In un colloquio per Embedded software engineer, l’intervistatore potrebbe rivolgerti domande per valutare la tua esperienza e le tue competenze di codifica. Aspettati anche di dover spiegare come ti poni nei confronti degli altri, perché questo ruolo può prevedere il lavoro in team.

Domande tipiche dei colloqui per Embedded software engineer e come rispondere

Question 1

Domanda 1: Dai una definizione di sistema integrato.

How to answer
Come rispondere: Dimostra le tue competenze fornendo una risposta sintetica e allo stesso tempo accurata. Spiega che un sistema integrato è un computer che risiede in una macchina di dimensioni maggiori e funziona in modo univoco per eseguire una determinata attività. Potresti anche fornire alcuni esempi concreti come un’automobile, un elettrodomestico o un lettore MP3.
Question 2

Domanda 2: Quali linguaggi di programmazione sai utilizzare?

How to answer
Come rispondere: Gli Embedded software engineer si occupano della realizzazione di sistemi funzionali complessi, quindi è utile mettere in evidenza le tue competenze tecniche. L’intervistatore si aspetta che tu faccia riferimento ai linguaggi di programmazione di base come C e C++. Puoi citare i linguaggi di programmazione che preferisci o quelli che vorresti approfondire, dimostrando passione e interesse per la formazione continua.
Question 3

Domanda 3: Hai mai collaborato con ingegneri e designer?

How to answer
Come rispondere: Il lavoro in team è fondamentale perché ti permettere di collaborare con gli altri per raggiungere un obiettivo comune. Puoi citare un episodio in cui hai collaborato con successo per risolvere un problema relativo a un prodotto. Soffermati a parlare della tua capacità di gestire lo stress, comunicare in maniera chiara i problemi complessi e ascoltare gli altri.

4,134 embedded software engineer interview questions shared by candidates

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.
avatar

Staff Embedded Software Engineer

Interviewed at Qualcomm

3.8★
Dec 11, 2019

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.

Explain pointers and when you could user a double pointer. Follow exponential drawing code. (Error with semi-colon after the for loop. And reason through it. What is a mutex and semaphore. How are they used. Basic buffer operations in OS. How to handle deadlock and context switch. Coding question on the use of pointers and passing by reference (* and &) using a class. Class c1, *c2, &c3. Coding question about parsing through Cstring in C. Turn a string into an integer and output it based on test cases.
avatar

Embedded Software Engineer

Interviewed at Garmin

3.7★
Feb 22, 2022

Explain pointers and when you could user a double pointer. Follow exponential drawing code. (Error with semi-colon after the for loop. And reason through it. What is a mutex and semaphore. How are they used. Basic buffer operations in OS. How to handle deadlock and context switch. Coding question on the use of pointers and passing by reference (* and &) using a class. Class c1, *c2, &c3. Coding question about parsing through Cstring in C. Turn a string into an integer and output it based on test cases.

Viewing 1311 - 1320 interview questions

Glassdoor has 4,134 interview questions and reports from Embedded software engineer interviews. Prepare for your interview. Get hired. Love your job.