The Da Vinci Satellite team is recruiting! The different positions within the Core team, Technical team, Education team, and Business team can be found below. All positions listed start as soon as possible unless otherwise specified. If you have any questions, please don’t hesitate to send us an email.
Core Team Positions
The Core Team is responsible for the overall coordination of the Da Vinci Satellite project. It brings together the project manager with the managers of the different departments to form a coherent vision and concrete plans for the entire project.
Technical positions
The technical team is responsible for designing, building and testing the satellite. The team is divided into different subteams, namely, Payload, Systems, Software, Electrical and Ground Station & Operations.
DICE – Payload Engineer (~8–12 hours per week)
As a DICE Payload Engineer, you will support the development and verification of the DICE payload. Your responsibilities include contributing to assembly, integration, testing, and documentation activities. You will work closely with the Lead DICE Engineer and other payload team members. Desired skills include hands-on hardware experience, familiarity with laboratory equipment, and attention to detail in documentation.
DICE – Lead (~12–20 hours per week)
As Lead DICE Payload Engineer, you will be responsible for preparing the Flight Model of the DICE payload, together with the DICE hardware and software engineers. You will coordinate the team, track open issues and NCRs, and ensure the payload meets its technical and schedule milestones. Desired skills include experience with CAD, knowledge of the space environment, good analytical skills, and project management skills.
Starting date: as soon as possible.
DICE – Hardware Engineer (~8–12 hours per week)
As a DICE Hardware Engineer, you will be responsible for the design, assembly, and testing of the DICE payload hardware. This includes supporting and/or manufacturing components, and test setups to support payload verification activities. Desired skills include electronics design, soldering, hardware debugging, and experience with lab instrumentation.
DICE – Software Engineer (~8-10 hours per week)
As a Software Engineer for Dice you will work on the on-board software controlling the Dice Payload. This consists of programming in C++, reviewing the existing codebase, gaining ownership over the software architecture, collaborating with fellow students to define the interfaces from the Dice Payload to other subsystems on board the satellite, and writing documentation. As part of supporting the test campaign, you are also expected to travel with the Dice Payload team to an ESA test facility in Belgium, and to help with writing test procedures.
DICE & AIV – AIV Engineer (~10 hours per week)
As an AIV Engineer for DICE, you will support the Assembly, Integration, and Verification activities of the DICE payload. You will assist in planning and executing test campaigns, maintaining test documentation, and coordinating integration with the satellite structure. Desired skills include hardware testing, documentation, and familiarity with environmental test procedures.
Starting date: April 2026.
EPS – Software Engineer (~10 hours per week)
The EPS Software Engineer is responsible for maintaining and testing the On-Board Computer (OBC) driver that interfaces with the Electrical Power System (ISIS iEPS Type A and B), communicating over I2C. As the driver is largely complete, the primary focus is on verifying power distribution commanding, battery and housekeeping telemetry readout, and fault protection behavior (e.g., emergency low power mode, overcurrent/thermal protection); implementing test scripts and preparing test documentation; and troubleshooting communication issues and fixing bugs found during integration testing. The role also involves hardware-in-the-loop (HIL) testing to confirm the OBC correctly commands the EPS and parses its telemetry under nominal and fault conditions. Limited driver development will still be required to close out any remaining functionality or address issues surfaced during integration testing. Beneficial prior experience includes embedded software testing, familiarity with I2C and other low-level communication protocols, and knowledge of electrical power systems in a space context. Strong debugging skills for diagnosing communication and hardware interface issues are a plus. Working knowledge of C++ is required, as all OBC software is developed in this language.
TT&C – Software Engineer (~8 hours per week)
As a TT&C Software Engineer, you will contribute to the software development for the Telemetry, Tracking & Command subsystem. This includes implementing packet framing, communication protocols, and testing software interfaces between TT&C and the On-Board Computer. You will work closely with the TT&C lead to ensure compliance with regulatory and mission requirements. Desired skills include C/C++, embedded software, and familiarity with communication protocols.
Starting date: April 2026.
Systems – Lead (~12–16 hours per week)
As Systems Lead, you will be responsible for the overall systems engineering of Da Vinci Satellite. This includes maintaining the requirements database, coordinating interface control between subsystems, tracking the verification matrix, and supporting technical reviews. You will work closely with the Technical Manager and all subsystem leads to ensure system-level coherence. Desired skills include systems engineering, requirements management, technical documentation, and cross-subsystem coordination experience.
CDH – Lead (~20–30 hours per week)
As CDH Lead you will be responsible for the command ans data handling subsystem of the DVS satellite. This subsystem holds the 2 on-board computers that coordinate the full satellite. In this role, you will work closely with hardware, software, environmental qualification campaign, interfaces among others. It is desired for you to have a basic understanding of electrical diagrams and hardware, experience with systems engineering, and some experience with embedded software.
CDH – AIV (~12 hours per week)
As a CDH AIV engineer you will support the assembly, integration, and verification of the Command and Data Handling subsystem. The CDH subsystem includes several interconnected electronic units, including the Databoard, Payload Manager, Main OBC, and GNSS stack. The role will involve supporting PCB and hardware integration, checking electrical and data interfaces, preparing and executing assembly and verification procedures, and performing functional tests of the integrated CDH hardware and documenting it all. Basic knowledge of electronics and digital interfaces will be useful. Experience with or knowledge of C or C++ as well as electrical circuits is highly recommended as is previous hands-on experience with hardware.
Bitflip – AIV (~10 hours per week)
As a Bitflip AIV engineer you will support the assembly, integration, and verification of the Bitflip Payload. The role will involve working with the payload electronics and supporting its functional verification. Because of the nature of the Bitflip Payload, experience or interest in programming, memory organisation/allocation, basic embedded systems, and electrical circuits concepts is highly recommended.
AOCS – Software Engineer (~8-10 hours per week)
The AOCS Software Engineer is responsible for testing and maintaining the On-Board Computer (OBC) driver that interfaces with the Attitude & Orbit Control Subsystem (the HT-iADCS200 unit), which communicates with the OBC over RS485. Since the driver development is largely complete, the primary focus is on verifying command and telemetry exchange across all AOCS modes (de-tumble, nadir pointing, target tracking, inertial pointing, magnetic control, and safe mode), implementing the test scripts and preparing test documentation, troubleshooting communication issues, and fixing bugs uncovered during integration testing. The role also involves hardware-in-the-loop (HIL) testing to confirm the OBC correctly commands the AOCS and parses its telemetry, including sun sensor and magnetometer data routed through the unit. Limited driver development will still be required to fix bugs or implement newly identified requirements. Beneficial prior experience includes embedded software testing, familiarity with RS485/serial communication protocols, and exposure to attitude determination and control concepts in a spacecraft or robotics context. Experience with HIL test setups and structured debugging of communication interfaces is a strong plus. Working knowledge of C++ is required, as all OBC software is developed in this language
Software – OBC Software Engineer (~12-16 hours per week)
The OBC Software Engineer is responsible for developing, testing, and maintaining the higher layers of the core on-board software (OBSW) running on the satellite’s On-Board Computer (OBC), built in C++ using Texas Instruments Code Composer Studio. While the peripheral access and hardware proxy layers (subsystem drivers) are close to being finalized, the logic layer, which covers the task scheduler, telecommand-driven services, bootloader, and the operational mode statemachine, still requires active development, as does the top-level application layer that ties everything together. A second major focus of the role is developing and verifying the test software for the databoard test campaign, which also requires active development. The role involves working closely with the Software Lead to design and implement this logic, translating system-level logic/requirements and Modes of Operation (MOO) into working OBC code and test software. Beneficial prior experience includes embedded C++ development, real-time scheduling concepts, and experience designing state machines or task-based execution logic. Working knowledge of C++ is required, as all OBC software is developed in this language.
GS&O – Systems & Data Engineer (~8-10 hours per week)
As a Systems and Data Engineer within the GS&O team, you will strictly collaborate with all the teams to finalize the parameters required for each subsystem to properly communicate with the ground station. You will also contribute to the creation of TM/TC packages, closely working with the GSO lead engineer. Desirable to have familiarity with space systems, basic knowledge of satellite architecture, and knowledge of Excel/data structuring.
GS&O – Software Engineer (~8-10 hours per week)
As a GS&O Software Engineer you will contribute to converting TM/TC data packets into XML (or similar formats) and to creating ground-based software to manage packets entering and leaving the ground station. You will strictly collaborate with the Systems and Data Engineer, and you will have to interface with the ground station hardware. Desirable to have programming skills and experience with data structures.
GS&O – Web & Data Engineer (~6 hours per week)
Description: As a Web & Data Integration Engineer you will create the interface between the Ground Station and the DVS educational website, in order for students and DVS members to interact with the satellite itself. You will collaborate both with the GS&O team and with the Educational team. Desirable skills include backend development and API design standards.
Educational positions
The education team is working hard on developing and testing the educational modules for both primary and secondary schools. These modules are direclty linked to the payload in the satellite.
Primary school (~4 hours per week)
You will be working in a team to develop an educational lesson package. These lessons are partly co-developed with the international primary school and focus on unconventional teaching methods with the aims of bringing space closer to Earth, literally.
High school (~4 hours per week)
You will be working in a team to develop masterclasses for high school students! The masterclass subjects range from, for example, Mars to Interplanetary Travel and aim to contain loads of unconventional educational methods. Expect loads of masterclass trial runs and testing sessions!
Business positions
The Business team focus on both finances as well as communications aspects.
The Communications team has a large range of responsibilities and opportunities to help with. Our team's main objectives involve expanding the project's outreach, as well as maintaining the Da Vinci Satellite corporate identity in order to build a following through recognizable and cohesive media and increasing team visibility towards students and the general public.
The Finance team is focused on getting funding for the project and taking care of the launch contract.
Social Media Strategist (~4 hours per week)
As a Social Media Strategist within the Communications team, you will be responsible for Da Vinci Satellite's social media, both planning and posting content. This notably includes keeping our Instagram and LinkedIn up to date, but also providing updates to our partners and writing blog posts for the website, and anything else you may wish to develop. You will have significant freedom in your function, using your own ideas and interpretation to expand the team's outreach, reaching students, professionals, and the general public.
Finance Team Member (~4 hours per week)
As a member of the Finance team of Da Vinci Satellite, it will be your main responsibility to locate and get in touch with companies and initiatives, willing to collaborate with the team, while sharing the same goals and objectives. These companies can range from small local businesses to multinationals and even national or global funds. Maintaining the financial health of the project requires professionalism, dedication and collaboration. You will be applying these principles in finance and business meetings as well as during our weekly work sessions. Contacting businesses, creating proposals and templates, scheduling prospect meetings, and gaining financial and corporate experience, having fun in the process, are all part of this invaluable work experience!
