Worst hiring experience I've had with a company. I initially reached out to a recruiter after seeing a position posted. We got in contact (he was nearly half an hour late) to talk about my background and what I was looking for. A week later, I had a screening with the hiring manager and team, which went very well...just a general mix of technical and behavioral questions. I was told from the hiring manager that he absolutely wanted to move forward, so I'd hear back from HR very shortly, and that he'd have my HR contact get back to me with answers to some questions I had asked that he didn't immediately know. And that's it. It's been a month and a half now, and I've heard nothing. My HR contact has ghosted me, despite a follow up I sent over a couple weeks ago. It's clear they don't take hiring seriously at all, and have no problem wasting candidates' time. If you read the other reviews here, you'll find many similar stories. Very disappointing.
A non technical phone interview with hiring manager
One onsite technical interview with hiring manager which included 2 technical questions.
One online technical interview took 2 hours with hiring team lead which included 3 technical questions
Questions d'entretien [1]
Question 1
One logical question and one leetcode style quesiton
Had a technical interview of 2 hours where they told me a little bit about the job, asked me to introduce myself, asked me about a project I did, and then there was a coding question.
Questions d'entretien [1]
Question 1
Asked me to explain about a project I did in university.
J'ai passé un entretien chez NVIDIA (San Jose, CA)
Entretien
A typical software engineering coding interview focuses on problem-solving under time pressure. Candidates are usually given one or more algorithmic problems similar to those found on LeetCode. The interviewer evaluates data structures, algorithm selection, code correctness, time and space complexity analysis, communication clarity, edge-case handling, and debugging ability. Interviews often begin with clarifying questions, followed by writing executable or near-executable code on a shared editor or whiteboard. Strong candidates explain trade-offs, optimize incrementally, test thoughtfully, and remain calm while reasoning through unfamiliar problems.