Lead Design Engineer
FN America, LLC · Columbia, SC · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role? Actually we have description about company, position summary, job duties, educational requirements, experience requirements, skills and competencies, tools knowledge, certifications/licenses, working conditions. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only those headings if content exists. We must not repeat job title. No Pay/Schedule/Benefits unless present. There's no explicit pay, schedule, benefits. So we should not include those sections. We need sections: About the role (maybe company description and position summary), Responsibilities (job duties), Requirements (educational + experience?), Qualifications (maybe skills and competencies?), Skills (tools knowledge?), but we need to avoid duplication. Let's think: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include based on content. We have:
- About the role: could include company description and position summary.
- Responsibilities: job duties.
- Requirements: educational requirements and experience requirements.
- Qualifications: maybe skills and competencies? But they also have Skills heading. Could separate: Qualifications = educational/experience? Actually Requirements already covers edu/experience. Qualifications could be skills and competencies. Skills could be tools knowledge and specific technical abilities. But we need to avoid thin sections. Perhaps combine Skills and Qualifications? But we need to follow headings exactly if we include them. We could include About the role, Responsibilities, Requirements, Qualifications, Skills. That's five sections.
Check content:
About the role: company description + position summary.
Responsibilities: job duties list.
Requirements: educational requirements + experience requirements.
Qualifications: skills and competencies (accountability, collaboration, etc.) plus maybe ability to author reports, etc.
Skills: tools knowledge (GD&T, lab equipment, 3D CAD, project management, design analysis software, MS Office, training on specific systems). Also maybe "Technical knowledge of all typical firearm processing technologies and expertise in at least one knowledge area..." That could be part of Skills.
We must not invent or summarize away detail. Must preserve all substantive information. So we need to include all details from those sections.
We must not include boilerplate like EEO, accommodation, etc. Remove those.
We must not include duplicated lines.
We must not include navigation/cookie etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Original text:
"Description FN America, LLC is a U.S. subsidiary of FN Herstal, S.A., a global leader in the development and manufacturing of high-quality, reliable firearms for military, law enforcement and commercial customers worldwide. Headquartered in Columbia, South Carolina, FN America is passionately committed to providing its customers with a portfolio of FN-branded products, training and support services that enhance user performance and safeguard their lives. For more information, visit us at or follow us on Facebook, Twitter and Instagram."
We need to keep substantive info: company description, location, commitment, maybe mention social media? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The social media links maybe considered navigation? It's not essential job info. Might be considered boilerplate? It's not required for job. Safer to omit? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The social media links are not substantive to the job. Could be considered navigation. I'd omit them.
Thus About the role: "FN America, LLC is a U.S. subsidiary of FN Herstal, S.A., a global leader in the development and manufacturing of high-quality, reliable firearms for military, law enforcement and commercial customers worldwide. Headquartered in Columbia, South Carolina, FN America is passionately committed to providing its customers with a portfolio of FN-branded products, training and support services that enhance user performance and safeguard their lives."
Position Summary: "The Lead Design Engineer is responsible for creating designs, performing evaluations and establishing the technical data package that results in the full product development. In this role, the Lead Design Engineer provides technical guidance and specific subject matter expertise to include analysis, testing, and evaluation of new products to predetermined specifications. The Lead Design Engineer will also support product line extensions and improvements to existing product designs."
Combine both into About the role section.
Responsibilities: list of duties.
Let's extract job duties bullet points:
"Contributes to the Product Development Process (PDP) initiative by developing new product platforms and derivatives.
Supports industrialization activities including feasibility review, risk analysis and mitigation, detailed development, data package creation and product support.
Plans, conducts and documents hands-on product testing, sometimes extensive.
Creates an execution strategy using work-based scheduling software and tools.
Manages execution of deliverable milestones by leading a team of engineers.
Collaborates effectively both within the department and in a cross-functional team environment.
Provides guidance to junior engineers.
Develops and implements product design improvements.
Creates execution strategies to include cost, work, and time for work assigned.
Other duties as assigned by management."
We need to put each as inside
- .
Requirements: educational + experience.
Educational Requirements: "Bachelor of Science in Mechanical Engineering, Applied Science, or equivalent required. Master of Science in Mechanical Engineering preferred."
Experience Requirements: "Six years of experience in a design engineering role is required."
Combine into Requirements section as prose or list? Could be
- ... ...
- All FN America employees are expected to demonstrate the behaviors of accountability, collaboration, communication, customer focus, and innovation.
- Ability to author thorough written and verbal status and technical reports.
- Ability to utilize and follow FNA and industry engineering standards and procedures.
- Technical knowledge of all typical firearm processing technologies and expertise in at least one knowledge area, including machining processes, plastic injection molding, metal injection molding, investment casting, surface treating, and spring manufacturing.
- Understanding of proper design components and subassemblies that result in the successful development and validation of major new products.
- Ability to use required tools on difficult tasks and/or group of tasks or equivalent.
- Knowledge of GD&T per ASME Y14.5 1994 and 1982.
- Lab equipment and measurement tools; development and execution of test procedures.
- 3D CAD software (PTC Creo preferred).
- Project Management Principles (work-based schedule development and execution).
- Design Analysis and Simulation Software (experience with CETOL, Ansys, Adams, and STAR-CCM+ preferred).
- Microsoft
with both sentences. Qualifications: skills and competencies. Extract: "All FN America employees are expected to demonstrate the behaviors of accountability, collaboration, communication, customer focus, and innovation. Additional requirements of this position include: Ability to author thorough written and verbal status and technical reports. Ability to utilize and follow FNA and industry engineering standards and procedures. Technical knowledge of all typical firearm processing technologies and expertise in at least one knowledge area, including machining processes, plastic injection molding, metal injection molding, investment casting, surface treating, and spring manufacturing. Understanding of proper design components and subassemblies that result in the successful development and validation of major new products. Ability to use required tools on difficult tasks and/or group of tasks or equivalent." We could break into
- items.
Skills: tools knowledge etc.
Extract: "Tools Knowledge of GD&T per ASME Y14.5 1994 and 1982. Lab Equipment and Measurement Tools Development and Execution of Test Procedures 3D CAD software (PTC Creo preferred) Project Management Principles (work-based schedule development and execution) Design Analysis and Simulation Software (experience with CETOL, Ansys, Adams, and STAR-CCM+ preferred) Microsoft Office Training Training on department specific Gateway (SharePoint based), PDS (PTC Windchill based), project management software will be required."
Also maybe "Certifications/Licenses None." That's not a skill; we could include under Skills? But it's basically none. Since it's "None", we should not create a section for it if it's just "None". The instruction: 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. "None" is similar to placeholder? It's a statement that there are none. Might be considered filler? Probably better to omit Certifications/Licenses section entirely because it's not substantive (just says none). So we skip.
Working Conditions: "Typical office environment with some travel between buildings and to other locations required. May be exposed to loud noises, toxic chemicals, and dangerous machinery when on the plant floor. All FN America employees have a responsibility to participate in the development of a safe and healthy workplace and to comply with instructions given for their own safety and health and that of others."
This is substantive. Should we include a section? The allowed headings do not include Working Conditions. We could maybe put under About the role or Responsibilities? But it's not exactly those. The instruction says use headings for section 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 only those headings. So we need to map Working Conditions into one of those. Perhaps it fits under Responsibilities? Not really. Could be under About the role? Maybe we can include a brief sentence about working conditions in About the role? But that would be mixing. However we must preserve all substantive information; we cannot drop it. We could add a
after the About the role section without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but suggests to use those for sections. Safer to include Working Conditions as a paragraph under About the role? Might be okay.
Alternatively we could create a section "Working Conditions" using even though not in list; but instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies examples, not exclusive list. So we could add other headings if needed. But they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; but not strictly prohibited others. However to be safe, we could incorporate Working Conditions into Responsibilities or About the role as a paragraph.
I'll add a paragraph after Responsibilities maybe as part of Responsibilities? Actually working conditions is not a duty. Could add a separate section "Working Conditions" with . I think it's acceptable as it's substantive and not covered elsewhere. The instruction didn't forbid other headings; just gave examples. I'll include Working Conditions.
Now we need to output only HTML fragment.
Structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies examples, not exclusive list. So we could add other headings if needed. But they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; but not strictly prohibited others. However to be safe, we could incorporate Working Conditions into Responsibilities or About the role as a paragraph.
I'll add a paragraph after Responsibilities maybe as part of Responsibilities? Actually working conditions is not a duty. Could add a separate section "Working Conditions" with . I think it's acceptable as it's substantive and not covered elsewhere. The instruction didn't forbid other headings; just gave examples. I'll include Working Conditions.
Now we need to output only HTML fragment.
Structure:
About the role
. I think it's acceptable as it's substantive and not covered elsewhere. The instruction didn't forbid other headings; just gave examples. I'll include Working Conditions.
Now we need to output only HTML fragment.
Structure:
About the role
... company description ...
... position summary ...
Responsibilities
Requirements
Bachelor of Science in Mechanical Engineering, Applied Science, or equivalent required. Master of Science in Mechanical Engineering preferred.
Six years of experience in a design engineering role is required.