1. LandOffer
  2. Blog
  3. All articles
  4. AIAA Career Center Review for Software Engineers: Aerospace Roles Beyond the Big Job Boards

Job search

AIAA Career Center Review for Software Engineers: Aerospace Roles Beyond the Big Job Boards

Review public aerospace software searches, distinguish FPGA and mixed system descriptions, and verify employer availability before preparing an application.

9 min readLandOffer team

AIAA Career Center is worth checking if you want software work in an aerospace setting and are willing to read beyond the job title. Our public searches found desktop application development, software testing and internships alongside adjacent engineering work. Treat the board as a source of leads: verify the deliverable, work location and original employer status before investing in an application. One software listing we followed still appeared on AIAA after its employer page said it had been filled.

This review covers anonymous browsing on October 13, 2026: two keyword searches, four detailed listings and one employer handoff. We also read the board's public help documentation. We did not create an account, upload a resume, subscribe to alerts or submit an application. Availability and listing details can change; the examples below record what those pages showed during this review.

LandOffer publishes this review and provides job-search tools. You can compare these leads with recent jobs on LandOffer.ai, using the same employer verification process. Neither a specialist board nor a broad search result establishes that a role is open or fits your background.

An engineer holding a job dossier stands between software and FPGA workbenches in a civilian aircraft hangar

AIAA's job-seeker page points readers toward its industry Career Center. This is separate from searching for employment at AIAA itself. The board gives an aerospace-oriented starting point, while individual employers define the work. Its homepage also includes academic, mechanical, electrical and production-related openings, so arriving through an aerospace association does not make every result a software vacancy.

That breadth can help an engineer who knows the work they want but has a short employer list. A desktop application team, an avionics consultancy and a laboratory internship can appear within the same discovery session. The benefit is finding organizations and responsibilities to investigate. We did not measure coverage against major boards or establish that the listings were exclusive to AIAA.

Keep your existing search if it already produces relevant employer-verified openings. AIAA adds value when its sector context introduces a team you would otherwise miss. It adds less when you need only fully remote product engineering and every interesting lead requires laboratory or office attendance. Set a location and work-type constraint before searching so you can discard unsuitable leads while their descriptions are still in front of you.

Search for a deliverable, then read the whole result

Entering software in the public search produced 116 results in our session. The visible list included software developers, test engineers, undergraduate and graduate internships, systems engineering, mechanical design and metallurgy. This count describes one dated search, not a stable inventory or a measure of search accuracy.

The interface showed a keyword field, a location field, a radius selector and a separate alert control. We left alerts off. The Internships navigation link used the keyword intern; follow it by checking the individual posting's education level and employment terms. A title mentioning summer is insufficient to distinguish an undergraduate internship from a graduate or high-school opportunity.

Start with the system you want to build: desktop applications, test automation, embedded software or data services. Read what the team asks the engineer to design, implement and verify. A mention of software within a mechanical or systems description may reflect collaboration with developers rather than ownership of production code. Conversely, an unfamiliar department label can still lead to substantial software development.

The results also displayed a Free Resume Review advertisement, visually separate from the job cards. Its claim about unseen applications was advertising copy, not a hiring statistic verified in this review. We did not use that service or the listings' AI Summary & Insights feature. The comparisons below come from the full descriptions and observed employer page.

A desktop software lead with specific conditions

The Sandia Code Management System team listing described desktop application design and implementation, software lifecycle practices, requirements, verification and change management. Its desired experience included production software, Rust, object-oriented languages such as C#, Java or C++, GUI development, version control and unit testing. Those details make it a software lead even though the board classified its job function as Research.

Preserve the required and desired sections separately. The required education-and-experience wording named a relevant bachelor's degree plus five years of directly relevant experience, or an equivalent combination. The desired section contained additional technical experience and a graduate-degree preference. A reader should not silently turn every desired item into a mandatory credential, or assume the equivalent route removes the need to demonstrate relevant work.

Location was explicit: the selected applicant must work onsite 100% of the time. General employer benefits elsewhere in the description mentioned flexible arrangements for many positions, but that broader paragraph did not change this role's requirement. A remote-only candidate can reject this lead before spending time matching the language list.

The posting also required the ability to obtain and maintain a DOE Q-level clearance with its stated caveat; its clearance section said US citizenship was required. This is a condition of the inspected opening, not a rule for all aerospace employment. We did not follow this posting to Sandia's original application system or verify that it was still accepting applications there. Its desktop responsibilities are documented on AIAA; current application availability at Sandia remains unverified in this review.

FPGA programming calls for different evidence

A separate FPGA search returned five results in our session. The Early Career R&D Electrical Engineer—FPGA Designer listing described register-transfer level (RTL) designs that can be synthesized into hardware, simulation testbenches, embedded electronics and laboratory troubleshooting. Desired experience included Verilog or VHDL, timing analysis, firmware validation and FPGA development tools. The relevant output is a hardware design and its verification, even though the description uses the word programming.

Compare the portfolio with the FPGA work the posting actually describes. C# desktop delivery and unit tests can establish useful engineering habits, but they do not by themselves show RTL design or timing analysis. Someone with HDL projects and lab experience has a different basis for evaluating this opening. Read the requested artifact before comparing familiar words such as debugging or testing.

This listing required a relevant bachelor's degree or an equivalent combination, onsite work and the ability to obtain and maintain its specified Q and SCI access. It placed the two-plus-years wording within desired experience. We retained that placement rather than converting “early career” into either a guaranteed beginner route or an invented minimum. Resolve the actual qualifications through the employer's current requisition.

A completed shortlist for one fictional engineer

Lee is a fictional candidate with six years of C# desktop development, a relevant bachelor's degree, unit-testing experience and responsibility for requirements and version control. Lee can consider Albuquerque onsite work, but has no professional HDL design or timing-analysis experience. This example compares technical evidence and known listing conditions; it does not decide clearance eligibility or predict selection.

Inspected lead Lee's supported overlap or gap Completed disposition
Sandia desktop software, AIAA 86230484 Desktop delivery and lifecycle work overlap; remaining qualifications and employer availability need confirmation Retain as a technical lead, with onsite and clearance conditions attached
Sandia FPGA designer, AIAA 86337793 No HDL, RTL or timing-design evidence for the core deliverable Set aside for this search rather than relabel desktop work as FPGA experience
Oliver Wyman aerospace developer, AIAA 86125399 The board describes software work, but the observed employer handoff says filled Archive the dated lead; do not prepare an application for that closed page

The result is a smaller, more usable shortlist. Lee has one lead to verify, one skills mismatch and one closed opportunity. The technical overlap, missing HDL experience and closed employer page each produce a different next action. If Lee changes the location constraint to remote-only, the desktop lead also leaves the shortlist because its description explicitly requires onsite work.

For the retained lead, Lee records a C# desktop release, a requirement linked to a unit test and a GUI defect investigated across components. These are illustrative examples of evidence to compare with the posted responsibilities, not extra Sandia requirements. The next step is to verify the original requisition and remaining conditions before tailoring a document.

A visible board notice links to an employer notice stamped Filled while a matching dossier is filed in an archive

Follow the employer handoff before tailoring

The Oliver Wyman Vector aerospace developer listing described Java or Python development, five-plus years of experience and familiarity with a DO-178C-driven process. Its card said Washington and onsite, while the body described Greater Seattle and hybrid work. We followed its public APPLY button, which opened a Marsh employer page in a new tab without submitting information.

That employer destination explicitly said the job had been filled. The completed verification record was therefore: board ID 86125399; employer URL containing R366737; observed status filled; disposition archive. The board's recent-looking age did not override the employer's notice. We did not determine the closing date or why the board remained visible.

This changes how much effort the lead deserves. Its description can teach you about an aerospace software team, but it is not an active opening we can recommend applying to. Do not continue into a resume-upload tool merely because the employer page offers other discovery features. Search a fresh requisition if the organization still interests you.

A second example requires a different outcome. The Voyager Systems Engineer—Aerospace page began with propulsion systems engineering, then included another introduction describing software engineering and software development duties. The card and body also displayed different salary ranges. We could not establish which description defined the intended vacancy. Our record marks it unresolved instead of selecting the software passage and calling it a match.

Save the title, board ID, original employer link and exact conflicting field. Check the current employer requisition or seek clarification through its normal recruiting route before proceeding. A duplicate-looking passage is a reason to verify, not evidence that every systems-engineering job is software development. The same treatment should apply to conflicts found through LandOffer or any other discovery source.

Decide separately whether to expose a resume

The board's help documentation describes an optional resume bank. It says employers can view profile information while name and contact information are hidden, and candidates can review contact requests before deciding whether to be considered. It also says a resume need not be listed in the bank to use it for supported online applications.

That description is narrower than complete anonymity. A distinctive project, employer history or small-team role can identify someone even without a name. Decide which details you want searchable, and inspect the current account controls before choosing visibility. We did not test those settings, upload a document or verify how an employer sees a profile. Public browsing provided the evidence for this review without those actions.

AIAA is useful when you want sector-specific leads and can assess the actual engineering work. Our sample found substantial software responsibilities, an adjacent FPGA role, a closed employer destination and a mixed description that needed clarification. Those are reasons to retain source-specific notes rather than treating the search result as a finished shortlist.

Use your next session to retain one lead whose original employer page confirms current availability and whose deliverable fits your evidence. Record its location, required qualifications and any unresolved condition. You can widen discovery through recent LandOffer.ai jobs, applying those same checks. Once the employer confirms an open role and you have checked its required conditions, use the saved record to prepare the requested application materials.

Sources and Further Reading