AI Agent Trajectory Annotator and Reviewer
Ogden, UT · On-site
$20 - $30/hr
... ve never used. • Linux -- Comfortable with logs, running processes, build failures, and ... engineer can check.
AI Agent Trajectory Annotator and Reviewer
Ogden, UT · On-site
$20 - $30/hr
... ve never used. • Linux -- Comfortable with logs, running processes, build failures, and ... engineer can check.
Work with clients and peers to build a high performing system using Elastic to aggregate logs from ... Knowledge of Linux or UNIX environments, including navigating and troubleshooting basic OS issues
Work with clients and peers to build a high performing system using Elastic to aggregate logs from ... Knowledge of Linux or UNIX environments, including navigating and troubleshooting basic OS issues
Linux Build Engineer information
See Roy, UT salary details
$10.32 - $17.34
0% of jobs
$17.34 - $24.37
0% of jobs
$24.37 - $31.39
2% of jobs
$31.39 - $38.41
11% of jobs
$38.41 - $45.44
11% of jobs
$46.16 is the 25th percentile. Wages below this are outliers.
$45.44 - $52.46
18% of jobs
The median wage is $55.18 / hr.
$52.46 - $59.49
23% of jobs
$63.28 is the 75th percentile. Wages above this are outliers.
$59.49 - $66.51
20% of jobs
$66.51 - $73.53
6% of jobs
$73.53 - $80.56
3% of jobs
$80.56 - $87.58
6% of jobs
$10
$56
$87
How much do linux build engineer jobs pay per hour?
As of Sep 9, 2026, the average hourly pay for linux build engineer in Roy, UT is $56.97, according to ZipRecruiter salary data. Most workers in this role earn between $45.87 and $63.99 per hour, depending on experience, location, and employer.
What does a Linux build engineer do?
A Linux Build Engineer is responsible for designing, implementing, and maintaining build systems for software projects that run on Linux operating systems. They automate build processes, manage dependencies, troubleshoot build failures, and ensure that software compiles and packages correctly. Additionally, they often collaborate with development and operations teams to streamline continuous integration and delivery pipelines, improving deployment efficiency and software quality.
What are the key skills and qualifications needed to thrive as a Linux build engineer?
To thrive as a Linux Build Engineer, you need strong expertise in Linux system administration, scripting languages (such as Bash or Python), and build automation concepts, often backed by a degree in computer science or related field. Familiarity with build tools like Jenkins, Git, Docker, and configuration management systems such as Ansible or Puppet is typically required. Problem-solving abilities, attention to detail, and effective teamwork are crucial soft skills for this role. These competencies ensure reliable, efficient build processes and enable smooth collaboration in fast-paced development environments.
What are some typical challenges faced by Linux build engineers in managing build automation pipelines?
Linux Build Engineers often encounter challenges such as maintaining consistency across multiple environments, troubleshooting complex build failures, and integrating new tools into existing CI/CD pipelines. They must ensure that builds remain reproducible and stable as codebases and dependencies evolve. Collaboration with development, QA, and operations teams is essential to quickly address issues and optimize the build process, making strong communication and problem-solving skills critical in this role.
What is the difference between Linux Build Engineer vs Linux System Administrator?
| Aspect | Linux Build Engineer | Linux System Administrator |
|---|---|---|
| Primary Focus | Building, maintaining, and optimizing Linux software builds and automation | Managing, configuring, and maintaining Linux systems and servers |
| Skills & Certifications | Linux scripting, build tools (e.g., Jenkins), version control, Linux certifications (e.g., RHCE) | Linux system management, networking, security, certifications like RHCE or CompTIA Linux+ |
| Work Environment | Development teams, CI/CD pipelines, software companies | IT departments, data centers, enterprise environments |
| Common Tasks | Automating builds, troubleshooting build failures, integrating software | System setup, user management, troubleshooting hardware/software issues |
While both roles require Linux expertise and certifications like RHCE, Linux Build Engineers focus on software build processes and automation, whereas Linux System Administrators manage and maintain Linux infrastructure. The roles often collaborate but serve different core functions within organizations.
What cities near Roy, UT are hiring for Linux Build Engineer jobs?
Cities near Roy, UT with the most Linux Build Engineer job openings:
AI Agent Trajectory Annotator and Reviewer
Ogden, UT • On-site
Bespoke Labs
$20 - $30/hr
Full-time
Posted 8 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.