Product Developer - Modular - Data Center

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the posting. Key sections: - Posting Title: Product Developer - Modular - Data Center (not heading) - Reports To: Manager, Product Development (metadata) - Location: Edgerton, WI | Remote | Salt Lake City, UT | Houston, TX | Greater San Francisco Bay Area (metadata) - Salary Range: $100,000 to $140,000 (Pay) - This position is eligible for the annual performance bonus plan. (Pay/Benefits? It's about compensation) - Final determination of a successful candidate’s starting pay will vary based on a number of factors, including market location and may vary depending on job-related knowledge, skills, education and experience. (Pay) - The pay scale listed for this position is generally for candidates that meet the specified qualifications and requirements listed on this specific job description. (Pay) - We provide a competitive compensation package that recognizes your experience, credentials, and education alongside a robust benefits program to meet your needs. (Benefits) - Our compensation reflects the cost of labor across several US geographic markets. (Pay) - Who We Are (section) – we can include as maybe "About the company"? Not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" not allowed, but we could incorporate into About the role? Probably not. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those as examples, but we should only include sections when posting has real specific content for it. It didn't forbid other headings, but says use

for section headings (e.g. ...). Likely they expect us to use those headings only. So we should map content to those headings. Thus we need sections: - About the role: description of role. - Responsibilities: list of duties. - Requirements: maybe "Minimum Qualifications" or "Education and Experience". - Qualifications: maybe licensure/certifications. - Skills: abilities list. - Benefits: benefits program. - Pay: salary range, bonus, etc. - Schedule: not mentioned; we should not include if no content. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include details like specific tasks, abilities, etc. We must remove boilerplate: EEO, scam warning, navigation, duplicated lines, application instructions. Also remove "Who We Are" maybe? It's not in allowed headings; but it's substantive info about company. Could we include it under About the role? Probably not. The instruction says "include a section ONLY when the posting has real, specific content for it". It didn't say we cannot add other sections besides those examples, but they gave examples. Safer to stick to those headings and maybe omit "Who We Are". However that would lose some substantive info about company. But maybe it's considered boilerplate? It's not boilerplate; it's descriptive. But the allowed headings list doesn't include "About the company". Could we treat "About the role" as covering both role and company? The "About The Role" section already exists in posting. So we can put that content under About the role heading. The "Who We Are" could be omitted? Might be considered not required. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. If we don't have a heading for it, we could incorporate it into a

under About the role? But that would mix role description with company description, but still preserve info. That might be acceptable. Similarly, "Goals & Objectives" could be part of Responsibilities or About the role. We need to produce HTML fragment only. Let's extract content. About The Role (from posting): "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 drawingsEquipment submittal review and implementationPackaging product submittalsWriting design narrativesProducing and maintaining a development schedule in MS ProjectObtaining product data from vendors or manufacturersProducing a bill of materialParticipating in team meetingsPresenting solution ideas during team meetingsConducting research on specific processes, materials or manufacturersCollaborating with their peer product developers on design best practices.Innovatively create cost savings opportunities Goals & Objectives: Complete tasks completely, accurately and on timePlay a dynamic role in a creative team collaboration environment.Maintain proficiency in the use of the tools providedSupport continuous improvement initiatives.Support the SPD/Director to a level of success." We need to format as prose or list. Responsibilities likely a list of duties. Responsibilities: list of duties from that paragraph. Let's list them: - Assists the Sr. Product Developer in translating customer requirements into specific product features, geometry, and functions. - Preparation of a development schedule. - Component design. - Producing drawings and submittals. - Specification mark-ups. - Researching materials or processes. - Preparing sketches or bills of material. - Involved with scope leveling such preparing scope documents, matrices, and CDE’s (Comply, Deviate and/or Exclude) duties. - 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 peer product developers on design best practices. - Innovatively create cost savings opportunities. - Goals & Objectives: 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. Some duplicates: preparing sketches or drawings appears twice; we can keep once. Now Requirements: maybe "Minimum Qualifications" section. Minimum Qualifications: "Any combination of education and experience that would likely provide the required knowledge, skills and abilities as well as possession of any required licenses or certifications is qualifying. 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. Applicants must be authorized to work in the United States. This position is not eligible for sponsorship." We can split into Requirements (education/experience) and Qualifications (licensure/certifications, work authorization). But the instruction says use headings Requirements, Qualifications. So we can put education/experience under Requirements, and licensure/certifications under Qualifications. Skills: list of abilities from "About You" section. About You: "Ability to do independent research on submittals, materials, functions, or processesAbility to draw, sketch or illustrate, Modeling Skills, Revit Preferred.Ability to translate abstract concepts into concrete design ideasFamiliarity with Office 365, Excel, Navis, MS Project, ACC and Bluebeam RevuAbility to read and accurately interpret electrical and mechanical design drawings including single line diagrams, control diagrams and process piping diagramsFamiliarity with OSHA provisionsFamiliarity with NFPA 70E Safety standardsFamiliarity with Electrical NEC and industry standards" We need to separate into list items. Benefits: "We provide a competitive compensation package that recognizes your experience, credentials, and education alongside a robust benefits program to meet your needs." Also maybe mention annual performance bonus plan? That's compensation. Benefits could be robust benefits program. We'll include that. Pay: Salary range $100,000 to $140,000, eligible for annual performance bonus plan, final determination varies based on market location, etc., compensation reflects cost of labor across several US geographic markets. Schedule: not mentioned, so omit. Also we might include location and reports to as metadata in a short

maybe under a generic heading? Not allowed. Could we include them as a

before sections? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and reports to in a short

before sections, not as heading. Thus output:

Reports To: Manager, Product Development. Location: Edgerton, WI | Remote | Salt Lake City, UT | Houston, TX | Greater San Francisco Bay Area.

Then sections. We need to ensure we don't repeat job title. Now produce HTML. We'll use

for each section heading. Inside sections, use

for prose,

• for lists. Let's craft. About the role: we can put the description as prose (maybe combine with responsibilities? But we have separate Responsibilities). So About the role could be a brief summary: "The Product Developer assists the Sr. Product Developer in translating customer requirements into specific product features, geometry, and functions." plus maybe mention development responsibilities as defined. We'll keep the prose from About The Role but not the list; we can keep the first sentences. Better: 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." Then Responsibilities: list. Requirements: list education/experience. Qualifications: list licensure/certifications, work authorization. Skills: list abilities. Benefits: paragraph. Pay: paragraph(s). Let's extract precise text. About the role prose: "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." But that includes many responsibilities; maybe we should keep that as About the role and then Responsibilities list the specific tasks. However that would duplicate content. To avoid duplication, we could keep About the role short and Responsibilities detailed. Thus About the role: short summary. Responsibilities: list all tasks. Let's craft Responsibilities list items: - Assists the Sr. Product Developer in translating customer requirements into specific product features, geometry, and functions. - Prepares a development schedule. - Performs component design. - Produces drawings and submittals. - Completes specification mark-ups. - Researches materials or processes. - Prepares sketches or bills of material