> Markdown version of [/jobs/ext/3967282-senior-manager-software-engineering](https://www.wearedevelopers.com/jobs/ext/3967282-senior-manager-software-engineering). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Manager, Software Engineering - **Company:** Helion LLC - **Location:** Everett, WA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Data Analysis, Systems Engineering, Data Infrastructure, Data Systems, Firmware, Software Construction, Software Engineering, Enterprise Data Management, Computer Networking Systems, Enterprise Software Applications, Large Language Models, Data Layers, Information Technology, Production Code, Data Management - **Published:** October 27, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-manager-software-engineering-everett-wa--d18fbfe6-8468-4236-be80-504bd4877c3a ## About the Role Software Engineering, Electricity, Power Plant, Plasma, Venture Capital, Prototyping, Data Management, Computer Firmware, Automation, Network Systems, * 10+ years building software for complex hardware systems. * 3+ years leading a multidisciplinary software team that includes firmware or embedded engineers and application engineers, across a range of seniority. * Depth in real-time, embedded, or control software for physical systems to hold technical direction with experienced engineers. Not necessarily writing production code, but able to evaluate tradeoffs and challenge designs. * The ability to recognize familiar engineering problems amidst unfamiliar applications. Fusion is new; time synchronization, fault handling, high-rate data capture, and hardware-in-the-loop testing are not. * Experience leading a team that builds data systems or internal tools for customers who are not engineers and prioritizing that work against product delivery. * A track record of hiring and growing engineers and engineering leaders over time. * The ability to work across disciplinary boundaries with electrical engineers, mechanical engineers, systems engineers, machine operators, and scientists, and to set expectations with peers you do not manage. * A degree in Computer Science, Electrical Engineering, or a related field, or equivalent practical experience. #LI-Onsite #LI-RR1 ## Description * Plant Software builds the software that runs the machine. Firmware and embedded control on the devices that command and measure each pulse, supervisory automation that sequences the plant as a system, the real-time network and timing infrastructure that ties thousands of edge devices together, the infrastructure and cybersecurity those systems depend on, and the pipelines that capture pulse data at the source. * Enterprise Software builds the data platform and internal applications the company runs on. The pipelines and storage that make per-pulse data usable for science and operations from single pulses to hundreds of millions, and the tools that machine operations, manufacturing, legal, inventory, and business operations teams use every day. What You Will Be Doing * Own the plant software stack across embedded, supervisory, networking, infrastructure, and data layers, and the enterprise data platform and application roadmap. Software ships against hardware on a shared schedule; the data platform ships against a machine that will run many pulses a day. You own the plan, the risks, and the result. * Our processes, review gates, and planning norms were designed for hardware. You will set how software plans, reviews, tests, deploys, responds to faults, and hands off to operations, fitted to a first-of-a-kind plant rather than imported from a previous employer: light enough to move at our pace, rigorous enough that the machine is safe to run. * Electrical, mechanical, systems, fuel cycle, operations, and science teams all depend on software and have their own expectations of it. You will set and hold clear expectations for how those groups engage the software teams, how priorities are negotiated, and how a shared-service team says no, without formal authority over any of them. * Hire, develop, and support engineers and leaders across both teams. Technical insight is one way to support them; removing a dependency, securing a resource, or asking the question that reframes a stuck problem are others. * Define and implement practices on the use of LLM-based tools and agents, in engineering workflows and beyond them: data analysis, process automation, and scientific discovery. Identify when to buy, what to build, and how to pursue in-house tools when there's a case for them.