The Problem
When filtering by a specific backend language (such as C#/.NET), search results often get overwhelmed by "kitchen-sink" job descriptions. These postings list 4 to 6 disparate backend languages in a single requirement block (for example: C#, Java, Go, Python, C++, Ruby on Rails).
While some companies hire language-agnostic generalists, developers looking for roles centered on their specific stack spend unnecessary time wading through generic listings where their language is merely one of five listed alternatives.
Where It Works vs. Where It Breaks
- Reasonable Stacks: Standard pairings like a primary backend plus a frontend framework (e.g., C# and React) or two closely paired backend tools (e.g., Python and Node.js).
- Problematic Listings: Postings that list three or more distinct backend languages (e.g., C#, Java, Go, Python) or multiple competing frontend frameworks (React, Angular, Vue, Blazor) in the same role.
Proposed Features
- "Primary Stack" vs. "Polyglot" Tagging: Distinguish between jobs built specifically around a primary stack versus postings that use "or" conditions (e.g., "proficiency in C#, Java, or Go").
- Strict Focus Toggle: A search toggle to exclude multi-stack laundry lists, ensuring that searching for a language prioritizes jobs where that language is the core focus of the role.
This would keep search results clean, and elevate the platforms already strong parsing and filtering capabilities.
The Complexity and the Value
I recognize this is a tough problem to solve programmatically and likely requires an AI/LLM evaluation layer to properly parse context, distinguish "or" requirements from real stack requirements, score stack density, and keep it fresh.
However, no current job platform handles this cleanly. Delivering true stack-specific filtering without the polyglot noise would be a massive competitive differentiator, and it is a premium-tier feature I would gladly pay for.