Railroad Safety Flagger UP South
RailPros · Oklahoma, United States · 1 mo ago
ConsultingFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually we have "Who We Are" (company description) maybe not a section heading but we could treat as "About the company"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if present. The posting includes: Who We Are (company overview), Job Summary, Essential Duties & Responsibilities, Travel Requirements, Qualifications (Knowledge, Skills and Abilities; Required Education And Experience; Additional Qualifications...), Why RailPros? (culture), Benefits & Perks, etc. No explicit Pay or Schedule. Travel Requirements maybe could be under Schedule? Not exactly. Travel is not schedule. We could include a section for Travel Requirements maybe as its own heading? But instruction says use those example headings; but we can also create other headings if needed? It says "use
Benefit: description .
Now Why RailPros? section: paragraphs about culture pillars. We'll keep as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if present. The posting includes: Who We Are (company overview), Job Summary, Essential Duties & Responsibilities, Travel Requirements, Qualifications (Knowledge, Skills and Abilities; Required Education And Experience; Additional Qualifications...), Why RailPros? (culture), Benefits & Perks, etc. No explicit Pay or Schedule. Travel Requirements maybe could be under Schedule? Not exactly. Travel is not schedule. We could include a section for Travel Requirements maybe as its own heading? But instruction says use those example headings; but we can also create other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when applicable; but we could also use other headings if needed? Probably better to stick to those. So we need sections: About the role (maybe Job Summary), Responsibilities (Essential Duties & Responsibilities), Requirements (Qualifications), Skills (maybe part of Qualifications), Benefits (Benefits & Perks). No Pay or Schedule. Also maybe "Travel Requirements" could be under Responsibilities? But it's separate. Could we include a section "Travel Requirements" as its own heading? The instruction didn't forbid other headings, just gave examples. Safer to include Travel Requirements as its own maybe "Travel Requirements". It's substantive.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove "Apply now and become a part of our exciting journey!" maybe considered boilerplate? It's a call to action; maybe remove as application instructions. Also remove "Equal Employment Opportunity (EEO)" etc.
We need to preserve all substantive information. So we need to include company description (Who We Are), Job Summary, Responsibilities, Travel Requirements, Qualifications (including Knowledge, Skills and Abilities, Required Education And Experience, Additional Qualifications), Benefits & Perks, Why RailPros? (culture). Also maybe "Why RailPros?" could be under About the role? But it's separate.
We'll structure:
About the role
maybe "Travel Requirements". It's substantive.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove "Apply now and become a part of our exciting journey!" maybe considered boilerplate? It's a call to action; maybe remove as application instructions. Also remove "Equal Employment Opportunity (EEO)" etc.
We need to preserve all substantive information. So we need to include company description (Who We Are), Job Summary, Responsibilities, Travel Requirements, Qualifications (including Knowledge, Skills and Abilities, Required Education And Experience, Additional Qualifications), Benefits & Perks, Why RailPros? (culture). Also maybe "Why RailPros?" could be under About the role? But it's separate.
We'll structure:
About the role
Job Summary ...
Responsibilities
- ... each duty
Travel Requirements
... travel across states, per diems, mileage reimbursement.
Qualifications
maybe split into sub-sections? Could haveKnowledge, Skills and Abilities
etc but instruction only mentions h3 for sections. Could keep as- ... each bullet
Qualifications
- Able to complete required physical demands and/or task ...
- Required Education And Experience: A high school diploma or equivalent (GED); A minimum of 2 years in Maintenance in Way (MOW) and/or Trade Yard & Engine (TY&E)
- Additional Qualifications, Certifications, Etc.: UP- South On-Track Worker and Operating Rules
Why RailPros?
maybe but not in examples. Could treat as "About the role"? Might be okay to have its own heading. Benefits:Benefits
- ... each benefit
maybe multiple paragraphs. We need to remove boilerplate: EEO, etc. Also remove "Apply now and become a part of our exciting journey!" (call to action). Also remove "Choose a career