
Nuvalence Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 28 interview experiences · FREE TO READ
Which role are you interviewing for?
5 roles · 28 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Nuvalence.
Full Stack Developer
A recruiter reached out, which was good. Then, there was a technical phone screening with a developer, which also went well. I answered all questions and had a good conversation with the engineer. Later, I got a call saying the original role I applied for (front-end engineer) was filled. They asked if I'd consider a similar role as a full-stack engineer, and despite some reservations, I agreed. The second technical interview was with an unpleasant interviewer via video call. They stated the interview would be 45 minutes, which I felt was too short to properly assess skills. The first 15 minutes were about my past experiences, and I felt the interviewer wasn't paying attention. They also reserved the last 15 minutes for my questions, leaving only 15 minutes for a technical challenge. This was insufficient time. I was given a difficult task with minimal explanation, and we coded in an online text editor. Throughout the coding, the interviewer offered no feedback or signs of engagement, only making noises like puffing and panting. Eventually, they muted their mic, and after about 10 minutes, I gave up on the task due to the time constraints and growing annoyance. It was one of the worst interview experiences I've had.
- How are you doing today?
- Implement object flattening across several nested levels
Product Manager
I had a laid-back first phone chat. The hiring manager was super nice and told me a lot about the role and company. Not too many tough questions. Then, I got a take-home assignment which was pretty simple and likely took 4-6 hours to do well, with plenty of time (5-6 days including a weekend). After that, I had 3 one-hour interviews with a senior product manager leader, a senior engineer, and a company partner. They were all friendly and seemed genuine, taking at least 15 minutes to answer my questions. Some hard questions came up, but they were typical for PM jobs. The last interview was with another partner. He was really down-to-earth, and it felt like they had already made up their minds to offer me the job, so he was mainly trying to sell me on the company and team. The whole thing wrapped up in under 2 weeks, was well-organized and communicated, and I got an offer the same day as my last interview.
- Can you share an instance where you assisted a colleague in accomplishing one of their objectives?
- Could you list some metrics that you monitored for your products or teams?
Software Developer
I was contacted by the recruiter. The interview process had 3 rounds. 1st: screening, 2nd: take-home exercise, and 3rd: three rounds of 1 hour each. The screening and take-home exercise were good and I got an offer for the final round of an interview which was the combination of three rounds 1 hour each. The first round consisted of a review of the take-home exercise and technical questions, the second round consisted of soft skills and customer-experience questions and the third round was totally based on REST API design. My overall experience was so good during the entire interview process and I performed very well in all rounds but I did not get an offer from the company. When I asked them to give me feedback regarding my application and they simply refused to give so and told me that for liability reasons they cannot give me any feedback. I again asked to consider me again but they simply rejected me and told me that they are not moving forward with my application. I am so disappointed by this rude behavior and did not understand which policy is restricted them to give feedback.
- A lot of technical questions based on your resume.
- take-home exam: Rectangle features, check for the adjacency, containment, and intersection of the rectangle sides and return the intersection points.
- What is rest API?
Marketing
The recruiter contacted me and rescheduled the interview two times on the day of the interview. Scheduled an interview with management after finally meeting with a recruiter. Two times I prepared for a video interview and booked the time out of my day to prepare for it only to have it be canceled TWICE the day of the interview. This rescheduling dragged the interview process out a good three weeks. This was a red flag I should not have ignored. The other red flag is the disproportionate number of negative and positive reviews. It's obvious when companies force their employees to leave positive reviews because they vastly differ from the "real" negative reviews. After my last interview, I was left with bad taste from management, who had an oddly negative attitude and didn't want to pursue the job further, knowing I'd be working for this person.
- Can you walk me through your background and previous experience?
Nuvalence Interview Questions
Quoted word for word from Nuvalence interview reports.
“Difference between 400 and 500 header-response.”
Read reports →“What is rest API?”
Read reports →“What's the difference between an abstract class and an interface?”
Read reports →“What are the different types of access modifiers and what is the purpose of each?”
Read reports →“What's a race condition?”
Read report →“How does Java compare to other programming languages?”
Read report →“How do you utilize NULL in Java, and what are the reasons for its use?”
Read report →“Can you explain what a REST API is?”
Read report →“What advantages does object-oriented programming offer?”
Read report →Formats, difficulty and experience
Across all 28 Nuvalence interview reports.