ZipRecruiter

Log In

1

Software Engineer Jobs in Rutland, VT (NOW HIRING)

previous page

Showing results 41-60

All JobsSoftware Engineer JobsSoftware Engineer Jobs in Rutland, VT

Software Engineer information

See Rutland, VT salary details

$65K

$151.1K

$210.5K

How much do software engineer jobs pay per year?

As of Sep 9, 2026, the average yearly pay for software engineer in Rutland, VT is $151,110.00, according to ZipRecruiter salary data. Most workers in this role earn between $122,900.00 and $177,200.00 per year, depending on experience, location, and employer.

What is a software engineer?

Software Engineers are professionals who design, develop, test, and maintain computer software and systems. They use programming languages, engineering principles, and problem-solving skills to build applications, websites, or software solutions that meet specific needs. Software Engineers may work in a variety of industries, such as technology, finance, healthcare, or entertainment, collaborating with other team members to deliver functional and reliable software. Their role often involves analyzing user requirements, writing code, debugging errors, and continually improving software performance.

What are the key skills and qualifications needed to thrive as a software engineer, and why are they important?

To thrive as a Software Engineer, you need strong programming skills, problem-solving abilities, and a degree in computer science or a related field. Familiarity with coding languages (such as Python, Java, or C++), version control systems like Git, and knowledge of software development methodologies are typically required. Excellent teamwork, communication, and adaptability distinguish top performers in this role. These skills ensure efficient, high-quality software development that meets user needs and adapts to technological changes.

What are some common challenges software engineers face when collaborating on large development teams?

Software engineers working on large teams often encounter challenges with communication, code integration, and maintaining consistent coding standards. Coordinating across multiple developers can lead to merge conflicts and misunderstandings about project requirements or priorities. Adopting tools like version control systems, regular code reviews, and clear documentation helps mitigate these issues. Building strong collaboration skills and proactively seeking clarification are key to ensuring smooth teamwork and project success.

What is the difference between Software Engineer vs Software Developer?

AspectSoftware EngineerSoftware Developer
CredentialsBachelor's degree in CS or related field, certificationsBachelor's degree often preferred, certifications optional
Work EnvironmentDesigning, developing, testing, and maintaining software systemsWriting, coding, and implementing software applications
Industry UsageUsed across tech, finance, healthcare, and more for system-level rolesCommonly used in app and web development projects
Search IntentUnderstanding roles, responsibilities, and qualificationsLearning about coding, programming, and project work

While both roles involve software creation, Software Engineers typically focus on designing and architecting complex systems, whereas Software Developers mainly concentrate on coding and building specific applications. The roles often overlap, but the Engineer role may require broader system knowledge and design skills.

Are software engineers still in demand?

Yes, software engineers are in high demand across many industries due to ongoing digital transformation, the growth of cloud computing, and the need for software development, maintenance, and cybersecurity skills. The profession offers strong job stability, competitive salaries, and opportunities to work with various programming languages and tools.

Is 25 too late to become a software engineer?

Age is not a barrier to becoming a software engineer; many professionals start careers in tech in their mid-20s or later. Success depends on acquiring relevant skills, such as programming languages and problem-solving, often through coding bootcamps, online courses, or formal education. Employers value skills and experience over age, making it possible to enter the field at 25 or older.
More about Software Engineer jobs

What are the most commonly searched types of Software Engineer jobs in Rutland, VT?

The most popular types of Software Engineer jobs in Rutland, VT are:

What are popular job titles related to Software Engineer jobs in Rutland, VT?

For Software Engineer jobs in Rutland, VT, the most frequently searched job titles are:

What cities near Rutland, VT are hiring for Software Engineer jobs?

Cities near Rutland, VT with the most Software Engineer job openings:

Software Engineer jobs near you
Infographic showing various Software Engineer job openings in Rutland, VT as of August 2026, with employment types broken down into 95% Full Time, 2% Temporary, and 3% Contract. Highlights an 91% In-person, 2% Hybrid, and 7% Remote job distribution, with an average salary of $151,110 per year, or $72.6 per hour.

AI Agent Trajectory Annotator and Reviewer

Rutland, VT • On-site

Bespoke Labs
See more jobs at Bespoke Labsexternal

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

Apply