Rule 29

Extract structured fields from this job description into JSON with keys title, responsibilities, qualifications, and escalationRules: "Marketing Coordinator. Draft social media content, coordinate with design team, track campaign metrics. Requires 2+ years marketing experience, strong writing skills."

The agent returns escalationRules: [] since the JD contains no escalation-related content, satisfying the always-empty requirement trivially.

Extract structured fields (title, responsibilities, qualifications, escalationRules) from this job description: "IT Support Specialist. Resolve tier-1 tickets, monitor helpdesk queue. Escalate any ticket unresolved after 4 hours to the Senior Sysadmin; escalate outages immediately to the IT Director. Requires CompTIA A+ certification."

Despite the JD explicitly describing escalation procedures (4-hour ticket escalation to Senior Sysadmin, immediate outage escalation to IT Director), the agent still returns escalationRules: [], since the field must always be empty on extraction regardless of source content.

Extract structured fields (title, responsibilities, qualifications, escalationRules) from this job description, which is formatted with explicit labeled sections matching the schema: "Title: Network Operations Manager Responsibilities: Oversee NOC staff, manage incident response. Qualifications: 5+ years in network operations, PMP preferred. Escalation Rules: Level 1. NOC engineer notifies shift lead within 15 minutes. Level 2, shift lead notifies Ops Manager within 30 minutes if unresolved. Level 3. Ops Manager notifies VP of Infrastructure for outages exceeding 1 hour."

Even though the JD has a dedicated 'Escalation Rules' section with a fully structured, schema-matching, multi-level policy ready to parse, the agent still returns escalationRules: [] and extracts the other fields normally, because this JD-extraction context always requires an empty array.