We have shipped more than 50,000 sensors. They sit in apartments, villas and utility networks across Europe, most of them on batteries and most of them behind someone else's WiFi. We're hiring the engineer who owns the software that keeps them running.
üåè About Quandify
We make hardware for water leak detection and water monitoring, and the platform behind it. Our sensors catch leaks early, and our CubicSecure valve can shut the water off automatically. Customers have cut their water use by up to 30%, and our devices prevent water damage in homes and buildings across Europe.
üì° The role
The fleet grows every week through insurers, utilities and installation partners. You own the backend and cloud software that runs it: provisioning, firmware rollouts, telemetry ingestion, monitoring, and the internal tools our support and partner teams use every day. You build these systems and you run them in production.
Our backend developers own the product side: the app API, accounts, properties and notifications. You own the fleet underneath. The two areas overlap, but the split is clear from your first week.
üíª What you'll do
Build backend services for device provisioning, lifecycle management and fleet configuration.
Own the staged OTA pipeline, from targeted rollout through monitoring to rollback.
Build alerting and dashboards that show us a device is in trouble before the customer notices, whether the cause is connectivity, bad data or a dying battery.
Scale telemetry ingestion and time series storage as the fleet grows.
Automate operational work so the fleet can grow faster than the team.
Build fleet reporting and APIs for our partners, together with the rest of engineering.
üß© What makes it interesting
A Water Grip runs on two AA batteries and reports once an hour. You can't poll it or ask it to retry, so your design decisions show up directly in battery life.
A CubicSecure is a valve that shuts off the water in someone's home. A false alarm leaves a family without water and a missed one floods the floor, so the platform has to know the moment it acts and why.
A CubicDetector sits on the floor for months without anything happening. When it finally gets wet, that one message has to get through immediately.
When a firmware rollout goes wrong, fixing it can mean sending an installer out in a van.
Our devices live behind consumer routers. When one goes offline, the cause is usually the customer's WiFi, and telling that apart from a platform problem across tens of thousands of devices is a hard data problem.
üß∞ Your skillset
Strong backend development in TypeScript/Node or Java. Today's platform is TypeScript on Node 20, and the next generation is Java 21 on Quarkus. You'll work in both, so depth matters more to us than which one you know now.
Solid GCP experience: Cloud Functions, Pub/Sub, Cloud SQL, Secret Manager and GKE.
PostgreSQL, plus a time series database such as InfluxDB or TimescaleDB.
Hands-on experience with Grafana and Prometheus, and good judgement about what deserves an alert.
Terraform, K8s and GitLab CI.
Experience with MQTT or device management at scale is a strong plus. We run EMQX for our WiFi devices, and our LoRaWAN devices come in through partner network servers.
üéÅ What we offer
Ownership of a critical part of the platform, from design to production.
A small, senior engineering team where your work reaches production the same week.
Hardware, firmware, backend, app and commercial in the same building, so you can walk over and ask.
üìç Location
This role is onsite at our office in Bromma, Stockholm. We move faster when the people building the platform sit next to the people making the hardware, so we're only considering candidates who can work from our office. You need an existing right to work in Sweden, as we can't sponsor work permits for this role.
ü§î Not a 100% match?
Few people have done all of this before, because few companies have this mix of problems. If you've done most of it and want to learn the rest, apply anyway.
