Senior Project Manager - Power Systems (PowerCab2)

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" description, then description of role. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We have content for About the role? The posting includes description of role (the paragraph after "View the SENS Product Catalog Summary The Senior Project Manager – PowerCab2 will lead..."). That could be "About the role". Also we have Responsibilities (multiple bullet-like paragraphs). We have Required Qualifications and Preferred Qualifications (these could be under Requirements/Qualifications). We have Benefits (list). We have Pay (Base Compensation and Bonus). We have Location (but not a heading). Schedule not present. Skills maybe not explicit; we could combine skills under Qualifications? The instruction: Use headings for those specific names if content exists. We must not repeat job title as heading. We must not put Job ID etc. We must preserve all substantive info. Remove boilerplate: EEO, equal opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove duplicated lines (like repeated Operating Model Development paragraph appears twice). We need to deduplicate. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, "Who We Are Stored Energy Systems (SENS) is an award-winning manufacturer ..." That's company overview. Could be placed under "About the role"? Actually "About the role" heading is for role description, not company. But we could include company overview under About the role? Might be okay. However instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role section containing description of role and maybe company overview. But we should not invent headings. We'll include About the role with the role description paragraph(s). The "Who We Are" could be considered part of About the role? Might be okay but maybe better to include it as part of About the role? The role description includes responsibilities etc. The "Who We Are" is company overview, not role. There's no heading for company overview in list, but we could still include it under About the role as introductory paragraph. It's not prohibited. We'll keep it. Now Responsibilities: we have many bullet-like sentences. We'll convert each sentence into

under a

. Need to avoid duplication: there is repeated "Operating Model Development" paragraph appears twice (identical). We'll include only once. Let's list responsibilities from text: - Lead PowerCab2 customer projects from order acceptance through final shipment and customer delivery. - Own the current portfolio and project execution rhythm for assigned PowerCab2 orders, including timeline, status, blockers, risks, customer commitments, and internal follow-through. - Serve as the primary cross-functional coordinator between Sales, Sales Operations, Order Management, Customer Success, Engineering, Production, Supply Chain, Finance, and other required teams. - Ensure each PowerCab2 project has clear scope, committed delivery expectations, defined owners, and documented handoffs. - Help build and refine the scalable PowerCab2 execution model, including process flows, swim lanes, handoffs, milestone definitions, escalation points, and ownership rules. - Support the transition from engineered-to-order work toward configured-to-order execution where appropriate. - Partner with Engineering and Commercial teams to operationalize PowerCab2 configuration rules, approved options, “Lego block” standards, and quote-to-build requirements. - Help define how PowerCab2 projects move through standard, repeatable, configurable, and engineered lanes. - Identify recurring process breakdowns and partner with functional leaders to eliminate root causes. - Communicate professionally with customer project managers, construction managers, switchgear OEMs, contractors, and internal account owners as needed. - Proactively identify customer needs, document expectations and desired outcomes early, and hold the customer/project manager accountable to agreed inputs, decisions, and timelines so SENS can operationally deliver the intended customer experience. - Translate internal project realities into clear, credible customer-facing updates. - Protect the customer experience by ensuring changes, delays, risks, and decisions are communicated clearly and timely. - Hold customers accountable when customer-driven changes, late inputs, unclear requirements, or scope changes create schedule or cost risk. - Balance customer advocacy with operational credibility, ensuring SENS does not make commitments that cannot be supported. - Drive internal teams toward clear commitments, timely decisions, and early escalation when delivery, scope, or customer commitments are at risk. - Hold Engineering, Production, Supply Chain, Sales, and other stakeholders accountable to agreed project requirements, timelines, and escalation paths. - Identify gaps between what was sold, what was ordered, what was engineered, what can be built, and what was promised to the customer. - (Duplicate) Help build and refine the scalable PowerCab2 execution model... (skip duplicate) - Support the transition from engineered-to-order work toward configured-to-order execution where appropriate. (duplicate) - Partner with Engineering and Commercial teams to operationalize PowerCab2 configuration rules... (duplicate) - Help define how PowerCab2 projects move through standard, repeatable, configurable, and engineered lanes. (duplicate) - Identify recurring process breakdowns and partner with functional leaders to eliminate root causes. (duplicate) - Identify recurring process breakdowns across the PowerCab2 quote-to-delivery lifecycle and partner with functional leaders to eliminate root causes. (similar but slightly different; we can keep as separate? It's essentially same. We'll keep one.) We'll deduplicate. Now Requirements/Qualifications: There's "Required Qualifications" and "Preferred Qualifications". We could combine under Requirements heading? The instruction includes Requirements and Qualifications as separate possible headings. We have both required and preferred. We could make a Requirements section for required qualifications, and a Qualifications section for preferred? Or we could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications. Let's do that:

Requirements

with required qualifications list.

Qualifications

with preferred qualifications list. Now Skills: Not explicitly listed; we could skip. Benefits: list includes Paid Time Off, Paid holidays, Medical insurance, Dental insurance, Vision insurance, Short-term and long-term disability, Life insurance, 401(k) plan with immediate vesting, Employee referral program. Also Onsite Perks: Free gym with 24/7 access, Free Electric Vehicle charging, Breakfast and Lunch Café, After hours Grab & Go snacks, Basketball court, Walking paths. Those are perks but could be considered benefits. We'll include them under Benefits. Pay: Base Compensation: $116,000 - $164,000 projected annual base salary range. Bonus: eligible for annual bonus based on individual and company performance. Schedule: Not present, so we omit. Now we need to preserve all substantive info. Also include location: "Location: This position is located onsite in Longmont, CO." Could be placed under About the role as a paragraph? Not a heading. We'll include it as a

maybe under About the role. Also include "Closing Date: October 15th." Could be included under About the role or maybe as a note. We'll keep it. Now we need to remove boilerplate: EEO statement, equal opportunity, etc. Also remove "While we expect to keep the position open through this date, the posting may be extended or closed early based on applicant volume and hiring needs." That's maybe considered boilerplate but it's substantive about closing date? It's about posting flexibility; could be considered boilerplate but it's not EEO. Might keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The closing date note is not exactly those; but it's about posting may be extended; could be considered boilerplate but not explicitly listed. Safer to keep? Might be considered part of posting details. I'd keep it. Now produce HTML. Structure:

About the role

Who We Are Stored Energy Systems (SENS) is an award-winning manufacturer of premium quality power conversion products located in Longmont, CO. In business for over 50 years, SENS is the market leader with a proven track record of providing highly reliable battery chargers, DC power systems, and related products to industrial markets. For more information on our company please see our web site at www.sens-usa.com . View the SENS Product Catalog Summary The Senior Project Manager – PowerCab2 will lead the execution model for PowerCab2 customer projects from commercial handoff through delivery. This role will serve as the operational quarterback for PowerCab2 orders, ensuring that customer commitments are clearly defined, cross-functional owners are aligned, risks are surfaced early, and projects move through Engineering, Production, Supply Chain, Order Management, and Customer Success with discipline and urgency. This is not a passive project-tracking role. The successful candidate must be comfortable driving accountability across functions, challenging unclear answers, escalating blockers, and protecting customer outcomes while maintaining credibility with internal teams. The role requires a blend of project management discipline, customer-facing communication, operational rigor, and the ability to work effectively in a fast-growing, high-change environment. Location: This position is located onsite in Longmont, CO. Closing Date: October 15th. While we expect to keep the position open through this date, the posting may be extended or closed early based on applicant volume and hiring needs.

Then Responsibilities:

Responsibilities

• Lead PowerCab2 customer projects from order acceptance through final shipment and customer delivery.
• Own the current portfolio and project execution rhythm for assigned PowerCab2 orders, including timeline, status, blockers, risks, customer commitments, and internal follow-through.
• Serve as the primary cross-functional coordinator between Sales, Sales Operations, Order Management, Customer Success, Engineering, Production, Supply Chain, Finance, and other required teams.
• Ensure each PowerCab2 project has clear scope, committed delivery expectations, defined owners, and documented handoffs.
• Help build and refine the scalable PowerCab2 execution model, including process flows, swim lanes, handoffs, milestone definitions, escalation points, and ownership rules.
• Support the transition from engineered-to-order work toward configured-to-order execution where appropriate.
• Partner with Engineering and Commercial teams to operationalize PowerCab2 configuration rules, approved options, “Lego block” standards, and quote-to-build requirements.
• Help define how PowerCab2 projects move through standard, repeatable, configurable, and engineered lanes.
• Identify recurring process breakdowns and partner with functional leaders to eliminate root causes.
• Communicate professionally with customer project managers, construction managers, switchgear OEMs, contractors, and internal account owners as needed.
• Proactively identify customer needs, document expectations and desired outcomes early, and hold the customer/project manager accountable to agreed inputs, decisions, and timelines so SENS can operationally deliver the intended customer experience.
• Translate internal project realities into clear, credible customer-facing updates.
• Protect the customer experience by ensuring changes, delays, risks, and decisions are communicated clearly and timely.
• Hold customers accountable when customer-driven changes, late inputs, unclear requirements, or scope changes create schedule or cost risk.
• Balance customer advocacy with operational credibility, ensuring SENS does not make commitments that cannot be supported.
• Drive internal teams toward clear commitments, timely decisions, and early escalation when delivery, scope, or customer commitments are at risk.
• Hold Engineering, Production, Supply Chain, Sales, and other stakeholders accountable to agreed project requirements, timelines, and escalation paths.
• Identify gaps between what was sold, what was ordered, what was engineered, what can be built, and what was promised to the customer.
• Identify recurring process breakdowns