Electric Hydrogen’s mission is to decarbonize our world! Our outstanding people deliver creative decarbonization energy solutions to our customers.

Electric Hydrogen builds and delivers the world's most powerful electrolyzers. One network estate carries our corporate traffic, our engineering workloads, our manufacturing floor, and our test benches, and it gets to fail at none of them.

We are hiring the person who owns that estate. Not a member of a network team. The owner.

What you would be working on

Our enterprise network is a settled, segmented Fortinet environment across corporate offices, a manufacturing facility, and test engineering. The routing is not the hard part. The hard part arrives when a piece of production or test equipment needs something your standards do not permit, and both the standard and the equipment have a legitimate claim.

In your first year:

Own the enterprise network end to end: campus, WAN, wireless, VPN, and data center
Implement and operate firewall policy across zones, working with our Cybersecurity Engineer, and bring the network perspective to the argument about what is permitted to talk to what
Support manufacturing and test engineering as they add equipment, much of it statically addressed, unpatchable, internet-restricted, and inflexible about what it needs
Maintain hybrid connectivity to Azure and AWS, and the VMware networking underneath it
Keep segmentation intact as the business grows, which mostly means finding accommodations rather than granting exceptions
Establish the standards, diagrams, and change practices that a second network engineer can be hired into

You report to the Director of IT and work alongside Systems Engineering, Cybersecurity, Cloud Infrastructure, Manufacturing, and Test Engineering.

To be clear about scope, because it matters at this level:

You own the enterprise network. Architecture, segmentation design, and operations are yours, and you are the final escalation point for them
Security is shared. Our Cybersecurity Engineer co-owns security standards, policy direction, and review. You implement and operate the network controls that carry them out, you are accountable for those working in practice, and your read on what the network can and should do carries real weight in those decisions
Industrial network design for the product belongs to our controls engineering team. You own the enterprise network and the accommodations it makes for internal OT, and you partner with controls at that boundary

What we need

Eight or more years in enterprise network engineering
A proven track record supporting internal OT: manufacturing, test, lab, or production equipment on a network you were responsible for. This is the requirement that distinguishes this role from a corporate networking job, and we will ask you about it in detail
A period where a multi-site estate was genuinely yours. Primary owner, final escalation point, accountable for the design and not only the tickets
Deep hands-on ownership of an enterprise firewall and switching platform at policy and architecture level. We run Fortinet, and familiarity helps, but we are more interested in whether you have owned a platform properly than in which one it was. We expect a strong engineer to be reasonably vendor-agnostic
VLAN and Layer 3 design, routing, and firewall policy between zones under real constraints
VMware networking, and hybrid connectivity to at least one major cloud
Bachelor's degree in a related field, or equivalent experience

What would set you apart

You have kept a segmented network intact while a manufacturing or test function grew fast, and can describe a compromise you were not happy about
You have been the only network engineer somewhere, and have a view on what that requires beyond technical skill
You have worked alongside a dedicated security function and can describe a firewall or access decision where you and security disagreed, and how it got resolved
You have worked closely with controls or automation engineers and know where the IT and OT boundary usually gets argued about