About Boon

Boon is a wellness-first water purification brand.

Tagline: Water For Every You.

Boon Homie is a connected purifier — commercial-grade filtration, mineral life modes (Daily, Active, Brew), and WaterAI, which makes performance visible and maintenance predictable. Purification you can trust. Enhancement you can feel. Proof you can see.

The proof layer is software. Every filter-health reading, every smart alert, every "your cartridge has three weeks left" notification runs through the platform you'd be building.

The Role

You'll own backend services that connect thousands of purifiers in real homes to the Boon app and to our internal fleet tooling. Device telemetry in, intelligence out.

This is a hands-on IC role with real ownership. You'll work across the seam where firmware meets cloud meets app — a place where the interesting problems live and where clean abstractions matter most.

What You'll Do

Design, build, and run backend services that ingest, store, and act on high-volume device telemetry from a growing fleet

Own device connectivity end to end: provisioning, secure onboarding, device shadows, command-and-control, and OTA update delivery

Build the APIs powering the Boon mobile app — life modes, filter health, usage history, alerts, subscriptions, and service requests

Turn raw sensor streams into the signals WaterAI needs for predictive maintenance and anomaly detection, in partnership with our data team

Build internal fleet tooling so support and service teams can see device state, diagnose issues remotely, and act before a customer notices anything

Integrate the commerce and ownership stack: filter replenishment, payments, warranty, CRM, and notification channels

Instrument everything. Latency, delivery rates, dropped connections, alert accuracy — if we can't measure it, we can't promise it





Work closely with firmware and mobile engineers to define protocols and contracts that hold up over years of field deployment

Participate in on-call for the services you own, and write the runbooks that make on-call boring

What You'll Bring

Core

3–6 years building and operating production backend systems

Robust in at least one of Node.js/TypeScript, Python, Go, or Java, and comfortable reading the others

Solid grasp of distributed systems fundamentals: queues, idempotency, retries, eventual consistency, backpressure

Relational and NoSQL data modelling (PostgreSQL, DynamoDB or similar), plus caching with Redis

API design that other teams enjoy consuming — REST or GraphQL, versioned thoughtfully

IoT

Hands-on with MQTT (or equivalent device protocols) and the realities of intermittent, low-bandwidth, unreliable connections

Device lifecycle experience: provisioning, certificate-based auth, device twins/shadows, fleet grouping, OTA firmware rollouts

Time-series telemetry at scale — ingestion, downsampling, retention strategy

Understanding that a device in someone's kitchen behaves nothing like a service in a data centre

AWS

Production experience across a meaningful slice of: IoT Core, Lambda, ECS/EKS, SQS/SNS/EventBridge, Kinesis, Timestream, RDS, DynamoDB, S3, API Gateway, CloudWatch

Infrastructure as code (Terraform or CDK) and CI/CD pipelines you've actually maintained

IAM least-privilege, secrets management,



and cost awareness — you know what your architecture costs to run

Nice to Have

Worked on a connected hardware product that shipped to consumers

Wi-Fi/BLE device onboarding flows and the UX failure modes that come with them

Edge compute, local buffering, or offline-first sync

Supporting ML pipelines in production — feature stores, model serving, drift monitoring

D2C stack integrations: Shopify, Razorpay, subscription billing, WhatsApp Business API, FCM/APNs

Kafka or similar event streaming

Early-stage experience where you set the standards rather than inherited them

What Success Looks Like

First 30 days — You've shipped to production, understand the device-to-cloud path end to end, and can explain how a single sensor reading becomes an alert in someone's hand.

First 90 days — You own at least one core service outright. You've closed a reliability or latency gap that was bothering the team.

First year — The fleet has grown severalfold and the platform absorbed it without drama. Your work is a reason people trust their Boon.

How We Work

Small team, real ownership, short distance between an idea and a device in someone's home

Hardware sets the pace. Firmware, app, and backend ship together, so we plan together

We write things down. Design docs before big builds, runbooks after

Proactive not reactive — we'd rather predict a failure than respond to one. That principle sits in the product, and it sits in how we run engineering

Interview Process

Intro call with the hiring manager (30 min)

Technical deep-dive on your past work (60 min)

System design — connected device platform (60 min)

Coding and problem solving (60 min)

Founder conversation (30 min)

We aim to close the loop within two weeks.

📌 Software Development Engineer (Gurugram)
🏢 Boon
📍 Gurugram