Hyperscience Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 9 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Hyperscience.
Hyperscience
Software Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding
A recruiter reached out about this role. I spoke to them first. Then came the technical interview. The interviewer asked me about the coin change problem. I presented two approaches: brute force and dynamic programming. When I pointed out the dynamic programming solution's better time complexity, the interviewer claimed it was the same as brute force. I suggested one might be O(n^m) and the other O(n*m), but they insisted they were identical. Perhaps they expected an explanation of basic math operations? Regardless, I proceeded to code the dynamic programming solution. It took me about 10-12 minutes to write, but I encountered a syntax error. I explained that the initial values needed to be set to infinity or a very large number for the logic to find the lowest denominations correctly. However, they didn't permit me to fix the syntax error, write a print statement, or even re-run the code. I didn't request to use Google. I copied the code later to run on my own machine, and upon correcting the initial value syntax, it worked. I reiterated that since the return statement was outside the loops and lacked a break, the loops must complete before evaluating the solution's outcome. Apparently, a nested FOR loop with an IF condition was considered too complex.
Confirmed questions1 question
- Regarding the coin change problem, can you provide solutions?
Hyperscience
Software Engineer
Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Coding System Design Behavioral
So the process was split into four parts: First, I had an initial recruiter chat where they sold the company and we got to know each other. Then came a coding test that was all about algorithm tricks. After that, there was a systems design test where I had to solve a problem similar to what they actually work on. Finally, I had a conversation with the manager, which was a good chance to ask my own questions and just geek out a bit.
Confirmed questions2 questions
- The coding test involved a boggle solver.
- The Systems test was about designing an image storage system.
Hyperscience
Software Engineer
Mid Average Neutral experience Accept offer 5 rounds
Interview process
Technical screen Recruiter call Onsite Background check Offer
Interview formats
Technical Behavioral
It was a long interview process with many people involved. The whole thing didn't take too long, but there were 5 interviews. Two of them were technical, and the rest were with different people from other departments. All in all, it gave a good idea of the company and the position you would have in the process.
Confirmed questions1 question
- How would you personally handle a specific task related to the Hyperscience product?
Hyperscience Software Engineer Interview Questions
Quoted word for word from Hyperscience interview reports.
“How many minimum buckets are needed to hold all elements in an array?”
Read reports →“Regarding the coin change problem, can you provide solutions?”
Read reports →“Can you write a working program with that algorithm on an online C++ compiler?”
Read reports →“Could you solve a simple algorithm problem on the white paper and explain it verbosely?”
Read reports →“Tell me about a project you really enjoyed and what you learned from it.”
Read report →“How would you personally handle a specific task related to the Hyperscience product?”
Read report →Formats, difficulty and experience
Across all 9 Hyperscience interview reports.