Embedded Firmware Engineer

[Gursahib Singh]

Hiiii guys... I have an interview for 'Embedded Firmware Engineer' after 10 days in a good automotive company. Can you people guide me how to prepare or it ? Its like a dream for me. Please guide me its a request. What kind of questions are expected?

 

[logu2289]

Dear Gursahib Singh,

You need strong knowledge in Embedded Concepts and C Language

Some of topics

How Interrupt service when 2 occurred at same time?
How volatile keyword is using explain with examples program
Structure padding
function pointer
Negative value storing in memory
How main and Sub functions differ from interrupt functions

 

[123jack]

As it is an automotive company I would look into what protocols are used in that industry
How communication is handled in vehicle systems and what family of chips etc may be used.
Anything specific to the industry. What processor/buses etc are used.
Do you know anything about failsafe technology etc.
If they ask anything specific it will probably be just to probe your level of knowledge
so don't panic if you dont know something - just say so.
Have a good scan of wikipedia.org for general info.

Good luck

 

[Dan Mills]

CAN bus basics, MISRA standards, use of volatile, const, meanings of the static keyword, why malloc is a really bad idea in small embedded things, safety integrity levels.

Meaning of 'realtime' and some considerations surrounding it.

Matlab and Simulink may be areas of enquiry, together with automated code generation using these tools.

Basically, lots of mostly low level embedded stuff, plus some car stuff and some use of automatic code generation bits and a few safety bits.

there is usually little point in interview prep in this sort of sense, any engineer worth their salt can tell very quickly if you claim experience in something but have only read the Wikipedia entry.
Far better to spend the time coming up with good answers to the 'soft' questions, you know the ever hated "Tell me about a time you had a disagreement with a college..." stuff, this is actually worth thinking about in advance so you have some good answers, the technical stuff just has far too many directions it could go in.

Regards, Dan.