Product Developer - Modular - Data Center
for each section heading.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tools, standards, etc.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the scam warning, EEO statement, contact email, etc. Also remove "Who We Are" etc? That's not boilerplate but maybe not needed for sections; we can ignore as it's not part of requested sections. We should not include it as it's not a section heading we are outputting. We can just omit.
We need to ensure we don't include placeholders like "not specified". We have actual content.
Now craft HTML.
Structure:
About the role
... prose ... maybe include some bullet list? The role description includes a sentence then a list of specific tasks. We could put the prose in
and then a
for the list of tasks.
But the instruction: Use - for any list of duties/requirements/benefits, and
for prose. So we can separate.
Thus:
About the role
The Product Developer assists the Sr. Product Developer in translating customer requirements into specific product features, geometry, and functions. The Product Developer will have specific development responsibilities as defined by the Sr. Product Developer and may include the preparation of a development schedule, component design, producing drawings and submittals, specification mark-ups, researching materials or processes, or preparing sketches or bills of material. The Product Developer will also be involved with scope leveling such preparing scope documents, matrices, and CDE’s (Comply, Deviate and/or Exclude) duties. The Product Developer is directly accountable for completing specific product development tasks or activities including:
- Preparing sketches or drawings
- Equipment submittal review and implementation
- Packaging product submittals
- Writing design narratives
- Producing and maintaining a development schedule in MS Project
- Obtaining product data from vendors or manufacturers
- Producing a bill of material
- Participating in team meetings
- Presenting solution ideas during team meetings
- Conducting research on specific processes, materials or manufacturers
- Collaborating with their peer product developers on design best practices
- Innovatively create cost savings opportunities
Then maybe a for Goals & Objectives? Could be part of responsibilities.
Next section: Responsibilities.
We could combine Goals & Objectives as responsibilities.
Responsibilities
- Complete tasks completely, accurately and on time
- Play a dynamic role in a creative team collaboration environment
- Maintain proficiency in the use of the tools provided
- Support continuous improvement initiatives
- Support the SPD/Director to a level of success
But we already listed many duties under About the role; maybe we should not duplicate. However the instruction: "Preserve ALL substantive information". So we need to include the Goals & Objectives somewhere. Could be under Responsibilities.
We could also include the earlier list under About the role as responsibilities; but we already used that list there. Might be okay.
Now Requirements: maybe the "Ability to..." list.
Requirements
- Ability to do independent research on submittals, materials, functions, or processes
- Ability to draw, sketch or illustrate, Modeling Skills, Revit Preferred
- Ability to translate abstract concepts into concrete design ideas
- Familiarity with Office 365, Excel, Navis, MS Project, ACC and Bluebeam Revu
- Ability to read and accurately interpret electrical and mechanical design drawings including single line diagrams, control diagrams and process piping diagrams
- Familiarity with OSHA provisions
- Familiarity with NFPA 70E Safety standards
- Familiarity with Electrical NEC and industry standards
- Applicants must be authorized to work in the United States. This position is not eligible for sponsorship.
But note: The last item is a sentence; still okay as - .
Now Qualifications:
Qualifications
Education and Experience: Vocational or Technical Certificate in engineering drafting or design, industrial technology, manufacturing design, mechanical design, or electrical design with 3 to 5 years’ experience in a product development role in an industrial manufacturing environment; or 3 to 5 years as a licensed journeyman electrician constructing modular building infrastructure components; or 3 to 5 years as a project manager working for an electrical contractor.
Licensure/Certifications: None required.
Now Skills: Could be overlapping; but we could list specific skills like drawing, modeling, Revit, Office 365, Excel, Navis, MS Project, ACC, Bluebeam Revu, reading drawings, OSHA, NFPA 70E, NEC. However many already in Requirements. To avoid duplication, maybe we combine Requirements and Skills? But we need separate sections only if posting has real specific content for it. The posting does list abilities and familiarity; those could be considered Skills. The "Minimum Qualifications" is Qualifications. The "About You" list is more like Skills/Requirements. To avoid duplication, we could treat "About You" as Skills, and Requirements as maybe "Eligibility" (work authorization). But the instruction says we must preserve all substantive information; duplication is not prohibited but we should avoid unnecessary repetition? It didn't forbid duplication, but we should aim for a few substantive sections over many thin ones. Having both Requirements and Skills may be thin if they overlap heavily. Perhaps better to merge them into one section called "Requirements and Skills" but we must use allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include Skills and omit Requirements if we can fit all content there. However the posting includes "Ability to..." which are skills, and also "Applicants must be authorized to work..." which is a requirement. So we could put all under Skills (including work auth). But
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tools, standards, etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the scam warning, EEO statement, contact email, etc. Also remove "Who We Are" etc? That's not boilerplate but maybe not needed for sections; we can ignore as it's not part of requested sections. We should not include it as it's not a section heading we are outputting. We can just omit. We need to ensure we don't include placeholders like "not specified". We have actual content. Now craft HTML. Structure:
About the role
... prose ... maybe include some bullet list? The role description includes a sentence then a list of specific tasks. We could put the prose in
and then a
- for the list of tasks.
But the instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can separate. Thus:
About the role
The Product Developer assists the Sr. Product Developer in translating customer requirements into specific product features, geometry, and functions. The Product Developer will have specific development responsibilities as defined by the Sr. Product Developer and may include the preparation of a development schedule, component design, producing drawings and submittals, specification mark-ups, researching materials or processes, or preparing sketches or bills of material. The Product Developer will also be involved with scope leveling such preparing scope documents, matrices, and CDE’s (Comply, Deviate and/or Exclude) duties. The Product Developer is directly accountable for completing specific product development tasks or activities including:
- Preparing sketches or drawings
- Equipment submittal review and implementation
- Packaging product submittals
- Writing design narratives
- Producing and maintaining a development schedule in MS Project
- Obtaining product data from vendors or manufacturers
- Producing a bill of material
- Participating in team meetings
- Presenting solution ideas during team meetings
- Conducting research on specific processes, materials or manufacturers
- Collaborating with their peer product developers on design best practices
- Innovatively create cost savings opportunities
for Goals & Objectives? Could be part of responsibilities. Next section: Responsibilities. We could combine Goals & Objectives as responsibilities.
Responsibilities
- Complete tasks completely, accurately and on time
- Play a dynamic role in a creative team collaboration environment
- Maintain proficiency in the use of the tools provided
- Support continuous improvement initiatives
- Support the SPD/Director to a level of success
Requirements
- Ability to do independent research on submittals, materials, functions, or processes
- Ability to draw, sketch or illustrate, Modeling Skills, Revit Preferred
- Ability to translate abstract concepts into concrete design ideas
- Familiarity with Office 365, Excel, Navis, MS Project, ACC and Bluebeam Revu
- Ability to read and accurately interpret electrical and mechanical design drawings including single line diagrams, control diagrams and process piping diagrams
- Familiarity with OSHA provisions
- Familiarity with NFPA 70E Safety standards
- Familiarity with Electrical NEC and industry standards
- Applicants must be authorized to work in the United States. This position is not eligible for sponsorship.
- .
Now Qualifications:
Qualifications
Education and Experience: Vocational or Technical Certificate in engineering drafting or design, industrial technology, manufacturing design, mechanical design, or electrical design with 3 to 5 years’ experience in a product development role in an industrial manufacturing environment; or 3 to 5 years as a licensed journeyman electrician constructing modular building infrastructure components; or 3 to 5 years as a project manager working for an electrical contractor.
Licensure/Certifications: None required.
Now Skills: Could be overlapping; but we could list specific skills like drawing, modeling, Revit, Office 365, Excel, Navis, MS Project, ACC, Bluebeam Revu, reading drawings, OSHA, NFPA 70E, NEC. However many already in Requirements. To avoid duplication, maybe we combine Requirements and Skills? But we need separate sections only if posting has real specific content for it. The posting does list abilities and familiarity; those could be considered Skills. The "Minimum Qualifications" is Qualifications. The "About You" list is more like Skills/Requirements. To avoid duplication, we could treat "About You" as Skills, and Requirements as maybe "Eligibility" (work authorization). But the instruction says we must preserve all substantive information; duplication is not prohibited but we should avoid unnecessary repetition? It didn't forbid duplication, but we should aim for a few substantive sections over many thin ones. Having both Requirements and Skills may be thin if they overlap heavily. Perhaps better to merge them into one section called "Requirements and Skills" but we must use allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include Skills and omit Requirements if we can fit all content there. However the posting includes "Ability to..." which are skills, and also "Applicants must be authorized to work..." which is a requirement. So we could put all under Skills (including work auth). But