Metal Fabricator I
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat job title as a heading (the page already shows it). Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. We need to decide which sections to include based on content. Content includes: - About Us (company description) - About The Opportunity (role description) - Responsibilities (list) - Required Qualifications (list) - Preferred Qualifications (list) - Working Conditions (description) - Benefits (list) - Equal Opportunity Employer (EEO) - we must remove EEO boilerplate. - Acknowledgements (some generic statement) - maybe not needed? It's boilerplate? It says "The above job description is not intended to be an all-inclusive list..." Might be considered boilerplate but it's part of job description. However we might keep it? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Acknowledgements might be considered legal boilerplate? It's not EEO but it's a disclaimer. Might be considered boilerplate; safer to remove? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Acknowledgements not explicitly mentioned, but it's a generic statement. Might be considered boilerplate; but it's part of job description. However we can keep if substantive? It's not substantive detail about role. I'd lean to remove it as it's generic. - Location: Stuart, FL – Onsite. Monday to Friday, 6:30 AM to 3 PM. This gives schedule and location. Schedule is provided: Monday to Friday, 6:30 AM to 3 PM. So we can include a Schedule section. Also location could be folded into a short
maybe under About the role? But we have a Schedule section allowed if posting actually states them. Yes schedule is stated. So we can have a
Schedule
withMonday to Friday, 6:30 AM to 3 PM. Onsite in Stuart, FL.
maybe combine location. - Benefits: listed: health and disability insurance, 401(k) match, flexible spending accounts, EAP, paid time off, company-paid holidays. So we can have Benefits section with- .
- Pay: not mentioned. So we should NOT create Pay section.
- About the role: we have "About The Opportunity" which describes role. Could be considered "About the role". So we can have
- each. Now Qualifications: Required Qualifications list: "High School Diploma or equivalent 1-3 years of related experience Must be authorized to work in the U.S. on a full-time bases without sponsorship now or in the future. The Company cannot offer employment to visa holders who require employer sponsorship in the future or cannot work now on a full-time basis. Must be able to perform work subject to ITAR/EAR regulations." We need to preserve all. We'll make list items. Preferred Qualifications list: "Completion of a recognized apprenticeship program or technical certification in Metal Fabrication, Welding, or Precision Manufacturing Proficiency in reading and interpreting, complex blueprints,
About the role
with paragraph(s) from that section. - Responsibilities: we have a list (though it's a bit messy). We need to extract list items. - Required Qualifications: list. - Preferred Qualifications: list. - Working Conditions: description. - Skills? Not explicitly separate; but we could combine Required and Preferred as Qualifications. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to use "Requirements" for Required Qualifications, "Preferred Qualifications" maybe as "Qualifications"? But we have both required and preferred. Could combine into two sections: "Required Qualifications" and "Preferred Qualifications". Or we could have "Requirements" for required, and "Preferred Qualifications" for preferred. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings; but we can also use others if needed? Safer to stick to those. So we need to map content to those headings.
We have:
- About the role: from About The Opportunity.
- Responsibilities: list.
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications? Or Skills? Could treat Preferred Qualifications as Qualifications.
- Skills: maybe we could extract skills from Preferred Qualifications (like mechanical aptitude, problem-solving, etc.) but we already have them there. Could combine.
But we must not create thin sections. Prefer few substantive sections. Could combine Required and Preferred into one "Qualifications" section with subheadings? But we cannot add extra headings beyond . Could use Qualifications
and then within that have
Qualifications
and then within that haveRequired: ...
Preferred: ...
. That would be one section. Similarly, we could have Skills as part of Qualifications. But we need to preserve all substantive information. If we combine, we still preserve. We also have Working Conditions: maybe we could put under Responsibilities? Not ideal. Could create a separate section "Working Conditions" but not in the list of example headings. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. But to be safe, we could include Working Conditions as a section with Working Conditions
. It's substantive.
Similarly, Benefits we have.
Schedule we have.
Location we could include in Schedule section or as a short paragraph.
Thus final sections:
About the role
... from About The Opportunity ...
Responsibilities
- ... list items ...
Qualifications
Required: ... list ...
Preferred: ... list ...
Working Conditions
... description ...
Benefits
- ... list ...
Schedule
Monday to Friday, 6:30 AM to 3 PM. Onsite in Stuart, FL.
We should not include Pay. We need to ensure we don't repeat job title. We need to remove boilerplate: About Us? Actually "About Us" is company description; maybe we could include as part of About the role? But it's separate company overview. Could we include as a section "About the company"? Not in examples but could be okay. However we might drop it because it's not directly about the role? The instruction says preserve ALL substantive information. About Us is substantive about company. Could we include it as a section? The examples didn't list About Us, but we could still use