Drimva

Google

Senior Hardware Emulation Engineer, Google

Sunnyvale, CA, USA · Senior · Full-time · Posted Oct 14, 2026

Experience
8 years; preferred experience across three or more SoC projects/tapeout cycles.
Education
Bachelor's degree in Electrical Engineering, Computer Engineering, a related field, or equivalent practical experience.

About the job

Builds and maintains hardware-emulation infrastructure and workflows to verify, bring up, and validate complex TPU and other ASIC designs before and after silicon production.

What you'll do

  • Build, compile, and debug full-chip and multi-die SoC RTL models and tests on emulation platforms.
  • Bring up external interfaces and develop emulation workflows, verification methodologies, and CI/CD automation.
  • Partner with firmware, software, and validation teams to co-verify hardware, debug platform issues, and reproduce silicon bugs on emulation.

What they ask for

  • Bachelor's degree in Electrical Engineering, Computer Engineering, a related field, or equivalent practical experience.
  • 8 years of experience with hardware emulation systems, model compilation, runtime performance optimization, and methodology enhancements.
  • Experience with Verilog/SystemVerilog, C/C++, Python or Perl/TCL scripting, CI/CD automation, and debugging high-speed protocols using waveform tools.
  • Experience working with emulation EDA vendors and internal infrastructure teams to triage issues and gauge emulation throughput.

Nice to have

  • Master's degree or PhD in Electrical Engineering, Computer Engineering, or Computer Science, emphasizing computer architecture.
  • Experience across three or more SoC projects/tapeout cycles; experience architecting and bringing up advanced emulation testbench environments.

Pay

$163000 - $236000 (USD) base salary; 15% bonus target (amount not stated) + equity (amount not stated)

Tools

TPU, Palladium, ZeBu, Veloce, Verilog/SystemVerilog, C/C++, Python, Perl/TCL

AI focus

Supports TPU hardware acceleration for AI/ML applications through emulation, verification, and hardware/software co-verification.

Model-written summary · the original posting is authoritative

First seen Oct 21, 2026 · Last verified Nov 5, 2026 (UTC)