ZipRecruiter

Log In

1

Internship Software Developer In Test Jobs in Pierre, SD

Workiva

Spring 2027 Intern - Sales Enablement

Pierre, SD · On-site

$21/hr

Build and test basic automation rules, email sequences, or lead routing. * Team Training: Write ... in a Workiva office Location: This internship is primarily a remote opportunity. However, if you ...

New

Workiva

Spring 2027 Intern - Sales Enablement

Pierre, SD · On-site +1

$21/hr

Build and test basic automation rules, email sequences, or lead routing. * Team Training: Write ... in a Workiva office Location: This internship is primarily a remote opportunity. However, if you ...

New

U.S. Navy

ENGINEERING AIDE

Pierre, SD

Every successful engineering career needs a solid foundation, and as an Engineering Aide in the ... Conducting concrete, soil and asphalt tests and quality control inspections * Reading and ...

U.S. Navy

ENGINEERING AIDE

Pierre, SD · On-site

Every successful engineering career needs a solid foundation, and as an Engineering Aide in the ... Conducting concrete, soil and asphalt tests and quality control inspections * Reading and ...

previous page

Showing results 41-60

All JobsSoftware Developer In Test JobsInternship Software Developer In Test JobsInternship Software Developer In Test Jobs in Pierre, SD

Internship Software Developer In Test information

See Pierre, SD salary details

$11

$22

$39

How much do internship software developer in test jobs pay per hour?

As of Sep 5, 2026, the average hourly pay for internship software developer in test in Pierre, SD is $22.81, according to ZipRecruiter salary data. Most workers in this role earn between $18.46 and $24.18 per hour, depending on experience, location, and employer.

What does an internship software developer in test do?

An Internship Software Developer In Test works with development and quality assurance teams to create and execute automated tests for software applications. Their main responsibility is to ensure that software products are reliable, functional, and meet quality standards before release. Interns in this role often write test scripts, identify bugs, and help improve testing processes, all while learning about software development and testing methodologies. This position is a great way to gain hands-on experience in both coding and quality assurance.

What are the key skills and qualifications needed to thrive as an internship software developer in test?

To thrive as an Internship Software Developer In Test, you need a basic understanding of software development, familiarity with testing methodologies, and foundational programming skills, often supported by coursework in computer science or related fields. Experience with test automation tools (like Selenium or JUnit), version control systems (such as Git), and exposure to CI/CD pipelines is typically expected. Attention to detail, problem-solving ability, and effective communication are standout soft skills in this position. These competencies ensure reliable software quality, smooth collaboration with development teams, and a solid foundation for future growth in software testing roles.

What types of projects or tasks can an internship software developer in test expect to work on?

As an Internship Software Developer In Test, you can expect to work on a variety of tasks such as writing automated test scripts, executing manual test cases, and assisting in debugging software applications. You'll often collaborate closely with software developers and QA engineers to ensure new features meet quality standards and help identify potential issues early in the development cycle. These responsibilities provide valuable hands-on experience with industry-standard tools and practices, and offer insight into the full software development lifecycle. This role is an excellent opportunity to build practical skills and expand your professional network within the tech industry.

What is the difference between Internship Software Developer In Test vs Software Developer In Test?

AspectInternship Software Developer In TestSoftware Developer In Test
CredentialsTypically pursuing or recently completed a degree in Computer Science or related fieldBachelor's or higher in Computer Science or related field, with some experience
Work EnvironmentEntry-level, learning-focused, often part-time or temporaryFull-time, professional environment with ongoing projects
Employer & Industry UsageInternships offered by tech companies, startups, and software firmsFull-time roles in software development companies, tech firms, and QA teams

The main difference is that an Internship Software Developer In Test is an entry-level, learning position designed for students or recent graduates, while a Software Developer In Test is a full-time professional role requiring more experience. Interns focus on gaining skills and understanding testing processes, whereas full-time developers In Test are responsible for designing and executing test automation and quality assurance tasks.

Internship Software Developer In Test jobs near you

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Pierre, SD

$20 - $30/hr

Full-time

Posted 4 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