ZipRecruiter

Log In

1

Bug Jobs in Minnesota (NOW HIRING)

Comtech, LLC

Oracle IAM Engineer

Minneapolis, MN · On-site

Troubleshooting any issues and deploys bug fixes. * Joining the production incident calls and help the team to resolve the issues related to OAM. Qualifications Minimum Requirement: * 5-7 years of ...

Harris

$55K - $65K/yr

Create, maintain, and execute test plans, test cases, and test scripts for new features, bug fixes, integrations, customer scenarios, and release validation, including functional, exploratory ...

Avalore, LLC

Software Tester / QA Engineer

Virginia, MN · On-site

$99 - $174/hr

This person will create detailed test reports and metrics to communicate test results, participate in defect triage meetings to prioritize issues, and verify bug fixes through confirmation testing.

New

Sweatpals

Develop and apply a bug priority rubric for revenue-generating and operations-critical workflows * Maintain backlog health: consolidate duplicates, triage stale items, and ensure active issues have ...

Sweatpals

Develop and apply a bug priority rubric for revenue-generating and operations-critical workflows * Maintain backlog health: consolidate duplicates, triage stale items, and ensure active issues have ...

Sweatpals

Develop and apply a bug priority rubric for revenue-generating and operations-critical workflows * Maintain backlog health: consolidate duplicates, triage stale items, and ensure active issues have ...

Sweatpals

Develop and apply a bug priority rubric for revenue-generating and operations-critical workflows * Maintain backlog health: consolidate duplicates, triage stale items, and ensure active issues have ...

Sweatpals

Develop and apply a bug priority rubric for revenue-generating and operations-critical workflows * Maintain backlog health: consolidate duplicates, triage stale items, and ensure active issues have ...

Ogilvy

Account Executive

Minneapolis, MN · Hybrid

Coordinates QA process across multiple rounds, including test plan development, sample data creation, internal testing, client User Acceptance Testing (UAT) rounds; manages client bug logging and ...

previous page

Showing results 41-60

All JobsBug JobsBug Jobs in Minnesota

Bug information

See Minnesota salary details

$10

$22

$56

How much do bug jobs pay per hour?

As of Sep 5, 2026, the average hourly pay for bug in Minnesota is $22.28, according to ZipRecruiter salary data. Most workers in this role earn between $14.48 and $24.29 per hour, depending on experience, location, and employer.

What is a bug?

In software development, a 'bug' refers to an error, flaw, or fault in a computer program that causes it to produce incorrect or unexpected results, or to behave in unintended ways. Bugs can arise from mistakes made by programmers, design errors, or unforeseen interactions within the code. Identifying and fixing bugs is a crucial part of the software development lifecycle, ensuring that applications work as intended and delivering a positive user experience.

What are the key skills and qualifications needed to thrive as a bug?

I'm sorry, but 'Bug' is not a recognized professional occupation, so I cannot provide a relevant answer.

What is the difference between Bug vs Software Tester?

AspectBugSoftware Tester
RoleIdentifies and reports defects in softwareEvaluates software quality through testing and validation
CredentialsNone specific, but technical knowledge helpsOften has testing certifications or QA training
Work EnvironmentDevelopers, QA teams, or support teamsTesting labs, development teams, or remote
Industry UsageCommonly used in software development and QA

While a bug is a defect or error found in software, a software tester is responsible for systematically testing the software to find bugs. Bugs are the issues reported during testing or after deployment, whereas testers proactively seek out bugs to improve software quality.

What profession works with bugs?

Entomologists and pest control professionals work with bugs as part of their job. Entomologists study insects for research and conservation, often requiring a background in biology and specialized training, while pest control workers focus on managing and eliminating insect infestations using various methods and tools.

What are popular job titles related to Bug jobs in Minnesota?

For Bug jobs in Minnesota, the most frequently searched job titles are:

What job categories do people searching Bug jobs in Minnesota look for?

The top searched job categories for Bug jobs in Minnesota are:

Bug jobs near you
Infographic showing various Bug job openings in Minnesota as of August 2026, with employment types broken down into 89% Full Time, 6% Part Time, and 5% Contract. Highlights an 83% Physical, 3% Hybrid, and 14% Remote job distribution, with an average salary of $46,349 per year, or $22.3 per hour.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Minneapolis, MN

$20 - $30/hr

Full-time

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

Apply