1

Rust Engineer Jobs in Utah (NOW HIRING)

Sandblaster

West Jordan, UT · On-site

$19 - $22/hr

We engineer change for a more stable and sustainable world. THE ROLE We're hiring a Sandblaster at our West Jordan, UT locations. You'll responsible for preparing surfaces of pipes by removing rust ...

Some background (academic, professional, or self-taught) in software development: comfortable in at least one programming language, such as Python, Javascript, Golang, C, or Rust. Preferences * Prior ...

Admin Assistant

Ogden, UT · On-site

$17.50 - $23.75/hr

Loud manufacturing environment, exposure to metals, machine lubricants, rust preventative, and ... Timken is a global technology leader in engineered bearings and industrial motion. Our expanding ...

Deburr Technician

Saint George, UT · On-site

$15.25 - $18.25/hr

... rust preventatives, CitraSafe, denatured alcohol, and 4USoap, to clean and preserve the metal ... Ability to learn or currently possess the ability to read engineering blueprints and use precision ...

Deburr Technician

Saint George, UT · On-site

$15.25 - $18.25/hr

... rust preventatives, CitraSafe, denatured alcohol, and 4USoap, to clean and preserve the metal ... Ability to learn or currently possess the ability to read engineering blueprints and use precision ...

Showing results 41-59

Rust Engineer information

See Utah salary details

$32.3K

$87.5K

$152.9K

How much do rust engineer jobs pay per year?

As of Sep 13, 2026, the average yearly pay for rust engineer in Utah is $87,493.00, according to ZipRecruiter salary data. Most workers in this role earn between $72,800.00 and $98,300.00 per year, depending on experience, location, and employer.

What is a Rust engineer?

Rust Engineers are software developers who specialize in using the Rust programming language to build reliable, efficient, and safe systems. They often work on performance-critical applications such as backend services, embedded software, systems programming, and blockchain technologies. Rust Engineers are valued for their ability to write code that minimizes bugs and security vulnerabilities, leveraging Rust's strict compiler and memory safety features. Their expertise is increasingly sought after in industries where safety, speed, and concurrency are essential.

What skills and qualifications are needed to thrive as a Rust engineer?

To thrive as a Rust Engineer, you need a strong understanding of systems programming concepts, the Rust language, and experience with software development best practices, often supported by a degree in computer science or a related field. Familiarity with version control systems like Git, build tools such as Cargo, and knowledge of CI/CD pipelines are typically required. Problem-solving skills, attention to detail, and effective communication set outstanding Rust Engineers apart. These skills and qualifications are essential for building reliable, high-performance, and secure software systems in collaborative development environments.

What are common challenges Rust engineers face when integrating Rust with existing systems?

Rust Engineers often encounter challenges when integrating Rust into codebases written in other languages, such as C, C++, or Python. These challenges can include managing foreign function interfaces (FFI), ensuring memory safety across language boundaries, and handling differences in build systems and tooling. Collaboration with teams familiar with legacy systems is often essential to navigate these complexities, and clear documentation is key to successful integration. Over time, these challenges can deepen your understanding of system interoperability and lead to broader career opportunities in systems programming.

What is the difference between Rust Engineer vs Software Developer?

AspectRust EngineerSoftware Developer
Required CredentialsBachelor's in Computer Science or related, familiarity with RustBachelor's in Computer Science or related, general programming skills
Work EnvironmentTech companies, startups, embedded systems, systems programmingVarious industries including tech, finance, healthcare, web development
Employer & Industry UsageCompanies developing performance-critical or system-level applicationsBroad range of companies developing software across sectors
Search & Comparison IntentFocus on Rust-specific roles, systems programmingGeneral software development roles across languages

Rust Engineers specialize in developing high-performance, safe systems using Rust, often in embedded or systems programming contexts. Software Developers have a broader scope, working across multiple languages and industries. While both roles require strong programming skills, Rust Engineers focus on Rust expertise, whereas Software Developers may work with various languages and technologies.

How do you become a Rust engineer?

To become a Rust engineer, you should learn the Rust programming language through official documentation, tutorials, and practice projects. Gaining experience with systems programming, understanding ownership and concurrency concepts, and familiarizing yourself with tools like Cargo and Rustup are also important. Building a portfolio of Rust projects and contributing to open-source can enhance your qualifications for such roles.

How much do Rust engineers make?

Rust engineers typically earn between $80,000 and $150,000 annually, depending on experience, location, and industry. Senior roles or those with specialized skills in systems programming and performance optimization tend to command higher salaries.

What are popular job titles related to Rust Engineer jobs in Utah?

For Rust Engineer jobs in Utah, the most frequently searched job titles are:

Infographic showing various Rust Engineer job openings in Utah as of August 2026, with employment types broken down into 90% Full Time, 7% Part Time, and 3% Contract. Highlights an 85% Physical, 5% Hybrid, and 10% Remote job distribution, with an average salary of $87,493 per year, or $42.1 per hour.

AI Agent Trajectory Annotator and Reviewer

Logan, UT • On-site

$20 - $30/hr

Full-time

Posted 13 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.