Cook (DODEA) NA-04.
- .
- Requirements: includes Conditions of employment bullet list. Should be
- .
- Qualifications: includes Resumes must be two pages..., A Qualified Candidate Must Possess..., Education..., etc. Should be
- for list items.
- Benefits: There's a paragraph about benefits: "Regular full-time and part-time employees are eligible for enrollment in health and life insurance, participation in 401k and retirement plans, and paid personal time off and federal holidays. NAF flexible employees..." Also mention "For a slideshow presentation regarding these benefits, please click the Review Our Benefits link below." That's a benefit description. So we can include Benefits section with
- items.
- Pay: There's mention of "Allowances and Differentials This job falls under the Federal Wage Schedule (FWS) pay system. FWS employees earn overtime pay for working more than 8 hours in a day or more than 40 hours in a week -- whichever gives the employee more benefit. Regular full-time, regular part-time, and regularly scheduled flexible employees may receive Sunday premium pay for working on Sundays. Employees may also be eligible to receive extra pay if the majority of their scheduled hours falls after 3:00 PM. Non-foreign overseas allowances, cost of living (COLA), and differentials will not be paid, contingent upon eligibility." That's pay info. So we can include Pay section.
- Schedule: Not explicitly stated. There's mention of "Regular full-time, regular part-time, and regularly scheduled flexible employees may receive Sunday premium pay for working on Sundays." That's schedule info but not explicit schedule like hours. There's no explicit schedule like "Monday-Friday 8am-5pm". So we should not create Schedule section unless posting actually states them. It does not give schedule details, so omit.
- Also there is "Additional information" with Area of Consideration, Manual Application Option, PCS Costs, etc. Those are metadata; we should fold minor metadata into short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a
for Area of Consideration etc. But we need to preserve ALL substantive information; not invent or summarize away detail. So we need to keep Area of Consideration, Manual Application Option, PCS Costs, etc. However they said "Prefer a few substantive sections over many thin ones." So maybe we can include a
after sections that captures these misc details. We must not include boilerplate like cookie/navigation/legal/EEO etc. The posting includes many paragraphs like "Discover Your Path to Success..." etc. That's promotional but still substantive? It's about benefits and mission. Might be considered boilerplate? It's not EEO/legal. It's about benefits and mission. Could keep as part of Benefits or a separate "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have About the role (maybe from introductory paragraph). The posting starts with "Duties Serves as a Cook...". There's no explicit "About the role". But we could treat the first paragraph as About the role? However they said do NOT repeat the job title as a heading (the page already shows it). So we could have About the role section with a brief description. But we need to preserve all substantive info; we could put the description of duties under Responsibilities (which we already have). The "About the role" could be a short paragraph summarizing role. But we don't have that explicitly; we could infer from duties. But better to stick to sections that have explicit headings in the posting: Duties, Requirements, Qualifications, Additional information (which includes Area of Consideration, Manual Application Option, PCS Costs, Allowances and Differentials, etc). Also there is "Important Information Regarding Access to Certain Federal Facilities". That's also substantive. Also "See Your Application may be Considered for Multiple Opportunities". Also "Termination of Spouse Employment Preference". Also "Discover Your Path to Success". Also "Working for Army Non-Appropriated Funds (NAF) can offer numerous advantages." That's benefits/mission. We need to decide what sections to output. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine many of these into a called "Additional Information" with
paragraphs. But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings, but they gave examples. Likely they expect us to use those headings only if content exists. So we should map content to those headings. Thus: - Responsibilities (
Responsibilities
) for duties. - Requirements (Requirements
) for conditions of employment. - Qualifications (Qualifications
) for resume, experience, communication, education. - Benefits (Benefits
) for health insurance, 401k, paid time off, federal holidays, NAF 401k, etc. - Pay (Pay
) for FWS, overtime, Sunday premium, extra pay after 3pm, etc. - Schedule: not present, so omit. - About the role: maybe we could include a brief paragraph from the introductory sentence before duties? The posting starts with "Duties Serves as a Cook...". There's no separate "About the role". Could we treat the first sentence as About the role? But it's essentially duty. Safer to omit About the role if no explicit content. Thus output:Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
- ... ...
- . **Requirements** (Conditions of employment): - Direct Deposit and Social Security Card is required. - Meet qualification/eligibility/background requirements for this position. - A one-year probationary period may be required. - Satisfactorily complete an employment verification (E-Verify) check. - Satisfactory completion of a minimum of 4 hours initial food sanitation and safety training is required within 30 days of employment and a minimum of 4 hours refresher training annually. - Subject to satisfactory completion of all pre-employment checks in accordance with AR 215-3, para.2 and a Child Care Tier 1 background investigation is required. - Must have current health assessment which documents good mental and physical health, freedom from communicable disease, and immunizations IAW current Army and DoD policy including annual influenza vaccinations. - Must be able to lift or move objects up to 40 pounds unassisted, and occasionally lift or move objects weighing Over 40 pounds with the assistance of Other workers or lifting devices. - Work is performed in kitchen areas, which are well lighted but are often hot and noisy. Employee is exposed to steam, fumes, odors from cooking, and to extreme temperature changes when entering walk-in refrigerators or freezing units. - Must stand on tile floor, subject to burns, cuts, and slipping on wet floors. Make each
- .
**Qualifications**:
- Resumes must be two pages (or less).
- Resumes should clearly demonstrate the applicant's relevant experience, skills, knowledge and abilities as they pertain to this position.
- A Qualified Candidate Must Possess The Following:
- Work experience related to the duties described above, that included skill in working with professional kitchen appliances and equipment.
- Be able to communicate (verbal and written) in English.
- Education: This job does not have an education qualification requirement.
- Additional information (maybe separate but we can include as part of Qualifications? Actually "Additional information" includes Area of Consideration, Manual Application Option, PCS Costs, Allowances and Differentials, etc. Those are not qualifications. So we should keep them separate maybe as a
after Qualifications or as a separate section like "Additional Information". But the instruction only gave examples of headings; we could still use
Additional Information
if we want, but they didn't list it as example. Safer to incorporate into existing sections where appropriate: Area of Consideration could be aafter Qualifications. Manual Application Option could be a
. PCS Costs Payment... could be a
. Allowances and Differentials we already used for Pay section? Actually Allowances and Differentials paragraph is about pay differentials; we already used that in Pay. Good. - Also there is "Important Information Regarding Access to Certain Federal Facilities". That could be a
after Pay or Benefits. - "See Your Application may be Considered for Multiple Opportunities" etc. - "Termination of Spouse Employment Preference". - "Discover Your Path to Success" etc. - "Working for Army Non-Appropriated Funds (NAF) can offer numerous advantages." etc. We need to preserve all substantive info. So we need to include those paragraphs somewhere. Could create a
Additional Information
withparagraphs for each. The instruction didn't forbid that; they just gave examples of headings. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections if they exist. It doesn't say we cannot use other headings, but to be safe we could use those headings only. However we have info that doesn't fit those categories: Area of Consideration, Manual Application Option, PCS Costs, Access to Federal Facilities, Multiple Opportunities, Spouse Employment Preference, Discover Your Path to Success, Working for Army NAF advantages. Some of those could be considered "About the role" or "Benefits". The NAF advantages could go under Benefits. The Discover Your Path to Success is promotional but could be considered part of Benefits or About the role. The "Working for Army NAF..." also benefits. The "Area of Consideration" is metadata about where applicants can be from; could be considered part of "Additional information" but not a standard heading. Could we fold it into a
under Qualifications? Not really. Could we put it under Requirements? Not appropriate. Given the instruction to "Prefer a few substantive sections over many thin ones", maybe we should combine all these misc items into a single
Additional Information
section withparagraphs. That would be a few
- items.
- Pay: There's mention of "Allowances and Differentials This job falls under the Federal Wage Schedule (FWS) pay system. FWS employees earn overtime pay for working more than 8 hours in a day or more than 40 hours in a week -- whichever gives the employee more benefit. Regular full-time, regular part-time, and regularly scheduled flexible employees may receive Sunday premium pay for working on Sundays. Employees may also be eligible to receive extra pay if the majority of their scheduled hours falls after 3:00 PM. Non-foreign overseas allowances, cost of living (COLA), and differentials will not be paid, contingent upon eligibility." That's pay info. So we can include Pay section.
- Schedule: Not explicitly stated. There's mention of "Regular full-time, regular part-time, and regularly scheduled flexible employees may receive Sunday premium pay for working on Sundays." That's schedule info but not explicit schedule like hours. There's no explicit schedule like "Monday-Friday 8am-5pm". So we should not create Schedule section unless posting actually states them. It does not give schedule details, so omit.
- Also there is "Additional information" with Area of Consideration, Manual Application Option, PCS Costs, etc. Those are metadata; we should fold minor metadata into short
- for list items.
- Benefits: There's a paragraph about benefits: "Regular full-time and part-time employees are eligible for enrollment in health and life insurance, participation in 401k and retirement plans, and paid personal time off and federal holidays. NAF flexible employees..." Also mention "For a slideshow presentation regarding these benefits, please click the Review Our Benefits link below." That's a benefit description. So we can include Benefits section with
- .
- Qualifications: includes Resumes must be two pages..., A Qualified Candidate Must Possess..., Education..., etc. Should be