1

Rust Programming Jobs in Portland, OR (NOW HIRING)

Mentor senior engineers and architects, settingbest practices forAIenabledsecurity discovery ... C++, Rust) and security automation, validation(e.g., Python) . Preferred Qualifications

Driller w/CDL

Vancouver, WA · On-site

$28 - $36.75/hr

... rust mitigation across all sectors. Headquartered in Tulsa, Oklahoma, ONEMESA encompasses multiple companies--MESA Products, MESA Services, Bass Engineering, and Hansen Drilling--each delivering ...

Driller Assistant w/CDL

Vancouver, WA · On-site

$25 - $30.50/hr

... rust mitigation across all sectors. Headquartered in Tulsa, Oklahoma, ONEMESA encompasses multiple companies--MESA Products, MESA Services, Bass Engineering, and Hansen Drilling--each delivering ...

Showing results 21-39

Rust Programming information

See Portland, OR salary details

$47.2K

$75.1K

$105K

How much do rust programming jobs pay per year?

As of Sep 7, 2026, the average yearly pay for rust programming in Portland, OR is $75,144.00, according to ZipRecruiter salary data. Most workers in this role earn between $54,100.00 and $93,900.00 per year, depending on experience, location, and employer.

What is a Rust programming job?

A Rust Programming job involves designing, developing, and maintaining software applications using the Rust programming language. Rust is known for its performance, memory safety, and concurrency features, making it popular for systems programming, web services, and embedded systems. Developers in this role typically work on optimizing performance, ensuring code safety, and integrating Rust with other technologies. Experience with Rust’s ownership model, concurrency features, and ecosystem tools like Cargo is often required.

What are some typical challenges faced by professionals working in Rust programming roles?

Professionals in Rust Programming roles often encounter challenges such as mastering the language's strict ownership and borrowing rules, which require a deep understanding of memory safety concepts. Additionally, working with complex, performance-critical systems demands close attention to detail and rigorous testing practices. Collaboration with team members, especially when integrating Rust code with projects in other languages or legacy systems, also presents opportunities for problem-solving. Over time, these challenges help developers build robust, scalable solutions and deepen their expertise in cutting-edge systems programming.

What are the key skills and qualifications needed to thrive in the Rust programming position, and why are they important?

Excelling in Rust Programming requires strong programming skills in Rust, understanding of systems programming concepts, and experience with memory management and concurrency. Familiarity with version control tools like Git, issue tracking systems, CI/CD pipelines, and optionally, certifications such as the Rust Programming Certificate, are often valuable. Problem-solving ability, collaboration, and clear communication are essential soft skills for success in team-based development environments. These skills and qualifications are vital because they ensure code safety, performance, and contribute to efficient, high-quality software development.

Are Rust programmers in demand?

Rust programmers are increasingly in demand due to the language's focus on safety, performance, and concurrency, especially in systems programming, embedded systems, and WebAssembly development. Companies in technology, finance, and gaming are actively hiring Rust developers to build reliable and efficient software solutions.

Can I learn Rust programming in 3 months?

Rust programming is a complex language that typically requires several months of dedicated study to achieve proficiency, especially for those new to systems programming. Learning core concepts such as ownership, borrowing, and concurrency can be feasible within three months with consistent practice, but mastering advanced topics and writing production-quality code usually takes longer. For job roles involving Rust, employers often expect a solid understanding of the language and related tools like Cargo and Rustup, which may require ongoing learning beyond initial months.

What are popular job titles related to Rust Programming jobs in Portland, OR?

For Rust Programming jobs in Portland, OR, the most frequently searched job titles are:

What job categories do people searching Rust Programming jobs in Portland, OR look for?

The top searched job categories for Rust Programming jobs in Portland, OR are:

What cities near Portland, OR are hiring for Rust Programming jobs?

Cities near Portland, OR with the most Rust Programming job openings:

Infographic showing various Rust Programming job openings in Portland, OR as of August 2026, with employment types broken down into 20% Internship, and 80% Full Time. Highlights an 60% In-person, and 40% Remote job distribution, with an average salary of $75,144 per year, or $36.1 per hour.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Vancouver, WA

$20 - $30/hr

Full-time

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