ZipRecruiter

Log In

1

Rust Developer Jobs in Iowa (NOW HIRING)

previous page

Showing results 41-60

All JobsRust Developer JobsRust Developer Jobs in Iowa

Rust Developer information

See Iowa salary details

$16

$49

$76

How much do rust developer jobs pay per hour?

As of Sep 4, 2026, the average hourly pay for rust developer in Iowa is $49.63, according to ZipRecruiter salary data. Most workers in this role earn between $37.93 and $60.72 per hour, depending on experience, location, and employer.

What does a Rust developer do?

The job duties of a Rust developer focus on performing computer programming tasks using the Rust programming language. As a Rust developer, you focus on coding and development for projects such as web browsers, operating systems, server and systems software, and blockchain projects. Your responsibilities vary depending on the requirements of the development projects on which you work. You typically work to ensure the safety and security of the software or systems that you develop and test and debug them as part of the development process.

What is a Rust developer?

Rust Developers are software engineers who specialize in using the Rust programming language to build safe, fast, and reliable applications. They write, test, and maintain code, often focusing on system-level programming, web servers, blockchain technologies, and performance-critical software. Rust Developers leverage the language’s unique features, like memory safety and concurrency, to build efficient and secure solutions. Their responsibilities may also include contributing to open-source projects, optimizing existing code, and collaborating with cross-functional teams.

What are the key skills and qualifications needed to thrive as a Rust developer, and why are they important?

To thrive as a Rust Developer, you need strong proficiency in Rust programming, a solid understanding of systems programming concepts, and a relevant degree or experience in software development. Familiarity with tools like Cargo, Git, and continuous integration systems, as well as experience with frameworks such as Actix or Rocket, are commonly required. Outstanding problem-solving skills, attention to detail, and effective communication set top Rust Developers apart. These skills ensure robust, efficient, and safe code, which is essential for building reliable software solutions.

What are some common challenges Rust developers face when working on large-scale projects?

Rust Developers often encounter challenges such as managing complex dependencies, ensuring memory safety without sacrificing performance, and integrating Rust code with existing systems written in other languages. Collaborating with cross-functional teams can also require clear communication, especially when explaining Rust’s unique concepts to those unfamiliar with the language. Staying up-to-date with the rapidly evolving Rust ecosystem and tooling is important, as new libraries and best practices frequently emerge.

What is the difference between Rust Developer vs C++ Developer?

AspectRust Developer
Required CredentialsProficiency in Rust programming, often with a computer science background or coding certifications
Work EnvironmentSoftware development teams, especially in systems programming, embedded systems, or performance-critical applications
Industry UsageTech companies focusing on safety, concurrency, and performance, including blockchain, embedded systems, and web assembly

Rust Developers and C++ Developers share similar skills in systems programming, requiring knowledge of low-level programming, memory management, and performance optimization. Both roles are common in industries demanding high efficiency and safety. While C++ Developers often have experience with legacy codebases and a broader range of tools, Rust Developers focus on modern safety features and concurrency. The choice between the two depends on project requirements and company preferences.

How much do Rust developers make?

Rust developers typically earn between $80,000 and $150,000 annually, depending on experience, location, and industry. Skilled developers with knowledge of systems programming, concurrency, and performance optimization tend to command higher salaries, especially in tech hubs or companies working on performance-critical applications.

Is Rust a high paying language?

Rust developers are generally among the higher-paid programmers due to the language's growing popularity in systems programming, security, and performance-critical applications. Salaries can vary based on experience, location, and industry, but expertise in Rust is often associated with competitive compensation. Knowledge of related tools like Cargo and understanding of low-level programming can further enhance earning potential.

Is a Rust developer in demand?

Rust developers are increasingly in demand due to Rust's focus on safety, performance, and concurrency, especially in systems programming, embedded systems, and WebAssembly. Companies value skills in Rust alongside knowledge of related tools like Cargo and familiarity with multi-threaded programming, leading to growing job opportunities in the tech industry.
More about Rust Developer jobs

What are the most commonly searched types of Rust Developer jobs in Iowa?

The most popular types of Rust Developer jobs in Iowa are:

What are popular job titles related to Rust Developer jobs in Iowa?

For Rust Developer jobs in Iowa, the most frequently searched job titles are:

What job categories do people searching Rust Developer jobs in Iowa look for?

The top searched job categories for Rust Developer jobs in Iowa are:

What cities in Iowa are hiring for Rust Developer jobs?

Cities in Iowa with the most Rust Developer job openings:

Rust Developer jobs near you
Infographic showing various Rust Developer job openings in Iowa as of August 2026, with employment types broken down into 63% Full Time, 11% Part Time, and 26% Contract. Highlights an 79% In-person, 4% Hybrid, and 17% Remote job distribution, with an average salary of $103,230 per year, or $49.6 per hour.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Cedar Rapids, IA • On-site

$20 - $30/hr

Full-time

Posted 3 days ago

New

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.

Apply