Back to blog
7 min read

Microchip and STMicroelectronics: Microcontroller and Embedded Silicon Interviews

Neither Microchip nor ST publishes a hardware-specific interview guide, so ask the recruiter whether the role is design, applications, firmware, or product engineering. Get your project story tight, rehearse fundamentals such as ADC sampling and C for peripherals, and treat candidate reports as anecdotal.

Practice these questions live in a mock interview with a verified chip design engineer. Find an expert

MicrochipSTMicroelectronicsMicrocontrollersEmbedded SystemsInterview Process

You see two postings on the same afternoon. One is an "Applications Engineer" role at a microcontroller company, the other is a "Design Engineer" role at a different one. Both mention C, both mention peripherals, and neither says whether you will spend your week in a lab, in Verilog, or on a customer call. How do you prepare for something that vague?

Neither Microchip nor STMicroelectronics (ST) publishes a hardware-specific interview guide that we could find. This post uses Microchip's own interview tips sheet and a Microchip product brochure, plus ST's public tooling pages as seen in search results, for the official picture. Candidate reports come from search summaries of Glassdoor, Prosple, GeeksforGeeks, and Levels.fyi, and they are anecdotal. The practice prompts are ours, not reported questions.

What do Microchip and ST say publicly?

Microchip's careers pages returned errors when we tried to open them, so we cannot describe its hiring stages from Microchip itself. What we could read is a one page sheet titled "Working For Microchip: Job Interview Tips". It tells candidates to practise motivational, career aspiration, competency, and strength-based questions, to research the employer, and to think about what skills they bring and what they achieved at university that relates to the role. It also says to prepare questions of your own, expect to show real interest in the organisation, and that pausing before an answer is fine. It also lists mistakes to avoid, such as sounding arrogant or unclear. The sheet reads as aimed at early-career candidates and says nothing about technical rounds.

ST's careers site would not load for us either. What we know about ST's work comes from its public tooling pages, as summarized in search results: STM32 microcontrollers are supported by STM32CubeIDE for editing, compiling, and debugging C and C++, STM32CubeMX for graphical peripheral and clock configuration, and STM32CubeProgrammer for flash programming. We did not open those pages directly, so treat that as a pointer, not a spec.

How do microcontroller teams differ from other chip teams?

A Microchip brochure, "16-bit Embedded Control Solutions", groups its PIC24 and dsPIC33 parts by application: low-power and general embedded use, motor control, digital power conversion, robust applications, and safety critical applications. That list is a rough map of what the work touches: peripherals such as timers, PWM, and ADCs, and firmware with real-time deadlines.

This is why "embedded silicon" interviews often mix topics that other tracks keep apart. You may get asked about a register map and a state machine in the same hour. Our guide to embedded firmware versus hardware design interviews separates those tracks, and embedded C for hardware engineers covers the C habits that show up everywhere.

TopicWhat the public material saysWhat to prepare or ask
Interview preparationMicrochip's sheet stresses motivation, competency questions, researching the company, and asking questionsA short story per project, plus why microcontrollers specifically
Product scopeMicrochip groups 16-bit parts by low power, motor control, digital power, and safety critical usesPick the application nearest the posting and learn its basic constraints
ToolingST's STM32Cube tools cover IDE, configuration, and programming (per search results)Ask which tools the team uses and how much is generated code versus hand written
Process stagesNot published by either company in material we could readAsk the recruiter how many rounds, who you meet, and whether there is a written test
Role typePostings use titles such as design, applications, firmware, and product engineerAsk what a typical week looks like and who the customers are

What candidates report (anecdotal)

The next two paragraphs come from search result summaries, not from pages we could open. Samples are self-selected, sometimes old, and differ by country and role.

For Microchip, a Glassdoor summary covering several hundred reports listed one-on-one interviews, phone interviews, skills tests, and panels as the most common stages, with difficulty around 3 out of 5 and average timelines that ranged from under 2 weeks to about 3 weeks depending on the sample. A Prosple page describes a possible written test, phone screen, problem-solving exercise, and on-site interviews. Glassdoor intern reports in the summary mentioned C questions, digital design with SystemVerilog and finite state machines, and for firmware, a deep dive into a past project plus RTOS and C topics.

For ST, a Glassdoor summary of roughly 580 reports listed one-on-one interviews, skills tests, and phone interviews as common, with average timelines of about 2 to 3 weeks and difficulty near 3 out of 5. A design engineer report mentioned a technical round and a managerial round. An intern report mentioned basic analog electronics, digital electronics, or programming. A GeeksforGeeks article describes campus hiring in India as a written test, a technical interview, and an HR interview, with topics such as projects, data structures, and SQL. It compiles other people's accounts and covers one hiring channel.

Pay data is thin and mixed. A Levels.fyi summary for Microchip hardware engineers in the US showed self-reported total compensation starting near $80K at the lowest level and a median near $130K. For ST, a summary showed a US hardware engineer median near $137K, with much lower figures reported in France and Italy. Titles like "hardware engineer" can cover applications roles, samples are small, and country matters, so check the Levels.fyi pages for Microchip and ST yourself.

How to prepare for the overlap

First, get your project story tight. Several reports center on resume depth, so be ready to explain requirements, your own contribution, what broke, and how you found out. Our post-silicon bring-up guide is useful practice for the debug part.

Second, rehearse a few fundamentals. Try this MockVise exercise: a 12-bit ADC on a microcontroller reads a noisy sensor once per millisecond. Explain sampling time, input source impedance, and what you would measure first. If the question leans analog, ADC and DAC architectures fills in the background.

Third, know the neighbors. Microcontroller roles sit close to automotive and industrial work, so skim our notes on NXP, Infineon, and Renesas. For how analog-heavy companies describe their process, compare Texas Instruments and Analog Devices, and watch for our post on the TI interview process.

Questions worth asking

Ask whether the role is design, applications, firmware, or product engineering, since titles differ by site. Ask how often engineers talk to customers and what bring-up looks like. Our list of questions that reveal team health can help you listen for the answers. To practice out loud, book a mock interview on MockVise.

Sources: Microchip interview tips sheet, Microchip 16-bit Embedded Control Solutions brochure, ST STM32CubeIDE page (search result), Glassdoor Microchip summary (search result), Glassdoor ST summary (search result), Prosple Microchip page (search result), GeeksforGeeks ST article, Levels.fyi Microchip, Levels.fyi ST. This is general preparation guidance, not an official Microchip or ST process or a list of reported company questions. Candidate reports and pay figures are anecdotal and may be out of date, so confirm the format and level with your recruiter. MockVise is not affiliated with or endorsed by Microchip Technology, STMicroelectronics, Glassdoor, Prosple, GeeksforGeeks, or Levels.fyi.

FAQ

Q: Do Microchip or ST publish their hardware interview stages? Not in material the post could read. Microchip's interview tips sheet stresses motivation, competency questions, and researching the company, and says nothing about technical rounds. Ask the recruiter how many rounds there are, who you meet, and whether there is a written test.

Q: Why do embedded silicon interviews mix so many topics? Microcontroller work touches peripherals such as timers, PWM, and ADCs, plus firmware with real-time deadlines. You may be asked about a register map and a state machine in the same hour.

Q: What do candidates report about Microchip and ST interviews? These reports are anecdotal. Glassdoor summaries list one-on-one interviews, phone interviews, and skills tests as common stages, with difficulty around 3 out of 5 and timelines of roughly 2 to 3 weeks.

Q: What should I ask when the role title is vague? Ask whether the role is design, applications, firmware, or product engineering, since titles differ by site. Also ask how often engineers talk to customers and what bring-up looks like.

Practice with engineers who've run these interviews

Book a 1-on-1 mock interview with verified experts from Intel, NVIDIA, Qualcomm, and Apple. Practice these questions live in a mock interview with a verified chip design engineer.

Find your expert

Already running these interviews at work? Get paid to run them on MockVise, anonymously and on your own hours. Become an expert