Events and Promotions Coordinator - On Call
Seminole Hard Rock Hotel & Casino Hollywood · Hollywood, FL · 1 mo ago
ManagementPart-time
We need to output HTML fragment with sections: About the role? Actually the posting includes: "About Seminole Hard Rock Hotel & Casino Hollywood" (company description). Then "Benefits & Perks". Then "Job Description" with "Job Summary:" and "Essential Job Functions". Then "Qualifications". Then "Work Environment". Then "Closing" (tribal preference). Then "Required" (gaming licensure). Then "Disclaimer". Also there is repeated tribal preference lines.
We must not repeat job title as heading. Use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to appropriate headings. The instructions: "use
.
Qualifications:
"High School Diploma required or the equivalent combination of education and/or experience.
College degree in Marketing, Hospitality, or Event Management preferred.
Strong guest relations experience of at least two years required.
Three years relevant experience in casino environment, promotions, productions, public speaking, or special events strongly preferred.
Strong knowledge of MS Office applications, including Outlook and Excel required."
We'll list each.
Requirements: we need to capture work environment, physical demands, schedule, communication, tribal preference, gaming licensure.
From Work Environment paragraph:
"May be exposed to casino related environmental factors including, but not limited to, second hand smoke and excessive noise.
While performing the duties of this job, the employee is frequently required to stand; walk; use hands to finger, handle, or feel; reach with hands and arms, talk or hear; and taste or smell.
The employee must frequently lift and/or move up to 50 pounds.
Specific vision abilities required by this job include close, distance, color, and peripheral vision, depth perception and ability to adjust focus.
The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job.
The Casino environment is hectic, fast-paced and often crowded and noisy.
May be exposed to casino related environmental factors including, but not limited to, second hand smoke, excessive noise and constant exposure to general public.
Must be able to communicate effectively with guests in English, specific to position duties and responsibilities.
Must be able and willing to work a variety of schedules, as position requires incumbent to work long hours, to include evenings, weekends and holidays without consecutive days off."
We'll condense into bullet points, preserving details.
Tribal preference: appears twice: "The Tribal Council gives preference in all of its employment practices to Native Americans. First preference in hiring, training, promoting and in all other aspects of employment is given to members of the Seminole Tribe who meet the job requirements. Second preference is given to members of other federally recognized Native American Tribes who meet the job requirements." and later duplicate: "The Company gives preference in all of its employment practices to Native Americans. First preference in hiring, promoting and in all other aspects of employment is given to members of the Seminole Tribe who meet the job requirements. Second preference is given to members of other federally recognized Native American Tribes who meet the job requirements."
We'll keep one version.
Required: "As part of Seminole Gaming’s employment process, final candidates will be required to obtain gaming licensure by completing a background check with Seminole Gaming Compliance and Regulations, prior to an offer being extended. These background checks may include, but are not limited to: Credit Check Criminal Background Check"
We'll include as bullet.
Now Benefits: "We offer rockin' benefits that include Medical, Dental, Vision & Life Insurances, 401K, Paid time off, Annual Bonus Opportunity & much more! Please visit www.gotoworkhappy.com/benefits to see our full list of benefits!"
We'll list each benefit.
Now About the role: we need to include the company description paragraph(s). Let's extract:
"About Seminole Hard Rock Hotel & Casino Hollywood Seminole Hard Rock Hotel & Casino Hollywood is the flagship casino resort of Hard Rock International, owned by the Seminole Tribe of Florida. This world-renowned entertainment, gaming and hospitality destination unveiled a $1.5 billion expansion on Oct. 24, 2019. New offerings include 638 upscale guestrooms in the first-ever Guitar Hotel, 168 luxury guestrooms and unique swim-up suites in the adjacent Oasis Tower at Seminole Hard Rock Hotel & Casino Hollywood, and 465 newly redesigned guestrooms in Hard Rock Hotel for a combined room count of 1,271 throughout the resort. Additional amenities include the lush, “Bora Bora” style lagoon with private cabanas and butler service; a 42,000 square-foot Rock Spa® & Salon; a 13.5-acre recreational water experience for swimming, kayaking and paddle boarding; 19 dining outlets and 20 bars and lounges; an
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to appropriate headings. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when appropriate. But we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings for sections. We need to decide which sections exist.
We have company description (About Seminole Hard Rock Hotel & Casino Hollywood). That could map to "About the role"? Actually "About the role" is about the job, not company. But we could use "About the role" heading for job summary? The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they give examples; we can use those headings if they match content. We need to include a section ONLY when posting has real, specific content for it. So we need to decide which sections we have content for.
We have:
- Job Summary / Essential Job Functions: that is responsibilities. So we can have Responsibilities
with list of essential job functions.
- Qualifications: we have qualifications section. So Qualifications
.
- Benefits & Perks: we have benefits. So Benefits
.
- Work Environment: maybe could be under "Requirements"? Or we could create a separate section? The examples didn't include Work Environment, but we could still use Requirements
for qualifications? Actually Qualifications is separate. Requirements could be things like "must be able to work variety of schedules", "must be able to lift 50 lbs", etc. That is more like job requirements. The posting includes Work Environment and also some requirements like "Must be able to communicate effectively...". So we could put those under Requirements
. But we also have Qualifications separate. The examples list both Qualifications and Requirements as possible headings. So we can split: Qualifications (education, experience, degree) and Requirements (physical, schedule, abilities). Let's do that.
- About the role: maybe we can put the company description under About the role
or maybe we could omit because it's not about the role. But we need to preserve all substantive information. The company description is substantive. Could we put it under a heading like "About Seminole Hard Rock Hotel & Casino Hollywood"? The 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 suggests using those. However we could still use About Seminole Hard Rock Hotel & Casino Hollywood
as a heading, but that is not in the examples. Safer to follow examples: use About the role for company overview? Might be okay.
But we also have "Closing" about tribal preference. That could be part of Requirements? Or maybe we could omit because it's boilerplate? It's not boilerplate; it's specific preference. Could be included under Requirements or maybe a separate section like "Equal Opportunity"? But we must remove EEO/equal-opportunity boilerplate. However this is tribal preference specific to Seminole Tribe; it's not generic EEO. It's substantive. Should we keep? Likely yes, as it's part of posting. Could be placed under a heading like "Requirements" or maybe its own section "Tribal Preference". But the instruction says remove EEO/equal-opportunity/boilerplate. This is not exactly EEO; it's a tribal preference. Might be considered similar but it's specific. I'd keep it.
We also have "Required" about gaming licensure background check. That is a requirement. Could be under Requirements.
We have "Disclaimer" about job may change. That's boilerplate; we should remove.
We also have repeated lines about tribal preference; we should deduplicate.
We also have "Please visit www.gotoworkhappy.com/benefits to see our full list of benefits!" That's a link; we should keep as part of Benefits section.
We have "For more information, visit us online at www.seminolehardrockhollywood.com, call 800-937-0010 or follow us: Facebook: SeminoleHardRockHollywood, Twitter: @HardRockHolly, Instagram: @HardRockHolly." That's company info; could be part of About the role.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings for sections. We need to decide which sections exist.
We have company description (About Seminole Hard Rock Hotel & Casino Hollywood). That could map to "About the role"? Actually "About the role" is about the job, not company. But we could use "About the role" heading for job summary? The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they give examples; we can use those headings if they match content. We need to include a section ONLY when posting has real, specific content for it. So we need to decide which sections we have content for.
We have:
- Job Summary / Essential Job Functions: that is responsibilities. So we can have Responsibilities
with list of essential job functions.
- Qualifications: we have qualifications section. So Qualifications
.
- Benefits & Perks: we have benefits. So Benefits
.
- Work Environment: maybe could be under "Requirements"? Or we could create a separate section? The examples didn't include Work Environment, but we could still use Requirements
for qualifications? Actually Qualifications is separate. Requirements could be things like "must be able to work variety of schedules", "must be able to lift 50 lbs", etc. That is more like job requirements. The posting includes Work Environment and also some requirements like "Must be able to communicate effectively...". So we could put those under Requirements
. But we also have Qualifications separate. The examples list both Qualifications and Requirements as possible headings. So we can split: Qualifications (education, experience, degree) and Requirements (physical, schedule, abilities). Let's do that.
- About the role: maybe we can put the company description under About the role
or maybe we could omit because it's not about the role. But we need to preserve all substantive information. The company description is substantive. Could we put it under a heading like "About Seminole Hard Rock Hotel & Casino Hollywood"? The 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 suggests using those. However we could still use About Seminole Hard Rock Hotel & Casino Hollywood
as a heading, but that is not in the examples. Safer to follow examples: use About the role for company overview? Might be okay.
But we also have "Closing" about tribal preference. That could be part of Requirements? Or maybe we could omit because it's boilerplate? It's not boilerplate; it's specific preference. Could be included under Requirements or maybe a separate section like "Equal Opportunity"? But we must remove EEO/equal-opportunity boilerplate. However this is tribal preference specific to Seminole Tribe; it's not generic EEO. It's substantive. Should we keep? Likely yes, as it's part of posting. Could be placed under a heading like "Requirements" or maybe its own section "Tribal Preference". But the instruction says remove EEO/equal-opportunity/boilerplate. This is not exactly EEO; it's a tribal preference. Might be considered similar but it's specific. I'd keep it.
We also have "Required" about gaming licensure background check. That is a requirement. Could be under Requirements.
We have "Disclaimer" about job may change. That's boilerplate; we should remove.
We also have repeated lines about tribal preference; we should deduplicate.
We also have "Please visit www.gotoworkhappy.com/benefits to see our full list of benefits!" That's a link; we should keep as part of Benefits section.
We have "For more information, visit us online at www.seminolehardrockhollywood.com, call 800-937-0010 or follow us: Facebook: SeminoleHardRockHollywood, Twitter: @HardRockHolly, Instagram: @HardRockHolly." That's company info; could be part of About the role.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
Responsibilities
with list of essential job functions. - Qualifications: we have qualifications section. SoQualifications
. - Benefits & Perks: we have benefits. SoBenefits
. - Work Environment: maybe could be under "Requirements"? Or we could create a separate section? The examples didn't include Work Environment, but we could still useRequirements
for qualifications? Actually Qualifications is separate. Requirements could be things like "must be able to work variety of schedules", "must be able to lift 50 lbs", etc. That is more like job requirements. The posting includes Work Environment and also some requirements like "Must be able to communicate effectively...". So we could put those underRequirements
. But we also have Qualifications separate. The examples list both Qualifications and Requirements as possible headings. So we can split: Qualifications (education, experience, degree) and Requirements (physical, schedule, abilities). Let's do that. - About the role: maybe we can put the company description underAbout the role
or maybe we could omit because it's not about the role. But we need to preserve all substantive information. The company description is substantive. Could we put it under a heading like "About Seminole Hard Rock Hotel & Casino Hollywood"? The 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 suggests using those. However we could still use About Seminole Hard Rock Hotel & Casino Hollywood
as a heading, but that is not in the examples. Safer to follow examples: use About the role for company overview? Might be okay.
But we also have "Closing" about tribal preference. That could be part of Requirements? Or maybe we could omit because it's boilerplate? It's not boilerplate; it's specific preference. Could be included under Requirements or maybe a separate section like "Equal Opportunity"? But we must remove EEO/equal-opportunity boilerplate. However this is tribal preference specific to Seminole Tribe; it's not generic EEO. It's substantive. Should we keep? Likely yes, as it's part of posting. Could be placed under a heading like "Requirements" or maybe its own section "Tribal Preference". But the instruction says remove EEO/equal-opportunity/boilerplate. This is not exactly EEO; it's a tribal preference. Might be considered similar but it's specific. I'd keep it.
We also have "Required" about gaming licensure background check. That is a requirement. Could be under Requirements.
We have "Disclaimer" about job may change. That's boilerplate; we should remove.
We also have repeated lines about tribal preference; we should deduplicate.
We also have "Please visit www.gotoworkhappy.com/benefits to see our full list of benefits!" That's a link; we should keep as part of Benefits section.
We have "For more information, visit us online at www.seminolehardrockhollywood.com, call 800-937-0010 or follow us: Facebook: SeminoleHardRockHollywood, Twitter: @HardRockHolly, Instagram: @HardRockHolly." That's company info; could be part of About the role.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
... company description ...
Responsibilities
- ... each essential job function ...
Qualifications
- ... education/degree ...
- ... experience ...
- ... knowledge ...
Requirements
- ... work environment physical demands ...
- ... schedule flexibility ...
- ... communication ...
- ... gaming licensure background check ...
- ... tribal preference ...
Benefits
- Medical, Dental, Vision & Life Insurances
- 401K
- Paid time off
- Annual Bonus Opportunity
- ... much more (see full list at www.gotoworkhappy.com/benefits)