Security / IoT Deployment Engineer

Rimward is building the decision layer for physical security.

We start with remote outdoor sites such as utility-scale solar, where recurring intrusion, false alarms, and limited on-site presence make existing monitoring hard to operate well. Most serious sites already have cameras, procedures, and supervision teams. The missing piece is reliable signal.

Our goal is to turn existing camera networks into operator-ready alerts: fewer false positives, faster video verification, better evidence, and a tighter path from detection to response.

We care about field reality more than demo quality.

That means working on products that respect messy deployments: mixed camera quality, outdoor conditions, patchy connectivity, constrained infrastructure, and real operator workflows. We are opinionated, hands-on, and demanding about usefulness. A system that looks impressive but does not help someone make a better decision is not good enough.

We work in person in Paris while we sharpen product-market fit.

Rimward builds software that turns existing camera infrastructure into low-noise, operator-ready intrusion alerts for remote outdoor industrial sites.

The company is led by F-G Fernandez, a repeat founder with a strong computer vision background, who previously built and deployed vision systems in the field with Pyronear. We are now applying that same deployment-first mindset to physical security: making existing camera networks actually useful for fast, reliable intrusion detection on real sites.

We are looking for a deployment-focused engineer who can make pilots go live in the real world. This role sits at the intersection of edge compute, CCTV/video systems, connectivity, customer IT, and field operations. You will work directly with customers to scope, deploy, debug, and harden on-prem or hybrid setups.

This is not a pure support role and not a pure software role. We want someone who is comfortable going from architecture discussion to deployment checklist to technical troubleshooting to internal product feedback.

Within your first 30 days, you should be able to take ownership of a pilot deployment plan: camera access, network constraints, edge hardware, connectivity, and validation steps. Within 60 days, you should be able to run a deployment end to end with customer stakeholders and turn field issues into concrete fixes or product requirements. Within 90 days, you should be one of the people we trust most to make a difficult site go live under real operational constraints.

You should enjoy messy environments: mixed camera fleets, weak connectivity, unclear documentation, customer IT constraints, and deployment conditions that do not look like clean product diagrams. A big part of the job is making these environments reliable enough for a serious security product to operate.

Rimward sits at the intersection of computer vision, video systems, edge inference, and operator workflow design.

The core technical challenge is not just detecting events in video. It is producing signal that stays useful under real deployment constraints: outdoor scenes, variable lighting, weather, noisy backgrounds, uneven camera quality, and low-connectivity environments. Low false positives matter because the product only works if operators keep trusting the alerts.

Our stack is pragmatic and software-heavy: Python for backend and ML, modern video/data pipelines, and lightweight product surfaces for alert review and operations. We work across model performance, deployment, evidence generation, and infrastructure that can run both in the cloud and close to the site when needed.

1. Intro call (30 min)
2. Systems deep dive (60 min)
3. AI-assisted take-home / live exercise (2–3 hours max)
4. Execution interview (60 min)
5. Founder final (45 min)