Red Canyon’s Secret Filter for Its Eight Engineering Hires

The Screening Gauntlet

Red Canyon Software has eight engineering roles open as of September 2026, each gated by a technical screen that demands proven embedded flight heritage. The company's selective hiring process emphasizes proven embedded software experience and cultural alignment, targeting engineers who have already built software that flies.

The hard gate is citizenship. U.S. citizenship or permanent residency is non-negotiable, driven by ITAR and export-control regulations that govern every contract the company holds. Beyond that, the technical baseline is explicit: at least five years of embedded software development experience, with relevant experience accepted in lieu of formal education. The language requirement is narrow: strong C/C++ for embedded systems, with a stated preference for softcore processor environments. That preference points directly at the LEON3 architecture, which runs the RTEMS real-time operating system. Candidates must show they have integrated, configured, and deployed RTEMS on LEON3 hardware.

SpaceWire is the next filter. The Embedded Software Engineer (SDR Development) role required experience implementing and testing SpaceWire protocols and cores in FPGA environments. The work involved designing embedded C/C++ for LEON3 softcore processors, architecting autoboot mechanisms for FPGA and soft-processor initialization, and integrating SpaceWire alongside other communication interfaces. In practice, the screen selects for engineers who have already crossed the hardware/software/firmware boundary.

The "plus" column reveals where Red Canyon's actual mission risk lives. Background in space or defense industries is explicitly valued. So are Ethernet and CAN interfaces in FPGA and embedded contexts, FPGA toolchains and SoC design principles, and fluency in the alphabet soup of space protocols: CCSDS, ETSI, ECSS. Spacecraft telecommunications terminology, SDR architectures, and radio communications concepts appear alongside NASA and ESA software standards (ECSS, NASA-STD-8739), NASA-STD-1006, and encryption best practices. The final listed requirement — "strong problem-solving skills and adaptability across HW/SW/FW boundaries" — describes the daily reality of a flat organization that maintains low overhead by expecting every engineer to operate across the full stack.

First-party board data from Zero G Talent confirms eight active engineering roles as of September 2026, including Senior Navigation Engineer, Navigation Engineer III, Senior Systems Engineer IV, Flight Software Engineer, Senior GNC Engineer, and Principal Software Systems Engineer, reflecting the seniority the screen targets. The screen measures whether a candidate has already built the kind of software that flies and whether they can do it again inside a team that ships flight code without layers of management between the engineer and the spacecraft.

Eight Roles, Three Domains

Red Canyon's current hiring slate comprises eight distinct engineering positions tied to specific mission sets across NASA, Department of Defense, and commercial programs. The roles cluster around three core domains: flight software and guidance, navigation and control (GNC), spacecraft navigation, and systems engineering for satellite operations and cybersecurity.

Flight Software Engineer

The most recurrent opening appears in multiple variants (full-time, contract, and remote), but the core requirement remains consistent: embedded software development for spacecraft flight computers. Listings emphasize C++ and Linux proficiency, with explicit calls for experience developing and testing flight software that runs on radiation-hardened processors. Candidates must demonstrate fluency in real-time operating systems, fault-tolerant design, and the full software lifecycle from requirements through on-orbit support.

Senior GNC Engineer

This contract role targets engineers who design and validate guidance, navigation, and control algorithms for spacecraft. The posting seeks experience with orbital mechanics, attitude determination, and control law implementation, skills that feed directly into lunar proximity operations and planetary landing sequences. First-party data lists this as a contract position; the technical bar implies prior flight heritage on missions with autonomous navigation or formation-flying requirements.

Principal Software Systems Engineer

This contract role bridges software architecture and systems engineering. The title signals responsibility for defining software interfaces, managing integration across flight and ground segments, and ensuring compliance with NASA or DoD standards. The "Principal" designation suggests the hire will lead technical reviews and mentor junior engineers on multi-program efforts.

Senior Systems Engineer IV

This contract position supports a space weather satellite mission operations program. The description highlights satellite operations, command & control systems, and hybrid cloud infrastructure, a blend of traditional ground systems and modern DevSecOps practices. The role demands fluency in both legacy C2 frameworks and containerized deployment pipelines, reflecting Red Canyon's push to modernize mission operations centers.

Senior Navigation Engineer

Based in Westminster, Colorado, this full-time role sits on a team "leading humanity back to the Moon." The posting seeks a spacecraft navigation engineer ready to advance the state of the art in orbit determination, maneuver planning, and deep-space tracking. First-party board data confirms the salary band and location; the emphasis on lunar missions aligns with Red Canyon's work on NASA's Commercial Lunar Payload Services and Artemis-adjacent programs.

Navigation Engineer III

The mid-level counterpart to the senior role, also in Westminster, carries similar mission context but targets engineers building flight heritage. The "III" grade typically maps to 5–8 years of experience with operational navigation software, filter tuning (Kalman, batch least-squares), and anomaly resolution during mission operations.

Network Security Engineer (Cyber Focus)

On a contract basis, this role stands apart from the flight software cluster. It calls for a "high-caliber Network Engineer with a specialty in cybersecurity" to protect ground systems and mission data. The posting's language, "take ownership of your job and responsibility for your actions," mirrors the cultural markers Red Canyon repeats across listings. With increasing DoD scrutiny on supply-chain security, this hire likely supports CMMC compliance and zero-trust architecture rollouts across classified and unclassified networks.

Remote Satellite Systems I&T Engineer

This full-time remote position seeks a senior/principal engineer for integration and test (I&T) of satellite systems. The description emphasizes functional verification and validation for aerospace projects, requiring hands-on experience with hardware-in-the-loop testbeds, environmental testing campaigns, and anomaly resolution during assembly, test, and launch operations (ATLO). The remote designation is notable for a discipline traditionally tied to cleanrooms; it suggests Red Canyon has invested in distributed test infrastructure or is staffing for programs where I&T occurs at partner facilities.

Across all eight roles, two threads dominate: embedded flight software heritage and direct experience with NASA or DoD mission assurance processes. The contract-heavy mix (five of eight) reflects program-specific funding cycles, while the Westminster cluster for navigation roles signals co-location with a customer or test facility.

What Red Canyon Builds

Red Canyon Engineering & Software has spent a quarter-century building the software and systems that fly on missions ranging from Mars landers to commercial crew vehicles. Founded in 2000 and headquartered in Denver, the 51-to-200-person firm holds SBA HUBZone and Service Disabled Veteran Owned Small Business certifications. Its client roster reads like a directory of the U.S. space enterprise: NASA, NOAA, NREL, JPL, the Defense Department, plus prime contractors Lockheed Martin Space, Raytheon, SpaceX, Blue Origin, Sierra Space, Ball Aerospace, and Maxar. The company's motto — "exploring other planets, improving our own" — captures a portfolio spanning human spaceflight, planetary science, Earth observation, and a growing commercial segment that now accounts for roughly 20 percent of revenue, according to CEO Barry Hamilton in a 2023 NASA technology transfer feature.

The technical spine of that portfolio is NASA's core Flight System (cFS), an open-source flight software framework the agency developed over two decades. Hamilton described cFS as a "highly customizable ecosystem for spacecraft development" that lets Red Canyon build reusable application modules — guidance, navigation, and control; sensor data handling; command ingestion — that plug into different hardware platforms without rewrite. That architecture is why the company's tech stack centers on C and C++, VxWorks, SpaceWire, FPGA design, and embedded Linux, and why its engineers move fluidly between flight software development, independent verification and validation (IV&V), hardware-in-the-loop simulation, and spacecraft assembly, integration, test, and evaluation (AIT&E). The same cFS fluency underpins Red Canyon's work on the Dream Chaser spacecraft, where it holds a two-year SNC subcontract for flight software IV&V, and on commercial programs like Sidus Space's LizzieSat constellation, where the firm handles design, development, integration, and deployment.

"Companies using cFS can start with less capital for flight software development costs and get to space quicker, achieving a quicker return on investment," Hamilton told NASA in 2023. Red Canyon has turned that advantage into a repeatable corporate culture: a library of validated cFS modules, automated testing pipelines, and simulation environments — MarsFlight, VenusFlight, LunarSim — that let new hires contribute across multiple programs within weeks.

The mission list explains the depth of required expertise. Red Canyon has delivered software or systems for Artemis I and II, the Human Landing System, Orion's EFT-1, and the Gateway program; for Mars missions including Perseverance, InSight, MAVEN, Phoenix, MRO, and Odyssey; for outer-planet missions Europa Clipper, Lucy, Juno, and Psyche; for small-body missions OSIRIS-REx, Stardust, Deep Impact, and Genesis; and for Earth-science platforms GOES-R, MethaneSat, WorldView Legion, and the Wallops Range contract awarded in mid-2026. Each domain imposes distinct constraints: radiation-tolerant FPGA logic for deep space, deterministic real-time response for crewed vehicles, high-throughput telemetry processing for Earth observation, and rigorous IV&V artifacts for NASA human-rating reviews. The company's capabilities page lists the resulting technical specialties explicitly: Flight Software, IV&V, Mechanical Design, Structural Analysis, Systems Engineering, FPGA Design and Verification, GNC, Spacecraft Operations, Telemetry Analysis, Dynamic Simulators, Hardware-in-the-Loop, and AIT&E.

Current active projects sharpen the picture further. Internal job board data and company updates show work on UST-Lite software-defined radio development, SpaceWire core implementation, embedded flight software for satellite platforms, command and control system integration, automation orchestration across hybrid cloud (AWS GovCloud, Azure, Kubernetes, Terraform, Ansible), space weather instrument and observatory development, and networking and data management architecture. These are not research prototypes; they are flight-bound or operational systems. The presence of React, JavaScript, SQL Server, Jira, Cucumber, Cypress, and Zephyr Scale in the stack reflects the ground-system and DevOps layer that wraps every flight build: test automation, configuration management, and mission operations tooling that must meet the same traceability standards as the onboard code.

Lockheed Martin's 2019 Outstanding Small Business award and the 2017 SBA Region 8 Subcontractor of the Year honor signal that Red Canyon delivers on the documentation, configuration control, and process rigor that prime contractors and NASA centers audit. That regulatory surface (ITAR, EAR, DCAA-compliant accounting, NASA Class A/B/C mission assurance) is why the screening process weighs proven embedded experience and cultural alignment as heavily as raw coding ability. An engineer who has never worked a flight software review board, never written a requirement that traces to a verification test, or never debugged a timing fault on a VxWorks target will not clear the filter, no matter how strong their GitHub profile.

The Application Journey

Red Canyon's board presence shows six salaried roles currently listed (the six roles detailed above). The main theme identifies eight engineering openings total. What the public record does not show is a step-by-step map of Red Canyon's internal hiring funnel: no published interview rubric, no named hiring managers, no timeline from application to offer. That silence is typical for companies building safety-critical flight software; the process itself is often treated as proprietary operational detail.

What can be inferred comes from the work itself. Red Canyon builds applications on cFS, the framework originally developed at Goddard Space Flight Center to run everything from high-altitude balloons to lunar-orbiting spacecraft. The company's modules support Sidus Space's LizzieSat constellation and feed into the lunar Gateway program. Engineers here write code that must survive radiation, thermal cycling, and the unforgiving physics of launch and on-orbit operations. A hiring process that filters for proven embedded experience — bare-metal C/C++, RTOS fluency, hardware bring-up, fault-tolerant design — is not a preference; it is a mission requirement.

Candidates should expect the technical screen to go deeper than algorithm puzzles. The domain demands fluency with flight software architecture: command and data handling, guidance navigation and control (GNC) loops, fault detection isolation and recovery (FDIR), and the cFS application layer (apps, libraries, and the executive services that bind them).

Cultural alignment is assessed in parallel, not as a separate "values interview" but woven into how candidates discuss trade-offs, own past failures, and communicate across disciplines. Red Canyon's CEO Barry Hamilton has emphasized building "a corporate culture around cFS technology, making it possible to quickly train employees and work effectively across projects." That implies a process that weighs teachability and cross-project mobility alongside depth.

The offer stage, when reached, reflects the market for cleared, flight-heritage engineers. Board data shows hourly roles (Flight Software Engineer, Senior GNC Engineer; Principal Software Systems Engineer) alongside salaried bands, a signal that Red Canyon structures engagements for both long-term programs and surge support. Candidates should prepare for a background check and, for many positions, a government security clearance initiation or transfer.

No public source documents Red Canyon's exact sequence, panel composition, or decision criteria. The outline above synthesizes the standard aerospace embedded software funnel with the specific technical gravity of Red Canyon's cFS-centric, flight-heritage workload. Applicants who treat the process as a generic software interview will not advance. The filter is built for the domain.

The Non-Technical Filter

The research record on Red Canyon Software's explicit cultural assessment process is thin. None of the available sources (whether the CEO's public interviews, the company's project disclosures, or the job-board telemetry) detail a formalized culture screen, a values rubric, or a structured peer-interview framework. What exists instead is a pattern: a founder-led, tightly held company pursuing high-stakes, long-horizon technical programs where team cohesion isn't optional. In that context, cultural alignment functions less as a checklist item and more as a survival trait.

Red Canyon's project portfolio — autonomous navigation, guidance/navigation/control (GNC), flight software, and systems engineering for missions that cannot be patched post-launch — selects for a specific temperament. The board data shows six salaried roles spanning the same six roles. These are not siloed positions; they intersect on the same flight stacks, the same verification campaigns, the same anomaly-resolution calls.

Barry Hamilton, Red Canyon's CEO, has described the company's origin as building from the ground up with a tight structure. That phrasing signals a culture that prizes accountability over hierarchy and ownership over execution-only mindsets. In a company where leadership's net worth rides on technical outcomes, the cultural filter implicitly favors engineers who think like stakeholders: people who flag schedule risk early, who document for the next shift, who treat a requirement ambiguity as their problem to resolve, not a ticket to bounce.

The non-technical filter likely operates through conversation, not ceremony. Candidates for the Senior Navigation Engineer role or the Principal Software Systems Engineer role will meet future peers who have lived through integration-test cycles. Those peers are evaluating: Does this person listen before coding? Do they admit uncertainty? Can they disagree without fracturing the room? The board data's salary bands reflect a market that pays for judgment as much as syntax.

What the research doesn't show is any evidence of a "culture fit" screen that masks homogeneity. The project scope demands multidisciplinary collaboration across software, systems, and operations. A filter that screens for a single personality type would undermine the very resilience the company's technical roadmap requires. The more plausible model: a filter for communication clarity, shared ownership, and mission-first prioritization, traits that surface in how a candidate describes a past failure, not in how they answer a values questionnaire.

For applicants, the takeaway is practical. Prepare to discuss a time you caught a spec error late, a time you rewrote someone else's module because the interface was ambiguous, a time you argued for a simpler design and lost, and what you did next. Red Canyon's work doesn't tolerate silent heroes or loud geniuses. It rewards engineers who make the team's output better than the sum of its parts. The screen isn't published. It's embedded in the questions your future teammates ask when you're not in the room.

How to Stand Out

Lead with flight heritage, not just language fluency. Every listed role (navigation, GNC, flight software, systems) sits on the critical path of a vehicle that must operate without ground intervention. The Mars helicopter Ingenuity proved the model: a smartphone-class processor spinning rotors at 2,500 rpm in atmosphere 1% of Earth's, autonomously correcting for gusts and sensor noise. Red Canyon's customer base (ULA, NASA Artemis, commercial lunar landers) demands the same discipline. If you have shipped code that flew — on a CubeSat, a sounding rocket, a high-altitude balloon, or a certified avionics box — put the mission name, your subsystem, and the outcome in the first bullet of your resume. "Wrote C++ for attitude determination" is noise. "Implemented EKF-based attitude estimator for NASA's LLCD mission; survived launch vibration and on-orbit thermal cycling" is signal.

Show the toolchain, not the tutorial. The board lists hourly rates for Flight Software Engineer and Senior GNC Engineer, and for Principal Software Systems Engineer, rates that imply immediate productivity. Be ready to discuss your daily environment: which RTOS (VxWorks, RTEMS, FreeRTOS, bare metal), which build system (CMake, Bazel, custom), which static analysis (Polyspace, Coverity, LDRA), which test framework (GoogleTest, Unity, custom HWIL). If you have configured a DO-178C or ECSS-Q-ST-80 qualification artifacts pipeline, say so. If you have only run ros2 run on a desktop, acknowledge the gap and describe the nearest safety-critical project you have touched.

Quantify the constraints you have owned. Navigation and GNC roles live inside tight error budgets. The Ingenuity team had to spin rotors at 2,500 rpm while managing a 100,000-foot-equivalent atmosphere and -130°F nights. Translate your experience into comparable terms: update rate, latency budget, processor margin, memory footprint, fault-detection coverage. "Reduced cycle time from 20 ms to 8 ms on a LEON3FT by rewriting the matrix library in fixed-point" beats "optimized flight software."

Demonstrate systems thinking across the interface. Senior Systems Engineer IV and Principal Software Systems Engineer roles imply you speak fluently with propulsion, structures, thermal, and operations. In interviews, walk a requirement from top-level mission success criteria down to a unit test case. Reference the 48-launches-per-year cadence ULA and the Cape are targeting; software that cannot be reused or rapidly reconfigured becomes a bottleneck. If you have participated in a software reuse review or a model-based systems engineering (MBSE) flow with Cameo or Capella, surface it.

Prepare for the cultural filter with concrete collaboration stories. The space industry's shift from government-only to billionaire-driven commercial cadence (SpaceX, Blue Origin, ULA) means teams now ship on commercial timelines with government rigor. Describe a time you resolved a conflict between a schedule-driven program manager and a safety-driven quality engineer. Describe a time you onboarded a junior engineer into a DO-178C flow without slowing the sprint. Red Canyon's scale means you will wear multiple hats; show you have done so without dropping the safety hat.

Target the geography honestly. Three roles list Westminster, CO; three list "United States" (likely remote-eligible). If you are in Colorado, emphasize it; commute reliability matters for HWIL lab days. If you are remote, have a home-lab story: a hardware-in-the-loop bench, a real-time target, a network latency profile you measured. The Cape Canaveral launch ecosystem runs on Eastern Range schedules; show you can align your sprint cadence to a range window.

Close the loop on the application. The board shows roles added in the past 7 days. Apply to the specific requisition, not a general portal. In the cover letter, name the role, cite one Red Canyon mission (e.g., "your GNC work on Vulcan Centaur's upper stage"), and map two of your flight artifacts to the job's stated constraints. No fluff. The screen is built to discard generic packets, and the mission profile it protects is the one that gets your code to orbit.

Working in space? Zero G Talent tracks the openings: see every open Journey role, browse space jobs, openings at Red Canyon Software, and the people building the field.