R3 Senior Software Engineer interview questions

Initail contact from internal recruiter, very nice and kind and helpful with clear instructions and guidance throughout the process. A take home code review exercise and then a live coding session with two other engineers with shared screen. Overall it was a positive experience even though I think they are a bit too pedantic despite you prove to have a sound knowledge and skill, even though not to the perfection level expected during a live coding session.

As previous candidate commented, code review test is very easy, you do it in your own time and send your comments back. Coding test is also very easy, but I failed it due to "helpful" instructions I was given. It's time-boxed to one hour and I was told it will be an algorithm design challenge and architecture/design task. I was told to put focus on the communication skills. All information I got was completely misleading and now I'm sorry for all the time invested and wasted. "Algorithm design" was about implementing a simple interface that doesn't really require any brain power nor preparation. As instructed, I was discussing what I'm doing and why, commenting all concerns that came to my mind and alternative solutions. For some comments I got feedback like "a good catch", "good thinking" so I thought everything was going fine. After I was done with the initial part, I was given the next functionality to implement. It all lasted about fifty minutes and at the end I got opportunity to ask general questions about the company. I was a bit confused after the interview as it was much easier than I expected, it was like someone was asking me to answer 1+1 questions, but also that there wasn't any design question. Several days later I got feedback that the coding assignment was not completed fully in the allotted time and we also didn't have time to go through a design question to assess my design so they cannot progress further with my application. So here are tips for future candidates. They don't give you scope of the coding task, you get pieces bit by bit instead, so you won't have any idea how much is still left nor how fast should you go. Regardless of what they say, it's a "coding monkey" type of assignment where you should not waste any time on communication, but hurry to finish it as fast as you can, which is obviously the most important criterion to pass it.