Build the machine that ends the power wait.

Three open engineering roles across hardware, controls, and software.

Open roles

Senior Power Electronics Engineer, Inverters

Own the inverter that turns motorsport-grade combustion into clean, grid-quality power.

The DOR (Distributed On-demand Resource) is a new class of on-site power: a 200 kW multi-fuel distributed power platform delivering permanent, active grid capacity, deployed rapidly instead of the 7-10+ years a grid upgrade takes. The part that makes its output usable, the grid-forming inverter and active rectifier, is yours to own. You will build the power-electronics subsystem from the ground up: the conversion stage that takes raw engine output and delivers clean power across standalone, grid-tied, and microgrid modes, with sub-5-second ramp and black-start capability.

What you will do

  • Architect and design the DOR power-electronics subsystem end to end: DC-AC conversion, the grid-forming inverter and active rectifier, magnetics, gate drives, and the DC link.
  • Develop control loops for grid-forming, grid-following, and seamless mode transitions, hitting sub-5-second ramp and black-start without an external grid reference.
  • Design the magnetics and power stage for high power density, since the inverter has to fit a unit at ~90 kVA/m3 (200 kW, 700 kg, 15 sq ft).
  • Run the full hardware loop: schematic, simulation, board bring-up, thermal and EMC validation, and iteration on real engine output.
  • Take inverter hardware from prototype through certification and into pre-series production, working with our validation partner and Bosch as ECU and components supplier.
  • Characterize efficiency, harmonics, and transient response to defend the 42% variable-load fuel-to-electrical claim.
  • Work directly with the engine, controls, and Power OS teams so the power electronics and software behave as one system across fleet deployments.

Must have

  • 7+ years designing power-electronics hardware, with deep hands-on inverter design experience, not just simulation or systems-level oversight.
  • Production pedigree from a leading commercial inverter manufacturer (string or solar-grade), having shipped inverter hardware that runs in the field at scale.
  • Grid-forming inverter expertise: topologies, droop and virtual-synchronous-machine control, and the control theory behind stable standalone and microgrid operation.
  • Strong command of DC-AC conversion, power magnetics design, gate-drive and DC-link design, and switching-device selection (SiC or IGBT).
  • Demonstrated ownership of EMC: meeting conducted and radiated limits and getting hardware through certification, not handing it off.
  • Proven track record taking an inverter from design through validation to production, including the failure analysis and design-for-manufacturing work in between.

Nice to have

  • Black-start and seamless grid-tied to islanded transitions in a shipping product.
  • Pairing inverters with rotating generation (gensets) rather than only solar PV or batteries.
  • Familiarity with UL, CE, and IEEE 1547 grid-interconnection requirements.
  • Firmware or DSP control implementation experience (C, real-time control), so you can prototype loops yourself.

System Architect, DOR Control Stack

Define the software that defines the hardware: the control architecture for 200 kW of rapidly deployed on-site power.

The DOR deploys rapidly, from site survey to energized, against the 7-10+ years a utility grid upgrade takes. The software is what makes that defensible: it sits between the Bosch ECU, the grid-forming active rectifier, and our proprietary Power OS, and it decides what compute, sensors, and controllers every engine carries. As System Architect you own that boundary. Your architecture drives the bill of materials, the real-time control loop, and how a fleet of units coordinates in the field.

What you will do

  • Own the on-unit software architecture end to end (the control stack that runs alongside the Bosch ECU, the grid-forming active rectifier control, and Power OS) and specify the compute, sensors, controllers, and electronics each unit carries as a direct output of those decisions.
  • Define the real-time control architecture: loop rates, latency budgets, and failure modes for grid-forming inverter control, multi-fuel combustion management, and load following down to the ramp.
  • Design the telemetry and data architecture that feeds Power OS: what gets measured on each engine, at what rate, and how it moves off-unit for predictive maintenance, demand forecasting, and load optimization.
  • Architect fleet-level coordination so multiple DOR units behave as one controllable resource behind the meter, including grid-forming handoff and load sharing.
  • Set the hardware-software interface contracts with the German hardware team and Bosch: partition functions across embedded targets, fix the BOM implications early, and keep cost and reliability inside spec.
  • Build the safety-critical control approach for a combustion-plus-power-electronics system and carry it through UL, EPA, and CE validation with BTD.
  • Establish the standards the rest of engineering builds against: real-time OS choice, comms buses, fault handling, OTA update path, and the test rigs that prove all of it before pilot.

Must have

  • 10+ years in embedded or distributed real-time systems, with direct ownership of a shipped hardware-software co-designed product, not architecture in the abstract.
  • Demonstrated hardware-software co-design: you have made the call on what compute and sensors a physical product carries and lived with the BOM and reliability consequences.
  • Deep real-time control experience (control loops, latency budgets, deterministic scheduling) on systems where missing a deadline has physical consequences.
  • Safety-critical or industrial control background (power electronics, automotive, motorsport, energy, aerospace, or comparable), including working through a formal validation or certification process.
  • Fluency at the embedded layer: RTOS, microcontrollers and SoCs, comms buses (CAN and similar), and integrating with a supplier ECU rather than owning every line of firmware.
  • Telemetry and data architecture for fielded hardware: defining what to measure, moving it reliably off constrained devices, and designing for predictive maintenance and fleet analytics.

Nice to have

  • Grid-forming inverters, active rectifiers, or power-electronics control experience.
  • Combustion engine controls, or working directly alongside an ECU supplier such as Bosch.
  • Fleet or distributed-energy coordination, making many units act as one controllable resource.
  • OTA update, edge compute, or device-fleet software at scale in the field.

Full-Stack Engineer, Power OS

Build the brains and the screen behind every DOR unit in the field.

A DOR unit is 200 kW of permanent on-site power, deployed rapidly instead of the 7-10+ years a grid upgrade takes. But a fleet of DOR units across dozens of customer sites is something more: a managed, anticipatory infrastructure asset. Power OS is the software layer that makes it one, and this role builds both the algorithms that orchestrate paralleled units and the dashboards customers open every morning. You own the path from raw sensor signature to the number a fleet operator acts on.

What you will do

  • Build and ship the customer-facing dashboards that turn fleet telemetry into the metrics operators actually want: uptime, cost per kWh, emissions per kWh, demand-charge avoidance, and payback. Think high data density, dark mode, real-time, and clear under pressure.
  • Write the load-management and load-sharing logic that coordinates multiple paralleled DOR units behind the meter: deciding how many units to bring online, how hard to run each one, and how the remaining units ramp to fill the gap when one trips.
  • Build the fuel efficiency and consumption tracking that holds the DOR to its 42% variable-load fuel-to-electrical claim in the field, surfacing per-unit and per-site BSFC, load factor, and real cost per kWh against the customer's contracted fuel price.
  • Design and operate the backend pipelines that ingest each unit's full sensor stream (vibration, temperature, pressure, electrical harmonics) at fleet scale, and keep it queryable for both live dispatch and historical analysis.
  • Turn the predictive-maintenance and load-forecasting models into production services: per-machine baselines, fault detection before failure, and forecasts that refresh on a 15-minute cadence and drive dispatch.
  • Own data visualization end to end (KPI tiles, live-updating charts, the composite site score) so a fleet operator can see where to look first and an executive can see how a site is performing from the same screen.
  • Work directly with the hardware and controls team to define what the units report, how often, and in what shape, so the telemetry contract serves the software instead of fighting it.

Must have

  • Genuine full-stack range: you can build a production React and TypeScript dashboard with real-time data visualization and also write the backend services and data pipelines feeding it.
  • Hands-on experience with time-series data at scale: ingesting, storing, downsampling, and querying high-frequency sensor or telemetry streams without the system falling over as the fleet grows.
  • You have shipped data visualization that holds up under real operational use: live charts, dense tables, and KPI views that stay readable and fast when the numbers are moving and the stakes are real.
  • Comfort writing optimization or control logic over streaming data (load following, forecasting, anomaly and drift detection, or scheduling) and reasoning about correctness when the inputs are noisy.
  • You design for the operator, not the demo. You can take an ambiguous question about whether a site is healthy and turn it into a defensible metric and a screen someone trusts at 3 a.m.
  • Strong engineering fundamentals: you write maintainable code, instrument what you ship, and can debug a data discrepancy across the full stack from sensor to pixel.

Nice to have

  • Background in energy, industrial IoT, fleet telemetry, EV charging, or SCADA and grid systems, anywhere machine data had to become an operational decision.
  • Forecasting or ML in production (load forecasting, predictive maintenance, time-series anomaly detection) as a service something depends on, not a notebook.
  • You have built a real-time operations or monitoring product where uptime and latency were features, not afterthoughts.
  • An eye for industrial UI: dense, technical dashboards that engineers and executives both actually use.

Do not see your exact role but think you can build a core part of this system? Apply and tell us where you fit.

Apply

Apply to Immedia Power

Send us your details and CV. We read every application and reply to strong fits within a few business days.

Engineer walking toward a DOR unit as its service door opens in a bright workshop