Engineer I – Avionics
NewSpace — Bengaluru
₹4–8 LPA (HireSetu estimate) · 1–3 yrs exp · Full-time · onsite
HireSetu listing reference 34ed0d — confirm requirements below, then apply on the employer site.
Quick answer: A junior firmware job inside the ArduPilot autopilot itself: changing the Copter and Plane codebase, running it on STM32 boards, then flying the result. Time spent in the source code counts for more here than stick time.
From NewSpace's job posting
Engineer I - Avionics
1-3
Job Summary
We are seeking a motivated Junior ArduPilot Developer to assist in extending and customizing the ArduPilot open-source flight control stack for our drone platforms. You’ll be part of a multidisciplinary team working on cutting-edge autonomous systems, supporting real-world testing and integration of sensors, payloads, and navigation systems.
Responsibilities
Assist in adding/modifying features in the ArduPilot (Copter/Plane) codebase.
Collaborate with senior developers to understand ArduPilot architecture.
Contribute to sensor and peripheral integration (e.g., GPS, IMUs, ESCs).
Debugging communication protocols (CAN, MAVLink, SBUS, etc.).
Debug flight control parameters for stability and performance.
Handle board bring-up and unit testing on new prototypes.
Major Contribution to real-world testing, flight logs analysis, and flight safety.
Participate in bench testing and field flight trials.
Maintain Git-based version control and follow CI/CD best practices.
Create developer documentation and support internal teams for integration.
Required Skills
Basic understanding of C/C++ , embedded development workflows and microcontroller programming.
Familiarity with MAVLink protocol and GCS tools (Mission Planner/QGroundControl).
Exposure to STM32 or similar microcontroller-based systems.
Hands-on experience with Arduino or other embedded platforms.
Good grasp of basic electronics and sensor interfacing.
Passion for drones, robotics, or open-source firmware projects.
Knowledge of real-time systems and interrupt-driven code.
Expertise in Use of debugging tools like oscilloscopes, and logic analyzers.
Experience with version control via Git.
Nice-to-Have
Python scripting for testing and automation.
Python or Lua scripting for onboard automation.
Familiarity with Gazebo or SITL simulations.
Familiarity with electromagnetic interference, EMI/EMC issues.
Hands-on experience with drone kits or robotics competitions.
Understanding of UAV dynamics, PID control, or mission planning concepts.
Experience with Git and collaborative development practices.
Text from NewSpace's official job posting, formatted by HireSetu. The employer's own page is the final word on details.
HireSetu's note
Getting inside ArduPilot
ArduPilot is a twenty-year-old codebase with its own conventions, and the first months go into learning where things sit: shared libraries, per-vehicle folders, the parameter tables that drive behaviour. A drone you assembled from a kit teaches the hardware half. Building SITL on your own laptop and stepping through a takeoff teaches the other half.
Git history gets read in this line of work. Fork ArduPilot, fix a small bug, open a pull request. One closed patch gives you something concrete to describe, whatever else is on your CV.
Bench days and field days
Expect the week to split between a bench and an airfield. Bench work means logic analyser traces, CAN and serial traffic, and board bring-up on prototypes where nothing behaves the first time. Field work means standing behind a safety line watching an aircraft fly code you partly wrote.
Flight logs are where the difficult debugging happens, and working through one from a long flight takes patience. Test days start early because calm air matters. Motors and ESCs throw out electrical noise, which is why EMI/EMC sits in the nice-to-haves; project time on grounding, shielding or cable routing is directly relevant here.
Pin these down before you join
Ask which airframes you would cover. Copter and Plane share libraries, but tuning, parameters and failure modes differ, and the answer decides what you learn. If the team runs a fork with local changes, find out how far it has drifted from upstream, since a heavily patched branch means more maintenance work and less new development.
Ask who reviews your code and how often the team flies. A junior engineer with no review process in place has a slow road to getting good.
Drafted with AI from NewSpace's job posting and checked by Prashanth Jakkula before publishing. See our Editorial Policy.
How to apply
- Open NewSpace's careers site with the Apply button.
- Follow the application steps on the site and upload your resume.
- Keep the confirmation email or application number for follow-up.
No fees, ever. HireSetu never charges candidates, and no genuine employer asks for money to apply, interview or join. If anyone asks you to pay, stop and report the job.
Similar openings on HireSetu
- Associate Embedded Software Engineer at Harmonic — Bengaluru — Embedded · Full-time
- Embedded Design Engineer at Park Controls and Communications — Bengaluru — Embedded · Full-time
- Embedded Systems Engineer at Bellatrix Aerospace — Bengaluru — Embedded · Full-time
- Embedded Systems Engineer at GALAXEYE SPACE SOLUTIONS — Bengaluru — Embedded · Full-time
- Associate I - Semiconductor S/W Product Development at UST — Bengaluru — Embedded · Full-time
View Engineer I – Avionics on HireSetu · More NewSpace jobs · Embedded jobs · Jobs in Bengaluru · Career Insights · FAQ · Companies