Earlier quoted context omitted.
Recently I started trying something new for our interviews. I start with a phone interview that is more about discussing their background, expertise, what they need to feel productive, and explain the role. If I think they’d be a good culture and expertise fit, I send them something like this (I’ve made a few): https://gist.github.com/tywalch/cf60e4c942ab6a80e481f4ba6754... . It’s a small “api service” that represent…
TL;DR: you're testing for likability and other emotional response.
That doesn't mean you got to fit some tight social profile, far from it.
But since we're a small team each person has a lot of responsibility, and so we need to trust the right decisions are made for the right reasons, that communication won't be an issue, that you can handle dealing with customers for projects and troubleshooting etc.
We don't need the best skilled coders. We need developers who're good at finding solutions to our customers problems, within the constraints of us being a small team with limited resources (time most of all). We need someone who's capable of learning new technologies as the needs arise, and we need someone who can communicate well within the team and with our customers.
When I got hired, my actual coding skill wasn't really a topic. I didn't get a single programming quiz or similar question. They were far more interested in my background, what sort of projects I had been working on, what motivated me etc.