25 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You’ll split time between the console and desk. Mornings often start with telemetry review, checking spacecraft health data and alarms, then logging issues in GitHub or your operations database (sometimes Microsoft Access).
Afternoons go to planning — updating production or operations schedules in Excel, coordinating with engineering on AutoCAD or SolidWorks drawings, and running tests on Linux systems. Expect meetings with mission control, quality reviews, and writing status slides in PowerPoint.
You’ll often use Microsoft Excel for schedules, data analysis, and capacity planning, plus PowerPoint for status reports. Linux is common for running spacecraft software and telemetry tools; C++ appears in flight code or simulators.
Engineers also open CAD files in AutoCAD or Dassault Systemes SolidWorks for hardware fit checks, store code and issues on GitHub, and sometimes use XML for configuration files or data exchange.
The U.S. Bureau of Labor Statistics lists 365,740 employed in this occupational group and gives a median annual wage of $102,440. The lowest tenth earned $74,370, and the top tenth earned $159,860 (BLS).
Pay varies by employer (NASA, private launch companies, contractors), location, and experience. Expect higher salaries near major aerospace hubs and for roles requiring software or systems expertise.
AI can help with data analysis, pattern detection in telemetry, and drafting reports or checklists, but you must not rely on it for final decisions. Use AI as a tool to summarize logs, suggest likely causes, or draft procedure text, then verify against raw data and engineering judgment.
Keep traceability: record which AI outputs you used, validate them against telemetry (on Linux or from CSVs in Excel), and have humans approve any operational command or change to flight software in C++ or configuration XML.
Situational troubleshooting under pressure. That means reading telemetry quickly, forming hypotheses, and testing them with minimal risk — for example, reproducing a fault in a simulator on Linux before sending commands to the spacecraft.
You need clear written procedures (PowerPoint and docs), good use of version control (GitHub), and the habit of checking CAD or requirements (AutoCAD/SolidWorks, specs in XML) so your fixes don’t break other systems.