The reason these products don't focus on people is that people are hard. Hiring is one the hardest things out there, with often warped incentives on both ends re: honesty. Building a product/service to solve this dilemma in a way that satisfies all parties is probably even harder, and then on top of that you need a business model for pulling dollars out of the matching process.
It's much easier to just build a product that matches technology stacks, and it's not immediately obvious that it's the wrong approach.
Matching based on what you want to work on sounds dreamy for developers, and a like a disaster for startup employers.
Startups are defined by change, and a critical thing you want to hire for is flexibility and tolerance for technology schleps. This seems like the opposite of what you're selecting for in developers.
If you want to make things more pleasant for engineers, perhaps you should be targeting more stable companies on the other end -- the ones that know precisely what they need, and know that it won't change next week.
The reason these products don't focus on people is that people are hard. Hiring is one the hardest things out there, with often warped incentives on both ends re: honesty. Building a product/service to solve this dilemma in a way that satisfies all parties is probably even harder, and then on top of that you need a business model for pulling dollars out of the matching process.
It's much easier to just build a product that matches technology stacks, and it's not immediately obvious that it's the wrong approach.