Principal Solution Engineer

<div class="content-intro"><p>ON.energy<span class="Apple-converted-space">&nbsp;</span>is setting the standard for large load interconnection. ON’s patented AI UPS™ is a medium-voltage UPS that serves as a firewall, protecting the data center from the grid, and the grid from the data center.&nbsp;With multiple gigawatts currently under construction, we are enabling grid-safe data centers.&nbsp;</p></div><p>&nbsp;</p> <p><strong>Principal Solution Engineer</strong></p> <p><strong>Location: Tysons, VA OR Houston, TX (Hybrid - 3 days in office) Preferred; Remote Considered&nbsp;</strong></p> <p>&nbsp;</p> <p><strong>Role Overview</strong></p> <p>The Principal Solution Engineer serves as the technical expert between Sales Engineering, Project Engineering, and Product Engineering. This role owns the intake, assessment, and resolution of all sales engineering and customer driven technical requests, driving each to conclusion. Where a request requires a change to an existing product or system baseline, this role defines the change impact and leads it through the formal Engineering Change Management (ECM) process. Success requires strong system level thinking across electrical, mechanical, and software (EMS) domains, along with the communication and interpersonal skills to align stakeholders across Sales, Engineering, and Product.</p> <p>&nbsp;</p> <p><strong>Key Responsibilities</strong></p> <p>1. Sales &amp; Customer Request Ownership</p> <ul> <li>Sales Interface: Serve as the primary technical point of contact between Sales Engineering and the Engineering organization for all incoming customer and sales driven requests.</li> <li>Assessment: Own and drive the assessment workflow, evaluate each request, determine disposition (proceed, reject, or route for further engineering review), and ensure timely, well documented decisions.</li> <li>Resolution Ownership: Coordinate with Sales and Project Engineering to resolve requests that do not require a formal change but still require cross functional alignment and follow through, driving each to conclusion.</li> </ul> <p>2. Engineering Change Management</p> <ul> <li>Change Impact Definition: For requests requiring a product or system change, define the scope and impact of the change across affected subsystems before it enters formal review.</li> <li>ECM Leadership: Lead approved changes through the Engineering Change Management (ECM) process to closure, ensuring documentation, approvals, and implementation stay on track.</li> <li>Product Alignment: Partner with the Product team to ensure customer and sales requests are reflected in product roadmap and configuration decisions