Platform Manager

We need to output HTML fragment with sections: Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the job posting. Content: - At IEM, we’re not just building... (intro). This could be "About the role" or maybe "About IEM". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading with prose summarizing the intro. - Platform Manager Location: US Remote Reports To: Director, Platform Execution & Delivery Salary Range: $70,000 - $105,000 Annually We need to include Pay section if salary range is given. Yes, salary range is given. So we need a Pay section with that info. Schedule: Not mentioned. So we should not include Schedule section. Benefits: The posting mentions "A bonus and/or long-term incentive units may be provided as part of the compensation package, in addition to the full range of medical, financial, and/or other benefits, dependent on the level and position offered." Also later: "We offer comprehensive and competitive benefits package designed to support our employees' well-being, growth, and long-term success." So we have benefits info. So include Benefits section. Qualifications: There's a "Qualifications" heading in posting: Bachelor’s degree in Business, Mathematics, Computer Science, or Engineering required. Minimum 2-4 years of experience in a Project Management or similar position. Also maybe "Compensation actually offered..." is not qualification. So we have qualifications. Requirements: Might be similar to qualifications. The posting also has "Position Summary" and "Key Responsibilities". So we can have "About the role" (position summary), "Responsibilities" (key responsibilities), "Requirements" maybe combine qualifications? But we have Qualifications section already. Could also have Requirements separate if there are specific requirements like experience, degree. But we can treat Qualifications as requirements. However we need to follow instruction: Use headings only when posting has real specific content. We have both Qualifications and maybe Requirements (like "Minimum 2-4 years of experience..." is a requirement). Could put that under Requirements. But we also have a "Qualifications" heading in the posting. So we should include both Requirements and Qualifications if they have distinct content. Let's see: The posting has a "Qualifications" subsection with bullet? Actually it's paragraph: "Qualifications Bachelor’s degree in Business, Mathematics, Computer Science, or Engineering required. Minimum 2-4 years of experience in a Project Management or similar position." That's qualifications. There's also "Compensation actually offered..." not a qualification. There's no separate "Requirements" heading. But we could still create a Requirements section if we have content like degree and experience. However to avoid duplication, maybe we just use Qualifications section for degree and experience, and not create Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we can combine degree/experience into Qualifications and not have Requirements. Skills: Not explicitly listed. Could infer from responsibilities but not explicit. Better not to create Skills section if no explicit skills list. Benefits: we have content. Pay: we have salary range. Schedule: none. Thus sections: About the role (position summary), Responsibilities (key responsibilities), Qualifications (degree/experience), Benefits, Pay. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. So we need to include all details from the posting within those sections. Let's extract: About the role: The position summary: "This position is responsible for effectively managing and maintaining relationships between the company and our customers during the order cycle by working directly with customers to access and help meet their needs." Also the intro paragraphs about IEM: "At IEM, we’re not just building innovative electrical distribution systems, we’re shaping the future. IEM is dedicated to delivering world-class solutions for complex power needs. After 75 years, we continue to push the boundaries of what’s possible. Whether you’re an experienced professional or just starting out, you’ll have the opportunity to contribute, grow, and make a lasting impact on industries that power the world’s most dynamic markets." This is about the company and role. Could be included in About the role. Responsibilities: List of key responsibilities bullet points. Need to preserve each as

. Let's list them: - Maintain and/or develop proven systems to track orders from order entry to shipment/delivery to ensure timeliness of shipment to meet customer’s expectation. - Maintain strong support for and interact with the Sr. Platform Manager, Director of Platform Execution and Delivery, and Strategic Platforms Division Director of Sales in the bid process, which includes all order management activities. - Coordinate with other internal departments and customers to achieve on-time shipment. - Review customer Purchase Order and resolves any commercial/technical issues. - Prepare order for entry along with managing all associated documents and correspondence. - Participate in engineering handoff meetings when applicable. - Work with engineering and customer through the submittal and release process. - Work with engineering, quotations, sales and customer to manage change orders. - Work with field service to schedule and resolve manufacturing deficiencies and site commissioning. - Work with client-specified integrator by communicating schedule and providing technical support services - Prepare cost proposals and deliver to clients for customer-driven order revisions. - Use system generated reports or develop effective reports that track order status and flag potential issues with orders. - Proactively anticipate, identify and resolve possible issues with orders that may cause delays or other customer complaints. - Perform other duties, which may be required by supervisor. We need to keep each as

. Qualifications: Bachelor’s degree in Business, Mathematics, Computer Science, or Engineering required. Minimum 2-4 years of experience in a Project Management or similar position. Also maybe "Compensation actually offered for this role will take into account internal equity and also may vary depending on the candidate's geographic region, job-related knowledge, skills, and experience among other factors." That's more about compensation, not qualification. Could be included in Pay section? But Pay section already has salary range. Could add note about variability. However instruction: do not include filler like "commensurate with experience". But this is actual statement about compensation variability. Might be relevant to Pay. We could include in Pay section as a note. Benefits: "A bonus and/or long-term incentive units may be provided as part of the compensation package, in addition to the full range of medical, financial, and/or other benefits, dependent on the level and position offered." Also later: "We offer comprehensive and competitive benefits package designed to support our employees' well-being, growth, and long-term success. View a snapshot of our benefits at https://www.iemfg.com/careers". So we can include that. Pay: Salary Range: $70,000 - $105,000 Annually. Also note about compensation variability and bonus etc. Could combine. We must not include boilerplate like recruiting scams, non-discrimination, privacy, AI use. So omit those. Now produce HTML fragment:

About the role

At IEM, we’re not just building innovative electrical distribution systems, we’re shaping the future. IEM is dedicated to delivering world-class solutions for complex power needs. After 75 years, we continue to push the boundaries of what’s possible. Whether you’re an experienced professional or just starting out, you’ll have the opportunity to contribute, grow, and make a lasting impact on industries that power the world’s most dynamic markets. This position is responsible for effectively managing and maintaining relationships between the company and our customers during the order cycle by working directly with customers to access and help meet their needs.

Responsibilities

• Maintain and/or develop proven systems to track orders from order entry to shipment/delivery to ensure timeliness of shipment to meet customer’s expectation.
• Maintain strong support for and interact with the Sr. Platform Manager, Director of Platform Execution and Delivery, and Strategic Platforms Division Director of Sales in the bid process, which includes all order management activities.
• Coordinate with other internal departments and customers to achieve on-time shipment.
• Review customer Purchase Order and resolves any commercial/technical issues.
• Prepare order for entry along with managing all associated documents and correspondence.
• Participate in engineering handoff meetings when applicable.
• Work with engineering and customer through the submittal and release process.
• Work with engineering, quotations, sales and customer to manage change orders.
• Work with field service to schedule and resolve manufacturing deficiencies and site commissioning.
• Work with client-specified integrator by communicating schedule and providing technical support services
• Prepare cost proposals and deliver to clients for customer-driven order revisions.
• Use system generated reports or develop effective reports that track order status and flag potential issues with orders.
• Proactively anticipate, identify and resolve possible issues with orders that may cause delays or other customer complaints.
• Perform other duties, which may be required by supervisor.

Qualifications

Bachelor’s degree in Business, Mathematics, Computer Science, or Engineering required. Minimum 2-4 years of experience in a Project Management or similar position.

Benefits

A bonus and/or long-term incentive units may be provided as part of the compensation package, in addition to the full range of medical, financial, and/or other benefits, dependent on the level and position offered. We offer a comprehensive and competitive benefits package designed to support employees' well-being, growth, and long-term success. View a snapshot of our benefits at https://www.iemfg.com/careers.

Pay

Salary Range: $70,000 - $105,000 Annually. Compensation actually offered for this role will take into account internal equity and may vary depending on the candidate's geographic region, job-related knowledge, skills, and experience among other factors.

We should not include Schedule section. Check for any duplicated lines: none. Check for any boilerplate: we omitted recruiting scams, non-discrimination, privacy, AI use. Check for any placeholders: none. All substantive info preserved: we included intro, position summary, responsibilities, qualifications, benefits, pay. Did we include the line "Platform Manager Location: US Remote Reports To: Director, Platform Execution & Delivery"? That's metadata; we omitted it as per instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. This is minor metadata (location, reports to). Should we include it somewhere? The instruction says fold minor metadata into a short

or drop it. Could include in About the role paragraph maybe. But we already have a long About the role paragraph; we could add a sentence: "Location: US Remote. Reports to: Director, Platform Execution & Delivery." However that might be considered minor metadata; we could drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can either drop it or include in a short p. Since we already have About the role paragraph, we could incorporate it there. But we must preserve ALL substantive information; location and reporting line is substantive? It's metadata but still info. The instruction says fold minor metadata into a short

or drop it. So we can drop it if we consider it minor. However to be safe, we could add a short paragraph after About the role:

Location: US Remote. Reports to: Director, Platform Execution & Delivery.

That is not a heading, just a p. That would preserve it. Let