Tandem React Developer interview questions

First round was a phone call with a senior dev. This was a get to know you/background interview. Not really technical pretty simple. After that they sent a code test. You have to build out one of two options, they give you three days. After that you show off your finished product/code to three developers. During this round they provided very good feedback, even said mine was one of the better ones submitted. I got along with them and we were joking around and laughing. This was probably the best round and least intimidating. Since that went well they wanted me to come in to do pair programming. Their office is very cool, and the people are incredibly nice. This round consists of 3 individual hours of pair programming with two devs each and lunch with some of their designers. To prepare for this I made sure I had my react down. (The job was react developer after all) The first hour was react. That went fine. I probably could have gone faster but it being an interview obviously throws it off a little. The next hour was Ruby. The previous two rounds I informed them that not only do I not know ruby but I’ve barely even seen it. They had every opportunity to deny me, but I figured this would be a react developer role so I thought they didn’t care. So the 2nd hour was basically the two devs telling me what files to go in, explaining how ruby works, and me trying my best to do what they are asking. I eventually accomplished what they were asking but it was a decent amount of hand holding. At this point I’m already kind of thrown for a loop. The two devs said everyone there is a full stack and works on both sides. Which is great but that’s not what I applied for, what I was told prior would happen to me, and to that point was even tested on. I figured maybe they were just seeing if I could do it, I don’t know. But the next hour was going to lunch with the designers. Not much here just getting to know each other. They were all very friendly and devmynd paid so at least I got a free lunch out of it. Going into my last hour I thought, okay they saw that I’m not super comfortable with backend but especially ruby. So they would go back to seeing my react. Especially since I didn’t really get to show off that much in the first hour. (They had me start a project from scratch so a lot of it was typing out components) Well last hour was more ruby. At this point I was already a little tilted and not really confident that it was going well. When I was told it would be more ruby I think it just messed me up. What they had me do wasn’t really difficult, but again going into a project that is built out in a language you don’t know during an interview can be stressful. By the end of this hour I just felt like I had wasted their time and they had wasted mine. I don’t want to talk bad about them because they all seem like good devs, and everyone I encountered were super nice. But if you are looking for a full stack dev then why even have people apply as a react or ruby dev. I couldn’t imagine having a ruby dev that has never used react before build anything in react. Like I said they had multiple opportunities to tell me it wouldn’t work out based on what skills I know. And if they had just labeled the job “Full stack dev” I probably wouldn’t have even applied. With all that said I like how they interview. No white boarding, and no gotcha problems. I think they are doing it better than most companies.