LeoLabs, Slingshot, ExoAnalytic and the New SDA Career Track in 2026

Why Space Domain Awareness has become a serious career track

Space Domain Awareness, usually shortened to SDA, is no longer a narrow government specialty hidden inside traditional aerospace programs. It has become a distinct technical and operational field connecting radar engineering, optical astronomy, orbit determination, data fusion, software, artificial intelligence, mission operations and national security.

The change is visible in the companies building commercial sensing networks and decision tools. LeoLabs operates a global radar network focused strongly on low Earth orbit and very low Earth orbit. Slingshot Aerospace combines sensor data, orbital intelligence, simulation, anomaly detection and coordination tools. ExoAnalytic Solutions operates a large optical telescope network that supports tracking and orbit determination for high-altitude objects, especially in geosynchronous orbit. The government counterpart is represented by organizations such as the U.S. Space Force's 18th Space Defense Squadron, which integrates sensors and maintains operational awareness of the geocentric space environment. (leolabs.space)

For engineers and analysts, this creates a career map with more branches than the traditional launch vehicle or spacecraft design route. You can work on phased-array radar scheduling, astrometric image processing, covariance analysis, catalog maintenance, conjunction assessment, breakup detection, maneuver characterization, mission planning, secure data systems or operator-facing decision support.

The market has expanded because orbit has become more crowded, more dynamic and more commercially important. Large satellite constellations create more objects to track. Spacecraft maneuver more frequently. Operators need faster and more reliable warnings. Governments want independent commercial data sources, while commercial operators need tools that help them coordinate with other spacecraft owners.

This is why an SDA job in 2026 should not be understood as simply a job counting satellites. It is a role in an operational data pipeline where a sensor observation becomes an orbit estimate, an orbit estimate becomes a risk assessment, and a risk assessment becomes a decision.

A useful way to think about the field is to separate it into four layers:

• Sensing, including radar, optical telescopes, radio observations and space-based sensors.
• Estimation, including initial orbit determination, precise orbit determination, tracking, filtering and uncertainty modeling.
• Intelligence, including object identification, behavior analysis, breakup analysis and maneuver detection.
• Operations, including conjunction response, sensor tasking, mission coordination and decision support.

Different employers emphasize different layers. That distinction matters when choosing a degree, building a portfolio or evaluating an offer. A radar company may value signal processing and estimation more than spacecraft thermal design. A government operations unit may care about disciplined analysis, communication and shift readiness as much as numerical methods. A software-heavy startup may expect one engineer to move between Python notebooks, C++ services, cloud infrastructure and customer demonstrations.

The opportunity is real, but the field is specialized. Candidates who combine orbital mechanics with software engineering and operational judgment are more competitive than candidates who know only one piece of the puzzle.

The SDA career map: four employer environments

The most useful career map starts with the working environment rather than the job title. Titles vary widely. One company may advertise an orbital analyst, another may use space domain awareness engineer, and a third may call the same general function a mission analyst, astrodynamics engineer or space operations specialist.

The underlying work usually falls into four employer categories.

Commercial sensing and analytics startups

Companies such as LeoLabs, Slingshot Aerospace and ExoAnalytic Solutions are building products from proprietary sensors, software, algorithms and operational services. Their engineers often work close to the data source and close to the customer. A new radar site, telescope observation or tracking event can lead directly to a software change, algorithm test, operations procedure or product requirement.

Startup work tends to reward breadth. You may be expected to understand orbital dynamics, inspect raw measurements, explain a covariance issue to a customer and help write a test harness. The pace can be faster than at a large prime, but priorities may change as contracts, funding and customer requirements evolve.

Legacy aerospace and defense primes

Large primes generally provide more structured engineering processes, formal verification, established program management and clearer role boundaries. A systems engineer may own requirements and interfaces while a flight dynamics specialist owns estimation performance. A software engineer may work within a defined product team rather than across the entire mission.

The tradeoff is that the work can feel less immediate. You may spend longer in design reviews, documentation cycles, configuration control and formal test planning. That structure is valuable if you want experience with large government programs, safety-critical development and complex integration.

Government operations and research organizations

The 18th Space Defense Squadron is a government operational environment rather than a commercial product company. Its mission includes space catalog administration, sensor integration, launch and tracking support, maneuver detection, breakup identification, reentry assessment and spaceflight safety. The squadron operates as part of Space Delta 2 and supports a broader common understanding of the space environment. (ussf-cfc.spaceforce.mil)

Government roles emphasize mission assurance, continuity, clear decision-making and the ability to operate under policy, security and organizational constraints. Depending on the position, candidates may enter through military service, civilian government employment or a contractor supporting government operations.

Universities, laboratories and specialized research groups

Research-oriented roles focus more heavily on new estimation methods, sensor phenomenology, machine learning, uncertainty quantification, cislunar tracking or space weather. These positions may offer deeper technical specialization, but they often expect graduate-level training or a record of research and publication.

The career map is therefore not a simple ladder. It is a network. An orbital analyst can move into sensor fusion. A software engineer can move into mission operations. A radar specialist can transition into systems architecture. A military or contractor analyst can join a commercial provider after gaining operational context.

The best technology career paths in 2026 are increasingly cross-functional, and SDA is one of the clearest examples. The strongest candidates are not necessarily those with the most impressive job title. They are the people who can follow a measurement from collection to operational consequence.

LeoLabs: radar network engineering and the LEO problem

LeoLabs is one of the clearest examples of a commercial SDA company built around a specific sensing advantage. Its global radar network uses active electronically scanned array technology, pulse-Doppler radar and software-defined processing to provide all-weather coverage and rapid revisit for objects in low Earth orbit and very low Earth orbit. The company describes its network as capable of persistent tracking and rapid deployment, with transportable radar systems designed for high-interest objects. (leolabs.space)

That technical emphasis shapes the types of careers available.

An orbital mechanics engineer at a radar-focused company may spend significant time working with short observation arcs, measurement quality, radar cross-section effects, Doppler information and track association. The problem is not merely to calculate an orbit from clean textbook observations. The problem is to decide whether several imperfect observations belong to the same object, estimate the state and covariance, maintain custody through gaps and identify when a track is behaving unexpectedly.

Typical LeoLabs-adjacent roles

A candidate may encounter roles such as:

• Orbit determination engineer.
• Radar data processing engineer.
• Tracking and catalog analyst.
• Sensor scheduling engineer.
• Astrodynamics software engineer.
• Signal processing engineer.
• Space domain awareness mission analyst.
• Customer solutions engineer for orbital data products.

The work can be mathematically demanding. Engineers may implement or evaluate filters, propagate state vectors, model atmospheric drag, tune measurement weighting, analyze residuals and validate catalog updates. LEO creates special challenges because atmospheric drag can change rapidly with solar activity and because small objects can have short observation windows.

The software environment may include Python for analysis and prototyping, C++ for high-performance or operational components, SQL for data investigation and cloud services for scalable processing. A strong candidate should be comfortable moving between an algorithmic question and a production concern. It is not enough to show that a filter works in a notebook. The team also needs to know how it behaves when measurements arrive late, sensors disagree, objects maneuver or data volume spikes.

What makes radar work different

Radar provides information that differs from optical tracking. It can operate during daylight and through cloud cover, and it can provide range, range rate and angular measurements depending on the system. That does not make radar data automatically easy. Calibration, interference, clutter, propagation effects, scheduling constraints and object characteristics all affect the quality of the final estimate.

A useful portfolio project would simulate a radar tracking pipeline rather than only propagating a Keplerian orbit. Generate noisy range and range-rate observations, apply an extended Kalman filter or unscented Kalman filter, introduce a missed pass, then evaluate how the covariance grows and how quickly the next observation restores confidence.

For a candidate who enjoys physics, signal processing and production systems, a radar network company may offer one of the most technically direct routes into SDA. The work connects hardware, algorithms and operational outcomes in a way that is difficult to replicate in a purely theoretical project.

Slingshot Aerospace: data fusion, coordination and operational software

Slingshot Aerospace represents a broader SDA model. Its products combine sensor-originated data, orbital analytics, artificial intelligence, simulation and operational workflows. The company describes capabilities spanning near real-time tracking, orbit determination, conjunction assessment, anomaly detection, maneuver planning and multi-party coordination. Beacon is designed to help operators communicate and coordinate around conjunctions and planned maneuvers, while other products support simulation and decision-making. (slingshot.space)

This makes Slingshot particularly relevant to candidates who want to combine astrodynamics with software products and human operations.

A role in this environment may involve building services that ingest observations from multiple providers, normalize object identifiers, calculate relative geometry, rank conjunctions or present recommendations to operators. The engineering challenge is not limited to orbital mechanics. It includes data contracts, latency, access control, system reliability, user experience and explainability.

The shift from awareness to action

Traditional SSA tools often focused on displaying where objects were and whether a close approach might occur. Modern SDA platforms are moving toward a closed operational loop: sense, fuse, decide and act. That means the software must help a user answer questions such as:

• Is this observation associated with a known object?
• Is the apparent maneuver real or a measurement artifact?
• How does the predicted miss distance change under different force models?
• Which satellite operator needs to be contacted?
• What maneuver options preserve mission objectives while reducing risk?
• What evidence supports the recommendation?

The last question is essential. Operators will not trust an opaque model simply because it uses artificial intelligence. They need to understand the inputs, assumptions, uncertainty and consequences. An engineer who can explain model behavior to a mission director has a major advantage over someone who can only produce a score.

Skills that matter in a Slingshot-style environment

The technical stack can include Python, cloud-native services, geospatial visualization, time-series databases, APIs, containerized deployment and machine learning. Familiarity with Kubernetes, Docker, CI pipelines and observability can matter as much as knowledge of orbital elements for some roles.

That does not mean orbital mechanics becomes secondary. It becomes embedded in a larger system. A conjunction assessment service must understand coordinate frames, time standards, state vectors, covariance propagation and probability of collision. A maneuver planning tool must model burns, constraints and downstream effects. A behavior analysis system must distinguish between a planned maneuver, a natural perturbation and a catalog error.

Candidates who enjoy building tools for operators should study both the equations and the workflow. Try designing a small web application that loads two trajectories, displays relative motion in an appropriate frame, calculates closest approach, shows uncertainty and records the assumptions behind each result. The project demonstrates more than a static plot because it addresses the human decision process.

ExoAnalytic Solutions: optical tracking, GEO and persistent observation

ExoAnalytic Solutions is differentiated by its optical sensing network. The company says its ExoAnalytic Global Telescope Network is a large commercial network of ground-based optical sensors that produces astrometric and photometric data for high-altitude satellites and debris. Its ExoTrack service is aimed at GEO operators and uses a distributed sensor network to provide updated orbit information and conjunction warnings. (exoanalytic.com)

The career experience at an optical SDA company is therefore different from the experience at a LEO radar provider.

Optical tracking engineers work with images, line-of-sight measurements, photometry, star catalogs, observatory scheduling and weather-dependent collection. The job may involve detecting a faint object against a background, measuring its apparent position, matching observations across nights and maintaining a high-quality orbit for a GEO or highly elliptical object.

Why GEO changes the engineering problem

GEO objects move slowly relative to the observer, but slow apparent motion does not make the problem simple. The objects can be faint, closely spaced in angular position and difficult to distinguish. Long gaps between observations can produce ambiguity. Small changes in station-keeping behavior may matter operationally even when the object remains near the geostationary belt.

Optical systems also introduce a different measurement geometry. A telescope may provide right ascension and declination without direct range. The orbit determination process must infer three-dimensional state from line-of-sight observations collected over time. The quality of the result depends on timing accuracy, calibration, atmospheric conditions, star-field processing and the diversity of observation geometry.

A candidate interested in ExoAnalytic-style work should understand astrometry, coordinate transformations, image processing and batch orbit determination. Familiarity with OpenCV, scientific Python, least-squares estimation and statistical residual analysis can be helpful. For more advanced positions, experience with parallel processing, sensor fusion and photometric classification may be relevant.

The day-to-day reality

An optical SDA engineer may investigate why an object disappeared from a track, whether two detections belong to the same spacecraft, or why an estimated orbit has developed a growing residual pattern. They may tune a scheduler to increase observation value, validate a new camera configuration, compare orbit solutions from different sites or work with operators to understand a customer request.

The work is often more iterative than the public description suggests. A production issue may begin with a simple question about a catalog entry and lead into image metadata, telescope pointing, time synchronization, atmospheric conditions and estimation quality. The engineer needs patience and a habit of preserving evidence.

For people who enjoy astronomy, image analysis and long-baseline orbital behavior, ExoAnalytic can be an attractive path. It also demonstrates why SDA is not just a LEO debris field problem. GEO, highly elliptical and cislunar regimes require different sensors, models and operational concepts.

18 SDS and government SDA careers

The U.S. Space Force's 18th Space Defense Squadron is a central government counterpart to commercial SDA providers. The squadron is located at Vandenberg Space Force Base in California and is described as a premier Space Domain Awareness unit responsible for maintaining a continuous and comprehensive understanding of the space situation. Its mission includes command and control of the Space Surveillance Network and the integration of government, multinational and commercial sensor data. (petersonschriever.spaceforce.mil)

The government environment differs from a startup in purpose, authority and operating rhythm. The objective is not to sell a data product or grow a software platform. The objective is to maintain an operationally useful understanding of the space domain and support decisions affecting safety, security and mission assurance.

What orbital analysts may do

An orbital analyst or operations specialist may support:

• Space catalog administration.
• Launch detection and tracking.
• Observation association.
• Maneuver detection and characterization.
• Breakup identification.
• Reentry assessment.
• Human spaceflight support.
• Sensor planning and tasking.
• Operational reporting and briefing.

The 18 SDS role is not necessarily a research role. Analysts must often make timely judgments with incomplete information. They may compare observations from multiple sensors, examine an object's historical behavior, assess whether a new track represents a real event and communicate the result through established command channels.

The Space Force has also been modernizing SDA software. In 2026, an official Space Force article described ATLAS as a scalable architecture used by 18 SDS operators for catalog administration, observation association, maneuver and de-orbit detection, sensor planning and calibration. (ussf-cfc.spaceforce.mil)

That modernization creates opportunities for software engineers, data engineers, systems integrators, mission analysts and user experience specialists in addition to traditional orbital mechanics roles.

Government versus commercial work

Government work may provide strong mission continuity, formal training and exposure to national-level operations. It can also involve shift schedules, security requirements, location constraints and a slower technology adoption cycle than a venture-backed startup. Some roles require citizenship, a security clearance or eligibility to obtain one.

Commercial work may offer faster experimentation, broader technical ownership and a more visible connection between engineering output and product decisions. It can also involve funding uncertainty, changing priorities, customer-driven deadlines and less predictable organizational structure.

A candidate should not treat one environment as universally superior. The right choice depends on whether you value operational continuity, technical breadth, rapid product iteration, public service, classified mission access or entrepreneurial upside.

A day in the life of an SDA engineer

Job descriptions often make SDA sound abstract. The daily workflow is more concrete. A typical day may begin with a data-quality review, an overnight alert or a planned analysis task. The engineer or analyst checks new observations, evaluates track continuity and examines whether any object has changed behavior.

Conjunction assessment

A conjunction assessment begins with predicted close approaches between two objects. The analyst reviews time of closest approach, relative position, miss distance, covariance, probability of collision and the quality of the underlying data. The result is not a single magic number. It is a risk estimate shaped by sensor coverage, force models, uncertainty assumptions and the time remaining before the event.

When a risk is significant, the process may include updated tracking, coordination with the spacecraft operator, maneuver planning and reassessment after new observations. A software engineer may work on the service that computes the screening results. An orbital analyst may evaluate whether the result is credible. An operations specialist may manage the communication workflow.

Catalog maintenance

Catalog work is central to SDA. Objects need stable identities, consistent metadata and current state estimates. A newly detected object may need to be associated with an existing object or added as a new catalog entry. A maneuver can create a period of uncertainty. A breakup can create many fragments and require rapid reassessment.

Good catalog maintenance is a discipline of evidence. Analysts examine historical states, sensor provenance, residuals, time tags and correlations. They avoid forcing a convenient answer when the data does not support one.

Breakup analysis

A breakup event can generate a large number of observations and a rapidly changing operational picture. The analyst may look for a sudden increase in tracked objects, changes in radar signatures, correlated orbital planes or unusual residual patterns. The engineering team may need to scale processing, improve association logic and produce a catalog update quickly.

Sensor planning

Sensor planning is an optimization problem. The team decides which sensor should observe which object, when the observation should occur and how the collection improves uncertainty. The plan may account for weather, daylight, radar resource limits, telescope pointing, customer priorities and the expected information gain from each observation.

Communication and documentation

SDA work is not complete when the code runs or the orbit is calculated. Results must be documented, reviewed and communicated. A strong practitioner can write a concise technical note, brief a non-specialist, explain uncertainty and preserve a reproducible record of the analysis.

The satellite engineer career guide is useful for understanding how these specialized skills fit into the wider space engineering landscape. SDA is a focused path, but it still depends on systems thinking, software quality and mission awareness.

The technical skill stack employers want in 2026

A competitive SDA candidate does not need to master every tool used by every employer. The goal is to develop a coherent technical stack that demonstrates useful depth and practical range.

Orbital mechanics and estimation

Start with two-body motion, orbital elements, coordinate frames and time systems. Then move into perturbations, atmospheric drag, solar radiation pressure, third-body effects and maneuver modeling. Understand the difference between a state vector, an ephemeris, a two-line element set and a covariance representation.

Estimation is equally important. Learn least-squares orbit determination, Kalman filtering, batch processing, residual analysis and uncertainty propagation. You should be able to explain why a solution becomes weak, how observation geometry affects observability and what a covariance ellipse does and does not mean.

Programming and data engineering

Python is valuable for analysis, simulation and rapid prototyping. NumPy, SciPy, pandas, Astropy and plotting libraries can support serious work when used carefully. C++ remains relevant for performance-sensitive operational systems, sensor processing and embedded components.

SQL matters because SDA data is historical, relational and heavily queried. Engineers investigate observations, track histories, object metadata, sensor provenance and event timelines. Experience with REST APIs, message queues, containers, Linux and cloud deployment can distinguish a candidate who can prototype from one who can ship.

Software assurance

SDA systems may influence collision avoidance, launch support, national security operations and customer decisions. Testing must therefore cover numerical correctness, edge cases, time handling, coordinate transformations, degraded data and failure recovery.

Learn to write unit tests for propagation and frame conversions. Build regression tests from known trajectories. Test leap seconds and time-zone assumptions. Add property-based tests where appropriate. Record model versions and input data so that an analyst can reproduce a result months later.

Domain communication

The ability to communicate technical uncertainty is a core skill. Avoid saying that an object definitely maneuvered when the evidence only indicates a change in the estimated state. Explain whether a result is sensor-limited, model-limited or association-limited. State what additional observation would reduce uncertainty.

Refonte Learning's Astrodynamics and orbital mechanics specialist program is one example of a structured route for developing orbit determination, mission design and trajectory optimization foundations. Those foundations are directly relevant to SDA, even when the final job title emphasizes analytics or operations rather than astrodynamics.

Building a portfolio that proves SDA readiness

A portfolio should show more than a polished orbital animation. Hiring teams need evidence that you can work with uncertainty, imperfect measurements, operational constraints and reproducible software.

Project one: radar-based orbit determination

Create a simulated LEO tracking pipeline. Generate a reference trajectory with a realistic force model, produce noisy range and range-rate observations, introduce missed observations and estimate the state with a filter. Compare the estimated trajectory with the truth model and report position uncertainty over time.

The important part is the analysis. Explain when the filter diverges, how the next observation improves the solution and how atmospheric drag affects the result. Include residual plots, test cases and a short operational summary.

Project two: optical track association

Build a simplified optical tracking project using right ascension and declination observations. Simulate two nearby objects, add timing noise and create a gap in observations. Implement a basic association method, then show where false associations occur and how additional observation geometry helps.

This project demonstrates an understanding of the difference between seeing an object and maintaining custody of an object.

Project three: conjunction screening service

Create a service that accepts two ephemerides, propagates them into a common frame, calculates closest approach and returns a risk report. Include uncertainty assumptions, time of closest approach, relative position and a clear explanation of limitations.

Add a small web interface or command-line workflow. Log input versions and model parameters. Provide tests for frame conversions, time boundaries and zero-relative-velocity cases.

Project four: breakup event investigation

Use publicly available orbital data or a synthetic dataset to simulate a fragmentation event. Detect a sudden rise in associated tracks, cluster the resulting objects and estimate how the dispersion changes over time. The purpose is not to recreate a classified analysis. It is to show that you understand event detection, catalog impact and evidence management.

Project five: operator-centered visualization

Build a display that shows object history, predicted conjunctions, uncertainty, sensor coverage and recommended next observations. The interface should make assumptions visible rather than hiding them behind a single risk color.

A portfolio like this gives interviewers material to discuss. It also creates a bridge between coursework and employment. Use version control, documentation and reproducible environments. A modest project with excellent testing is more valuable than a spectacular demo that cannot be trusted.

The space software engineer interview questions resource can help candidates prepare for the software portion of these conversations, especially around testing, debugging, systems design and technical communication.

Compensation and tradeoffs: startup, prime or government

Compensation in SDA depends on more than the job title. Location, clearance eligibility, education, years of experience, technical depth, customer exposure and the employer's funding model all influence the package. Public job postings may show a base salary range, but they do not always capture bonus structures, equity terms, overtime, relocation, clearance incentives or long-term progression.

The right comparison is therefore total career value, not just base pay.

Commercial startups

A startup may offer competitive base compensation plus equity, growth opportunities and broader technical ownership. Equity can become meaningful if the company grows, wins major contracts or reaches a liquidity event, but it can also remain illiquid or lose value. Candidates should understand vesting, exercise terms, dilution, preferred versus common shares and what happens if they leave.

Startup engineers may gain responsibility quickly. A junior engineer could contribute to a customer-facing analysis tool, participate in field testing or own a subsystem earlier than would be possible at a large organization. The cost may be less predictable workload, shifting priorities and fewer layers of support.

Legacy primes

A prime contractor often provides stable programs, formal benefits, structured training and a recognizable path through technical levels. The base salary may be easier to compare, and the employment model can be more predictable. Large programs also provide valuable experience with requirements, verification, configuration management and government contracting.

The tradeoff is that an engineer may have narrower ownership. You may contribute to one component of a large system and need several approvals before changing an algorithm or interface.

Government roles

Government employment and military service can provide mission continuity, training, leadership opportunities and direct exposure to national SDA operations. Compensation should be assessed alongside retirement benefits, health coverage, locality adjustments, clearance value and promotion structure.

Government roles may impose geographic, eligibility and schedule requirements. Classified work can also limit what you can discuss publicly or include in a portfolio.

How to compare offers

Ask each employer:

• What percentage of the role is analysis, software, operations and customer support?
• Is the work focused on LEO, GEO, cislunar space or multiple regimes?
• What sensors and data sources will I use?
• Is the position subject to shift work or on-call duty?
• What security clearance is required?
• How are technical decisions reviewed?
• What does success look like after six and twelve months?
• How much of the compensation is fixed versus variable?
• What training and conference support are available?
• Can I move between technical and operational roles?

The orbital mechanics engineer salary and roadmap resource can support broader compensation planning, but candidates should still evaluate each offer using current employer data and the full benefits package.

How to move into SDA from adjacent careers

Many successful SDA candidates do not begin with a job labeled Space Domain Awareness. They enter from satellite operations, flight dynamics, software engineering, data science, radar engineering, astronomy, aerospace systems or military space operations.

From satellite operations

Satellite operators already understand command timelines, telemetry, anomaly response, procedures and the consequences of poor orbital information. To move into SDA, add orbit determination, conjunction assessment, catalog concepts and sensor data analysis. Document how you have used ephemerides, managed maneuver planning or communicated operational risk.

The satellite operations career progression guide provides useful context for how console and mission roles can develop into broader operational leadership. That experience can be valuable to commercial SDA companies building tools for operators because you understand the user, not only the algorithm.

From software engineering

Software engineers should learn the domain vocabulary and build one or two physics-based projects. Be able to explain coordinate frames, propagation, covariance, conjunction screening and time systems. You do not need to become a research astrodynamicist before applying, but you do need to show that you can reason about the data your software processes.

A software engineer with strong testing, distributed systems and observability skills can be highly valuable in SDA, especially as companies build scalable platforms and secure operational environments.

From data science or machine learning

Machine learning can support anomaly detection, object classification, sensor scheduling and behavior analysis. However, SDA employers generally need candidates who understand the physics and the limitations of the data. A model that identifies unusual behavior must distinguish a real maneuver from a sensor calibration issue or orbit determination artifact.

Use machine learning as one component of a physics-informed workflow. Compare model output with a baseline estimator. Measure false positives. Explain how analysts review and override recommendations.

From astronomy or physics

Astronomy and physics graduates often have strong quantitative foundations. Add production software, databases, cloud deployment and operational communication. A telescope research project becomes more relevant when you can describe data quality, scheduling constraints, calibration, uncertainty and how the result would support a decision.

From military or cleared work

Experience with classified operations, structured reporting and mission decision-making can be valuable, but candidates must translate it into unclassified language. Describe the type of problem, the analytical method, the operational tempo and the outcome without revealing protected information.

The common pattern is clear: build a bridge between your current capability and the SDA workflow. Do not wait until you meet every requirement. Demonstrate the missing skill through a project, course, research contribution or adjacent assignment.

A practical 12-month entry plan for 2026

A focused plan is more effective than collecting disconnected certificates. The aim is to produce evidence of competence in orbital mechanics, software and operational analysis.

Months one to three: establish the foundations

Review classical orbital mechanics, Keplerian elements, coordinate frames, time systems and numerical propagation. Implement basic two-body propagation from scratch, then compare it with a trusted scientific library. Learn how numerical error appears and how to validate a result.

At the same time, improve Python, Git, Linux and scientific testing. Keep a technical notebook that records assumptions and mistakes. Employers value the ability to investigate a discrepancy, not only the ability to produce a correct answer on the first attempt.

Months four to six: work with observations

Build a measurement model for radar or optical observations. Add noise, gaps, outliers and time-tag errors. Implement a simple least-squares or Kalman filter and study how geometry and measurement quality affect the solution.

Read operational documentation from government and commercial providers. The goal is to understand how sensors, catalogs and decision workflows connect. Avoid treating orbital mechanics as a closed mathematical exercise.

Months seven to nine: build a production-style project

Turn your best notebook into a documented application or service. Add automated tests, structured logs, a reproducible environment and a clear user workflow. Include a short technical design document and a limitations section.

If you are targeting a radar company, emphasize tracking, filtering and sensor scheduling. If you are targeting an optical provider, emphasize astrometry, image processing and long-baseline orbit determination. If you are targeting a software-heavy company, emphasize APIs, data fusion, visualization and operator workflow.

Months ten to twelve: target the market

Study job descriptions from LeoLabs, Slingshot Aerospace, ExoAnalytic Solutions, primes and government contractors. Track recurring requirements. Prepare separate versions of your resume for orbital analysis, software engineering, mission operations and systems integration.

Practice explaining one project at three levels: a two-minute hiring manager summary, a ten-minute technical walkthrough and a detailed whiteboard discussion. Be ready to discuss a failure, not just a success.

Ask practitioners for informational conversations, attend space industry events and contribute to technical communities where appropriate. Do not lead with a generic request for a job. Lead with a specific question about sensor data, orbit determination, operations or career transitions.

This approach gives you multiple entry points. You may not land directly in a title containing SDA, but you can enter through flight dynamics, mission software, sensor systems, satellite operations or data engineering and move toward the mission.

The future of SDA careers beyond the first job

The first role is only the beginning. SDA is becoming more integrated with space traffic coordination, autonomous operations, national security, satellite servicing, launch support and cislunar activity. As the domain expands, career paths will branch into technical leadership, product management, mission direction, sensor architecture, algorithm research and customer operations.

The most durable skills are likely to be the ones that remain valuable across sensor types and organizational models. These include estimation under uncertainty, disciplined software development, data provenance, systems thinking, operational communication and the ability to evaluate automated recommendations.

Artificial intelligence will change the work, but it will not remove the need for domain expertise. An AI system can rank anomalies or suggest a maneuver. People still need to determine whether the input data is trustworthy, whether the recommendation respects mission constraints and whether the consequence of an error is acceptable.

The same principle applies to automation. Automated catalog updates can reduce manual workload, but they also create new responsibilities around validation, alert thresholds, auditability and human override. Engineers who understand both the benefit and the failure mode of automation will be in demand.

SDA also creates a stronger connection between commercial and government work. Government operators increasingly use commercial data and software. Commercial providers design products around government mission needs while also serving satellite operators, launch companies and insurers. Professionals who can operate across those boundaries will have more mobility.

That mobility is one of the most attractive features of the field. A person can start with a radar algorithm, move into a catalog product, join a government operations team, return to industry as a mission architect and eventually lead a multi-sensor program. The technical foundation remains useful throughout.

Refonte Learning approaches astrodynamics as a practical professional capability, connecting orbit determination and trajectory optimization with the wider skills needed in modern space technology. For candidates who want to make SDA a deliberate career choice, that combination of physics, software and mission context is more valuable than a generic interest in space.

The central question for 2026 candidates is not whether there will be more objects in orbit. There will be. The better question is whether you can help turn imperfect observations into decisions that operators can trust.

If the answer is yes, begin with a focused technical project, strengthen your orbital mechanics foundation and target the employer environment that matches your working style. Explore the Astrodynamics and orbital mechanics specialist program as one structured route, then compare commercial sensing companies, software platforms, legacy primes and government operations teams. The new SDA career track is broad enough for analysts, engineers, operators and researchers, but it rewards people who can connect every layer of the mission.