One guide per company: how the rounds usually run, the topics they go deepest on, practice questions in their style, and a two-week plan. Real candidate experiences are added as people share them.
Computer architecture, digital fundamentals and more.
Read the guide →MOBILE SoCs · MODEMS · AUTOMOTIVELow-power design, bus protocols and more.
Read the guide →GPUs · AI ACCELERATORS · NETWORKINGComputer architecture, strong rtl coding and more.
Read the guide →CPUs · GPUs · ADAPTIVE SoCsCPU/GPU architecture, fpga knowledge and more.
Read the guide →ANALOG · EMBEDDED · POWERAnalog fundamentals, op-amps and stability and more.
Read the guide →EDA TOOLS · IPC++ and algorithms (R&D), the asic flow and more.
Read the guide →EDA TOOLS · IP · SYSTEM ANALYSISProgramming (R&D), custom / analog flow and more.
Read the guide →CPU IP · GPU IP · SYSTEM IPComputer architecture, verification strategy and more.
Read the guide →Company flavour matters, but these decide most outcomes.
Setup/hold, blocking vs non-blocking, FSMs, metastability. Hesitation on basics costs more than a missed advanced question.
Anything on your resume can become a 20-minute conversation. Prepare every project as if it's the main topic.
Interviewers score your reasoning. A clear wrong turn you correct yourself often beats a silent right answer.
Block diagrams, waveforms and FSMs. Practise drawing them quickly and neatly, because every round involves some.
Saying what you'd try next is far better than bluffing. Interviewers can tell straight away.
Ask about the team's product, the tape-out schedule and how new hires ramp up. It shows real interest.
Send us the company, role, rounds and the questions you remember, and whether it ended in an offer. We check each submission and publish only with your permission, without your name unless you ask for it.