Corporate Director, Engineering
Starwood Hotels · Miami-Fort Lauderdale Area · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: headings using for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting.
The posting includes:
- Intro: "Grow with us... Life at Starwood Hotels..." repeated. This is about company culture. Could be "About the role"? Actually it's about company. Might be "About Us" but not a required heading. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also include other headings? The instruction: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting.
The posting includes:
- Intro: "Grow with us... Life at Starwood Hotels..." repeated. This is about company culture. Could be "About the role"? Actually it's about company. Might be "About Us" but not a required heading. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also include other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use other headings? Probably we should stick to those. But we need to include sections only when posting has real specific content for it. The posting includes responsibilities (the role description), qualifications (Required Qualifications & Experience), maybe skills (Preferred Professional Engineer etc). Benefits? Not mentioned. Pay? Not mentioned. Schedule? Not mentioned. About the role? Could be the introductory paragraph describing the role. Could treat that as About the role.
Thus we can have sections:
- About the role: includes description of role, reporting, portfolio, etc.
- Responsibilities: maybe list of duties: oversee engineering operations, capital planning, standardizing processes, resolving escalations, mentoring regional leaders, establishing portfolio-wide engineering framework, partnering with various functions, providing technical leadership for CAPEX planning, major renovations, preventive maintenance, utility performance, regulatory compliance, building-system reliability, managing projects in occupied hotels minimizing disruption.
- Requirements: maybe the Required Qualifications & Experience list.
- Qualifications: maybe the Preferred Professional Engineer etc? Actually those are "Preferred". Could be Skills? Or we could treat them as Skills. The instruction includes Skills as a possible heading. So we could put preferred credentials under Skills.
- Benefits, Pay, Schedule: not present, so omit.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement; we should drop that.
Also duplicate intro lines: "Grow with us... Life at Starwood Hotels is based on a simple idea..." appears twice; we should keep only once? The instruction: remove duplicated lines. So we should keep only one occurrence.
Also "Our Company 1 Hotels invites guests..." etc. That's about brands; could be part of About the role? Might be considered company description. Could be part of About the role or maybe a separate section like About Us but not allowed. Could incorporate into About the role as context.
We need to preserve all substantive information: so we need to include details about brands, purpose, mission, etc. Might be better to put under "About the role" or maybe a separate heading like "About Us" but not in allowed list. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. ...)". Likely they expect us to use those headings only. But we can also include other headings if needed? Safer to stick to those.
Thus we need to fit all info into those sections.
Let's extract:
About the role: Should include role title, reporting, purpose, portfolio, etc. Also include company description maybe.
Responsibilities: list of duties.
Requirements: Required Qualifications & Experience (the bullet list). Could be a list.
Qualifications: maybe the "Preferred Professional Engineer..." etc. Could be considered Skills? Actually they are preferred credentials, could be Skills.
Skills: maybe the preferred credentials and experience with multiple brands, acquisitions, etc. Could be placed under Skills.
But we have both Qualifications and Skills headings allowed. We could put required qualifications under Requirements, and preferred qualifications under Skills. Or we could put required under Qualifications and preferred under Skills. The instruction: Use headings as examples; we can decide.
Better: Requirements = Required Qualifications & Experience. Skills = Preferred credentials and additional experience (like experience with multiple luxury brands, acquisitions, etc). Qualifications maybe not needed if we already have Requirements. But we could also have Qualifications for education requirement? However the required qualifications includes education. So we can put all required under Requirements.
Thus:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. ...)". Likely they expect us to use those headings only. But we can also include other headings if needed? Safer to stick to those.
Thus we need to fit all info into those sections.
Let's extract:
About the role: Should include role title, reporting, purpose, portfolio, etc. Also include company description maybe.
Responsibilities: list of duties.
Requirements: Required Qualifications & Experience (the bullet list). Could be a list.
Qualifications: maybe the "Preferred Professional Engineer..." etc. Could be considered Skills? Actually they are preferred credentials, could be Skills.
Skills: maybe the preferred credentials and experience with multiple brands, acquisitions, etc. Could be placed under Skills.
But we have both Qualifications and Skills headings allowed. We could put required qualifications under Requirements, and preferred qualifications under Skills. Or we could put required under Qualifications and preferred under Skills. The instruction: Use headings as examples; we can decide.
Better: Requirements = Required Qualifications & Experience. Skills = Preferred credentials and additional experience (like experience with multiple luxury brands, acquisitions, etc). Qualifications maybe not needed if we already have Requirements. But we could also have Qualifications for education requirement? However the required qualifications includes education. So we can put all required under Requirements.
Thus:
About the role
About the role
...
Responsibilities
- ...
Requirements
- ...
Skills
- ...