The interviews were pretty standard. A simple coding task. Initial interview with an Engineering Manage who I really enjoyed talking to. Then a technical interview with seniors having decades of experience as Java developers. However, their knowledge seemed to be limited. I mean which engineering manager, who has worked his whole life as a java developer, would not know how ConcurrentHashMap works? They asked weird questions and were fixated on me providing exact names and keywords in the answers. I knew then and there that I won't be selected because they were unable to explain the requirements. The task that was written did not match the clarification provided even when I tried to ask questions about it. Ever since the interview started they seemed uninterested, as if they were being forced to sit and interview me. I would never work in a team with such dull colleagues. It is a pity that a company like Scalable Capital, that has great potential, has hired such people to lead their engineering team. I am even skeptical of using SC as my investment app after talking to supposed leaders of the tech team with such limited understanding of the programming construct they live upon. Never again, SC.

Without an initial interview I was assigned a Codility test. The tasks were easy, below junior level. However, you're forced to do them using the Codility in-browser "environment", which is hardly better than using Window's Notepad, in Java 8 (a decade old). You're given the DTOs and entities stacked in a sidebar with no kind of syntax highlighting. You're forced to write imports by hand, without any sort of autocomplete or basic error handling. Tests cannot be run individually, so you cannot only test one method and the whole stacktrace of every test is dumped to a console and you have to scroll to infinity to find the relevant information. The task itself is very easy, but using such a tool wastes at least half of the time you're allotted. The tool doesn't even have a "save last working version" functionality to allow you to work to the last second. There is no warning about the time running out, and it will leave you hanging while writing. I had a single small error left after choosing the wrong provided constructor. While fixing it the time ran out just as I needed to close a parentheses leading to a syntax error and the code not being able to compile. All I needed to pass 100% of the tests was two keystrokes. However, the rule is that no matter what, should it occur the interview process is ended. Without trying to fix the error the code would have been 95% and the process would have continued. I explained this situation and was simply written an inflexible generic copy and paste rejection message. My feedback about a lackluster system and unrealistic way of skill assessment went ignored.