2

No Experience Coder Jobs in Frederick, MD (NOW HIRING)

Software Developer

Gaithersburg, MD · On-site

$69.55 - $125.72/hr

Leverage AI-assisted development tools (e.g., Roo Code, Claude, ChatGPT, or similar) to improve ... Experience with programming languages such as C++, Python, or Qt * Practical experience using AI ...

Showing results 41-60

No Experience Coder information

See Frederick, MD salary details

$15

$27

$43

How much do no experience coder jobs pay per hour?

As of Sep 6, 2026, the average hourly pay for no experience coder in Frederick, MD is $27.33, according to ZipRecruiter salary data. Most workers in this role earn between $18.89 and $34.42 per hour, depending on experience, location, and employer.

What is a no experience coder?

A No Experience Coder is someone who is just starting out in programming and typically has little to no prior experience in coding or software development. These individuals are often beginners who are learning the basics of programming languages, problem-solving, and computer science concepts. Many No Experience Coders start by taking online courses, attending coding bootcamps, or using free resources to build foundational skills. With dedication and practice, they can progress to more advanced coding roles over time.

What are the key skills and qualifications needed to thrive as a no experience coder?

To thrive as a No Experience Coder, you need a basic understanding of programming fundamentals, logical thinking, and a willingness to learn, often supported by self-study or entry-level coding courses. Familiarity with beginner-friendly languages like Python or JavaScript and the ability to use code editors and version control systems (like Git) are helpful for practical development tasks. Curiosity, problem-solving skills, and persistence are crucial soft skills that enable continuous learning and overcoming challenges. These skills and qualities are important because they help new coders adapt quickly, build a strong foundation, and progress in a dynamic and evolving field.

What types of projects or tasks can a no experience coder expect to work on when starting their first job?

As a no experience coder, you will typically begin with smaller, well-defined tasks such as fixing minor bugs, writing simple scripts, or assisting with documentation. These projects are designed to help you become familiar with the codebase and development tools while learning best practices from more experienced team members. Over time, you may gradually take on more complex assignments as your skills grow. Collaboration is key, and you'll likely participate in code reviews and pair programming sessions to accelerate your learning and integration into the team.

What is the easiest coding job to get?

Entry-level coding jobs such as web development, data entry, or quality assurance testing are generally considered the easiest to obtain with minimal experience. These roles often require basic knowledge of HTML, CSS, or scripting languages and may accept self-taught skills or online certifications. Building a portfolio and gaining familiarity with common tools like Git can improve chances of securing such positions.

What are the most commonly searched types of Coder jobs in Frederick, MD?

The most popular types of Coder jobs in Frederick, MD are:

What cities near Frederick, MD are hiring for No Experience Coder jobs?

Cities near Frederick, MD with the most No Experience Coder job openings:

Infographic showing various No Experience Coder job openings in Frederick, MD as of August 2026, with employment types broken down into 52% Full Time, 44% Part Time, and 4% Temporary. Highlights an 96% In-person, and 4% Hybrid job distribution, with an average salary of $56,854 per year, or $27.3 per hour.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Frederick, MD

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