Production Worker
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Input Text:**
Let me extract the meaningful content, structure, and metadata from the provided job posting.
Text:
Job Details Division: Nucor Rebar Fabrication Northwest Location: Tacoma, WA, United States Other Available Locations: N/A Welcome to Nucor, where our unique culture sets us apart. Joining Nucor means becoming part of North America's largest steel and steel products manufacturer, offering unmatched career opportunities and stability. We are known for our innovative sustainability practices and are the continent's largest recycler. Our vibrant culture, built on personal connections and teamwork, empowers every team member with the freedom to innovate and contribute to our collective success. Experience a workplace where safety, efficiency, and meaningful personal connections define every day, enriching both our teammates and the communities we serve. Nucor supports its teammates with top-tier benefits like Medical, Dental, Vision, and Disability Insurance, 401K and Roth accounts, Profit sharing, Pay-for-performance bonuses, Paid parental leave, Tuition reimbursement, Stock program, Scholarships and more. Compensation Data: Entry Level Base Wage $17.49 + Production Bonus Weekly Production Bonus 6 Mo. Average - 90.76% of base wage. Profit Sharing: 20.17% 5 - Year Average Purpose: Bend, cut, bundle, and load reinforcing steel bars in accordance with customer’s orders. You’ll work with a mentor who will train you on safely using all machinery. Responsibilities: Safety is the most important part of all jobs within Nucor; therefore, candidates must be able to demonstrate the ability to initiate, lead, and uphold safety policies, practices, procedures, and housekeeping standards at all times. Responsibilities Unload trailers and store material in storage bins. Operate a shearing machine or a power saw to cut reinforcing steel bars to specific lengths, and a bending machine to bend reinforcing steel bars to specified shape. Operate overhead crane to move, assemble and select material to be fabricated or shipped. Assemble and load orders onto trailers for shipping. Operate a spray gun in the application of epoxy touch up or reinforcing steel bars. Maintain the shop or designated area in a clean and safe manner. Minimum Requirements: Must be legally authorized to work in the United States without company sponsorship now or in the future Must be age 18 or over Physical Demands: Working conditions can be noisy/dusty/hot/cold Some heavy lifting may be necessary Nucor is an Equal Opportunity Employer and a drug-free workplace
Let's parse it into sections:
- **Job Details / Location**: "Division: Nucor Rebar Fabrication Northwest Location: Tacoma, WA, United States Other Available Locations: N/A" -> This is metadata. The rules say: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I should fold this into a short `
` or handle it carefully. Since it's minor metadata, I'll put it in a `
` at the top or integrate it without a heading. The rules also say: "Output ONLY the HTML fragment — no /, no markdown code fences." and "Preserve ALL substantive information; do NOT invent or summarize away detail."
- **About/Welcome section**: "Welcome to Nucor, where our unique culture sets us apart. Joining Nucor means becoming part of North America's largest steel and steel products manufacturer, offering unmatched career opportunities and stability. We are known for our innovative sustainability practices and are the continent's largest recycler. Our vibrant culture, built on personal connections and teamwork, empowers every team member with the freedom to innovate and contribute to our collective success. Experience a workplace where safety, efficiency, and meaningful personal connections define every day, enriching both our teammates and the communities we serve." -> This is prose. Could be an "About the role" or intro section. The rules say use `
` for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to decide which headings to use based on actual content. The prompt gives examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use these or similar, but only if there's real content. I must not create sections with filler.
- **Compensation Data**: "Compensation Data: Entry Level Base Wage $17.49 + Production Bonus Weekly Production Bonus 6 Mo. Average - 90.76% of base wage. Profit Sharing: 20.17% 5 - Year Average" -> This has specific Pay information. Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So I can have a Pay section. But careful: the rule says "Prefer a few substantive sections over many thin ones." and "never emit a heading followed by filler/placeholder text". The Pay section has specific numbers, so it's valid.
- **Purpose**: "Purpose: Bend, cut, bundle, and load reinforcing steel bars in accordance with customer’s orders. You’ll work with a mentor who will train you on safely using all machinery." -> This is a purpose/intro line. Could be part of "About the role" or a separate small section. I'll likely integrate it into an "About the role" or "Purpose" section, but the allowed headings are listed. I can use `About the role
` and include purpose and description there, or use a `
` within that section.
- **Responsibilities**: Has "Responsibilities:" then a list of duties. Rule: "Use
- for any list of duties/requirements/benefits". So I'll make a `
- ` list for responsibilities.
- **Minimum Requirements**: "Minimum Requirements: Must be legally authorized to work in the United States without company sponsorship now or in the future Must be age 18 or over" -> This is requirements. Could be a "Requirements" or "Minimum Requirements" section. I'll use `
Requirements
` or similar, but only if there's real content. There is.
- **Physical Demands**: "Physical Demands: Working conditions can be noisy/dusty/hot/cold Some heavy lifting may be necessary" -> This is part of requirements or a separate section. I'll integrate it into Requirements or make a separate "Physical Demands" if it's substantial, but the allowed headings don't explicitly list it. I can fold it into Requirements or use a heading if it's specific content. The rule says include a section ONLY when the posting has real, specific content for it. Physical demands is specific. I'll likely include it under Requirements or as a separate `` if I have enough sections. But I need to be careful not to create too many thin sections. I'll probably fold it into Requirements or have a "Requirements" section that includes both minimum requirements and physical demands.
- **Benefits mentions**: "Nucor supports its teammates with top-tier benefits like Medical, Dental, Vision, and Disability Insurance, 401K and Roth accounts, Profit sharing, Pay-for-performance bonuses, Paid parental leave, Tuition reimbursement, Stock program, Scholarships and more." -> This is benefits content. But there's also "Compensation Data" with pay info. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits. However, I need to decide whether to have a separate Benefits section. The prompt's example headings include "Benefits". I could have a Benefits section with the list. But I also have Pay data. I'll need to parse carefully.
- **EEO/Equal Opportunity**: "Nucor is an Equal Opportunity Employer and a drug-free workplace" -> This is boilerplate that must be removed per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions."
- **Other**: "Job Details Division: ... Other Available Locations: N/A" -> metadata, fold into `
`.
Let's restructure the content logically, following the rules strictly.
Allowed headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should only use those headings if there's substantive content. I'll map the text:
- "About the role": The welcome culture text + Purpose line. I'll use `
About the role
` and put the prose there.
- "Responsibilities": The list of duties. `- ` list.
- "Requirements": Minimum requirements + physical demands. I'll combine them.
- "Qualifications": Not explicitly separate, but minimum requirements could qualify. I'll see if there's distinct "Qualifications" content. The text has "Minimum Requirements:" which covers it. I might not create a separate Qualifications section if it's the same. Rule: "Prefer a few substantive sections over many thin ones." So I'll likely have Requirements covering both minimum reqs and physical demands.
- "Skills": Not explicitly mentioned. I'll skip.
- "Benefits": The benefits list is substantial. I'll create a `
Benefits
` with `- `.
- "Pay": The compensation data is specific. I'll create a `
Pay
` with the wage/profit sharing info.
- "Schedule": Not mentioned. I'll skip.
Wait, the rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. "and never emit a heading followed by filler/placeholder text". So I must ensure each section has real content, no "commensurate with experience" etc.
Let's re-read the input carefully and extract only substantive, non-boilerplate content.
Stripping removed parts:
- Remove: "Job Details Division: Nucor Rebar Fabrication Northwest Location: Tacoma, WA, United States Other Available Locations: N/A" -> I'll fold into a short `` at the top, not as a heading.
- Remove: "Nucor is an Equal Opportunity Employer and a drug-free workplace" -> boilerplate, remove.
- Remove: any duplicated lines, application instructions, cookie/legal stuff. Not much beyond the EEO which I'll
` for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** Let me extract the meaningful content, structure, and metadata from the provided job posting. Text: Job Details Division: Nucor Rebar Fabrication Northwest Location: Tacoma, WA, United States Other Available Locations: N/A Welcome to Nucor, where our unique culture sets us apart. Joining Nucor means becoming part of North America's largest steel and steel products manufacturer, offering unmatched career opportunities and stability. We are known for our innovative sustainability practices and are the continent's largest recycler. Our vibrant culture, built on personal connections and teamwork, empowers every team member with the freedom to innovate and contribute to our collective success. Experience a workplace where safety, efficiency, and meaningful personal connections define every day, enriching both our teammates and the communities we serve. Nucor supports its teammates with top-tier benefits like Medical, Dental, Vision, and Disability Insurance, 401K and Roth accounts, Profit sharing, Pay-for-performance bonuses, Paid parental leave, Tuition reimbursement, Stock program, Scholarships and more. Compensation Data: Entry Level Base Wage $17.49 + Production Bonus Weekly Production Bonus 6 Mo. Average - 90.76% of base wage. Profit Sharing: 20.17% 5 - Year Average Purpose: Bend, cut, bundle, and load reinforcing steel bars in accordance with customer’s orders. You’ll work with a mentor who will train you on safely using all machinery. Responsibilities: Safety is the most important part of all jobs within Nucor; therefore, candidates must be able to demonstrate the ability to initiate, lead, and uphold safety policies, practices, procedures, and housekeeping standards at all times. Responsibilities Unload trailers and store material in storage bins. Operate a shearing machine or a power saw to cut reinforcing steel bars to specific lengths, and a bending machine to bend reinforcing steel bars to specified shape. Operate overhead crane to move, assemble and select material to be fabricated or shipped. Assemble and load orders onto trailers for shipping. Operate a spray gun in the application of epoxy touch up or reinforcing steel bars. Maintain the shop or designated area in a clean and safe manner. Minimum Requirements: Must be legally authorized to work in the United States without company sponsorship now or in the future Must be age 18 or over Physical Demands: Working conditions can be noisy/dusty/hot/cold Some heavy lifting may be necessary Nucor is an Equal Opportunity Employer and a drug-free workplace Let's parse it into sections: - **Job Details / Location**: "Division: Nucor Rebar Fabrication Northwest Location: Tacoma, WA, United States Other Available Locations: N/A" -> This is metadata. The rules say: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I should fold this into a short `
` or handle it carefully. Since it's minor metadata, I'll put it in a `
` at the top or integrate it without a heading. The rules also say: "Output ONLY the HTML fragment — no /, no markdown code fences." and "Preserve ALL substantive information; do NOT invent or summarize away detail." - **About/Welcome section**: "Welcome to Nucor, where our unique culture sets us apart. Joining Nucor means becoming part of North America's largest steel and steel products manufacturer, offering unmatched career opportunities and stability. We are known for our innovative sustainability practices and are the continent's largest recycler. Our vibrant culture, built on personal connections and teamwork, empowers every team member with the freedom to innovate and contribute to our collective success. Experience a workplace where safety, efficiency, and meaningful personal connections define every day, enriching both our teammates and the communities we serve." -> This is prose. Could be an "About the role" or intro section. The rules say use `
` for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to decide which headings to use based on actual content. The prompt gives examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use these or similar, but only if there's real content. I must not create sections with filler.
- **Compensation Data**: "Compensation Data: Entry Level Base Wage $17.49 + Production Bonus Weekly Production Bonus 6 Mo. Average - 90.76% of base wage. Profit Sharing: 20.17% 5 - Year Average" -> This has specific Pay information. Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So I can have a Pay section. But careful: the rule says "Prefer a few substantive sections over many thin ones." and "never emit a heading followed by filler/placeholder text". The Pay section has specific numbers, so it's valid.
- **Purpose**: "Purpose: Bend, cut, bundle, and load reinforcing steel bars in accordance with customer’s orders. You’ll work with a mentor who will train you on safely using all machinery." -> This is a purpose/intro line. Could be part of "About the role" or a separate small section. I'll likely integrate it into an "About the role" or "Purpose" section, but the allowed headings are listed. I can use `About the role
` and include purpose and description there, or use a `
` within that section. - **Responsibilities**: Has "Responsibilities:" then a list of duties. Rule: "Use
- for any list of duties/requirements/benefits". So I'll make a `
- ` list for responsibilities.
- **Minimum Requirements**: "Minimum Requirements: Must be legally authorized to work in the United States without company sponsorship now or in the future Must be age 18 or over" -> This is requirements. Could be a "Requirements" or "Minimum Requirements" section. I'll use `
Requirements
` or similar, but only if there's real content. There is. - **Physical Demands**: "Physical Demands: Working conditions can be noisy/dusty/hot/cold Some heavy lifting may be necessary" -> This is part of requirements or a separate section. I'll integrate it into Requirements or make a separate "Physical Demands" if it's substantial, but the allowed headings don't explicitly list it. I can fold it into Requirements or use a heading if it's specific content. The rule says include a section ONLY when the posting has real, specific content for it. Physical demands is specific. I'll likely include it under Requirements or as a separate `` if I have enough sections. But I need to be careful not to create too many thin sections. I'll probably fold it into Requirements or have a "Requirements" section that includes both minimum requirements and physical demands. - **Benefits mentions**: "Nucor supports its teammates with top-tier benefits like Medical, Dental, Vision, and Disability Insurance, 401K and Roth accounts, Profit sharing, Pay-for-performance bonuses, Paid parental leave, Tuition reimbursement, Stock program, Scholarships and more." -> This is benefits content. But there's also "Compensation Data" with pay info. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits. However, I need to decide whether to have a separate Benefits section. The prompt's example headings include "Benefits". I could have a Benefits section with the list. But I also have Pay data. I'll need to parse carefully. - **EEO/Equal Opportunity**: "Nucor is an Equal Opportunity Employer and a drug-free workplace" -> This is boilerplate that must be removed per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - **Other**: "Job Details Division: ... Other Available Locations: N/A" -> metadata, fold into `
`. Let's restructure the content logically, following the rules strictly. Allowed headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should only use those headings if there's substantive content. I'll map the text: - "About the role": The welcome culture text + Purpose line. I'll use `
About the role
` and put the prose there. - "Responsibilities": The list of duties. `- ` list.
- "Requirements": Minimum requirements + physical demands. I'll combine them.
- "Qualifications": Not explicitly separate, but minimum requirements could qualify. I'll see if there's distinct "Qualifications" content. The text has "Minimum Requirements:" which covers it. I might not create a separate Qualifications section if it's the same. Rule: "Prefer a few substantive sections over many thin ones." So I'll likely have Requirements covering both minimum reqs and physical demands.
- "Skills": Not explicitly mentioned. I'll skip.
- "Benefits": The benefits list is substantial. I'll create a `
Benefits
` with `- `.
- "Pay": The compensation data is specific. I'll create a `
Pay
` with the wage/profit sharing info. - "Schedule": Not mentioned. I'll skip. Wait, the rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. "and never emit a heading followed by filler/placeholder text". So I must ensure each section has real content, no "commensurate with experience" etc. Let's re-read the input carefully and extract only substantive, non-boilerplate content. Stripping removed parts: - Remove: "Job Details Division: Nucor Rebar Fabrication Northwest Location: Tacoma, WA, United States Other Available Locations: N/A" -> I'll fold into a short `` at the top, not as a heading. - Remove: "Nucor is an Equal Opportunity Employer and a drug-free workplace" -> boilerplate, remove. - Remove: any duplicated lines, application instructions, cookie/legal stuff. Not much beyond the EEO which I'll
- `.
- "Pay": The compensation data is specific. I'll create a `
- ` list.
- "Requirements": Minimum requirements + physical demands. I'll combine them.
- "Qualifications": Not explicitly separate, but minimum requirements could qualify. I'll see if there's distinct "Qualifications" content. The text has "Minimum Requirements:" which covers it. I might not create a separate Qualifications section if it's the same. Rule: "Prefer a few substantive sections over many thin ones." So I'll likely have Requirements covering both minimum reqs and physical demands.
- "Skills": Not explicitly mentioned. I'll skip.
- "Benefits": The benefits list is substantial. I'll create a `
- ` list for responsibilities.
- **Minimum Requirements**: "Minimum Requirements: Must be legally authorized to work in the United States without company sponsorship now or in the future Must be age 18 or over" -> This is requirements. Could be a "Requirements" or "Minimum Requirements" section. I'll use `