1

Trajectory Jobs in Indiana (NOW HIRING)

Senior Mach-TB Mission Engineer

Crane, IN · On-site

$104K - $143K/yr

This role involves the generation of Best Estimate Trajectory (BET) and Quick-Look Brief (QLB) data products by processing Launch Vehicle (LV) and MACH-TB "owned" Test Vehicle telemetry data.

Senior Mach-TB Mission Engineer

Crane, IN · On-site

$104K - $143K/yr

This role involves the generation of Best Estimate Trajectory (BET) and Quick-Look Brief (QLB) data products by processing Launch Vehicle (LV) and MACH-TB "owned" Test Vehicle telemetry data.

next page

Showing results 1-20

Trajectory information

What is a trajectory job?

Trajectory jobs typically refer to roles focused on planning, analyzing, and predicting the path or course of objects, vehicles, or systems—often in fields like aerospace, robotics, or data science. Professionals working in trajectory jobs use mathematical models and simulation software to calculate optimal paths for spacecraft, aircraft, missiles, or autonomous vehicles. These jobs require strong analytical skills and expertise in physics, mathematics, and computer programming. The work is critical in ensuring safety, efficiency, and mission success in both commercial and research settings.

What are the key skills and qualifications needed to thrive as a trajectory analyst?

To thrive as a Trajectory Analyst, you need strong analytical skills, a background in mathematics or physics, and a relevant degree such as aerospace engineering or applied mathematics. Familiarity with trajectory modeling software, programming languages like MATLAB or Python, and simulation tools are typically required. Attention to detail, problem-solving abilities, and effective communication help analysts interpret complex data and collaborate with engineering teams. These skills ensure accurate trajectory planning, risk mitigation, and successful mission outcomes in aerospace projects.

What are the typical daily tasks and collaboration points for a trajectory analyst in the aerospace industry?

As a Trajectory Analyst in the aerospace industry, your daily tasks often involve calculating and optimizing flight paths for spacecraft, satellites, or missiles. You will use specialized software to simulate trajectories, analyze mission parameters, and identify potential risks. Collaboration is key; you'll frequently work with engineers, mission planners, and software developers to ensure trajectory solutions align with mission objectives and technical constraints. Regular meetings and data reviews are common, allowing you to integrate feedback and adjust plans as missions progress.

What is the difference between Trajectory vs Data Analyst?

AspectTrajectoryData Analyst
Required CredentialsTypically a degree in education, psychology, or related fieldsDegree in statistics, mathematics, or computer science
Work EnvironmentEducational institutions, training programs, or corporate learning departmentsBusiness, finance, healthcare, or tech companies
Industry UsageUsed in education, career development, and training sectorsUsed across industries for data interpretation and reporting
Common Search/ComparisonTrajectory vs Data Analyst

While both roles involve analysis, Trajectory focuses on educational pathways and career development, often within learning environments, whereas Data Analysts interpret data to inform business decisions across various industries.

What are popular job titles related to Trajectory jobs in Indiana?

For Trajectory jobs in Indiana, the most frequently searched job titles are:

What job categories do people searching Trajectory jobs in Indiana look for?

The top searched job categories for Trajectory jobs in Indiana are:

What cities in Indiana are hiring for Trajectory jobs?

Cities in Indiana with the most Trajectory job openings:

Infographic showing various Trajectory job openings in Indiana as of September 2026, with employment types broken down into 1% As Needed, 91% Full Time, 6% Part Time, and 2% Contract. Highlights an 68% Physical, 2% Hybrid, and 30% Remote job distribution.

AI Agent Trajectory Annotator and Reviewer

Hammond, IN

$20 - $30/hr

Full-time

Posted 11 days ago


Job description

Type: Contract, hourly

Location: Remote

Hours: 20–30 per week

Pay: $20–30/hour, based on experience and language coverage

Start: Immediate

ABOUT THE ROLE

We evaluate how well advanced AI coding agents solve real engineering problems. An agent is given a real open source codebase inside a container and a hard task, then works on its own for 80 to 250 steps. A trajectory is the full record of that run — every command, result, and decision.

You will do two jobs, and you should expect either on any given day.

•Annotate — Read a trajectory nobody has looked at yet and judge it step by step.

• Review — Take an existing annotation, written by our AI tooling or another person, and confirm, correct, or reject it.

TASKS YOU'LL SEE

• Feature build — Add a working feature to a live library without breaking anything that already worked.

• Rebuild — Work out what a compiled tool does by running it, then rebuild it to match its output, exit codes, and file effects.

• Bug hunt — Find and fix twenty undocumented bugs across a dozen files with no test suite, then record what caused them.

Mostly Python and Go, with some Rust, C, and Ct+. A trajectory runs about 100 steps.

WHAT YOU JUDGE IN A TRAJECTORY

• Was the command right for the state the environment was actually in?

• Did the agent read the previous output correctly?

• Was the step wrong, or only inefficient — these are scored differently.

• Where did the run first go off course — usually earlier than where it visibly broke.

• Did the agent notice its own mistake and recover, or keep building on a false assumption?

• Did it game the grader instead of solving the task (e.g., weakening a test or hardcoding an expected value)?

WHAT WE NEED FROM YOU

• Experience — 2+ years in software engineering, DevOps, or site reliability, with real debugging in real codebases.

• Languages — Strong in Python or Go, and able to read a language you've never used.

• Linux — Comfortable with logs, running processes, build failures, and containers.

• Workflow — Everyday Git, diffs, pull requests, and issue tracking.

• Debugging — Able to work with no test suite and no error message pointing at the cause.

• Focus — Able to hold context across a long run, because step 74 can depend on step 12.

• Writing — Clear English, since every judgement needs an explanation another engineer can check.