Senior Cook- Culinary and Nutrition Orange- PT Day Shift 24hrs
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use those exact headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings from that list based on content. We have sections: About the role (maybe "About the role" corresponds to company description? Actually "About the role" is about the job, but we have "Who We Are" (company) and "Your Role on the Team Position Summary" (role summary). Could map "About the role" to the role summary. Could also have "Responsibilities" for duties. "Requirements" or "Qualifications" for required/preferred. "Skills" maybe for skill list. "Benefits" for Total Rewards. "Pay" and "Schedule" only if present; not present (no pay or schedule specifics). So we should not include Pay or Schedule sections.
We need to preserve all substantive information. So we need to include company description (Who We Are) maybe under "About the role"? But that heading is for role, not company. However we could still use "About the role" heading and put the role summary there, and maybe we need a separate section for company description? Not in the list. Could we use "About the role" to include both company and role? Might be okay but we might lose company info. Better to create a section "About the role" for role summary, and maybe we can add a preceding paragraph before headings? The instruction: Output ONLY the HTML fragment — no /. It didn't forbid having a preamble paragraph before headings. But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot have other headings, but we should follow that pattern. Probably they expect we use those headings only. So we need to map content to those headings.
Thus we need sections:
- About the role: includes position summary (role description) maybe also company description? Could include both? The "Who We Are" is about the organization, not the role. But maybe we can treat that as "About the role" as well? Might be okay.
- Responsibilities: list of duties from position summary: conception and implementation of upscale, culturally diverse menus and recipes; prepares, seasons and cooks food; cost control, requisitioning, ensuring proper storage; observance of sanitation and safety procedures; adherence to policies; etc.
- Requirements: required qualifications list.
- Qualifications: maybe preferred qualifications? Or we could combine required and preferred under Qualifications? But we have both Required Qualifications and Preferred Qualifications headings in the source. Could map Required Qualifications to "Requirements" and Preferred Qualifications to "Qualifications". Or we could have "Skills" for skill list. But we have skill list within required qualifications. Might be better to have:
About the role
(position summary + maybe company)
Responsibilities
(list)
Requirements
(required qualifications)
Qualifications
(preferred qualifications)
Benefits
(Total Rewards)
We should not include Pay or Schedule.
We need to use - for any list of duties/requirements/benefits. So for responsibilities, requirements, qualifications, benefits we need lists.
We need
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet exactly as in source, but we can rephrase? It says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the wording, maybe as list items.
We need to remove boilerplate: EEO, closing statement, etc. Also remove "Conditions Of Employment" maybe? It's not in the allowed headings list but could be considered part of Requirements? However it's substantive: background check, live scan, etc. Should we include it? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Conditions Of Employment is legal/HR policy; might be considered boilerplate? It's not exactly EEO but it's legal conditions. The instruction says remove legal boilerplate? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So legal boilerplate includes Conditions Of Employment. So we should remove that section entirely. Also remove "Consideration for Work Authorization Sponsorship" maybe also legal. So we will omit Conditions Of Employment and the work authorization line.
Thus we keep: Who We Are, Position Summary, Responsibilities (implied), Required Qualifications, Preferred Qualifications, Total Rewards.
Now we need to craft HTML.
Let's extract content.
Who We Are paragraph:
"UCI Health is one of California's largest academic health systems and the clinical enterprise of the University of California, Irvine. Established on July 1, 1976, UCI Health has grown into a 1,461-bed health system that includes UCI Health - Orange, UCI Health - Irvine, four Community Network hospitals and a growing network of ambulatory care centers across Orange and Los Angeles counties. As Orange County’s only academic health systems, UCI Health is home to the only National Cancer Institute-designated comprehensive cancer center based in the county, the region’s only American College of Surgeons-verified Level I adult and Level II pediatric trauma center, American College of Emergency Physicians Gold Level 1 Geriatric Emergency Department and a nationally recognized regional burn center verified by the American Burn Association. Powered by UC Irvine, UCI Health serves 5.6 million people across Orange County, western Riverside County and southeast Los Angeles County through excellence in patient care, research and medical education."
We'll put that in a
under About the role? Or maybe we need a separate heading for About the role (role summary). But we could put company description as a paragraph before the heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having a preamble paragraph before any heading. However they might expect each section to start with heading. Safer to put company description under About the role heading as well, maybe as a paragraph preceding the role summary.
Thus:
About the role
[Who We Are]
[Position Summary]
But that mixes two topics. Might be okay.
Alternatively we could have two headings: About the role (company) and Responsibilities (role). But they didn't list a heading for company. However we could still use About the role for company description and then Responsibilities for role summary. But the role summary includes responsibilities; we could split.
Better: Use About the role for company description, Responsibilities for role summary and duties, Requirements for required qualifications, Qualifications for preferred qualifications, Benefits for Total Rewards.
Let's do that.
Thus:
About the role
UCI Health is one of California's largest academic health systems and the clinical enterprise of the University of California, Irvine. Established on July 1, 1976, UCI Health has grown into a 1,461-bed health system that includes UCI Health - Orange, UCI Health - Irvine, four Community Network hospitals and a growing network of ambulatory care centers across Orange and Los Angeles counties. As Orange County’s only academic health systems, UCI Health is home to the only National Cancer Institute-designated comprehensive cancer center based in the county, the region’s only American College of Surgeons-verified Level I adult and Level II pediatric trauma center, American College of Emergency Physicians Gold Level 1 Geriatric Emergency Department and a nationally recognized regional burn center verified by the American Burn Association. Powered by UC Irvine, UCI Health serves 5.6 million people across Orange County, western Riverside County and southeast Los Angeles County through excellence in patient care, research and medical education.
Responsibilities
Under general supervision of the Executive Chef, the Senior Cook is responsible for the conception and implementation of upscale, culturally diverse menus and recipes for patient care, retail operations and catering services. The Senior Cook also prepares, seasons and cooks (steaming, poaching, broiling, braising, etc.) food according to the recipes using basic ingredients, from scratch and some convenience items for patient meal service, Medical Center Cafeteria, and special catered functions, in a safe and sanitary manner. Other responsibilities include cost control, requisitioning and ensuring proper storage of food items, observance of all sanitation and safety procedures and adherence to all policies outlined by JCAHO, the University of California and the UC Medical Center.
But we need to use - for any list of duties/requirements/benefits. The responsibilities are not a list but prose; we could keep as
. However the instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid using
for prose. So we can keep responsibilities as prose.
But we could also break into list items for clarity. However we must preserve all substantive information; converting to list is okay as long as we keep the same info. Might be better to use list for duties. Let's extract duties as bullet points:
- Conception and implementation of upscale, culturally diverse menus and recipes for patient care, retail operations and catering services.
- Prepares, seasons and cooks (steaming, poaching, broiling, braising, etc.) food according to the recipes using basic ingredients, from scratch and some convenience items for patient meal service, Medical Center Cafeteria, and special catered functions, in a safe and sanitary manner.
- Cost control, requisitioning and ensuring proper storage of food items.
- Observance of all sanitation and safety procedures.
- Adherence to all policies outlined by JCAHO, the University of California and the UC Medical Center.
That preserves all.
Now Required Qualifications: list items:
- Verbal and written communication in the English language
- Active listening
- Dynamic flexibility
- Critical thinking
- Multi-task and time management
- Skill in various cooking techniques with the ability to follow recipes and specifications for regular and therapeutic diets
- Previous experience as a cook, or related experience in main kitchen and/or cafeteria
- Must demonstrate customer service skills appropriate to the job
- Must be able to work alternate schedules. days and nights, weekends and holidays
- Knowledge of common cooking terminology, mathematics and standard weights and measures to prepare and adjust recipes
- Ability to maintain a work pace appropriate to
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot have other headings, but we should follow that pattern. Probably they expect we use those headings only. So we need to map content to those headings.
Thus we need sections:
- About the role: includes position summary (role description) maybe also company description? Could include both? The "Who We Are" is about the organization, not the role. But maybe we can treat that as "About the role" as well? Might be okay.
- Responsibilities: list of duties from position summary: conception and implementation of upscale, culturally diverse menus and recipes; prepares, seasons and cooks food; cost control, requisitioning, ensuring proper storage; observance of sanitation and safety procedures; adherence to policies; etc.
- Requirements: required qualifications list.
- Qualifications: maybe preferred qualifications? Or we could combine required and preferred under Qualifications? But we have both Required Qualifications and Preferred Qualifications headings in the source. Could map Required Qualifications to "Requirements" and Preferred Qualifications to "Qualifications". Or we could have "Skills" for skill list. But we have skill list within required qualifications. Might be better to have:
About the role
(position summary + maybe company)
Responsibilities
(list)
Requirements
(required qualifications)
Qualifications
(preferred qualifications)
Benefits
(Total Rewards)
We should not include Pay or Schedule.
We need to use - for any list of duties/requirements/benefits. So for responsibilities, requirements, qualifications, benefits we need lists.
We need
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet exactly as in source, but we can rephrase? It says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the wording, maybe as list items.
We need to remove boilerplate: EEO, closing statement, etc. Also remove "Conditions Of Employment" maybe? It's not in the allowed headings list but could be considered part of Requirements? However it's substantive: background check, live scan, etc. Should we include it? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Conditions Of Employment is legal/HR policy; might be considered boilerplate? It's not exactly EEO but it's legal conditions. The instruction says remove legal boilerplate? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So legal boilerplate includes Conditions Of Employment. So we should remove that section entirely. Also remove "Consideration for Work Authorization Sponsorship" maybe also legal. So we will omit Conditions Of Employment and the work authorization line.
Thus we keep: Who We Are, Position Summary, Responsibilities (implied), Required Qualifications, Preferred Qualifications, Total Rewards.
Now we need to craft HTML.
Let's extract content.
Who We Are paragraph:
"UCI Health is one of California's largest academic health systems and the clinical enterprise of the University of California, Irvine. Established on July 1, 1976, UCI Health has grown into a 1,461-bed health system that includes UCI Health - Orange, UCI Health - Irvine, four Community Network hospitals and a growing network of ambulatory care centers across Orange and Los Angeles counties. As Orange County’s only academic health systems, UCI Health is home to the only National Cancer Institute-designated comprehensive cancer center based in the county, the region’s only American College of Surgeons-verified Level I adult and Level II pediatric trauma center, American College of Emergency Physicians Gold Level 1 Geriatric Emergency Department and a nationally recognized regional burn center verified by the American Burn Association. Powered by UC Irvine, UCI Health serves 5.6 million people across Orange County, western Riverside County and southeast Los Angeles County through excellence in patient care, research and medical education."
We'll put that in a
under About the role? Or maybe we need a separate heading for About the role (role summary). But we could put company description as a paragraph before the heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having a preamble paragraph before any heading. However they might expect each section to start with heading. Safer to put company description under About the role heading as well, maybe as a paragraph preceding the role summary.
Thus:
About the role
[Who We Are]
[Position Summary]
But that mixes two topics. Might be okay.
Alternatively we could have two headings: About the role (company) and Responsibilities (role). But they didn't list a heading for company. However we could still use About the role for company description and then Responsibilities for role summary. But the role summary includes responsibilities; we could split.
Better: Use About the role for company description, Responsibilities for role summary and duties, Requirements for required qualifications, Qualifications for preferred qualifications, Benefits for Total Rewards.
Let's do that.
Thus:
About the role
UCI Health is one of California's largest academic health systems and the clinical enterprise of the University of California, Irvine. Established on July 1, 1976, UCI Health has grown into a 1,461-bed health system that includes UCI Health - Orange, UCI Health - Irvine, four Community Network hospitals and a growing network of ambulatory care centers across Orange and Los Angeles counties. As Orange County’s only academic health systems, UCI Health is home to the only National Cancer Institute-designated comprehensive cancer center based in the county, the region’s only American College of Surgeons-verified Level I adult and Level II pediatric trauma center, American College of Emergency Physicians Gold Level 1 Geriatric Emergency Department and a nationally recognized regional burn center verified by the American Burn Association. Powered by UC Irvine, UCI Health serves 5.6 million people across Orange County, western Riverside County and southeast Los Angeles County through excellence in patient care, research and medical education.
Responsibilities
Under general supervision of the Executive Chef, the Senior Cook is responsible for the conception and implementation of upscale, culturally diverse menus and recipes for patient care, retail operations and catering services. The Senior Cook also prepares, seasons and cooks (steaming, poaching, broiling, braising, etc.) food according to the recipes using basic ingredients, from scratch and some convenience items for patient meal service, Medical Center Cafeteria, and special catered functions, in a safe and sanitary manner. Other responsibilities include cost control, requisitioning and ensuring proper storage of food items, observance of all sanitation and safety procedures and adherence to all policies outlined by JCAHO, the University of California and the UC Medical Center.
But we need to use - for any list of duties/requirements/benefits. The responsibilities are not a list but prose; we could keep as
. However the instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid using
for prose. So we can keep responsibilities as prose.
But we could also break into list items for clarity. However we must preserve all substantive information; converting to list is okay as long as we keep the same info. Might be better to use list for duties. Let's extract duties as bullet points:
- Conception and implementation of upscale, culturally diverse menus and recipes for patient care, retail operations and catering services.
- Prepares, seasons and cooks (steaming, poaching, broiling, braising, etc.) food according to the recipes using basic ingredients, from scratch and some convenience items for patient meal service, Medical Center Cafeteria, and special catered functions, in a safe and sanitary manner.
- Cost control, requisitioning and ensuring proper storage of food items.
- Observance of all sanitation and safety procedures.
- Adherence to all policies outlined by JCAHO, the University of California and the UC Medical Center.
That preserves all.
Now Required Qualifications: list items:
- Verbal and written communication in the English language
- Active listening
- Dynamic flexibility
- Critical thinking
- Multi-task and time management
- Skill in various cooking techniques with the ability to follow recipes and specifications for regular and therapeutic diets
- Previous experience as a cook, or related experience in main kitchen and/or cafeteria
- Must demonstrate customer service skills appropriate to the job
- Must be able to work alternate schedules. days and nights, weekends and holidays
- Knowledge of common cooking terminology, mathematics and standard weights and measures to prepare and adjust recipes
- Ability to maintain a work pace appropriate to
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet exactly as in source, but we can rephrase? It says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the wording, maybe as list items. We need to remove boilerplate: EEO, closing statement, etc. Also remove "Conditions Of Employment" maybe? It's not in the allowed headings list but could be considered part of Requirements? However it's substantive: background check, live scan, etc. Should we include it? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Conditions Of Employment is legal/HR policy; might be considered boilerplate? It's not exactly EEO but it's legal conditions. The instruction says remove legal boilerplate? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So legal boilerplate includes Conditions Of Employment. So we should remove that section entirely. Also remove "Consideration for Work Authorization Sponsorship" maybe also legal. So we will omit Conditions Of Employment and the work authorization line. Thus we keep: Who We Are, Position Summary, Responsibilities (implied), Required Qualifications, Preferred Qualifications, Total Rewards. Now we need to craft HTML. Let's extract content. Who We Are paragraph: "UCI Health is one of California's largest academic health systems and the clinical enterprise of the University of California, Irvine. Established on July 1, 1976, UCI Health has grown into a 1,461-bed health system that includes UCI Health - Orange, UCI Health - Irvine, four Community Network hospitals and a growing network of ambulatory care centers across Orange and Los Angeles counties. As Orange County’s only academic health systems, UCI Health is home to the only National Cancer Institute-designated comprehensive cancer center based in the county, the region’s only American College of Surgeons-verified Level I adult and Level II pediatric trauma center, American College of Emergency Physicians Gold Level 1 Geriatric Emergency Department and a nationally recognized regional burn center verified by the American Burn Association. Powered by UC Irvine, UCI Health serves 5.6 million people across Orange County, western Riverside County and southeast Los Angeles County through excellence in patient care, research and medical education." We'll put that in a
under About the role? Or maybe we need a separate heading for About the role (role summary). But we could put company description as a paragraph before the heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having a preamble paragraph before any heading. However they might expect each section to start with heading. Safer to put company description under About the role heading as well, maybe as a paragraph preceding the role summary.
Thus:
About the role
[Who We Are]
[Position Summary]
But that mixes two topics. Might be okay. Alternatively we could have two headings: About the role (company) and Responsibilities (role). But they didn't list a heading for company. However we could still use About the role for company description and then Responsibilities for role summary. But the role summary includes responsibilities; we could split. Better: Use About the role for company description, Responsibilities for role summary and duties, Requirements for required qualifications, Qualifications for preferred qualifications, Benefits for Total Rewards. Let's do that. Thus:About the role
UCI Health is one of California's largest academic health systems and the clinical enterprise of the University of California, Irvine. Established on July 1, 1976, UCI Health has grown into a 1,461-bed health system that includes UCI Health - Orange, UCI Health - Irvine, four Community Network hospitals and a growing network of ambulatory care centers across Orange and Los Angeles counties. As Orange County’s only academic health systems, UCI Health is home to the only National Cancer Institute-designated comprehensive cancer center based in the county, the region’s only American College of Surgeons-verified Level I adult and Level II pediatric trauma center, American College of Emergency Physicians Gold Level 1 Geriatric Emergency Department and a nationally recognized regional burn center verified by the American Burn Association. Powered by UC Irvine, UCI Health serves 5.6 million people across Orange County, western Riverside County and southeast Los Angeles County through excellence in patient care, research and medical education.
Responsibilities
Under general supervision of the Executive Chef, the Senior Cook is responsible for the conception and implementation of upscale, culturally diverse menus and recipes for patient care, retail operations and catering services. The Senior Cook also prepares, seasons and cooks (steaming, poaching, broiling, braising, etc.) food according to the recipes using basic ingredients, from scratch and some convenience items for patient meal service, Medical Center Cafeteria, and special catered functions, in a safe and sanitary manner. Other responsibilities include cost control, requisitioning and ensuring proper storage of food items, observance of all sanitation and safety procedures and adherence to all policies outlined by JCAHO, the University of California and the UC Medical Center.
But we need to use- for any list of duties/requirements/benefits. The responsibilities are not a list but prose; we could keep as
. However the instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid using
for prose. So we can keep responsibilities as prose. But we could also break into list items for clarity. However we must preserve all substantive information; converting to list is okay as long as we keep the same info. Might be better to use list for duties. Let's extract duties as bullet points: - Conception and implementation of upscale, culturally diverse menus and recipes for patient care, retail operations and catering services. - Prepares, seasons and cooks (steaming, poaching, broiling, braising, etc.) food according to the recipes using basic ingredients, from scratch and some convenience items for patient meal service, Medical Center Cafeteria, and special catered functions, in a safe and sanitary manner. - Cost control, requisitioning and ensuring proper storage of food items. - Observance of all sanitation and safety procedures. - Adherence to all policies outlined by JCAHO, the University of California and the UC Medical Center. That preserves all. Now Required Qualifications: list items: - Verbal and written communication in the English language - Active listening - Dynamic flexibility - Critical thinking - Multi-task and time management - Skill in various cooking techniques with the ability to follow recipes and specifications for regular and therapeutic diets - Previous experience as a cook, or related experience in main kitchen and/or cafeteria - Must demonstrate customer service skills appropriate to the job - Must be able to work alternate schedules. days and nights, weekends and holidays - Knowledge of common cooking terminology, mathematics and standard weights and measures to prepare and adjust recipes - Ability to maintain a work pace appropriate to
- for any list of duties/requirements/benefits. It doesn't forbid using