25 Sep
|
Calance Software
|
Bengaluru
25 Sep
Calance Software
Bengaluru
The programme is already live across multiple global regions with further sites in progress. This is not a greenfield project it is an active, quick-moving delivery programme with real operational complexity. The engineer hired will be joining a small, senior team and will be expected to own problems independently.
WHAT YOU WILL DO
- Onboard, configure, and troubleshoot IoT devices — occupancy sensors, air quality monitors, smart lighting, CCTV, and building-adjacent systems — from initial deployment through to stable operation and data flowing to the cloud platform
- Administer and troubleshoot Linux and Windows servers hosting IoT application services — checking broker services, reading application logs, diagnosing why device data has stopped flowing at the application layer before escalating to network or vendor teams
- Manage IoT device endpoints at the device level — firmware updates, certificate lifecycle management, configuration deployment, and device lifecycle from onboarding through decommission
- Work across networking, security, proxy, firewall, and vendor teams to resolve device connectivity issues — engaging the right team with the right question rather than owning specialist network or security engineering
- Support building migrations — coordinating with facilities engineers and internal teams to onboard devices onto the SD Access fabric, validate end-to-end connectivity, and confirm data is flowing to the cloud dashboard
- Manage security approval processes for IoT device changes — navigating regulated change control, security architecture reviews, and multi-team sign-off workflows
- Maintain technical documentation, asset lifecycle records, and operational runbooks for the IoT device estate
- Support PoC and RFE initiatives for new device categories being evaluated for the programme
- Participate in out-of-hours and weekend work during active building migration periods
- SKILLS & REQUIREMENTS |
- Skill Area | What Is Required | Level | | --- | --- | --- | | IoT Application Layer | Hands-on experience with IoT devices at the application and data layer — not just network connectivity. Understanding of device-to-server-to-cloud communication chains. Candidates must be able to describe what happens on the server side when an IoT device sends data, and how to verify data is flowing end to end. |
- Essential | | MQTT Protocol | Working knowledge of MQTT — publisher/broker/subscriber model, common brokers (Mosquitto, EMQX), how to check whether a broker is running and healthy, and how to verify a device is publishing messages. Port 8883 (encrypted) and 1883 (unencrypted) awareness. This is tested at every interview. |
Essential | | IoT Device Types | Direct experience with occupancy sensors, air quality monitors, smart lighting, CCTV, or similar smart building and connected device environments. Experience with BMS-adjacent systems is a plus but not required. What matters is working with these devices at the configuration and application layer, not just the network layer. | Essential | | IoT Endpoint Management | Managing IoT device fleets at the device level — firmware updates, certificate lifecycle management (installation, expiry, rotation), configuration deployment, and asset lifecycle from onboarding through decommission. Experience with device management platforms (Claroty, AWS IoT Core, Azure IoT Hub, Cisco Catalyst Center) is a plus. | Essential | | Regulated Environment | Experience navigating security approval processes, change control workflows,
and multi-team sign-off in a regulated environment — financial services, government, healthcare, or critical infrastructure. Understanding that getting a device to communicate outbound in a Tier 1 bank involves a structured approval process. | Essential | | Networking Fundamentals | DNS, DHCP, NTP, proxy configuration, firewall awareness, MAC address registration, 802.1X/MAB concepts. Sufficient to engage networking and firewall teams with the right question at the right time. This is not a network engineering role — specialist network depth is not required or expected. | Essential | | Linux Administration | Hands-on Linux administration at the service and application layer — systemctl, journalctl, log file analysis, service troubleshooting, connectivity diagnostics. Ability to diagnose why an application service on a Linux server has stopped receiving device data before escalating to the network team. | Important | | Windows Server | Working knowledge of Windows Server in a mixed environment. The programme includes Windows servers hosting IoT application services. Cross-platform competency is expected — Windows does not need to be a primary specialism. | Important | | Security & Identity | SAML and OIDC — ability to explain what each is, the difference between them, and when each is used. Certificate-based device authentication. This question is asked at every interview for this role. Previous candidates with years of experience have failed it. |
Important | | Scripting & Automation | Python, PowerShell, or Bash for infrastructure automation and device management tasks. Not a scripting specialist role — practical automation capability to reduce manual effort is sufficient. |
Desirable | | Cloud Platforms | AWS or Azure exposure in the context of IoT data pipelines or device management. Understanding of how device data flows from a Linux server through to a cloud platform or dashboard.
📌 IoT / OT Infrastructure Engineer Hybrid at Bangalore (Bengaluru)
🏢 Calance Software
📍 Bengaluru