nayel rehman / electrical engineer
for networkocean
offshore power + compute

electrical systems that survive contact with reality

the ocean does not care if it worked on the bench.

NetworkOcean is combining power, compute, cooling, and the harshest deployment environment on earth. I build the same way that challenge demands: own the full system, instrument it, take it outside, and keep fixing it until it works.

why I fit NetworkOcean
Illustration of Nayel wearing a NetworkOcean cap beside floating solar and an offshore data center
candidate visual / 01built for open water
4.0electrical engineering at uiuc
10 mthrough-wall sensing proven in field tests
15+electrical systems built end to end

01 / why networkocean

the company is the system.

Floating solar is only useful when the electrical architecture, cooling, compute, telemetry, and marine operations reinforce one another. That kind of tightly coupled physical system is exactly where I do my best work.

01

full-loop ownership

I move between schematics, PCB layout, sensors, low-voltage power, embedded code, test, and the larger mission instead of stopping at a clean handoff.

02

field proof first

I took WiFind from synchronized RF capture to live trials with four search-and-rescue teams. Hardware becomes real when the environment starts fighting back.

03

fast learning, measured

I built production evaluation infrastructure at Orchard and embedded benchmarks at GMU. I learn quickly because I make performance visible.

02 / closest evidence

I already build past the demo.

NetworkOcean needs engineers who can build quickly without confusing motion for progress. My projects are organized around the same standard: a working system, tested under real constraints, with enough instrumentation to understand failure.

Nayel and teammates testing a waterborne prototype at Albacore's Maritime Hardware Hackathon
Albacore's Maritime Hardware Hackathon Testing a waterborne prototype with my team. Maritime hardware was already a space I wanted to build in.
wifind / deployed sensing hardware

a rescue device that left the lab.

I designed a three-router wireless sensing system to detect breathing and micro-motion through walls, then built the synchronized capture and real-time edge processing needed to use it outside a controlled setup.

Four search-and-rescue teams tested it at ranges up to ten meters. The environment was part of the engineering, not an afterthought.

01architectConnect sensing, power, processing, and interfaces into one dependable system.
02instrumentCapture the signals that expose drift, edge cases, and hidden failure modes.
03validateUse bench tests and field tests to separate confidence from evidence.
04iterateTurn every failure into a shorter path to the next working build.

03 / electrical engineer

useful on day one.

NetworkOcean says deep experience is not required. What matters is agency, rate of learning, and the urge to build what would not otherwise exist. I can bring those traits with real electrical depth behind them.

  • power + boardsAltium and KiCad schematics, PCB layout, component selection, soldering, rework, and board bring-up.
  • sensingRF capture, sensors, data acquisition, signal processing, and embedded hardware integration.
  • testOscilloscopes, circuit debugging, automated validation, failure analysis, and reproducible benchmarks.
  • operationsField trials, operator feedback, technical documentation, and the patience to make hardware dependable.