PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/System Design/NVIDIA

Design signals across power and clock domains

Last updated: Mar 29, 2026

Quick Overview

This question evaluates competency in designing signal interfaces across multiple power and clock domains in SoC-level system design, including power gating, level shifters, isolation strategies, clock-domain crossing considerations, and power-intent verification.

  • hard
  • NVIDIA
  • System Design
  • Software Engineer

Design signals across power and clock domains

Company: NVIDIA

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Onsite

In a SoC with two power domains A and B, design the interface for a signal (signal_ 1) that originates in A and is consumed in B. Address the following: ( 1) Normal operation: how would you architect signal_1 for A->B, including required cells (e.g., level shifters, isolation) and their placement (always-on vs. switchable)? ( 2) Different clock domains: if A and B use different clocks and signal_1 must meet timing/ordering requirements, what timing and CDC constraints would you add, and which design techniques (e.g., synchronizers, handshakes, FIFOs) would you use? ( 3) Same clock domain: how does the approach change if A and B share the same clock; what constraints remain, and how would you verify timing? ( 4) Feedthrough via B: if signal_1 passes A -> B -> A, how do you handle cases where B is powered off; should isolation clamp to 1, 0, or another scheme (e.g., retention/latched), and how do you decide and verify using power intent (UPF/CPF) and signoff checks?

Quick Answer: This question evaluates competency in designing signal interfaces across multiple power and clock domains in SoC-level system design, including power gating, level shifters, isolation strategies, clock-domain crossing considerations, and power-intent verification.

Related Interview Questions

  • Design a URL shortening service - NVIDIA (hard)
  • Design a bidirectional data sync dashboard - NVIDIA (medium)
  • Design first-time Kubernetes deployment in new cloud - NVIDIA (medium)
  • Design an artifact store on K8s and Cassandra - NVIDIA (hard)
  • Design a distributed multi-user counter - NVIDIA (hard)
NVIDIA logo
NVIDIA
Sep 6, 2025, 12:00 AM
Software Engineer
Onsite
System Design
6
0

Interface Design for A → B Signal Across Power and Clock Domains

Context: You are designing an SoC with two power domains, A and B. A signal (signal_1) is generated in domain A and consumed in domain B. Domains may have different voltages, may power on/off independently, and may use different clocks.

Address the following:

  1. Normal Operation (Power and Voltage): How would you architect signal_1 for A → B, including required cells (level shifters, isolation) and their placement (always-on vs. switchable)?
  2. Different Clock Domains (CDC): If A and B use different clocks and signal_1 must meet timing/ordering requirements, what timing and CDC constraints would you add, and which design techniques (synchronizers, handshakes, FIFOs) would you use?
  3. Same Clock Domain: How does the approach change if A and B share the same clock? What constraints remain, and how would you verify timing?
  4. Feedthrough via B (A → B → A): If signal_1 passes A → B → A, how do you handle cases where B is powered off? Should isolation clamp to 1, 0, or another scheme (retention/latched), and how do you decide and verify using power intent (UPF/CPF) and signoff checks?

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More NVIDIA•More Software Engineer•NVIDIA Software Engineer•NVIDIA System Design•Software Engineer System Design
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.