🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
N-iX is looking for Lead/Senior Software Engineer with Protocols to join our team. In this role, you will design real-time telemetry pipelines, integrate with datacenter power and compute systems, and implement control and optimization logic that dynamically adjusts workloads based on grid and infrastructure conditions. This role bridges IT and OT environments - turning raw operational data into safe, reliable, production-grade control systems. As an early engineering hire, you’ll shape system architecture, own projects end-to-end, and work closely across teams to translate real-world constraints into scalable software. Key Responsibilities Build software modules that interact with datacenters, on-site industrial power systems and the electrical grid Architect and implement data ingest pipelines that collect, normalize, and persist high-frequency telemetry from power meters, PDUs, UPS systems, cooling infrastructure, and compute hardware. Design fault-tolerant integration layers between IT systems (cloud APIs, databases, orchestration platforms) and OT systems, handling protocol translation and data model definition and mapping. Ensure high safety, reliability, and correctness when interacting with real-world energy assets and critical facilities — including behavior in degraded, disconnected, or split-brain network states. Collaborate across teams to deliver end-to-end solutions from edge device to control plane. Requirements 7+ years of software engineering experience, with strong proficiency in Python or C++ Hands-on experience building telemetry ingest pipelines or distributed systems that handle high-volume, time-series data. Familiarity with at least one async messaging system: Kafka, RabbitMQ or equivalent Exposure to IT or OT systems (SCADA, EMS, BMS, DCIM) and understanding of how data flows between them. Experience with Kubernetes. Direct experience with industrial telemetry protocols : Modbus TCP/RTU, DNP3, OPC-UA, BACnet, or SNMP. English: At least Upper-intermediate Will be a plus Familiarity with time-series databases (InfluxDB, TimescaleDB, Prometheus) or industrial historian platforms (AVEVA PI / OSIsoft, Ignition). Experience with containerized deployments, or HPC job scheduling in datacenter environments. Experience with Rust, Go or C/C++. We offer*: Flexible working format - remote, office-based or flexible A competitive salary and good compensation package Personalized career growth Professional development tools (mentorship program, tech talks and trainings, centers of excellence, and more) Active tech communities with regular knowledge sharing Education reimbursement Memorable anniversary presents Corporate events and team buildings Other location-specific benefits *not applicable for freelancers
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.