Autocoder

NXP Interview Questions and Answers for India Embedded Software Roles

Last updated 2026-11-19

NXP supplies microcontrollers and processors for automotive, industrial and IoT products, so embedded software interviews in this area lean on how a microcontroller starts up, how tasks share the CPU, and how devices talk over buses such as CAN. This page has twelve practice questions with worked answers across those topics, plus HR questions.

They are written for topics such roles are commonly reported to cover, not copied from any interview. For coding practice in the same style, see NXP coding round questions.

Typical rolesEmbedded software, driver and BSP, automotive software, validation
Core topicsEmbedded C, RTOS, buses (CAN, SPI, I2C, UART), startup and memory map, MISRA C
Rounds (commonly reported)Online test, technical interviews, HR

Rounds as commonly reported

Prep write-ups describe an online screening with C, electronics and aptitude questions, followed by technical interviews and an HR round. NXP does not publish a fixed process, and it varies by team, so rely on your invitation for the real structure.

Technical interviewers often follow the hardware path: what happens at reset, how an interrupt is taken, how data gets from a peripheral to your code. Be ready to answer at the level of registers, memory sections and priorities, and to say what you would measure to confirm.

Topics to revise

Hiring status

This site holds no sourced hiring statements for NXP, so it quotes no drive dates, number of openings or packages. Treat posts that give them without a source link with caution.

Check the company's own careers site for current openings and application instructions.

NXP Interview Questions and Answers for India Embedded Software Roles: questions with worked answers

  1. 1

    How does CAN bus arbitration work? Which of IDs 0x100 and 0x200 wins?

    medium

    CAN is a multi-master bus with a dominant bit (logical 0) that overrides a recessive bit (logical 1) on the wires. Every node that starts transmitting sends its identifier from the most significant bit and watches the bus; a node that sends a recessive bit but reads a dominant one has lost and stops. So the lowest identifier wins, with no collision and no lost frame. Between 0x100 and 0x200 the first differing bit is where 0x100 sends 0 and 0x200 sends 1, so 0x100 wins and 0x200 retries afterwards.

  2. 2

    What is bit stuffing in CAN and why is it needed?

    medium

    After five consecutive bits of the same value, the transmitter inserts a bit of the opposite value, and the receiver removes it. This guarantees regular edges so that receivers can stay synchronised without a separate clock line, and it lets an error be detected when six equal bits appear in a row. The cost is that the frame is slightly longer than its nominal bit count, and the length depends on the data.

  3. 3

    Compare CAN and LIN.

    easy

    CAN is a two-wire differential bus with multi-master arbitration, speeds up to 1 Mbit/s for classic CAN, strong error detection, and is used for critical communication between control units. LIN is a single-wire, low-cost, slower bus (up to about 20 kbit/s) with one master and several slaves, used for simple body functions such as window or seat controls. Pick CAN where robustness and multi-master behaviour matter and LIN where cost matters.

  4. 4

    What happens between reset and main() on a Cortex-M microcontroller?

    medium

    The core reads the initial stack pointer from the first word of the vector table and the reset handler address from the second, and jumps to the handler. The startup code then sets up the clock if needed, copies the initialised data section from flash to RAM, zeroes the uninitialised (bss) section, may run constructors or library initialisation, and calls main. This is why a global with an initial value works and why an uninitialised global reads as zero.

  5. 5

    Which linker section holds each of these: code, initialised globals, uninitialised globals, constants?

    easy

    Code goes in .text, in flash. Initialised globals and statics go in .data, which is stored in flash and copied to RAM at startup. Uninitialised or zero-initialised globals and statics go in .bss in RAM and are cleared at startup. Constants and string literals go in .rodata, in flash. Local variables live on the stack, and malloc memory comes from the heap. Reading the map file to see these sizes is a good habit.

  6. 6

    Explain priority inversion and priority inheritance.

    medium

    Priority inversion occurs when a high-priority task waits for a mutex held by a low-priority task, which is itself preempted by a medium-priority task, so the high-priority task is effectively delayed by the medium one. Priority inheritance temporarily raises the holder's priority to that of the highest waiting task so it finishes quickly and releases the lock. A priority ceiling protocol is an alternative. It is a well-known cause of real-time failures, so RTOS mutexes usually support inheritance.

  7. 7

    Mutex versus binary semaphore in an RTOS: which would you use to protect a resource, and which to signal from an ISR?

    medium

    Use a mutex to protect a shared resource: it has an owner, supports priority inheritance and should be released by the task that took it. Use a binary semaphore for signalling, where one context gives and another takes, such as an ISR signalling a task that data is ready. A mutex must not be taken from an ISR, since an ISR cannot block, so ISRs use the interrupt-safe variants of give or queue-send calls.

  8. 8

    How do you check that a set of periodic tasks is schedulable under rate-monotonic scheduling?

    medium

    Rate-monotonic scheduling gives higher priority to shorter periods. A sufficient test is the utilisation bound: the sum of C/T must not exceed n (2^(1/n) - 1), which is 0.78 for three tasks. If it holds, all deadlines are met. If it fails the set may still be schedulable, so apply an exact response-time analysis. For tasks (C, T) of (1, 4), (1, 5) and (2, 10), utilisation is 0.25 + 0.2 + 0.2 = 0.65, which is below 0.78, so they are schedulable.

  9. 9

    How do you access a peripheral register in C, and why use volatile?

    medium

    Define the register address as a pointer to a volatile fixed-width integer, or overlay a struct of registers on the peripheral base address. The volatile qualifier tells the compiler that the value can change independently and that each access has an effect, so reads and writes cannot be removed or reordered. Use read-modify-write carefully on registers with write-one-to-clear bits, and check the datasheet for the access width.

    c
    #include <stdint.h>
    typedef struct {
        volatile uint32_t CTRL;
        volatile uint32_t STATUS;
        volatile uint32_t DATA;
    } Uart;
    #define UART0 ((Uart *)0x40004000u)
    
    void uart_send(uint8_t b) {
        while ((UART0->STATUS & 0x1u) == 0) { }   /* wait until TX ready */
        UART0->DATA = b;
    }
  10. 10

    Name some MISRA C rules or directives and why they exist.

    medium

    MISRA C is a set of guidelines for safe C in embedded systems. Typical ones: do not use dynamic memory allocation after initialisation, avoid recursion because stack depth is unbounded, do not use unions for type punning without care, use fixed-width types, initialise every variable before use, make every switch have a default, and do not mix signed and unsigned arithmetic carelessly. They exist to avoid undefined and implementation-defined behaviour and to make code reviewable and analysable by tools.

  11. 11

    What is a watchdog and how would you use it in a safety-related ECU?

    medium

    A watchdog resets the system if software fails to service it in time. In a safety context, do not service it from a timer interrupt; service it from the main loop only when all monitored tasks have reported progress (alive supervision). A windowed watchdog also catches code that services too early. After a reset, record the cause and enter a safe state or limp mode if resets repeat. Functional-safety standards expect such supervision for higher safety levels.

  12. 12

    HR: Why NXP, and what embedded project are you proudest of?

    easy

    Choose a project with a microcontroller, a bus or an RTOS, and explain your own part: the peripheral you drove, the bug you found with a scope or logic analyser, the result. Connect to the company by naming what you want to learn, such as automotive networking or low-power design, and avoid generic praise. Also see how to crack the HR interview.

Frequently asked questions

What embedded topics are asked in NXP interviews?

Commonly reported are C, startup code and memory sections, interrupts, RTOS concepts, communication buses such as CAN, SPI and I2C, and project discussion. The mix depends on the team.

Do I need to know AUTOSAR?

For automotive teams it helps, but fundamentals come first: C, RTOS and buses. Read the job description to see whether AUTOSAR is mentioned.

Are these real NXP questions?

No. They are practice questions in the style of topics such roles commonly cover. The company does not publish its interview questions.

Where do I check NXP openings?

Use the company's own careers site. This site has no sourced hiring facts for NXP, so it quotes none.

Related guides

More in Company Interview Questions

See all in this section