Bit checking a 32 bit number, recursive searching of binary trees. Writing unit tests for simple code algorithms. After writing code, was asked to optimize it. All questions were C.
Also, they wanted details about my Sr. project (which was FW for an embedded system).

Question

Bit checking a 32 bit number, recursive searching of binary trees. Writing unit tests for simple code algorithms. After writing code, was asked to optimize it. All questions were C. 
Also, they wanted details about my Sr. project (which was FW for an embedded system).

Anonymous · Accepted Answer

All code was on white board. Pseudo code was fine. Be sure to talk your way through questions, even if you don't know the answer. Showing your thought process is 50% of the work

Anonymous · Answer

Any questions on heaps + hash maps? did you  have to write your own : LL, stack , queue, B- tree ?

Anonymous · Answer

Through questions like this, interviewers are mostly trying to test your skillset (and its relevance to the role) as robustly as possible, so be prepared for multiple offshoots and followups.


It could be a useful exercise to do mocks with friends or colleagues in Intel to get a real sense of what the interview is actually like. Alternatively Prepfully has a ton of Intel  Firmware Engineer experts who provide mock interviews for a pretty reasonable amount.


prepfully.com/practice-interviews

Intel Corporation

Intel Corporation Interview Question

Interview Answers

Want the inside scoop on your own company?

Bowls

Followed companies

Job searches