1

Rust Contract Jobs in West Virginia (NOW HIRING)

Rust Contract information

What is a Rust contract developer?

Rust contract developers are programmers who specialize in writing smart contracts using the Rust programming language, commonly for blockchain platforms like Solana, NEAR, and Polkadot. These developers use Rust's safety and performance features to create secure and efficient decentralized applications (dApps) and protocols. Their work involves designing, coding, testing, and deploying smart contracts, ensuring that they function correctly and securely on the blockchain.

What types of projects and teams do Rust contract developers typically work on, and how is collaboration managed in these environments?

Rust contract developers are often brought on to contribute to high-performance systems, such as blockchain infrastructure, network services, or embedded applications. They usually join agile, cross-functional teams comprising other engineers, product managers, and sometimes DevOps professionals. Collaboration is managed through daily standups, code reviews, and regular communication via tools like Slack or GitHub. Contractors are expected to quickly familiarize themselves with project-specific codebases and processes, contributing clean, maintainable code while adhering to established development standards.

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

To thrive as a Rust Smart Contract Developer, you need strong proficiency in Rust programming, blockchain fundamentals, and experience with smart contract development, often supported by a relevant degree or certifications. Familiarity with tools like Cargo, testing frameworks, and blockchain platforms such as Solana or NEAR is essential. Attention to detail, problem-solving ability, and effective communication are crucial soft skills for collaborating with teams and ensuring secure code. These skills are vital to building reliable, efficient, and secure smart contracts that meet project requirements and industry standards.

What is the difference between Rust Contract vs Rust Developer?

AspectRust ContractRust Developer
Required CredentialsExperience with Rust, contract law knowledge (if applicable)Proficiency in Rust programming, coding certifications
Work EnvironmentProject-based, freelance or consultingFull-time or part-time employment, in-house or remote
Industry UsageUsed in blockchain, smart contracts, and software projectsDevelops software applications, systems, or tools

The main difference is that a Rust Contract typically refers to a contractual role involving Rust skills, often project-based or freelance, focusing on specific deliverables. A Rust Developer is a full-time or part-time professional who writes and maintains Rust code within a company or organization. Both roles require Rust proficiency, but their work settings and responsibilities differ.

What are popular job titles related to Rust Contract jobs in West Virginia?

For Rust Contract jobs in West Virginia, the most frequently searched job titles are:

What job categories do people searching Rust Contract jobs in West Virginia look for?

The top searched job categories for Rust Contract jobs in West Virginia are:

Infographic showing various Rust Contract job openings in West Virginia as of August 2026, with employment types broken down into 100% Contract. Highlights an 100% Remote job distribution.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Parkersburg, WV

$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.