
Rimward
Low-false-positive intrusion detection for remote outdoor sites
What Rimward does
Rimward helps operators of solar farms and other remote outdoor infrastructure detect intrusions from existing camera networks. We turn existing CCTV into operator-ready alerts with video verification, so security teams can reduce false alarms, respond faster, and avoid heavy hardware retrofits. We are focused on sites where recurring theft, perimeter intrusion, and low staffing make traditional monitoring noisy and operationally weak. Our approach is software-heavy, field-oriented, and built to work with real site constraints.
2 open roles
What the role involves
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: building the software and systems layer that makes existing camera networks actually usable for fast, reliable intrusion detection on real sites. We are looking for a platform engineer to help turn early pilots into a reliable product and internal platform. You will work on the backend and systems layer that make deployments repeatable: alerting pipelines, integrations, auth, observability, fleet management, admin tooling, and product infrastructure. This is not a generic backend role. The product has to work across messy field realities: remote sites, uneven connectivity, mixed hardware environments, customer IT constraints, and workflows that bridge edge devices, video pipelines, cloud services, and human operators. A bug is not just a failed request. It can mean a broken deployment on a live site, poor operator trust, or a field issue that is expensive to diagnose. Within your first 30 days, you should be able to understand the current deployment architecture, backend stack, and operational bottlenecks across pilots. Within 60 days, you should be shipping improvements that make deployments more repeatable and the system easier to operate internally. Within 90 days, you should own meaningful parts of the platform: reliability of alerting flows, internal tooling, deployment hygiene, and the productization of patterns discovered in the field. You should enjoy building robust systems, reducing operational friction, and turning messy real-world constraints into clean product and infrastructure decisions. You should also be comfortable working with AI coding tools, while being strong enough to review, correct, and shape the output rather than just accept generated code.
What the role involves
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.
Roles are as last read from the company’s own listings. Openings close without notice — check the date on the listing before you spend an evening on the application.
Check the company’s own careers page — linked at the top — before a job board. A role appears there first, sometimes weeks before it is syndicated anywhere else.
Questions and experiences
Nobody has asked anything about Rimward yet. If you have interviewed here, what you know is worth more to the next person than anything on the rest of this page.
Company facts compiled from public sources and last refreshed 9 September 2026. Details change; treat the company’s own site as the authority.