Associate IoT Engineer (Part-Time), Mahindra World City, Jaipur
There's a part-time Associate IoT Engineer role open in Mahindra World City, paying up to ₹51,000 a month for on-site work. If you've spent time building or testing connected devices, sensors talking to a cloud dashboard, a prototype that streams data over MQTT, this is the kind of team that would put that experience to real use.
The work sits between hardware and software: firmware running on physical devices, sensors feeding data to useful destinations, and the connectivity layer tying it all together. It's a role for someone who likes debugging a circuit in the morning and chasing a flaky MQTT connection in the afternoon.
Most of what this team builds ends up deployed somewhere physical, a facility, a piece of equipment, an environment being monitored, rather than staying in a lab indefinitely. That means the hardware side of decisions carries real weight: a firmware update that works fine on the bench needs to also survive a device that's been running unattended for months in conditions nobody fully controls.
Day-to-day work
- Design and test firmware for IoT devices and embedded hardware
- Debug circuit-level and system-level issues, from a misbehaving sensor to a device that won't reconnect after a power cycle
- Implement and troubleshoot MQTT-based communication between devices and cloud platforms
- Work with sensor integration, calibration, and data validation before readings get trusted downstream
- Document technical specifications clearly enough that another engineer could pick up the work without a walkthrough
A lot of the debugging here isn't purely software or purely hardware; it's figuring out which side of that line the actual problem lives on. A sensor reading that looks wrong could be due to a bad calibration, a loose connection, or a bug in how the data is parsed on the receiving end, and sorting that out quickly is most of the job.
Documentation matters more than it might seem at first. A device deployed in the field months from now, with a problem showing up only through unusual sensor readings, needs someone able to trace back through specs and notes to understand what was actually built and why certain decisions got made. Sloppy documentation today makes debugging much harder for someone later.
What the role is looking for
The degree expected here is a four-year program in a hardware-focused discipline; electronics or electrical engineering both fit, since the day-to-day work leans heavily on physical systems rather than pure software. One year of relevant, practical background is the bar, and the hiring team weighs a candidate who's actually prototyped a working device or debugged a live circuit board more heavily than one who's only studied the theory behind embedded programming.
The electronics-specific degree requirement is worth flagging, since general computer science backgrounds without hardware exposure tend to struggle with the circuit-level debugging this role involves day-to-day. It's not a snobbery thing; it's that the two skill sets genuinely don't overlap as much as people expect going in.
Naukri Mitra has seen steady interest in IoT roles outside Jaipur over the past year, and part-time positions like this one tend to draw candidates juggling a side project, further study, or another part-time commitment alongside their work.
Skills that matter
- Familiarity with IoT communication protocols, particularly MQTT
- Embedded systems programming, comfortable working close to the hardware rather than only at the application layer
- Experience integrating sensors and validating the data they produce
Beyond the basics
Some exposure to how device data actually lands in a cloud pipeline, publishing to a broker, routing into storage, triggering an alert when a reading crosses a threshold, is genuinely useful, whichever specific vendor stack that experience came from. Comfort with a hardware description language or scripting language for automating tests also speeds things up. None of this needs to be deep expertise yet, since it's an associate-level role designed to grow into these areas.
A candidate with strong core hardware and firmware skills but limited cloud exposure will still be seriously considered. The cloud side tends to be the fastest thing to pick up once someone's comfortable with the embedded fundamentals, since the underlying logic transfers well.
Pay and what's included
The role pays up to ₹51,000 monthly on a part-time basis, with in-office hours set flexibly rather than tied to a fixed shift block. Leave scales to match the part-time hours, and there's a bonus tied to how well projects actually land rather than a flat annual figure. For anyone relocating to Jaipur specifically for this position, the employer helps cover the move and assists with finding a place to stay while settling in.
Working in Mahindra World City
Mahindra World City is a planned industrial and IT zone a bit outside Jaipur's older core, with several hardware and manufacturing companies based nearby, which makes it a reasonable place to be if this kind of embedded and IoT work is the direction you want your career to go. The infrastructure around the office itself is decent, though it's a longer commute for anyone living centrally in the city.
The hardware lab here is shared across a couple of small teams rather than dedicated purely to this project, so there's some coordination involved in booking bench time for testing. It's not a bottleneck most weeks, but it's worth knowing going in rather than discovering it during a tight deadline.
Since the role is part-time, scheduling around bench access and any hands-on testing generally gets worked out a few days ahead rather than left to whoever grabs the lab first. It's a small logistical detail, but it keeps the shared space from becoming a source of friction between teams.
Applying
Send a resume along with any projects, personal or professional, that show real hands-on IoT or embedded work; a working prototype matters more here than a list of coursework. Shortlisted candidates go through a technical conversation centered on a real debugging scenario, tracing a problem from a symptom back to its actual cause, since that mirrors what the job looks like most days.
If your experience leans more toward embedded systems generally than IoT specifically, that's still a reasonable starting point. The MQTT and cloud-integration side of this role is genuinely teachable on the job, provided the underlying hardware and firmware instincts are already solid.
