Be aware that Nvidia's interview process can be chaotic. What you will be asked is akin to rolling a dice. I have interviewed for multiple teams at Nvidia, so this review covers various interviews, from initial screenings to panel interviews.

First, you will not know at the start of coding interviews if you will receive one or two questions. This varies depending on the interviewer, and they will not tell you if you ask, which makes time management difficult.

More importantly, the interviewer may not be familiar with the question they are asking. This means they cannot answer questions you may have about edge cases. One interviewer did not know the optimal solution to their own LeetCode question and, worse, did not understand the suggested solution. This was despite my explaining every step, having all test cases pass, and presenting one of the canonical optimal answers from LeetCode.

Moreover, interviewers may actively try to mislead you and ask trap questions, especially while you are writing your solution. They might try to steer you away from a working solution, possibly to see if you stand your ground. Often, interviewers expect you to find a solution exactly as they would implement it. If you come up with a solution, they may make you change it so it more closely resembles their approach, even if the time and space complexities are the same.

However, the most shocking aspect of this process was that Nvidia's recruiters were the first from any company I've interviewed with to insult me. They told me I was barely qualified for the job (Why then did you make me go through the panels? To tell me that?). Then they reviewed my education and 10+ years of experience. Whatever level of education you have, they will complain you don't have better, or say they wanted just one more year of experience, disregarding what was stated in the job posting. So, be mentally prepared for that "interview."

Time and space complexity for all coding questions.