The fact is, people tend to over-emphasize their area of competence and de-emphasize areas outside of it. It was probably the case that the architectural problems you solved were above their paygrade, so they ignored that and over-emphasized what they knew. The fact that you didn't share their enthusiasm for unit tests just shows you weren't a top notch developer (which always happens to be a mirror image of the interviewer).
That is the problem with soft skill interviews, in hard skill interviews there isn't much debate whether the solution is correct or not so your typical programmer can administer them correctly.
My interpretation was similar, but slightly different.
The company itself wasn't actually solving complex problems and therefore the developers involved couldn't actually understand the level of complexity I was able to deal with.
I get the feeling a lot of developers believe dealing with state in a react app is a complex problem, but I've been doing this stuff for 25+ years and left that behind as complex long ago. I know that's probably going to come across as arrogant, but it's how I feel about the entire thing. I see people all the time squabbling online over very specific source code related things as if they're important.
It was a VPS automated deployment system that could deploy both windows and linux to various datacenters around the world while also installing some 50+ pieces of software (as configured).
