General Manager 39489
Dhanani Group Inc · Donna, TX · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- About The Role: description of role, why join, leadership style. Could be "About the role" section.
- Responsibilities: list of duties: Floor Leadership & Restaurant Operations, Team Leadership & Development, Financial Management.
- Requirements: maybe "Who You Are" and "Education & Experience". Could be combined into Requirements/Qualifications.
- Qualifications: maybe "Education & Experience" and "Performance Metrics"? Actually performance metrics are metrics used, not qualifications.
- Skills: maybe "Leadership Style" and "Who You Are" traits.
- Benefits: list of benefits: Competitive salary and bonus opportunities, Leadership coaching and development, Career advancement opportunities, Recognition for outstanding performance, Medical, dental, and vision benefits (based on eligibility), discount program, provider finder/cost estimation tool, wellness program, pregnancy planning tool, GED credentials at no cost, Tuition Assistance.
- Pay: Not explicitly given; only "Competitive salary and bonus opportunities" but no specific numbers. According to rule: do NOT create Pay section unless posting actually states them. It says "Competitive salary and bonus opportunities" but not actual numbers. That's vague; maybe we should not create Pay section because it's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting unless actually states them. "Competitive salary and bonus opportunities" is vague but still a statement. However it's not a specific number; but it's still a statement about pay. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (competitive salary and bonus opportunities). That is a statement, albeit vague. Should we include? The rule also says prefer a few substantive sections over many thin ones. Might be okay to include Pay with that statement. But we need to see if it's considered filler. It's not "commensurate with experience" etc. It's a generic statement but still a statement. I'd include Pay section with that sentence.
- Schedule: Not mentioned. No schedule info. So do not include Schedule.
- Benefits: we have specific benefits list. So include Benefits.
- Skills: maybe we can extract from "Leadership Style We're Looking For" and "Who You Are". Could be a Skills section.
- Qualifications: maybe "Education & Experience" and "Performance Metrics"? Performance metrics are not qualifications but metrics used. Could be part of Requirements.
We need to avoid duplication. Let's structure:
About the role
... (the paragraph about role, why join, leadership style)
Responsibilities
- ... (list items from Floor Leadership & Restaurant Operations, Team Leadership & Development, Financial Management)
Requirements
- ... (Who You Are traits? maybe better as Skills)