There was 1 round of tough technical stuff, specifically sitting down with an engineer for 2 hours and trying to add a feature to a sample code base.
The second round would have been behavioral, which was really tough.
They brought me to a terminal, and then asked me to look through a code base and make some changes.
The catch was that the code was all C, and very poorly named. It was really tough to figure out what was going on. I guess one thing I should have done is asked more questions or opened up the files in a text editor it would save my search time. Don't focus on algs, and data structures it won't help you much. It is best to understand C and system calls. I would also get really good at using advanced text editor tools. They brought me to a terminal, and then asked me to look through a code base and make some changes.
The catch was that the code was all C, and very poorly named. It was really tough to figure out what was going on. I guess one thing I should have done is asked more questions or opened up the files in a text editor it would save my search time. Don't focus on algs, and data structures it won't help you much. It is best to understand C and system calls. I would also get really good at using advanced text editor tools.
The following metrics were computed from 8 interview experiences for the SingleStore Software Engineer role in San Francisco, California.
SingleStore's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for SingleStore's Software Engineer interview process in San Francisco, California.