A raw score can be useful as one input, but it should not be the only thing a customer sees. A posting may contain strong keyword overlap while still failing a practical requirement such as location, seniority, compensation, or required domain experience. Layiq separates raw scoring from the visible recommendation so those issues can be handled.
Why Layiq separates them
Raw score
A numeric estimate based on available matching signals. It can be directionally useful but may be too optimistic if the posting is thin or contradictory.
Public recommendation
The customer-facing band after fit gates, mismatch flags, and explanation consistency checks are applied.
Explanation
The plain-language reason for the label. It should call out the strongest evidence and the most important uncertainty.
Common reasons a label is capped
- The role asks for a required industry or technical domain that your profile does not show.
- The posting title looks aligned, but the responsibilities point to a different function.
- The location or work mode conflicts with your criteria.
- Compensation is missing or outside the stated range.
- The posting appears stale, duplicated, or too vague to support a strong label.