Quality Assurance Analyst

Job Purpose:

Manually test the company's web and mobile applications to improve release stability and protect the customer experience. Partner closely with the Product team to make sure acceptance criteria on every story are crystal clear, testable, and complete before work begins. Build and maintain test plans, test cases, and step-by-step testing instructions that any team member can follow. Execute regression, smoke, exploratory, and acceptance testing across new features and existing functionality. File clear, reproducible bug reports and verify fixes before they ship. Help the team ship fewer regressions, catch issues earlier, and continuously raise the bar on quality. ALL VIVE employees will be vigilant to support the positive compliant company posture by familiarizing themselves with all policies, procedures, standards, and guidelines and act accordingly. 

About VIVE:

Headquartered in Flint, MI, VIVE is a fast-paced, growing company providing real estate compliance

software and services to property managers. VIVE enables customers to find, onboard, and manage

vendors across property portfolios. VIVE is the most effective risk management tool for vendor compliance

in the market, with services that include screening for proper licensing, adequate and current insurance,

criminal activity, government watch lists, and financial capacity. For more information about VIVE, visit

www.GetVIVED.com.

Duties and Responsibilities:

• Execute manual test cases against new features, bug fixes, and release candidates to validate behavior before deployment.
• Build and maintain test plans, test suites, and step-by-step test instructions that are clear enough for anyone on the team to run.
• Partner with Product Managers and engineers during refinement and sprint planning to pressure-test acceptance criteria and make sure stories are testable before they're committed.
• Perform exploratory testing on new functionality to surface edge cases that scripted test cases miss.
• Run smoke tests and regression passes against staging and production environments on a regular cadence.
• Verify bug fixes and confirm tickets are truly resolved before they're closed out.
• Write clear, reproducible bug reports in Jira with steps to reproduce, expected vs. actual behavior, environment details, screenshots, and severity.
• Help triage incoming bugs from internal users and customers, including reproducing reported issues and assigning priority.
• Track defect trends across releases and surface patterns to engineering and product leadership.
• Participate in release readiness reviews and give a clear go / no-go recommendation based on test results.
• Maintain an organized library of test cases, test data, and testing documentation in Confluence (or the team's documentation tool of choice).
• Coordinate user acceptance testing (UAT) sessions with internal stakeholders when needed and document the results.
• Continuously look for ways to improve the team's QA process, tooling, and feedback loop with engineering.
• Stay close to the product so you can be a reliable second set of eyes on customer-facing changes.

Minimum Experience Required:

Zero (0) to five (5) years of experience in a software quality assurance, testing, support, or similar role is preferred. We're open to candidates who are early in their QA career as well as those with several years of hands-on testing experience. 

Required Experience Requirements:

• Hands-on exposure to testing software applications, whether through prior work, internships, coursework, or self-directed projects.
• Comfort working with web and/or mobile applications across common browsers and devices.
• Experience writing or following structured test cases and test plans (or a willingness to learn quickly).
• Familiarity with how software development teams work — sprints, tickets, releases, etc.
• Strong written communication: able to file a bug report that an engineer can act on without follow-up questions.

MINIMUM EDUCATION REQUIREMENTS

Minimum Education Requirements:

High School Diploma / GED 

Work Activity:

• Interacting with computers for extended periods.
• Communicating with team members and occasionally with persons outside the organization.
• Updating and using relevant knowledge about the product and testing best practices.
• Processing information and identifying patterns across many small details.
• Documenting test results, bugs, and acceptance criteria clearly.
• Coordinating with engineers, product managers, designers, and customer-facing teammates.
• Providing notifications to stakeholders when blocking issues are found.
• Responding to questions from product, engineering, and support about quality and known issues.
• Desire to continuously learn and improve skills.
• Ability to keep up to date with QA and software testing best practices.

Required Skills:

• Attention to Detail

Noticing the small things — copy errors, off-by-one bugs, broken states, weird edge cases — that other people miss. 

• Manual Testing

Walking through an application as a real user would, exercising both the happy path and the unhappy paths, and capturing what you observe. 

• Test Case Design

Translating requirements and acceptance criteria into a set of clear, repeatable test steps with expected results. 

• Bug Reporting

Writing reproducible bug reports with steps, expected vs. actual behavior, environment, severity, and supporting evidence. 

• Acceptance Criteria Review

Reading product stories critically and asking the questions that surface ambiguity before code gets written. 

• Critical Thinking

Thinking about how a feature could fail, not just how it's supposed to work. 

• Communication

Writing clearly, asking good questions, and giving direct, respectful feedback to product and engineering teammates. 

• Organization

Keeping test plans, test runs, and bug lists organized so the team can trust the state of quality at any given moment. 

• Curiosity

Wanting to understand how the product actually works, not just what the ticket says it should do. 

• Time Management

Balancing focused testing time with the interrupt-driven reality of supporting a release. 

Preferred Skills:

• Some software development experience or working understanding of how software is built — even at a hobbyist or coursework level. You don't need to be a developer, but knowing what code looks like, how a build pipeline works, or what a database query does will help you test smarter.
• Interest in growing into a software engineering role over time. We're happy to support a career path from QA into engineering for someone who wants it.
• Or, alternatively, interest in growing into a product management role. The QA-to-PM path is a great one, and this role gives you a front-row seat to product decisions, customer pain points, and acceptance criteria.
• Familiarity with reading code (even just being able to follow along in a pull request) — not required, but a real advantage.
• Exposure to API testing, browser dev tools, or SQL queries for digging into data while testing.
• Curiosity about test automation and a desire to eventually contribute to automated test coverage.

Tooling:

• Jira (or a similar issue tracker) for filing and triaging bugs and tracking test work.
• Confluence (or a similar wiki) for maintaining test plans and documentation.
• Modern web browsers (Chrome, Safari, Firefox, Edge) and their developer tools.
• Mobile device testing across iOS and Android (physical devices and/or simulators).
• Microsoft Word, Excel, PowerPoint, Teams, OneNote, and SharePoint.
• Screen capture and screen recording tools for documenting bugs.
• Familiarity with a test case management tool (TestRail, Zephyr, Xray, or similar) is a plus, not a requirement.
• Familiarity with API testing tools (Postman or similar) is a plus, not a requirement.

Physical Requirements:

• Sitting for extended periods.
• Repetitive typing and data entry.
• Use hands to finger, handle, or feel.
• Reach with hands and arms.
• Talk or hear.
• Visual focus on screens for extended periods.