Structured LLM router misclassifies SAP BASIS Trainer job description,...

handyman_hank

What we are trying to achieve We have a multi-step LLM-driven recruitment pipeline. The Role Router classifies a job description (JD) as either TECHNICAL or NON_TECHNICAL . Next, the Language Router selects a programming language for a coding assessment. For training-focused roles that demand deep system expertise but no hands-on software engineering or code implementation (such as an SAP BASIS Trainer), the expected behavior is: role_type =...

Originally asked by Rishabh Singh on Stack Exchange (stackoverflow) (CC BY-SA 4.0).

uphilltech

Great question — answering as the UphillTech team:

I would not make "technical" imply "coding assessment." You have at least two separate axes: domain depth and assessment mode. An SAP BASIS Trainer can be technical-domain=true while assessment_mode=training/no_code. That value should stop the task generator before it ever asks for Python. Add a deterministic circuit breaker after the LLM router: if requires_software_implementation=false, language must be plaintext if assessment_mode is training, architecture, operations, or no_code, skip coding-task generation if the router cannot cite evidence for code-writing/debugging/implementation deliverables, set no_code or needs_human_review Example output: { "domain_is_technical": true,...

Full answer by Ken Dellinger: https://stackoverflow.stackexchange.com/a/79962322 (CC BY-SA 4.0).

Need it done for your business? UphillTech.