I can't comment on the back-end jobs, but I did interview at Uken a couple of weeks ago, with bizarre results.
I was interviewing for a Team Lead role. When I mentioned to people in my network that I was interviewing at Uken, they generally told me to steer clear. I decided not to pay much attention to this, since I knew the company had a couple of rough / cancelled projects a couple of years ago. I decided to look at them through fresh eyes. Also, I was excited to take on a formal team lead role, as I have often performed these duties informally, and I'm getting older.
The first set of interviews went well. There was a minor coding test and I seemed to ace it. The role would have been all about C# with Unity, but I had my choice of coding language for the question, and chose Python. One of the interviewers that day seemed to imply that the project I'd be taking over had some serious code quality issues. To me this was an opportunity, rather than a turn-off. I'd have a chance to make an immediate impact, I thought.
Then came the second set of interviews. First, I talked to the CEO. That seemed to go well, and got me further excited about the role. The next step was white-boarding with the other team lead (not the one from the first tech interview).
The question was to architect / design a card and deck API in C#. I felt well prepared for this, as I've worked on card / casino-like games in the past. Before getting very far in, he threw me a curve-ball: you should also support Magic-style collectible card games. He kind of seemed to be making things up as we went along -- it seemed pretty clear that he hadn't run through this exercise himself. By the end of the interview, he was saying things like "maybe I shouldn't have thrown in the Magic requirement".
It could have gone better. I don't think I aced it, but I also don't think I did poorly. I made a couple of unforced errors e.g. defining enums where I got confused between C++ and C#. I also started to use an ArrayList instead of a List&lt;T.
The exercise didn't test any of the advanced or esoteric features of C#. In fact, the interviewer said that they don't use advanced features. They just use plain-vanilla C# because they have a lot of interns, and frankly he didn't know Unity when he started the job.
So, I leave thinking, "well, I could have done better, but they seemed satisfied".
A couple of days later, I get a call from HR stating that my knowledge of C# is not sufficient. Having a C# expert is critical to the role. Keep in touch...
Now, keep in mind the interviewer's statements re: C#. Also, C# is a dead-easy language. Also, I taught C# using Unity, for game programming for a couple of years. But apparently I don't know C#.
Had they said, we weren't satisfied with how well you architected the solution, I would have found that disappointing, but not bizarre. Maybe this was lost in translation between the dev and HR?
But, here's the thing. I mention my weird interview to some friends, without naming the company. A friend asks "was that Uken?". Apparently he interviewed there within the last few months for a Senior Dev role. He aced the first technical test (same problem as me), after being told by HR that there would be no technical test that day. He even implemented unit tests, and they all passed to the interviewer's satisfaction. A day or two later, he gets feedback that he did not pass the technical test.
So, something's up. Whether by accident, or on purpose, these guys seem unable to hire good people. I'd be cautious about burning any time on them. Of course, YMMV, anti-loops, etc.