Quality Assurance Engineer jobs in Charleston, SC

Who We Are:
Omatic solutions are purpose-built using the direct feedback of our 3,000 social good customers. With over 80% of nonprofit organizations leveraging 4 or more cloud solutions today, the need for a uniquely tailored integration solution has never been greater. 

Omatic is a place where the employees thrive on helping others, both through business goals and personal pursuits. Fun, energetic, and lively are terms frequently used to describe the culture at Omatic, and this is balanced by an undercurrent of hard work and commitment. The team tackles challenges, revels in the process of solving problems, celebrates the wins for our company and our customers, all while existing to empower social good organizations. 

What You Will Do:
The focus of this role is improving our cost-of-mistake curve by aligning our delivery teams with a shared understanding of quality before development work begins. This role will facilitate spec workshops and help the teams create executable acceptance criteria that can be published and referenced by all teams at Omatic.

• Facilitate delivery team spec workshops to modulate scope. This will involve working with product delivery to determine how much work should be accommodated in sprints.
• Provide a grouping strategy for features and abilities with the product delivery team. This will involve collaboration on and publishing of feature breakdowns.
• Provide an organizing strategy for executable specs with the test delivery team. This will involve the maintenance of a persistent, shareable repository of specifications.
• Facilitate discussions with the development team on appropriate abstractions to test at, such as unit, integration or system. This will also involve collaboration on contract tests.
• Facilitate additions and modifications to the style guide for all user interface elements that are undefined.

What You Will Bring to Omatic:
Successful candidates will demonstrate the ability to do the following:

• Think and act experimentally.
• Demonstrate how to think about test and data conditions.
• Articulate and demonstrate various test techniques.
• Articulate and demonstrate various test heuristics.
• Spot bad tests and turn them into good tests.
• Craft requirements as tests.
• Communicate testability ideas to engineers.