ZipRecruiter

Log In

2

Manual Software Testing Remote Jobs in Indiana (NOW HIRING)

Preventia

Software Developer

Indianapolis, IN · On-site +1

We have a flexible work environment with a mixture of remote work and in office hours ... Experience with test-driven development and automated testing frameworks. * Experience with cloud ...

BC Forward

Fullstack Software Developer

Indianapolis, IN · Remote

$68 - $71/hr

Remote Duration: Contract - 6 months Pay Range: $68/hr $71/hr (W2) Job ID: 373649 About BCforward ... Approve, schedule, and supervise installation and testing of new products and system improvements.

Allegion

Software Development Tools Manager

Carmel, IN · Remote

$123K - $162K/yr

... testing, release management, and observability. This is a hands-on leadership role that ... Drive automation: reduce manual steps in build/test/deploy pipelines, improve reproducibility, and ...

E-gineering

Software Engineer

Indianapolis, IN · On-site +1

Current opportunities allow for remote work from home. At E-gineering, we handle a variety of ... Experience with unit and integration testing and designing test systems * Awareness of ...

E-gineering, Inc.

Software Engineer

Indianapolis, IN · On-site +1

Current opportunities allow for remote work from home. At E-gineering, we handle a variety of ... Experience with unit and integration testing and designing test systems * Awareness of ...

next page

Showing results 1-20

All JobsManual Software Testing Remote JobsManual Software Testing Remote Jobs in Indiana

Manual Software Testing Remote information

See Indiana salary details

$9

$39

$57

How much do manual software testing remote jobs pay per hour?

As of Jun 17, 2026, the average hourly pay for manual software testing remote in Indiana is $39.88, according to ZipRecruiter salary data. Most workers in this role earn between $32.02 and $46.44 per hour, depending on experience, location, and employer.

What are the key skills and qualifications needed to thrive as a Manual Software Tester working remotely, and why are they important?

To thrive as a Manual Software Tester in a remote setting, you need a solid understanding of software development life cycles, test case design, and defect tracking, typically supported by a degree in computer science or a related field. Familiarity with bug tracking tools like Jira, test management systems such as TestRail, and basic knowledge of SQL are commonly required. Strong attention to detail, effective written communication, and self-motivation are crucial soft skills for remote collaboration and problem-solving. These skills ensure accurate testing, clear reporting, and efficient teamwork, leading to higher software quality in distributed environments.

How does a remote manual software tester typically collaborate with development teams to resolve bugs and improve product quality?

Remote manual software testers regularly communicate with developers and product managers using tools like JIRA, Slack, or Microsoft Teams. They document defects clearly, provide detailed reproduction steps, and may participate in virtual stand-up meetings or sprint reviews. Strong written communication and proactive status updates are key to ensuring issues are understood and resolved efficiently. Building positive, solution-oriented relationships with team members helps testers advocate for quality while working remotely.

What is manual software testing in a remote job?

Manual software testing in a remote job involves evaluating software applications for defects or issues without using automated tools, all while working from a location outside of a traditional office. Testers follow test cases, report bugs, and collaborate with development teams using online communication and project management tools. Remote manual testers need strong attention to detail, clear documentation skills, and the ability to work independently. This role is crucial for identifying user experience issues and ensuring software quality before release.

What is the difference between Manual Software Testing Remote vs Manual QA Tester?

AspectManual Software Testing RemoteManual QA Tester
CredentialsTypically requires a QA or testing certification, basic technical skillsOften requires similar certifications, testing experience, and understanding of QA processes
Work EnvironmentRemote, often freelance or contract-basedCan be remote or on-site, depending on employer
Industry UsageCommon in software development, tech companiesUsed across various industries including tech, finance, healthcare
Search & Comparison IntentOften searched by those looking for remote testing rolesCompared for similar testing roles, often in job searches

Manual Software Testing Remote and Manual QA Tester roles share similar skills and certifications, but differ mainly in work environment and job search intent. Manual Software Testing Remote emphasizes remote work, while Manual QA Tester may be on-site or remote. Both roles are vital in ensuring software quality across industries.

What are the most commonly searched types of Manual Software Testing jobs in Indiana? The most popular types of Manual Software Testing jobs in Indiana are:
What are popular job titles related to Manual Software Testing Remote jobs in Indiana? For Manual Software Testing Remote jobs in Indiana, the most frequently searched job titles are:
What job categories do people searching Manual Software Testing Remote jobs in Indiana look for? The top searched job categories for Manual Software Testing Remote jobs in Indiana are:
What cities in Indiana are hiring for Manual Software Testing Remote jobs? Cities in Indiana with the most Manual Software Testing Remote job openings:
Manual Software Testing Remote jobs near you

Controls MBD Engineer

Pentangle Tech Services | P5 Group

Columbus, IN • Remote

$77K - $100K/yr

Other

Posted 8 days ago

Job description

Controls MBD Engineer

Job Description & Skill Requirement:

1. Creation and maintenance of tuning guides, testing reports, testing plans, certification documents of relevant engine system features

2. Systems engineering of the software change requests including analysis of a problem statement and solution proposition

3. Software requirements development

4. Feature simulation model development

5. Software Development

6. Verify the implementation using simulation and open/closed-loop test with Model In-Loop or Hardware In-Loop.

7. Perform required bench testing (remote access to benches will be provided).

Apply