MaiaSpace Paris, France
Flight Software System Tools Developer
Employment
Not statedLevel
Not statedTeam
Avionics & EGSECountry assessment
Not doable from Austria because the employer's own board marks it as not remote.
Our assessment is guidance. Confirm arrangements with the employer.
Skills mentioned in this posting
Job description
🚀MaiaSpace is a European space tech company, designing, manufacturing and operating competitive and sustainable solutions for space mobility. We are driven by the belief that access to space is a major enabler for a better and more sustainable life on Earth, addressing the challenges faced by humanity: climate, resources, connectivity, and data. Our aim is to successfully design and test a cost-effective and reusable mini-launch vehicle.
🚀 Flight Software System Tools Developer We are looking for a flight software system tools developer to join one of our team in charge of the development of the Avionics embedded software. Some of our missions are : Integrate and configure algorithms from GNC and tanks teams (code generation from Matlab). Integrate and configure all our different software together into a single flight software deliverable.
Configure our flight software with inputs coming from: o The system team (command plan, measurement plan, ...) o The mission team (mission sequence, mission trajectory, ...) Provide other teams with information they need: o The system team (telemetry link budget) o The EGSE (Electrical Ground Support Equipment) team with the ICDs (Interface Control Documents) required for ground / board communication Those processes can all be mostly automated using algorithms, APIs, graphical tools, etc.
This work has already started, but a lot is remaining to be done. Your goal is to participate and drive this development. You will contribute to building an end-to-end pipeline from the developer that pushes code to the final software loaded into the launcher Your work will consist mainly of two things: Understand the needs of the embedded software team and other teams we interact with.
Those needs are not expressed clearly on a requirement document. This definition is a collaborative endeavor we will undertake as a team where you’ll have to be proactive and ask/understand/challenge us. Implement (mostly in Python) the glue between all the processes of our pipeline (e.g. code generation, auto configuration, system rules checks, testing, deployment, internal graphical tools addons, etc...)
Our way of working: Our team's hierarchy is flat; you will be given a direction for which you’ll have to identify yourself what is most important, identify our needs, challenge them, and implement a solution. Our code iterates quickly, and the documentation procedure is still being ironed out. You should be able to adapt quickly to changes in an environment that evolves rapidly.