Interviews

Noise and Mixed-Signal Interview Questions

Practise the question, then the follow-ups an interviewer asks next.

Start with a Question TreeAI Mock Interview

7
Question trees
54
Follow-ups
29
Wrong answers explained
3
Runnable on a simulator
Question tree The interviewer asksMonte Carlo says your input pair's offset meets the budget. What can the layout still do to the offset, and how do you plan the layout to prevent it? WhyWhy Common Centroid Cancels a GradientCompareRandom Mismatch vs Systematic Layout ErrorScale ItReviewing an Analog Block Before Tape-OutWhyWhy a Bench Must Fail Known FaultsWhat IfChoosing the Faults to Plant in a Bench + 7 more follow-ups · Open this tree

Flagship Questions · With follow-ups

Question Trees

Each question opens into the follow-ups an interviewer asks next, the wrong answers people give, and what a fresher's and a senior's answer sound like.

Quick revision · One flat list

Question Bank

All 30 Noise and Mixed-Signal questions, main and follow-up. Open a track, then a topic. Answer out loud first, then open the short answer.

Jump to a Track
30 questions · 6 topicsNoise and Mixed-Signal
kT/C Noise on a Sampling Capacitor5
A resistor charges a capacitor. What is the total thermal noise voltage on the capacitor, and why does the resistor value not matter? L0L1

The total noise is √(kT/C), about 64.4 µV rms for 1 pF at 27 °C. A bigger resistor makes more noise per hertz, 4kTR. But it also narrows the bandwidth, 1/(4RC) in noise terms, by the same factor. The two cancel, so only C sets the total. To halve the noise you need four times the capacitance.

QuestionPractise kT/C Noise on a Sampling Capacitor →
Show in words why the resistor cancels out of the kT/C result. L1L2

The noise density is 4kTR, so ten times R gives ten times the power per hertz. The RC filter's noise bandwidth is 1/(4RC), so ten times R gives a tenth of the bandwidth. The total is density times bandwidth, 4kTR · 1/(4RC) = kT/C. The R cancels.

Follow-upPractise Why the Resistor Drops Out of kT/C →
Why is the noise bandwidth π/2 times the -3 dB bandwidth, and not equal to it? L1L2

A first-order filter does not cut off sharply. Its response falls slowly past the corner, so noise above f_-3dB still gets through. Integrating the whole curve gives the same total as a sharp filter π/2 times wider. That width is 1/(4RC), against 1/(2πRC) for the corner.

Follow-upPractise Why Noise Bandwidth Is Wider Than the Corner →
How does kT/C limit the resolution of a sampling ADC? L2L3

Each extra bit halves the quantization step, so the sampled noise must halve too. Noise goes as one over the square root of C, so each bit needs four times the capacitance. A bigger sampling capacitor also needs more drive current to charge in the same time. That makes kT/C a power limit for high-resolution converters.

Follow-upPractise kT/C and ADC Resolution →
Compare kT/C noise with charge injection as errors of a sample-and-hold switch. L1L2

kT/C noise is random and set only by the hold capacitor, about 64 µV on 1 pF. Charge injection is a step left when the switch opens: channel charge and clock feedthrough land on the capacitor. It grows with switch width, falls with C_H, and depends on the input, so it is distortion, not just offset. A half-width dummy switch on the inverted clock cancels most of it.

Follow-upPractise kT/C Noise vs Charge Injection in a Sample-and-Hold →
Input-Referred Noise of an OTA5
This bench runs a noise analysis on a five-transistor OTA. Why does it read the input-referred spectrum, and which devices dominate it? L1L2

Input-referred noise is output noise divided by gain, so amplifiers with different gains can be compared fairly. In a 5T OTA the input pair dominates. The load mirror adds its noise scaled by g_m3/g_m1, and the tail cancels as common mode. Here flicker noise dominates up to about 939 kHz. Above that, the thermal floor needs the model's γ, about 2 for the NMOS pair, not the textbook 2/3.

QuestionPractise Input-Referred Noise of an OTA →
Why does noise from the tail current source not appear at the OTA's input? L2

Tail noise changes the current in both halves of the pair equally. That is a common-mode change. The OTA rejects common mode, so the tail noise barely reaches the differential output. It returns if the halves are badly mismatched.

Follow-upPractise Why the Tail Current Source Adds No Noise →
Compare the load mirror with the tail. Why does the load's noise reach the input when the tail's does not? L2

Each load device's noise current flows into one side of the OTA only. So it is a differential signal, and the OTA does not reject it. Referred to the input, the load's noise appears scaled by g_m3/g_m1. A smaller g_m3/g_m1 lowers its share.

Follow-upPractise Why the Load Mirror Noise Does Not Cancel →
Compare flicker noise with thermal noise in a MOSFET. How do you reduce each one? L1L2

Thermal noise is white, 4kTγg_m in the channel, and falls when g_m rises. Flicker noise falls with frequency and with gate area. The flicker corner is where the two meet. In the lesson, 16 times the area moved the corner from 1.29 MHz to 48 kHz. Read a device's noise over the band you use, because a 100 kHz number says nothing about 10 Hz.

Follow-upPractise Flicker Noise vs Thermal Noise →
You own the front end of a sensor chain. How do you split the noise budget between the amplifier, the sampling capacitor and later stages? L3

Independent noise sources add as powers, so write the budget in squared volts. Refer every stage to the input by dividing by the gain in front of it. The first stage usually dominates, so give it most of the budget and enough gain. Size the sampling capacitor from kT/C. Check the total over the real signal band, flicker included.

Follow-upPractise Splitting a Noise Budget Across a Signal Chain →
Monte Carlo on an Amplifier's Offset5
Set up a Monte Carlo run for an OTA's offset. What do you report from it, and what number do you sign off? L1L2

Give every transistor in every copy its own random draw. In sky130, turn mismatch on with MC_MM_SWITCH=1 and fix the seed, so the run repeats. Report the mean and σ. The mean is the systematic offset plus a small sampling error. Sign off at the mean plus or minus 3σ, not at the worst die you happened to sample. In the lesson 30 dies gave a mean of -2.62 mV and σ of 1.83 mV.

QuestionPractise Monte Carlo on an Amplifier's Offset →
Why does a bigger device match better, and by how much? L1L2

Random variations in doping and edges average out over a larger gate. For a pair, σ of the threshold difference is A_VT divided by √(W·L). Four times the area halves it. For sky130 the lesson found A_VT of about 4.75 mV·µm for the NMOS and 8.28 mV·µm for the PMOS.

Follow-upPractise Pelgrom's Law →
Why does mismatch fall with 1/√(W·L), and not with 1/(W·L)? L2

The threshold error comes from many small random events, such as single dopant atoms, spread over the gate. Their number grows with the area. The spread of a sum of random events grows only as its square root. Averaged over the area, the error therefore falls as 1/√(W·L).

Follow-upPractise Why Mismatch Falls as the Square Root of Area →
What if you can afford more area for only one device pair? Which do you grow? L2L3

Grow the pair whose share dominates the offset. Each pair's part adds as a power: the input pair one to one, the load mirror scaled by g_m3/g_m1. Four times the area of every device halves σ. Sixteen times the area of one pair leaves the other pair's part untouched, so it helps only if that pair dominated.

Follow-upPractise Which Device to Make Bigger →
Compare process corners with a mismatch Monte Carlo run. Do you need both? L1L2

Yes. A process corner moves every transistor of a type together, the global spread between wafers. Mismatch moves each transistor alone, the local spread on one die. Offset comes mostly from mismatch, while bias currents and speed move mostly with corners. Sign-off runs corners crossed with supply and temperature, plus Monte Carlo.

Follow-upPractise Process Corners vs Monte Carlo →
Layout for a Matched Input Pair8
Monte Carlo says your input pair's offset meets the budget. What can the layout still do to the offset, and how do you plan the layout to prevent it? L3

A schematic Monte Carlo sees only random mismatch. Layout adds gradients and edge effects, which depend on position and shift every die of a wafer the same way. Under a linear gradient, offset equals the gradient times the distance between the devices' centres. A common-centroid pattern such as ABBA makes that distance zero. Dummy fingers at the ends remove the edge effect.

QuestionPractise Layout for a Matched Input Pair →
Why does an ABBA arrangement cancel a linear gradient? L2

A linear gradient shifts each finger by an amount proportional to its position. In ABBA, the A fingers sit at both ends and the B fingers in the middle. Both devices then have their average position, their centroid, at the same point. So the gradient shifts both by the same amount, and the difference cancels.

Follow-upPractise Why Common Centroid Cancels a Gradient →
Compare random mismatch with systematic layout errors. Which one does more area fix? L2L3

Random mismatch is different on every die and falls with area, so bigger devices help. Systematic errors from gradients and edges shift every die the same way. They depend on where the devices sit, so more area alone may not help. Placement fixes them: common centroid, dummies and the same orientation.

Follow-upPractise Random Mismatch vs Systematic Layout Error →
You review a colleague's op-amp and bias block a month before tape-out. What evidence do you ask for before you accept it? L3L4

Ask for every specification line with its measured margin at every corner, crossed with supply and temperature. Ask for Monte Carlo mean plus or minus 3σ on offset and matching. Check stability at the worst load and feedback factor, with a step as well as a margin. Check start-up with supply ramps, fast and cold-slow. Finally, ask which known faults the benches were shown to catch.

QuestionPractise Reviewing an Analog Block Before Tape-Out →
Why should a test bench be shown to fail on purpose before you trust it? L2L3

A bench that passes everything may not be measuring what you think. Insert known faults, such as a missing R_z, a starved bias or a swapped input. A good bench fails each one with a clear reason. In the lesson, DC-level checks missed both a missing R_z and a starved bias.

Follow-upPractise Why a Bench Must Fail Known Faults →
Which faults would you plant in a DAC output buffer bench, and which check should catch each one? L2L3

Plant faults that a weak bench would miss. Remove R_z: the step settling check at speed must show ringing. Starve the bias: the input-range check at speed must fail near the top code. Swap the inputs: the open-loop sign check must fail. Each check that never fails is measuring nothing useful.

Follow-upPractise Choosing the Faults to Plant in a Bench →
You must hand over a bias block to other designers. How do you write its specification and prove it? L3

Write each requirement as one line with a limit and a measurement, set after measuring a reference design at every corner. Use one bench per check. Run a supply sweep and a temperature and supply sweep for the worst case. Add an output sweep for compliance and power-up transients, fast and slow. A constant-g_m reference moves its current on purpose, so specify the tail current as a band.

Follow-upPractise Writing a Bias Block Specification →
What if a DAC output buffer passes at typical but a corner moves its input range? L2L3

A corner can push an edge of the input range past the top or bottom code. Then the buffer's tail leaves saturation at that code and the output error jumps. Choose the DAC references inside the buffer's range at speed, not just where the DC error is small. Check them at every corner.

Follow-upPractise A DAC Buffer's Input Range at the Corners →
A Latched Comparator's Decision Time4
How long does a latched comparator take to decide, and what happens as the input difference goes to zero? L1L2

The latch amplifies the small input difference by positive feedback, so it grows as e^(t/τ). The time constant τ is about C/g_m of the cross-coupled inverters. The decision time is τ times the log of the ratio between the full swing and the starting difference. Each tenfold smaller input adds ln 10 · τ, 105 ps in the lesson. As the input goes to zero, the time has no limit.

QuestionPractise A Latched Comparator's Decision Time →
Why does the difference in a cross-coupled latch grow exponentially? L1L2

Each inverter drives the other's input. A small difference makes each one push its output further apart, and the rate of growth is proportional to the difference itself. Growth proportional to size is exponential growth. The time constant is the node capacitance over the inverter g_m.

Follow-upPractise Why Regeneration Is Exponential →
What if the input difference is ten times smaller? How much longer does the decision take? L1L2

The difference grows as v_0·e^(t/τ), so a ten times smaller start needs ln 10 times τ more. In the lesson that was 105 ps per decade, with τ = 45.6 ps. There is no upper limit: an input near zero can take any length of time. That is metastability, and it sets the comparator's error rate.

Follow-upPractise A Ten Times Smaller Comparator Input →
Compare a comparator's slow decision with flip-flop metastability. L2L3

They are the same physics. A flip-flop sampling a changing input is a latch that starts from a tiny difference. The undecided window shrinks as e^(-t/τ) with the time allowed to settle. That is why MTBF grows exponentially with settling time, and why synchronizers add a whole clock period of settling.

Follow-upPractise Comparator Decisions vs Flip-Flop Metastability →
Defending an Analog Block You Designed3
Walk me through an analog block you designed. Cover the specification, how you sized it, what went wrong, and how you knew it was ready. L2L3

A strong answer starts from the specification lines and the margins you set. It explains the sizing method with one or two real numbers. An example is g_m/I_D charts, which plot transconductance per unit current against current density. It tells one problem in detail, such as poor phase margin at the heaviest load, with what you tried and what worked. It ends with the evidence: corners, Monte Carlo, start-up and post-layout results.

QuestionPractise Defending an Analog Block You Designed →
Tell me about a time your block behaved differently after layout. What changed, and what did you learn? L2L3

A good story names the effect, such as extra parasitic capacitance that cut phase margin or a gradient that added offset. It shows how it was found, by post-layout simulation or measurement, and how it was fixed. It ends with what changed in the method, such as margins kept for parasitics or common-centroid placement planned from the start.

Follow-upPractise A Post-Layout Surprise →
Compare biasing a transistor at high g_m/I_D with biasing it at low g_m/I_D. L1L2

High g_m/I_D, near weak inversion, gives the most transconductance per microamp. But the device is wide and slow, and its threshold mismatch becomes a larger current error. Low g_m/I_D, strong inversion, costs current but gives small, fast devices and better current matching. Input pairs often sit high for noise and offset; mirrors and fast stages sit lower.

Follow-upPractise High vs Low gm/ID →

Your Review Queue

Saved review reminders are coming soon.