VLSI interviews have a fairly predictable shape once you've sat through a few of them: they usually move from fundamentals, to flow-specific technical questions, to a deep-dive on your own project work. Knowing that structure in advance makes preparation much more targeted.
Part 1: Fundamentals questions
These check whether your core digital logic and CMOS understanding is solid, regardless of which specialisation you're interviewing for. Common areas:
- Explain the difference between combinational and sequential circuits, with examples
- What is setup time and hold time, and what happens if either is violated?
- Draw and explain a CMOS inverter — why does it consume power only while switching?
- What is metastability, and how do designers guard against it?
- Explain the difference between synchronous and asynchronous design
How to prepare: Don't just memorise definitions — be able to draw the circuits and explain the reasoning out loud. Interviewers often ask a follow-up "why" after a correct answer, specifically to see if you understand the reasoning or just recalled a fact.
Part 2: Flow-specific technical questions
These vary significantly depending on the role:
For Physical Design roles
- Walk me through the RTL-to-GDSII flow
- What's the difference between global and detailed routing?
- How do you fix a hold time violation? A setup time violation?
- What causes congestion, and how would you address it during placement?
For Design Verification roles
- What is the difference between verification and validation?
- Explain the UVM testbench architecture — what does each component do?
- What's the difference between directed and constrained-random testing?
- How do you measure whether your verification is "done"?
For Analog Layout roles
- Why does device matching matter, and how do you achieve it in layout?
- What is a guard ring, and when would you use one?
- Explain common-centroid layout and when it's necessary
For DFT roles
- What is a scan chain, and how does scan insertion work?
- Explain the difference between stuck-at faults and delay faults
- What is ATPG, and why can't you just test every possible input combination?
How to prepare: These questions reward hands-on experience heavily. If you've actually run a placement tool and seen a congestion report, that question stops being theoretical for you — you have a real example to reach for.
Part 3: Your project, in depth
This is often where interviews are actually won or lost. Expect to be asked to walk through a project you list on your resume, in real detail:
- What was the specific problem you were solving?
- What choices did you make, and why those and not alternatives?
- What went wrong along the way, and how did you debug it?
- What would you do differently if you did it again?
How to prepare: Don't just be able to describe what your project did — be ready to explain the reasoning behind specific decisions and, ideally, a real problem you hit and solved. That last part especially signals genuine hands-on experience, since it's very hard to fake convincingly.
A few practical tips
- Practice explaining out loud, not just reading. Interviews are verbal — comfort explaining a concept out loud is a different skill from recognising it on a page.
- Get comfortable at a whiteboard (or virtual equivalent). Many technical questions expect you to sketch a circuit or a flow diagram while explaining.
- Do mock interviews with someone who's actually hired for these roles. They'll ask the follow-up questions a general interview coach wouldn't think to ask.
The common thread across all of this: interview performance in VLSI tracks hands-on experience closely. The more of this you've actually done — not just read about — the more naturally these conversations go.