Synopsys SpyGlass Lint CDC Engineer Jobs: Find RTL QA Roles
SpyGlass is the static-analysis gate most front-end teams run before RTL ever reaches simulation or synthesis. A Synopsys SpyGlass lint and CDC engineer owns that gate: catching coding-style violations, clock domain crossing bugs, reset domain crossing problems, and DFT-unfriendly constructs while they are still cheap to fix.
The job is running SpyGlass Lint, SpyGlass CDC, and SpyGlass RDC across the RTL, then triaging what comes back. Most of the real work is judgment: deciding which violations are genuine and need an RTL fix, and which are false positives that get waived with a documented reason. Maintaining a clean, auditable waiver database is a large part of the role, and so is writing the SpyGlass methodology other designers follow.
Teams that run SpyGlass hand off lint- and CDC-clean RTL to synthesis and DFT, so the role sits next to RTL design engineer positions and overlaps heavily with CDC engineer jobs. SpyGlass shows up as a required tool in a lot of front-end RTL and verification postings, usually alongside a simulator like VCS.
Companies with strict RTL quality gates hire for this: large fabless SoC teams, networking and storage chip makers, automotive IC groups where CDC sign-off is a safety requirement, and IP vendors who ship RTL that has to pass a customer's own lint deck. If a design org has an internal methodology team, SpyGlass ownership often lives there.
US roles centered on SpyGlass lint and CDC generally run about $120K to $165K base at the mid level, with senior RTL-QA and methodology engineers reaching $180K to $240K in total comp at large fabless companies. The semiconductor salary guide has wider ranges by role and level.
Browse semidesignjobs.com for openings that name SpyGlass, and save a search so you get an email when a new front-end RTL or CDC role matching your filters opens.
FAQ
What lint rules does Synopsys SpyGlass enforce and why are they important?
SpyGlass Lint flags RTL problems such as inferred latches, combinational feedback loops, uninitialized variables, multiple drivers, and synthesis-simulation mismatches. These often pass simulation but cause wrong behavior in silicon. Lint-clean RTL is a standard quality gate before synthesis at most professional design teams, which is why hiring managers treat SpyGlass fluency as a baseline for front-end roles.
How does SpyGlass CDC analysis work and what does it check?
SpyGlass CDC runs structural analysis on the RTL to find signals crossing between clock domains without proper synchronization. It flags missing synchronizers, synchronizers placed in the wrong spot, and multi-bit bus crossings that need a specific protocol. It also separates user-verified, waived crossings from open violations, which keeps CDC sign-off manageable on a large SoC.
What is the waiver management process in SpyGlass lint and CDC flows?
SpyGlass produces a violation database that engineers classify as real issues needing RTL fixes or false positives to waive. Waivers live in a file that references the specific violation IDs, RTL locations, and the engineer's rationale. Keeping that waiver database clean and documented is a core part of RTL QA sign-off, and auditors expect a justification for every waived item.