Counsel / Senior Counsel — Commercial & Regulatory
Sylvan, Inc. · Southfield, MI · 1 mo ago
LegalFull-time
We need to output only HTML fragment, no /. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. Let's parse.
Posting includes:
- Intro paragraph about Sylvan and role description: could be "About the role". Should we include that? Yes.
- Essential Duties & Responsibilities: list of duties. That's responsibilities.
- Required Skills & Experience: that's requirements/qualifications/skills. We need to decide which headings to use. The instruction: use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. Let's parse.
Posting includes:
- Intro paragraph about Sylvan and role description: could be "About the role". Should we include that? Yes.
- Essential Duties & Responsibilities: list of duties. That's responsibilities.
- Required Skills & Experience: that's requirements/qualifications/skills. We need to decide which headings to use. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple headings but only if content present.
We have "Required Skills & Experience" which includes both required and preferred qualifications. Could split into Requirements and Preferred Qualifications? But we have only headings list: Requirements, Qualifications, Skills. Might combine.
We also have "What We Offer": that's benefits etc. It includes: opportunity to help build..., broad work..., potential for incentive units..., competitive base salary..., comprehensive benefits..., collaborative culture... So we have Benefits, maybe Pay (salary). The posting mentions "Competitive base salary and performance-based bonus, commensurate with experience." That's pay info but it's vague "commensurate with experience". According to instruction: 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 actually states them. The phrase "competitive base salary and performance-based bonus, commensurate with experience." is somewhat vague but still states there is a competitive base salary and performance-based bonus. Is that considered filler? It says "commensurate with experience" which is a placeholder. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", ...). So we should not create a Pay section if the only pay info is "commensurate with experience". However they also say "competitive base salary and performance-based bonus". That's somewhat specific but still includes "commensurate with experience". Might be considered filler. Safer to omit Pay section.
Benefits: they list comprehensive benefits including medical, dental, vision, retirement plan with company contribution, paid time off. That's specific enough. So we can have Benefits section.
Schedule: not mentioned. So omit.
Qualifications: we have Required Skills & Experience (including required and preferred). Could split into Requirements (required) and Qualifications (preferred). But we have headings Requirements, Qualifications, Skills. Could use Requirements for required, Qualifications for preferred, Skills for skills list. However the posting lumps skills and experience together. Might be better to have a single "Requirements" section containing both required and preferred? But we need to avoid filler headings. If we put Qualifications heading but only have preferred qualifications, that's okay if there is content. Similarly Skills heading maybe redundant.
We could do:
About the role
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...