Engineering Operations Lead - Configuration Management & Tools

At REGENT, we’re on a mission to revolutionize regional transportation between coastal cities. We're not just building vehicles, we're creating a new category of transportation: the Seaglider. These groundbreaking wing-in-ground-effect craft travel just above the water’s surface, combining the speed of an airplane with the low operating costs of a boat. Capable of 180 miles at 180 mph on today's battery tech (and up to 400 miles with next-gen batteries), Seagliders will unlock fast, affordable, and sustainable coastal transit for passengers and cargo - connecting cities, islands, and communities like never before.

Backed by leading investors and powered by a team of passionate, forward-thinking engineers, builders, and operators, we’re now scaling from a breakthrough prototype to full production - and building the team to make it happen.

Role Overview Every part on a Seaglider has a story: who designed it, what revision was approved, what changed and why, and which one the shop floor built. As REGENT grows from prototype to certified production and moves our Viceroy program through certification, that story has to be true, complete, and available to everyone who needs it — engineers, manufacturing, and the regulators who will certify the vehicle.

We're hiring an Engineering Operations Lead to build the configuration management discipline that scales with us, and to own the engineering toolchain that enforces it.

You'll define and run REGENT's configuration and change management process: baselines, release workflows, the change control board, and the record of what is released and why — built for a growing engineering organization and for the regulatory path ahead. You'll own the hardware engineering toolchain — Siemens Teamcenter (with NX and Capital), and our Jira/Confluence standards — administering it, setting the rules, and keeping it a system engineers trust rather than a hurdle they route around.

And you'll define how released drawings and bills of materials flow from PLM into our manufacturing execution system, so Manufacturing builds to the right revision from a single source of truth.

Success looks like a Viceroy with a defensible design baseline, a change process that reaches effectivity decisions in days rather than weeks, a Teamcenter environment run as a service to the engineering team, and a shop floor that pulls from PLM. It looks like the Chief Engineer, Manufacturing, and Certification all agreeing on what "released" means — because you wrote it down and built the tools to enforce it.

This is a builder's role. You'll establish the CM function at REGENT with direct partnership from the VP of Programs, the Chief Engineer, and the CTO's engineering-lifecycle team, and shape it for the team we're becoming. If you have lived in the seam between engineering and manufacturing, if you can hold a release on procedure and then help the engineer get it through the same afternoon, and if you want to shape how a new class of vehicle gets designed, changed, and built — we want to hear from you.

What You'll DoOwn configuration management for REGENT's programs. Author and maintain the Configuration Management Plan, define HW/SW/System baselines, and act as Release Manager for the Viceroy program — the procedural authority on what is released, in-work, or obsolete.

Stand up and run the change process. Write the Engineering Change Process (ECR impact assessment CCB ECO ECN), charter and run the Change Control Board across Engineering, Manufacturing, Supply Chain, and Certification, and drive effectivity decisions.

Own the hardware engineering toolchain. Administer Siemens Teamcenter (Active Workspace, workflows, roles, attributes, release statuses) with NX and Capital integrations; own…