Space industry resume guide: what space job postings ask for (2026)

What rocket, satellite and spacecraft employers actually ask for, measured across every open space industry job posting on SpaceJobs.Now, and how to turn it into a resume that gets read.

Most resume advice is written for every industry at once, which is why so much of it misses what matters in space. A launch company, a satellite manufacturer and a NASA contractor screen applicants against constraints that a software startup or a bank never faces: export-control law decides who may even be hired, many programs need a security clearance before day one, and the hardware is regulated by quality standards that leave a paper trail for every bolt. A resume that ignores those constraints can be strong on paper and still never reach an engineer.

So instead of repeating general tips, this guide starts from the postings themselves. On 3 November 2026 we read every open role on SpaceJobs.Now (18,507 postings from the job boards of about 150 space employers, among them SpaceX, Blue Origin, Rocket Lab, NASA, JPL, Lockheed Martin and Northrop Grumman) and counted what they ask for: citizenship, clearances, degrees, programming languages, CAD and analysis tools, quality standards, certifications and documents. The skills, tools, certifications and portfolios are now counted every day by our research on the skills space employers ask for, and those figures below are today's; the rest are that first reading, dated where they appear. The method is at the end.

A few findings set the tone for everything that follows:

• 63.3% of postings named U.S. citizenship and 33.0% named ITAR, the U.S. export-control regulations, on 3 November 2026. Who you are allowed to be hired as matters before what you can do.
• 31.7% mentioned a security clearance that day. For roughly one role in three, your clearance status belongs on the first page.
• Python is the single most named technical skill ( 25.9% of all postings today, 54% of software and IT and 61% of flight software and GNC postings), ahead of C++ ( 13.0%) and MATLAB ( 11.0%).
• 60.1% of postings named a bachelor's degree on 3 November, but only 7% of technician, machinist and inspector postings did. Engineering roles expect a degree (73% of postings with "engineer" in the title name one); the hands-on side of the industry hires on skills and certifications.
• Hardly any posting asked for a cover letter (1.2% on 3 November), while 6.0% name a portfolio or work samples today. The resume carries the application.

The rest of this guide turns those numbers into concrete choices: what goes at the top, which tools to name and how, how a federal resume for NASA or the Space Force differs, what hiring software does with your file, and how students and career changers can compete. If you want the wider picture of the industry first, start with our guide on how to get a job in the space industry; for the rules behind citizenship and clearances, see ITAR, U.S.-person rules and security clearances.

Contents

1. Citizenship, export control and clearances: the first screen
2. What each kind of space role asks for
3. How resumes should differ by employer
4. Software and flight software resumes
5. Guidance, navigation and control resumes
6. Mechanical, structures and propulsion resumes
7. Electrical, avionics and test resumes
8. Manufacturing, quality and supply chain resumes
9. Technician, machinist and inspector resumes
10. Program management, business and mission operations resumes
11. Federal resumes for NASA and the Space Force
12. Hiring software: what happens to your file
13. Degrees, portfolios, transcripts and cover letters
14. Internships, new graduates and career changers
15. Writing bullets that prove you built real things
16. A sample one-page layout
17. A checklist before you apply
18. Frequently asked questions
19. How we measured

1. Citizenship, export control and clearances: the first screen

Start with the line most applicants leave out. Nearly two in three space postings on our board name U.S. citizenship, and 2,982 of them (16%) carry a sentence that begins "To conform to U.S. Government export regulations". The most common version, on 2,628 postings and standard on SpaceX roles, reads: "applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C. § 1157, or (iv) Asylee under 8 U.S.C. § 1158, or be eligible to obtain the required authorizations from the U.S. Department of State." One posting in three names ITAR directly.

The reason is legal, not preferential. Rockets, many satellites and much of the software and test data around them are controlled as defense articles or technical data, and sharing that information with a foreign person counts as an export that needs a license. An employer that cannot get licenses for every hire simply limits the role to "U.S. persons": citizens, lawful permanent residents and people granted asylum or refugee status. Our ITAR and clearance guide covers the definitions and the exceptions in detail.

What that means for a resume is simple and often ignored: a recruiter screening a stack of applications for an ITAR role needs to know your status, and the fastest way to be set aside is to make them guess. If you are a U.S. citizen or permanent resident, say so in one plain line near your contact details, such as "U.S. citizen" or "U.S. lawful permanent resident". You do not need a passport number, a birth date or a photo; status is enough.

Stating a security clearance

Clearances work the same way. 5,873 of the 18,507 postings (31.7%) mention a security clearance, from "ability to obtain a Secret clearance" to "active TS/SCI with polygraph". If you hold one, write its level and status the way the government phrases it: "Active Secret clearance" or "Active TS/SCI (CI polygraph)", with the year it was granted or last investigated if you know it. If yours lapsed, write "Secret clearance (inactive since 2024)": a clearance that lapsed recently is cheaper and faster to reinstate than a new one, and employers know it.

If you do not hold a clearance, do not write "clearable" or "eligible for a clearance". Those words promise something only an investigation can establish, and screeners read them as filler. When a posting says "ability to obtain", your citizenship line already answers what the screener needs to know.

Where the line goes

Put status and clearance in your header, under your name and contact details, not in a skills list near the bottom. A typical header for an ITAR role reads: name, city and state, phone, email, LinkedIn or portfolio link, then one line: "U.S. citizen · Active Secret clearance". Everything else on the page is about what you can do; this line is about whether the employer may hire you, so it comes first.

Outside the United States the same logic applies to the local rules. European space employers working under national security programs ask for EU or national citizenship and sometimes national clearances; the British ones name "SC" (Security Check) or "DV" (Developed Vetting). If a posting names a nationality or vetting level, mirror its wording in your header.

2. What each kind of space role asks for

The second thing a screener checks is whether you can do the work, and the postings say precisely which tools they mean. On 3 November 2026 we grouped the postings by the words in their titles into eight families and counted the tools and requirements named in their text. The table shows the most named items in each family that day; percentages are shares of that family's postings. The same reading by the board's own kinds of work is kept current every day in which kinds of work ask for which skills and, for certifications, which kinds of space work name which certifications.

Three patterns stand out.

Python has become the common language of space engineering, not only of software. It is named in 47% of test roles, 29% of propulsion and electrical roles and 21% of mechanical ones. Test engineers script data acquisition and analysis in it, propulsion engineers reduce hot-fire data with it, and structural engineers automate load cases. If you use Python at all in your engineering work, it belongs on your resume, attached to what you did with it.

Tool names are specific, so your resume should be too. Mechanical postings name Siemens NX (25%), ANSYS (22%), SolidWorks (17%) and Creo (17%) far more than "CAD" in general. A screener searching for "NX" will not find "3D modeling software". Name each tool you have actually used, in the form the postings use.

Quality standards are part of the job outside the quality department. AS9100, the aerospace quality management standard, appears in 24% of manufacturing and quality postings and 8% of technician postings, and IPC J-STD-001, the soldering standard for electronics assembly, in 11% of technician roles. Certifications against these standards are concrete, checkable facts, which is exactly what a screener wants.

The sections that follow go family by family. Read the one closest to the roles you are applying for, then the sections on federal resumes, hiring software and bullets, which apply to everyone.

3. How resumes should differ by employer

The same engineer may apply to a launch company, a defense prime and a federally funded research center in one week, and the postings show how differently those employers screen. Here are the largest employers on our board on 3 November 2026, with the share of their open postings naming a security clearance, U.S. citizenship and Python that day (every employer's clearance and citizenship shares today are in the research on who can apply):

Three kinds of employer emerge, and each rewards a slightly different resume.

Commercial launch and satellite companies (SpaceX, Blue Origin, Amazon Leo, Rocket Lab and their peers) almost all require U.S. person status for export reasons but rarely ask for a clearance. They hire for speed and hands-on results: what you built, how fast, and what you learned when it broke. Put hardware, test and production results first, keep the resume to one page early in your career, and make the citizenship line unmissable.

Defense primes (Lockheed Martin, Northrop Grumman and the other large contractors) mention a clearance in three of every four postings. For them, an active clearance can matter as much as any technical skill, because it lets you start on a classified program at once. If you hold one, it belongs in the header with its level; if you do not, emphasize the work on unclassified programs and the standards these employers live by (AS9100, earned value, DFARS, configuration management).

Federally funded research and development centers such as The Aerospace Corporation (96% of postings mention a clearance, 47% name Python) sit between government and industry. They hire analysts and engineers who write code, model systems and advise the Space Force and other agencies. Analytical depth reads best here: methods, models, publications, and the decisions your analysis supported.

Outside the United States the picture changes again. European employers such as Thales Alenia Space name neither U.S. citizenship nor U.S. clearances, but many of their defense and institutional programs carry national security requirements of their own. A resume for a European space employer should list languages with levels and, where a posting names it, nationality or vetting status.

4. Software and flight software resumes

Software is the largest single family of space roles once you count everything that writes code: flight software, ground software, simulation, test automation, tooling, data and IT. Our 1,793 software postings name Python in 61% and C++ in 55%, Linux in 38% and a security clearance in 38%, the highest clearance share of any family. FPGA work appears in 7%, at the boundary with electrical engineering.

That mix tells you how space software differs from web or app development. Much of it runs on embedded processors under real-time constraints, talks to hardware through buses and drivers, and has to be verified to a standard that a crash in orbit cannot be patched around. Screeners for flight software look for evidence of three things: systems-level languages (C and C++), work close to hardware (embedded Linux, RTOS, drivers, interfaces such as SPI, I2C, CAN or MIL-STD-1553), and disciplined verification (unit and integration tests, hardware-in-the-loop, code review, requirements traceability).

On the resume that translates into a few concrete choices:

• Name languages with the version or context you used them in. "C++17 flight software for a CubeSat attitude control board" tells a screener far more than "C++" in a skills list.
• Put hardware next to code. If you have written drivers, bring-up code or firmware, say which processor family and which interface. "Wrote SPI driver for an IMU on an STM32 running FreeRTOS" is the kind of line that matches what these postings describe.
• Show how you verified it. Space employers read testing as a sign of judgment. Name the test framework, the share of code under test, hardware-in-the-loop rigs you used, or a defect you caught before it flew.
• Keep ground and cloud work in its own words. Ground software, mission operations tools and data pipelines use the same vocabulary as other industries (Python, Kubernetes, AWS, PostgreSQL). Kubernetes appears in 819 postings and AWS in 911 across the board, most of them (74% and 60%) with software, data, IT or ground systems in the title.

If your background is web or general software, the most useful step is a small embedded project you can describe in those terms: a microcontroller that reads a sensor, filters the signal and logs it, with tests. It costs little, and it turns "I write Python" into evidence of the work these teams do.

Postings for software roles at space companies also come with coding interviews and, at many employers, a system design round. The software engineers page shows how each employer currently hiring software engineers runs its assessments, as its own hiring pages describe them. What happens after the resume, from the application form's screening questions to the checks after an offer, is in our space industry interview guide.

5. Guidance, navigation and control resumes

Guidance, navigation and control (GNC) roles are the most tool-specific family we measured. Across 408 postings, Python is named in 64%, C++ in 54%, MATLAB in 50% and Simulink in 31%, and 37% mention a security clearance. No other family names MATLAB in more than a quarter of its postings.

The pattern reflects how GNC work is done: algorithms are designed and simulated in MATLAB and Simulink, then implemented in flight code, often C++, and analyzed with Python. A GNC resume that names only one side of that pipeline reads as half a profile. The strongest ones show the whole loop: "Designed a sliding-mode attitude controller in Simulink, auto-generated C code with Embedded Coder, verified on a three-axis air-bearing table".

Specific vocabulary matters more here than almost anywhere else, because the field is technical enough that screeners search for it: Kalman filtering (extended or unscented), attitude determination, orbit determination, trajectory optimization, six-degree-of-freedom simulation, Monte Carlo analysis, sensor models for star trackers, IMUs and GPS receivers, reaction wheels and thrusters. Use only the terms you have actually worked with, and attach each to a result.

Students should note how often a thesis or capstone project is the best evidence available. A senior design project that closed a control loop on real hardware, or a CubeSat team's attitude determination and control subsystem, belongs high on a new graduate's GNC resume, described like a job: the problem, the method, the tools and what was measured at the end.

6. Mechanical, structures and propulsion resumes

Mechanical and structures postings (1,891 of them) are where analysis tools dominate. FEA or NASTRAN is named in 31%, Siemens NX in 25%, ANSYS in 22%, SolidWorks and Creo in 17% each, and Python in 21%. Propulsion postings (524) lean toward Python (29%), Siemens NX (26%), MATLAB (23%) and ANSYS (18%), reflecting the mix of hardware design and test-data analysis in engine and thruster work.

Two practical consequences follow for a mechanical resume.

Name the CAD system you used, and be honest about depth. Employers standardize on one system, and moving between NX, Creo, SolidWorks and CATIA takes weeks, not hours. A screener matching a posting that says "Siemens NX" will look for NX. If you know a different system well, say so plainly and add any exposure to theirs; do not list every CAD package you have opened once. CATIA appears in 285 postings across the whole board. GD&T (geometric dimensioning and tolerancing to ASME Y14.5) is named in 1,315, including 28% of mechanical and 26% of propulsion postings: if you can read and apply it, say so explicitly.

Describe analysis by what it decided. "Ran FEA" is a task; "Ran random-vibration FEA in NASTRAN on a 40 kg avionics tray, found a first mode at 92 Hz against a 100 Hz requirement, added two ribs and closed at 118 Hz with 3% mass growth" is evidence. Structural and thermal analysts are hired for their judgment about margins, so show the margin.

For propulsion, the strongest evidence is test. If you have worked on a test stand (university rocketry, a student liquid engine team, a company test site), say what you ran and what you measured: chamber pressure, injector stiffness, thrust, specific impulse, a failure you diagnosed. Propulsion teams hire people who have seen hardware behave unexpectedly and reasoned their way to the cause.

7. Electrical, avionics and test resumes

Electrical and avionics postings (1,294) name Python in 29%, a security clearance in 25%, MATLAB in 16%, C++ in 15% and FPGA work in 13%, and the soldering and assembly standard IPC J-STD-001 in 8%. Test postings (1,154) name Python in 47%, C++ and MATLAB in 17% each, LabVIEW in 16% and Linux in 15%.

Electrical resumes for space roles tend to be judged on three questions: did you design boards that were built, did you bring them up and debug them, and do you know what space does to electronics. On the page, that means naming the schematic and layout tools you used (Altium, OrCAD, KiCad), the parts of the design you owned (power, RF, digital, mixed signal), the test equipment you used to bring the board up, and any work on radiation tolerance, derating, conformal coating or thermal-vacuum testing. FPGA engineers should name the device family, the language (VHDL or Verilog, named in 245 postings) and the verification approach.

RF deserves a note of its own: "RF" appears in 2,399 postings, many of them communications and payload roles at satellite builders. If you have link budgets, antenna design, RF test or radio software in your background, say so with numbers (frequency bands, data rates, noise figures).

Test engineering resumes should read like test reports. A test engineer at a launch or satellite company plans campaigns, builds or modifies the setup, writes the automation (Python and LabVIEW, in our counts), runs the test and decides whether the hardware passed. The best bullets cover that whole chain: "Wrote Python test sequencer for thermal-vacuum testing of 12 reaction wheels; cut setup time from 3 days to 4 hours and caught a bearing torque anomaly at -30 °C that led to a vendor lot change."

8. Manufacturing, quality and supply chain resumes

Manufacturing and quality roles are where space companies turn designs into flight hardware, and their postings speak the language of standards. Across 1,522 manufacturing and quality postings, AS9100 is named in 24% and Six Sigma in 24%, a security clearance in 21%, Excel in 18% and Siemens NX in 11%. Looked at by title, 66% of quality postings, 41% of manufacturing postings and 30% of supply chain postings name a certification of some kind, and Lean Six Sigma alone appears in 32%, 25% and 15% of them.

AS9100 is the aerospace version of the ISO 9001 quality management standard. Suppliers to aerospace and defense primes are audited against it, which is why so many postings expect you to know what it requires in practice: controlled documents, first article inspection (often to AS9102), nonconformance reports, corrective and preventive action, and traceability from raw material to the finished part. A manufacturing or quality resume that names those processes, and shows you have run them, reads as ready for an aerospace floor.

Three things make these resumes stronger:

• Name the systems of record. Quality and manufacturing work lives in software: an ERP system (SAP is named in 930 postings), a manufacturing execution system, a quality management system for nonconformances and corrective actions. If you have worked in them, name them.
• Quantify improvements the way the standards measure them. Yield, scrap rate, first-pass yield, cycle time, defects per unit, on-time delivery, supplier escapes. "Cut harness rework from 14% to 3% by adding an in-process continuity check" is a quality engineer's bullet.
• List certifications with their issuer and year. A Lean Six Sigma Green Belt, an ASQ certification (Certified Quality Engineer, Certified Quality Auditor), an AS9100 internal auditor course or an IPC trainer credential are checkable facts. Put them in their own short section rather than burying them in a skills list. Our space industry certifications guide counts which ones the postings name, role by role, and what each takes to earn.

Supply chain postings at space companies add their own vocabulary: the Defense Federal Acquisition Regulation Supplement (DFARS) and its sourcing rules, ITAR-controlled purchasing, supplier quality audits, long-lead parts and obsolescence. Buyers and planners who have worked in aerospace or defense should make that experience visible, because it shortens the learning curve the employer would otherwise pay for.

9. Technician, machinist and inspector resumes

Technicians build, wire, test and inspect the hardware, and they are hired in large numbers: our board held 1,317 technician, assembler, machinist, welder and inspector postings on 3 November. Their postings name fewer software tools and more schedules, standards and clearances: shift work in 50%, a security clearance in 18%, Excel in 15%, GD&T in 14%, IPC J-STD-001 in 11% and AS9100 in 8%. Only 7% name a four-year degree.

For these roles the resume is short, factual and full of specifics that a hiring lead can check:

• Certifications, with their level and expiry. IPC J-STD-001 (soldering), IPC/WHMA-A-620 (cable and harness), IPC-A-610 (acceptability of electronic assemblies), welding certifications to AWS D17.1 (the aerospace fusion welding specification) or AWS D1.1, nondestructive testing levels (named with "Level II" or "Level III" in 54 postings), an FAA Airframe and Powerplant certificate (named in 117).
• Equipment and processes. Name the machines and controls you have run (for example 5-axis mills with Haas or Fanuc controls), the inspection tools (CMM, calipers, height gauges, borescopes), the cleanroom class you have worked in, and the electrostatic-discharge and foreign object debris controls you followed.
• Drawings and procedures. Say that you work from engineering drawings and work instructions, and whether you read GD&T. In aerospace a technician's discipline in following, and correctly stopping, a procedure is valued as highly as speed.
• Shifts and travel. Half of technician postings mention shift work: launch and test sites run second and third shifts and campaigns away from home. If you are open to them, say so; it removes a question.

Military experience translates directly here. Avionics, missile and aircraft maintenance specialties map onto space technician work, and employers who hire technicians know that military maintenance training covers much of what a civilian certificate does. Translate your specialty code into the civilian terms the postings use (for example "aircraft electrical systems technician, 6 years, troubleshooting to component level"), and list the platforms you maintained. Our space jobs for veterans page shows the roles where that experience counts most.

10. Program management, business and mission operations resumes

Not every space job touches hardware or code. Programs need managers, schedulers, cost analysts, contracts and finance staff, and satellites in orbit need operators around the clock. Their postings are just as specific as the engineering ones.

Program and project management (709 postings) name a security clearance in 44%, Excel in 29%, Microsoft Project in 26%, the PMP certification in 23% and earned value management in 20%. Earned value is how government programs measure cost and schedule performance, and a program manager or program control analyst who has reported cost and schedule variance on a contract should say so in those words, with the size of the program: "Ran monthly earned value reporting (CPI, SPI, estimate at completion) for a $140M satellite program under DFARS 252.234-7002". Name the scheduling tool (Microsoft Project, Primavera P6), the contract types you have managed (firm fixed price, cost plus) and the milestones you delivered. A PMP certificate belongs in its own section with the year.

Business, finance and contracts roles (587 postings) name a security clearance in 46% and the Federal Acquisition Regulation or its defense supplement (FAR or DFARS) in 35%, with Excel in 30% and SAP in 20%. For these roles, government contracting experience is the single most valuable line on a resume, because it is expensive to train: proposal pricing, cost accounting standards, audits by the Defense Contract Audit Agency, subcontract management. Name the regulations you have worked under and the value of the contracts you supported.

Mission operations (282 postings) look different again: Python in 54%, shift work or on-call duty in 34%, a security clearance in 28% and Linux in 17%. Satellite and spacecraft operators run passes, monitor telemetry, respond to anomalies and automate their own tools, which is why Python is named so often. A strong operations resume names the spacecraft or ground systems you operated, the command and telemetry software, the number of passes or contacts you supported, an anomaly you resolved and any automation you wrote. Say plainly that you are willing to work shifts if you are; one posting in three asks.

11. Federal resumes for NASA and the Space Force

Federal roles follow different rules, and the most important one changed recently. On our board, NASA's civil service roles and the U.S. Space Force's civilian roles come through USAJOBS, the federal government's hiring site: 8 NASA postings and 30 Space Force postings on 3 November. (NASA's Jet Propulsion Laboratory is a different case: JPL is run by Caltech, hires its 117 currently open roles through its own system, and expects an ordinary resume.)

Since 27 September 2025, a federal resume may be at most two pages. The U.S. Office of Personnel Management announced the limit as part of its Merit Hiring Plan, and its guidance to agencies is explicit: "Starting September 27, 2025, USAJOBS will restrict all resumes to two pages. This includes resumes stored in a job seeker profile, new uploaded resumes, resume builder resumes, and searchable resumes in the Agency Talent Portal" - OPM agency guidance on the two-page limit. The same guidance says resumes "must be legible so they can be reviewed for eligibility, minimum qualifications and other position requirements listed in the job announcement."

The two-page limit changed the length, not the content federal reviewers need. The U.S. Treasury's applicant guidance lists what each job on a federal resume should show: "Start and end dates (include the month and year)", "The number of hours you worked per week", "Brief descriptions that show you can perform the tasks at the required level listed in the job announcement", and the "Series and grade for federal jobs only" - Treasury resume tips. Hours per week matter because federal qualifications are counted in months of full-time experience; a 20-hour-a-week job counts half as much, and a reviewer who cannot tell may not count it at all.

Federal reviewers also screen the resume against the announcement's own words more literally than a company recruiter does. Treasury's guidance gives the example directly: if the announcement asks for experience with MS Project, your resume should say "MS Project". Read the "Qualifications" and "Specialized experience" sections of the announcement and make sure each requirement appears, in its own words, in a bullet that shows you did it.

Our board's job pages make one part of this easier: when a federal posting's own text says what the resume must show, the page says so under the posting, together with a federal resume service where we have one. A few practical rules for the two pages:

1. Lead with the most relevant role, even if it is not the most recent, and give older or unrelated jobs a line each.
2. Write qualifications as accomplishments: the specialized experience the announcement names, then what you achieved with it, with a number where you have one.
3. Keep the federal fields on every relevant job: month and year, hours per week, and series and grade for federal jobs.
4. Do not shrink the font to fit. The guidance asks for legible resumes; a cramped page defeats the purpose of the limit.
5. Answer the assessment questionnaire consistently with the resume. Many announcements ask you to rate your own experience in an assessment questionnaire; reviewers check those ratings against what the resume shows.

The Space Force's civilian roles add a further layer: many require a security clearance, and the announcement says which. Apply the advice from section 1 to the header of a federal resume too.

12. Hiring software: what happens to your file

Almost every space employer receives applications through an applicant tracking system, and knowing which one shapes a few formatting choices. Among the employer job boards SpaceJobs.Now reads through a hiring system's own feed, Workday runs the most (23), followed by BambooHR (10), Teamtailor (6), SAP SuccessFactors (5), Phenom (5), Rippling (4) and Personio (4); the large primes and many launch companies sit on Workday, while smaller satellite and startup employers spread across the others.

These systems do two things with a resume. They parse it into a candidate profile (name, contact details, employers, titles, dates, education, skills) that recruiters search and filter, and they store the original file that a recruiter or hiring manager opens and reads. The popular claim that software rejects most resumes before a person sees them is not something the vendors or the evidence support. In practice the automatic filtering happens mostly in the application form itself: fixed screening questions about work authorization, citizenship, clearance, location or willingness to work shifts, which a recruiter sets as must-pass. The resume's job is to survive parsing intact and then read well to a human who searched for the right words.

That leads to a short list of formatting rules that hold across all of these systems:

• Use one column and standard headings. "Experience", "Education", "Skills", "Certifications", "Projects". Two-column layouts, text boxes and headers or footers can scramble parsing, putting your phone number into a job title or your dates into a skills list.
• Keep text as text. Do not put your skills or contact details in an image or a chart. A logo or a skill bar is invisible to the parser and adds nothing for the reader.
• Write dates consistently, as month and year ("03/2024 - 09/2026" or "Mar 2024 - Sep 2026"). Parsers compute your years of experience from them, and federal reviewers need them anyway.
• Send the file type the form asks for. A text-based PDF or a Word document both parse well in current systems; a scanned PDF does not.
• Use the posting's words for the same thing. If a posting says "Siemens NX" and you wrote "Unigraphics", a recruiter's search for NX may miss you. Use the current name, and add the older one in brackets if it helps.
• Answer the screening questions truthfully and consistently with the resume. A "yes" to "Do you hold an active Secret clearance?" with no clearance on the resume invites a closer look, not a faster one.

None of this requires a special "ATS template". A clean, single-column document that says plainly what you did, with the tools named as the postings name them, parses well and reads well. If you want help producing one, our job search tools page lists the resume builders and services we point applicants to, with what each does.

13. Degrees, portfolios, transcripts and cover letters

60.1% of postings name a bachelor's degree and 24.1% a master's degree. The split by role is sharp: 73% of postings with "engineer" in the title name a bachelor's degree, against 7% of technician, machinist and inspector postings. A large share of space work is open to people without a four-year degree, provided they can show the skills and certifications; engineering work mostly is not, unless years of directly relevant experience stand in for it.

On the resume, education goes near the top for students and recent graduates and near the bottom for everyone else. List the degree, the school, the year and, for engineering roles, the specialty and any relevant coursework or thesis. A grade point average is worth including when it is strong (3.5 or higher on a 4.0 scale) or when a posting asks for it; internship postings sometimes do.

Portfolios are named in 1,099 postings (5.9%), more often than cover letters. For design, analysis and software roles, a portfolio link in the header (a personal site, a GitHub profile, a PDF of project write-ups) lets a hiring manager see your work in a minute. Keep it focused: three to five projects, each with the problem, what you did, the tools and the result, with photos of hardware where you can share them. Check every image and file for anything export-controlled or confidential before you publish it; a portfolio that leaks a former employer's technical data is an instant rejection at a company that lives under ITAR.

Transcripts appear in 150 postings (0.8%), 90 of them internships, student or new-graduate roles. Have an unofficial copy ready as a PDF before you start applying.

Cover letters appear in only 215 postings (1.2%). When a posting asks for one, write it, keep it to a few short paragraphs and make it about the role: why this program, which of your projects is closest to its work, and the one thing in your background the resume cannot show. When a posting does not ask, put the time into tailoring the resume instead.

14. Internships, new graduates and career changers

Space internships are competitive, and they are also how most of the industry's engineers got in. Our space internships page lists the internships and co-ops currently open by employer and field. Their resumes face the same first screen as everyone else's: of the 996 internship, co-op, student and new-graduate postings on our board, 605 (61%) name U.S. citizenship, so a student's citizenship or permanent residency line matters just as much.

For a student, the experience section is usually projects. Many space employers recruit from student teams (rocketry, CubeSat and satellite teams, rover and robotics competitions, Formula SAE, design-build-fly), and they read team experience as real engineering when it is written like engineering. Name your subsystem and your role, the hardware you designed, built or tested, the tools, and a result: a successful launch, a passed vibration test, a requirement you verified, a failure you diagnosed. "Propulsion lead, university liquid rocket team: designed a pintle injector in Siemens NX, ran 14 cold-flow tests, raised measured discharge coefficient from 0.61 to 0.74" tells a reviewer more than a semester's grades.

New graduates without a team or internship can still compete by building something small and finishing it: a sensor payload on a high-altitude balloon, an attitude-control simulation in Python, a test fixture, an open-source contribution to flight software or a mission analysis tool. The point is evidence that you can take a technical problem from start to finish, which is what the first year on a space team demands.

Career changers bring something students cannot: years of professional practice. The task is translation. A manufacturing engineer from automotive already knows statistical process control and production ramps; an IT administrator already knows the Linux, networks and security controls that ground systems run on; a power-plant technician already knows high-pressure systems, procedures and lockout. Rewrite your bullets in the vocabulary of the space postings in sections 4 to 10, name the standards and tools you share with them, and say plainly in your summary which kind of space role you are aiming at. Our page on space jobs with no experience lists the roles that hire people new to the industry.

15. Writing bullets that prove you built real things

Space hiring managers read a resume for one thing above all: evidence that you have made hardware or software work under real constraints, and that you know how you know it worked. SpaceX puts it bluntly in the "preferred skills" of some of its postings: "Evidence of exceptional ability". The word that matters is evidence.

A bullet that provides it has four parts:

1. What you did, with a strong verb: designed, built, tested, wrote, ran, led, cut, qualified.
2. To what, named specifically: the subsystem, part, code, test or process, with its scale.
3. How, with the tools and methods the postings name.
4. The result, measured: a margin closed, a time cut, a failure found, a test passed, a cost saved.

Compare the weak and strong versions of the same work:

Thermal Desktop, by the way, appears in 196 postings; it is the kind of specific name a strong bullet carries naturally.

A few further habits make bullets stronger:

• Lead with the most impressive result in each role. Reviewers read the first two bullets of a job and skim the rest.
• Keep each bullet to one or two lines. If it needs three, it is two achievements.
• Use numbers you can defend in an interview. Space interviews go deep on resume details; anything you write may become a 20-minute technical question.
• Never include controlled or confidential data. Describe work at the level a public conference paper would. "Designed injector for a 5,000 lbf engine" is fine; drawings, test data files and program code names usually are not.

16. A sample one-page layout

Putting the sections together, here is how a one-page resume for an early-career mechanical engineer applying to a satellite manufacturer is laid out. The same order works for most space roles; only the tools and the evidence change.

Header. Name. City, state. Phone. Email. Portfolio link. Then: "U.S. citizen". If you hold a clearance, add it on the same line.

Summary (two lines). "Mechanical engineer focused on spacecraft structures and mechanisms; two years of design and test in Siemens NX and NASTRAN, from CubeSat structures to vibration qualification."

Experience. Most recent first, unless an older role is far more relevant. For each: title, employer, city, month and year to month and year, then three to five bullets in the four-part form of section 15, the strongest first.

Projects. For a student or early-career engineer, the one or two projects that best show the work the posting describes: team, subsystem, role, tools, result.

Skills. Grouped and specific: "CAD: Siemens NX (3 years), SolidWorks. Analysis: NASTRAN/Femap, ANSYS Mechanical, hand calcs to NASA-STD-5001. Programming: Python (data reduction, test automation). Manufacturing: GD&T (ASME Y14.5), sheet metal and machined part design, DFM reviews."

Certifications. Only real ones, with issuer and year.

Education. Degree, school, year, specialty; thesis or capstone in one line if relevant.

Everything on the page answers one of two questions a space screener asks: may we hire this person, and have they done this kind of work before. If a line answers neither, it can usually go.

17. A checklist before you apply

Run through this list for each application. It takes ten minutes and catches most of what costs space applicants an interview.

1. Header: name, city and state, phone, email, LinkedIn or portfolio, and one line with citizenship or permanent residency and any active clearance.
2. Summary (optional): two lines saying what kind of space role you are aiming at and the two or three strongest things you bring to it.
3. Tools named the way the posting names them: the exact CAD system, analysis tools, languages, test software and standards, each attached to work you did.
4. Standards and certifications in their own section, with issuer and year: IPC, AS9100, Six Sigma, ASQ, FAA, welding, NDT, PMP, Security+.
5. Bullets with results, measured, at the level of detail you can discuss for twenty minutes.
6. One column, standard headings, text-based PDF or Word, consistent month and year dates.
7. For federal roles: two pages at most, month and year plus hours per week on every job, series and grade for federal jobs, the announcement's own words for each specialized experience.
8. For internships: school, expected graduation, relevant coursework and team projects; an unofficial transcript ready.
9. Portfolio checked for anything export-controlled or confidential.
10. Screening questions answered consistently with the resume.

Tailoring does not mean rewriting. Keep a complete master resume, then for each application reorder bullets so the most relevant come first, adjust tool names to the posting's, and trim what does not serve this role. On our board, every job page shows the posting's full text, which makes it easy to check the exact words an employer used.

18. Frequently asked questions

How long should a space industry resume be? One page for students and early-career applicants, two pages for experienced engineers and technicians. Federal resumes submitted through USAJOBS may not exceed two pages since 27 September 2025. Longer is rarely better: reviewers read the first page closely and skim the second.

Should I put my citizenship on my resume? For U.S. space roles, yes, if you are a U.S. citizen or permanent resident. 63.3% of the postings we measured name U.S. citizenship and 33.0% name ITAR. One plain line in the header ("U.S. citizen") answers the question every screener of an export-controlled role has to ask.

Do space employers really screen resumes with software? They receive them through applicant tracking systems (Workday is the most common among the employers we read) that parse resumes into searchable profiles. Automatic filtering mostly comes from the application's screening questions, such as work authorization and clearance. A clean, single-column resume that names tools the way the postings do parses well and is easy for the recruiter to find.

Which programming language should a space engineer learn? Python. It is named in 25.9% of all space postings we read, including 61% of software, 64% of guidance and control, 47% of test and 29% of propulsion and electrical roles. C++ follows for flight software (55% of software postings) and MATLAB with Simulink for guidance and control (50% and 31%).

Is a degree required for space jobs? For engineering roles, usually: 73% of postings with "engineer" in the title name a bachelor's degree. For technician, machinist and inspector roles, rarely: only 7% do, and those roles value certifications and experience instead (IPC soldering, welding, FAA, NDT, AS9100 work).

What certifications help most? It depends on the role family. Lean Six Sigma and AS9100 experience for manufacturing and quality (each named in 24% of those postings), IPC J-STD-001 for technicians (11%), PMP for program management (415 postings), Security+ or the DoD 8570/8140 baseline (316 postings) or CISSP (188) for cleared IT and cyber roles, and an FAA Airframe and Powerplant certificate for some launch and test technician roles.

Should I write a cover letter? Only when the posting asks for one, which 1.2% of the postings we measured do. Spend the time tailoring the resume instead, and keep a short letter ready for the roles that ask.

Can I apply to space jobs as a non-U.S. citizen? Yes, but read each posting's export-control language. Some U.S. roles are open to anyone who can be granted an export license, and many space employers outside the United States hire internationally. Our ITAR and clearance guide explains the rules and the exceptions.

19. How we measured

On 3 November 2026 we read every open role in SpaceJobs.Now's job feed: 18,507 postings, collected from the employers' own job boards (their applicant tracking systems' public feeds, and USAJOBS for federal roles) by the same pipeline that builds this site's job pages. For each posting we decoded the text and searched the title and the full text for the requirements, tools and standards named in this guide, counting a posting once per term however many times it repeats the word. Role families were assigned from the words in the posting's title (for example "software", "developer" or "DevOps" for software; "propulsion", "engine" or "combustion" for propulsion), so one posting can belong to two families and some postings belong to none.

Two limits are worth knowing. First, a posting that does not name a requirement may still expect it: an engineering role rarely spells out that it wants an engineering degree. The figures are therefore the share of postings that name something, a lower bound on how often it is expected. Second, the board covers the space employers we track, about 150 of them, weighted toward the United States; it is a large sample of the industry's open roles, not all of them.

The counts behind every figure, including the full table by role family, are kept with the research for this guide and refreshed when the guide is updated.