Small consulting company (~30 developers). I only interview for developer positions. For me a signal is something (good or bad) that hints about a the develop

Small consulting company (~30 developers). 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.