Value Stream Coach: Las Vegas
Wabtec Corporation · Las Vegas, NV · 1 mo ago
On-siteOTHR$79k–$113k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No placeholder like "commensurate with experience". We need to parse the job description.
We need to extract:
- About the role: maybe the introductory paragraphs: "Who will you be working with?" and "How will you make a difference?" Could be combined as About the role.
- Responsibilities: The "What will your typical day look like?" list of duties.
- Requirements/Qualifications: The "What do we want to know about you?" includes minimum experience, etc. Also "Bachelor's degree..." etc. Also "Prior manufacturing leadership experience preferred." etc. Also "Strong written, verbal..." etc. Also "Ability to lead cross-functional teams..." etc. Also "Willingness to travel approximately 10%." That's a requirement.
- Skills: maybe separate but could be part of Requirements. But we can have a Skills section for specific skills like "Lean Manufacturing, TPS, pull systems, flow, kanban, kaizen events, Daily Management, A3 problem-solving, value stream mapping, standard work, visual management, waste elimination, project management, coaching, mentoring, influencing, presentation, stakeholder management, matrixed environment."
- Benefits: The posting mentions "More information on offered benefits, which include health, welfare, and retirement, are available at mywabtecbenefits.com. Other benefit offerings for this role may include annual bonus, if eligible." Also "Relocation assistance may be provided if eligibility requirements are met." So we have benefits: health, welfare, retirement, possible annual bonus, relocation assistance.
- Pay: The salary range: "$79100-112800". Also mention base pay range subject to change. So we have Pay.
- Schedule: Not mentioned explicitly. No schedule details. So we should not include Schedule section.
- Location: Could be included maybe as part of About the role or separate? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Location not listed, but we could embed location in About the role as a paragraph. Or we could create a separate section but not in list; but instruction says prefer those headings; we can add others if needed but better to stick to given headings. So location can be in About the role paragraph.
- Also "Work Authorization" etc is boilerplate; we should remove.
- "Additional Information" about job titles spanning levels etc is maybe not needed; but it's not boilerplate? It's generic but maybe we can drop as not substantive? It's about salary range etc but we already captured pay. The line "More information on offered benefits..." we captured benefits. The line "Other benefit offerings..." we captured.
- The "What could you accomplish..." etc is fluff; could be considered boilerplate? It's motivational but maybe we can drop as not substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That motivational paragraph is not boilerplate but could be considered fluff; but we might keep as part of About the role? It's not specific to role. Safer to drop.
- "Who are we?" description of company is also boilerplate; drop.
- "Culture powers us..." also boilerplate; drop.
Thus we will produce sections:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No placeholder like "commensurate with experience". We need to parse the job description.
We need to extract:
- About the role: maybe the introductory paragraphs: "Who will you be working with?" and "How will you make a difference?" Could be combined as About the role.
- Responsibilities: The "What will your typical day look like?" list of duties.
- Requirements/Qualifications: The "What do we want to know about you?" includes minimum experience, etc. Also "Bachelor's degree..." etc. Also "Prior manufacturing leadership experience preferred." etc. Also "Strong written, verbal..." etc. Also "Ability to lead cross-functional teams..." etc. Also "Willingness to travel approximately 10%." That's a requirement.
- Skills: maybe separate but could be part of Requirements. But we can have a Skills section for specific skills like "Lean Manufacturing, TPS, pull systems, flow, kanban, kaizen events, Daily Management, A3 problem-solving, value stream mapping, standard work, visual management, waste elimination, project management, coaching, mentoring, influencing, presentation, stakeholder management, matrixed environment."
- Benefits: The posting mentions "More information on offered benefits, which include health, welfare, and retirement, are available at mywabtecbenefits.com. Other benefit offerings for this role may include annual bonus, if eligible." Also "Relocation assistance may be provided if eligibility requirements are met." So we have benefits: health, welfare, retirement, possible annual bonus, relocation assistance.
- Pay: The salary range: "$79100-112800". Also mention base pay range subject to change. So we have Pay.
- Schedule: Not mentioned explicitly. No schedule details. So we should not include Schedule section.
- Location: Could be included maybe as part of About the role or separate? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Location not listed, but we could embed location in About the role as a paragraph. Or we could create a separate section but not in list; but instruction says prefer those headings; we can add others if needed but better to stick to given headings. So location can be in About the role paragraph.
- Also "Work Authorization" etc is boilerplate; we should remove.
- "Additional Information" about job titles spanning levels etc is maybe not needed; but it's not boilerplate? It's generic but maybe we can drop as not substantive? It's about salary range etc but we already captured pay. The line "More information on offered benefits..." we captured benefits. The line "Other benefit offerings..." we captured.
- The "What could you accomplish..." etc is fluff; could be considered boilerplate? It's motivational but maybe we can drop as not substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That motivational paragraph is not boilerplate but could be considered fluff; but we might keep as part of About the role? It's not specific to role. Safer to drop.
- "Who are we?" description of company is also boilerplate; drop.
- "Culture powers us..." also boilerplate; drop.
Thus we will produce sections:
About the role
... combine who you will be working with and how you will make a difference, plus location.
Responsibilities
- ... list from typical day.
Requirements
- ... list from what we want to know about you (experience, change leadership, Lean/TPS, pull systems, coaching, kaizen, Daily Management, A3, project management, degree preferred, manufacturing leadership preferred, communication skills, cross-functional teams, stakeholder buy-in, travel 10%).
Qualifications
but we can combine with Requirements. The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications if we have distinct content. Qualifications could be education: Bachelor's degree preferred. But we already have that in Requirements. Could split: Requirements: experience and skills; Qualifications: education. But we can keep one section to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to follow the heading list; we can choose either. I'd use Requirements for experience and skills, and Qualifications for education. But that's two thin sections; maybe better to have one Requirements that includes education as well. Let's do that.Skills
- ... list specific lean tools etc.
About the role
... combined paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- Health, welfare, and retirement benefits (details available at mywabtecbenefits.com)
- Potential annual bonus, if eligible
- Relocation assistance, if eligibility requirements are met
Similar jobs
Travel PCU RN - $1,744 per week
apply on vivian.com
Travel PCU RN - $1,742 per week
Healthcare
Travel PCU RN - $1,742 per week
Healthcareapply on vivian.com
Travel PCU RN - $1,743 per week
Healthcare
Travel PCU RN - $1,743 per week
Healthcare
Travel PCU RN - $1,741 per week
Healthcare