Careers

Three open roles, and what you would actually be doing in them

We are a small aerospace team in Bengaluru. That means the person who writes the failsafe is the person who defends it in review, and the work below is the work, not a summary of a department.

Open positions

Every role here is open and funded. If a listing is filled we take it down rather than leave it collecting applications.

Flight software and SITL

Flight Software Engineer

Own the firmware, parameter sets and failure behaviour that fly on customer airframes, and the software in the loop harness that proves a build before it does.

What you would do

  • Build and version PX4 or ArduPilot configurations across several airframe types, so the build flying today is provably the build that was tested.
  • Author autonomy behaviour as reviewable artefacts: search patterns, contingency actions, geofence responses, payload triggering.
  • Extend our SITL regression harness so a parameter change that breaks a failsafe is caught on a laptop, not on a runway.
  • Write the fault detection and recovery logic, and the reasoning a regulator will ask you to defend.

What we need to see

  • C or C++ on embedded targets, and Python for tooling and test.
  • Hands on with PX4, ArduPilot or an equivalent flight stack, including its parameter system.
  • Comfortable with git, CI, and treating configuration as code rather than as a file someone emailed you.
  • Two years or more in flight software, robotics or a comparable safety relevant embedded domain.

Helps, not required. Experience with DO-178C, or with a civil UAS certification submission.

Apply for Flight Software Engineer

Ground segment and link budget

Ground Segment Engineer

Design the link, build the ground station tooling, and make the schedule risk in a communications plan visible before it becomes a flight delay.

What you would do

  • Close link budgets for UAS and small satellite programmes, and document the margin so it survives review.
  • Stand up and maintain ground station software: telemetry ingest, command paths, health monitoring.
  • Turn contact schedules and pass geometry into something a programme manager can plan against.
  • Instrument the ground segment so a degraded link is diagnosed from data rather than from memory.

What we need to see

  • RF fundamentals: link budgets, antenna patterns, modulation and coding tradeoffs.
  • Python, and enough systems engineering to argue a margin with a customer.
  • Familiarity with MAVLink, CCSDS or a comparable telemetry and command standard.
  • Two years or more in ground segment, satellite operations or UAS communications.

Helps, not required. Prior work on a ground station that someone else had to operate at three in the morning.

Apply for Ground Segment Engineer

Simulation and flight data

Simulation and Flight Data Engineer

Run the dispersions that find the failure before the aircraft does, and turn flight logs into the evidence that explains what actually happened.

What you would do

  • Build and run Monte Carlo dispersion campaigns, and report what the tails mean rather than only the mean.
  • Maintain the simulation models that back our design and certification work, including the assumptions register.
  • Analyse flight logs to find the degradation that preceded an event, not just the event.
  • Turn recurring analysis into tooling the rest of the team can run without you.

What we need to see

  • Python with the numerical stack, and the judgement to know when a result is an artefact of the model.
  • Flight dynamics or a closely related simulation background: coordinate frames, sensor models, actuator limits.
  • Experience with real flight data, including the parts that are missing or wrong.
  • Two years or more in simulation, flight test analysis or a comparable data heavy engineering role.

Helps, not required. You have written a post mortem that changed a design decision.

Apply for Simulation and Flight Data Engineer

How we hire

Four steps, about two weeks, and you will speak to the people you would work with.

Step one

You send something real

A CV is fine. A repository, a flight log you analysed or a write up of something that went wrong is better, because it tells us how you think.

Step two

A conversation, not a quiz

Forty five minutes on what you have built and where it broke. No whiteboard algorithms.

Step three

A problem from our actual backlog

Timeboxed, paid, and small enough to fit an evening. You keep the work.

Step four

Offer or a straight no

Either way you hear back with a reason. Silence is not a hiring strategy.

Not ready to apply

If you are still building the experience these roles ask for, the paid programme is the honest route in.

Our industry programme runs the same three tracks as the roles above, over eight weeks, with a certificate issued by EDUSHARK TRAINING. It is training that you pay for, not employment, and we say so plainly on that page.

Think you fit one of these?

Write to careers@aerodesignsolutions.com and tell us which role and what you have built.

Apply now