I applied through a recruiter. I interviewed at Highnote
Interview
Initial screening with a recruiter with some basic, non-technical questions.
Next, one-on-one interview with a Highnote Engineer in which you are given a coding assignment and an hour to implement. If you selected to move on, you then expand on that coding assignment with other Highnote engineers. The assignment isn't too difficult. The mistake I made was that I think I over engineered it. Your goal should be first to get it working.
Interview questions [1]
Question 1
Implement a transaction processor for a virtual bank. Given an input, you will need to parse it, make some account calculations and validations, and test your solution.
I applied through a recruiter. The process took 3 weeks. I interviewed at Highnote (San Francisco, CA) in Jan 2025
Interview
The interviewers were nice and communicative. First interview was a take home assignment, second interview was technical where we reviewed the solution for the home assignment and expended it. Third interview was with technical about multithreads
Interview questions [1]
Question 1
Implement a Transaction Processor on virtual bank accounts
I applied through a recruiter. The process took 3 weeks. I interviewed at Highnote (San Francisco, CA) in Apr 2025
Interview
The interview process was structured and engaging. It included two live coding exercises focused on practical, real-world problem solving, followed by a system design round. I also had conversations with team leads to assess mutual fit, a behavioral “Ethos” interview, and a final discussion with the CTO to align on team placement and long-term goals.
The recruiter, Catherine, was very responsive and helpful throughout the entire process, and I genuinely enjoyed the interviews - they felt relevant, thoughtful, and aligned with the kind of work I'd be doing on the job.
Interview questions [1]
Question 1
One of the coding rounds involved designing a lightweight transaction processing system, with a focus on input parsing, validation, and modularity. It was a practical problem, close to real-world scenarios.