
Numecent Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Which role are you interviewing for?
4 roles · 7 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Numecent.
Software Engineer
I first spoke with a recruiter at a university career fair and did a quick on-the-spot interview covering some basic computer science concepts. After passing that, I was invited for an in-person interview. During the in-person interview, I met with two people. The first person asked me a lot about my resume, focusing on my coursework and project experience, and then asked some C++ questions. The second person also asked about my resume and projects, and then asked some questions that seemed more hardware-related.
- Can you explain what a driver is?
- What is a union in C++ and what would be the output of this code involving a union?
Software Engineer in Test
So I had 3 rounds for this role. The first was a technical round where we discussed programming and OOP concepts, though I didn't have to code anything. Since I have a hardware background, they asked a few computer architecture questions too, which weren't too tough. The second round was all about solving puzzles to test logic. The interviewers were super chill and helpful, even offering a hand if I got stuck, which I didn't need.
- If you had to debug an ATM, what would be your approach?
- Can you talk about a project you worked on and how you approached testing it?
- Could you explain what Client Server architecture is?
QA Engineer
The first part screened basic SDLC questions, like talking about different models, their weaknesses, and why Agile is preferred. The second round involved the hiring manager going over my resume and asking about my roles and how I handled situations, along with testing and development questions. The third round had logic questions (math and other types to gauge thinking and persistence) and an executive meeting, which was similar to the resume overview but focused more on understanding leadership. Overall, I learned a lot.
- How would you approach testing a basic application, such as a calculator or ATM?
Senior Software Engineer
In total there were 3 rounds. Round 1 was a 1:1 with the CTO, Round 2 was Coding with peers, and Round 3 was the Behavioural round. I did not get the offer because I had less work experience than the position required.
- What improvements can you suggest for our systems?
- Can you elaborate on event-driven programming?
Numecent Interview Questions
Quoted word for word from Numecent interview reports.
“Given 9 marbles that look the same but one is heavier, what is the minimum number of weighings needed on a balance scale to find the heaviest one?”
Read reports →“Can you explain why manhole covers are round?”
Read reports →“What is a union in C++ and what would be the output of this code involving a union?”
Read reports →“Given 5 boxes of 10-ounce widgets, where one box contains 9-ounce widgets, and you have a scale that can only be used once, how would you identify the box with the lighter widgets?”
Read reports →“Can you explain what a driver is?”
Read report →“Could you explain what Client Server architecture is?”
Read report →“Can you elaborate on event-driven programming?”
Read report →“How would you approach testing an ATM?”
Read report →“If you had to debug an ATM, what would be your approach?”
Read report →Formats, difficulty and experience
Across all 7 Numecent interview reports.