How does TypeScript handle strict null checks?

You have a function that returns a string or null. How would you call it and safely use the result with strictNullChecks enabled?

If you assign undefined to a variable typed as number, what compile error do you see with strictNullChecks on, and how can you fix it?

What does the ! non‑null assertion operator do, and when would you use it in a small component?

We recently enabled strictNullChecks in our project and a component started throwing type errors around optional props. Walk me through how you'd resolve those errors.

During a refactor, a utility function that previously returned any now returns string | null. Explain why a call site might break and how you'd adjust the code.

You notice a runtime crash because a value was null despite TypeScript not complaining. What could cause that under strictNullChecks, and how would you debug it?

Our large codebase mixes JavaScript and TypeScript files, and we want to enable strictNullChecks across the repo. What strategy would you use to roll it out without breaking many modules?

Design a pattern for handling API responses that may have missing fields while keeping strict null checks on, and discuss trade‑offs of using type guards versus a utility library.

Explain any performance implications of enabling strictNullChecks in a high‑throughput Node service, and how you'd monitor for issues after the change.

As a staff engineer, you need to lead a migration of a legacy monorepo to strict null checks, affecting multiple teams. How would you structure the migration plan, tooling, and communication to minimize risk?

Discuss the long‑term maintenance impact of strict null checks on cross‑team shared libraries, especially regarding versioning and backward compatibility.

If a critical third‑party library lacks proper nullability typings, how would you integrate it while keeping strictNullChecks enabled across the organization?