
HPR Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 19 interview experiences · FREE TO READ
Which role are you interviewing for?
4 roles · 19 reportsCandidate interview experiences
First-hand accounts from people who interviewed at HPR.
FPGA Engineer
Started with a 30-minute intro phone call, then a 45-minute technical interview with the team lead. After that, I had 4 back-to-back 45-minute technical interviews with the whole FPGA team on the same day (though they said I could split them up). Then, there were a few calls where they tried to figure out my salary expectations, even though I'd already mentioned my current pay and what I was looking for. This was followed by a 45-minute chat with the VP, which was great and I learned a lot about the company. Finally, they had an offer call.
- Lots of design questions, some with very clear answers and some more open ended.
- They paid a lot of attention to critical paths and minimizing logic usage/latency because that's their bread and butter.
Applications Support Engineer
The hiring process was pretty smooth and moved fast. It began with a 30-minute behavioral phone chat, then a 45-minute technical phone interview. After that, they offered me a third interview, which would have been on-site. But, they told me their needs changed and they were looking for someone to work European business hours, so I decided not to proceed.
- Tell me about your experience with C/C++ programming.
Software Engineer Intern
Submitted my application online and also pinged the head university recruiter, Avery Hale. The process involved an online assessment (which I didn't totally ace) followed by a phone screen. Then, there were two 45-minute technical interviews, plus a 45-minute informal chat with a director. I ended up getting an offer. Important note: the online assessment is only offered in C, and so are the technical interviews. You're expected to be comfortable with C syntax and, to some extent, its lower-level features like bitwise operations. For the 2x45 technical interviews, about 15-20 minutes was spent on behavioral/technical Q&A, and the remaining 25-30 minutes was for a coding problem. The chat with the tech director was completely non-technical and non-behavioral; it was just a casual conversation about the intern experience at HPR.
- Given a computer clock frequency of 3 GHz and a program runtime of 360 ns, calculate the number of instructions executed.
- Can you explain what a computer thread is?
- What is TCP/IP?
Director of Technology
I started with a phone screen call with their Director of Hiring. After that, I had a long phone interview with their VP of Engineering. This then led to an onsite interview, which included a really long 1 hour 45 minute interview with the CEO.
- It covered a spectrum from technical talks to process discussions and behavioral questions concerning management and leadership.
- Most of the questions were about very fundamental things like introducing yourself, etc.
HPR Interview Questions
Quoted word for word from HPR interview reports.
“Implement the function: bool isPrime(uint8_t num).”
Read reports →“Given a computer clock frequency of 3 GHz and a program runtime of 360 ns, calculate the number of instructions executed.”
Read reports →“Write code to find a cycle in a linked list.”
Read reports →“Can you reverse a linked list in C?”
Read reports →“Given a description of the ipconfig command, what command is it?”
Read report →“What is the impact of the GIL on Python concurrency?”
Read report →“What are the average and worst-case runtimes for hash table operations?”
Read report →“What is TCP/IP?”
Read report →“How would you detect a cycle in a linked list?”
Read report →Formats, difficulty and experience
Across all 19 HPR interview reports.