I´ve recently been in charge of hiring a lot of people and have probably done +100 interviews in the last year. I generally don´t mind the stack/language candidates have been using but I always value very highly that they have used different stacks and languages during their whole carrer. When I interview 5+ years .NET developers who haven't used another language, not even in their spare time, the result is usually a…
If you don't mind me asking, how long have you been recruiting for and what size/type of companies are you recruiting for? Top tier, Fortune 500 or just mere funded startups? Context is everything. Also, I find people abuse the word signal. How are you generating your signal? And is it just within your domain of companies you recruit for or across the whole industry?
I only interview for developer positions.
For me a signal is something (good or bad) that hints about a the developer skills and curiosity. They can be as simple as knowing about their preferred programming environment: if you claim you are a 5+ year senior .NET programmer and you haven't even heard about .NET Core to me, that is a bad signal.