The interview process began with a recruiter e-mail scheduling a phone interview. I was rescheduled with another recruiter at the last minute. It was clear the recruiter I talked to spent zero time reading my resume, because she kept getting simple details wrong that I had to correct her on (what school I went to, details about my projects/experience that were clearly written). As a candidate who spent several days/hours preparing for the screen, its disrespectful to talk to someone who spent no time at all getting simple details about the candidate you're talking to correct. I then got an invitation for a coding test. The coding platform is horrible (testdome) and the formatting of the question was very bad. The question/examples was just one large block of text with no line breaks, and made it very hard to read. Furthermore, it didn't even let me copy/paste the question to a text editor to make it easier to read. The instructions for the test were very unclear, and I did not realize until several minutes in that we are allowed and expected to use STL for the test. Much of the test is just figuring out what library to import and use. When you run the code, it is tested against several test cases with bad naming (test case name "backity back") that you can't see the output to. Not only is this unrealistic, it means you have to account for any error that may go wrong with the program, and the instructions don't tell you how to handle cases which may throw these errors. For example, if the program should only take alphabetical characters, the question has no instructions on how to handle numeric input when you know its probably one of the test cases. Since you can't see the output, you're left guessing on whether you're returning the correct error value or if you're even doing a correct test case. Overall a pretty bad interview experience. Things were timely, but the recruiter was a bit rude and the coding platform and questions were pretty bad and could have been much more directly asked.