Lead verification strategy and execution for CPU Core Hardware Prefetch in a high-performance out-of-order core.
Originally posted July 19, 2026 by the employer.
About the role
SiFive is looking for a Principal Design Verification Engineer to lead verification strategy and execution for CPU Core Hardware Prefetch in a high-performance out-of-order core. The primary technical scope includes advanced hardware prefetch verification with emphasis on prefetch training behavior, stream detection and replacement, issue-queue behavior, DCache interactions, and CSR configurability across block-level and core-level integration contexts.
What you'll do
- Lead verification planning and execution for CPU hardware prefetch functionality in a high-performance out-of-order core, spanning unit-level and core-level verification strategy, debug, coverage closure, and signoff readiness.
- Define verification strategy, test plans, checkers, scoreboards, assertions, stimulus strategies, and coverage models for advanced hardware prefetch microarchitecture and corner cases.
- Drive verification of hardware prefetch behaviors including stream allocation and replacement, training from demand requests, prefetch generation, request replay and kill behavior, issue-queue interactions, and feedback-driven control of prefetch aggressiveness.
- Verify runtime configurability through hardware prefetch CSRs, including windowing, initial distance, maximum allowed distance, linear-to-exponential growth thresholds, queue-allocation controls, and thresholds tied to L1/L2 cache and MSHR behavior.
- Drive verification of interactions between the hardware prefetch engine and the memory hierarchy, including DCache pipeline behavior, cacheable-read-only training conditions, MSHR fullness backpressure, and arbitration with other core-generated traffic.
- Apply verification methods including simulation, formal techniques, emulation, and performance-oriented validation for high-risk or hard-to-observe hardware prefetch behaviors.
What you'll need
- BS, MS, or PhD in Electrical Engineering, Computer Engineering, Computer Science, or a related field.
- 12+ years of relevant experience in CPU/core or SoC functional verification.
- Direct experience with out-of-order CPU core verification and deep understanding of CPU microarchitecture.
- Deep expertise in hardware prefetch verification or closely related CPU memory-subsystem verification.
- Strong knowledge of verification flow methodology, including test planning, stimulus generation, failure analysis, coverage analysis, and coverage closure.
- Strong software or scripting fundamentals for building verification infrastructure, automation, and analysis workflows.
Nice to have
- Experience verifying advanced hardware prefetch architectures, such as stride-based or stream-based prefetchers with training, confirmation, throttling, and adaptive distance control.
- Experience verifying prefetch engines integrated with DCache or memory-subsystem pipelines, including interactions with issue queues, MSHRs, cache feedback, and replay behavior.
- Experience developing or reviewing verification content that uses performance counters, constrained-random traffic, directed corner-case scenarios, and software-driven stress patterns.
- Experience with formal verification targeting bounded, control-heavy, or interface-sensitive microarchitectural problems.
- Experience using emulation or other acceleration techniques to improve turnaround on large CPU verification workloads.
Skills: CPU Core, Hardware Prefetch, Design Verification, prefetch training, memory hierarchy, SystemVerilog
- Employer posting date: 19 Jul 2026
- First seen in our index: 19 Jul 2026 (our observation date)
- Last confirmed on the employer's career site: 18 Nov 2026
- Specialty: Design Verification (Design Verification)
- Comparable active jobs: 1447 at 104 employers, as of 18 Nov 2026
- Related specialties (Digital Design & Verification family): 3703 active jobs at 129 employers
View all SiFive jobs · Verification engineer jobs
How we counted: postings read from employer career sites; dates are our observations unless labelled as the employer's. How we count