Quality Engineer

Title: QE Engineer

Location: North Carolina

Job Description

Role Overview

We are seeking a skilled Quality Engineering Automation Engineer to embed directly within our application development teams. This is an engineering-led role focused on designing, building, and sustaining automated test systems that improve product quality, delivery confidence, and system resiliency.

The ideal candidate approaches quality as a software engineering discipline — writing maintainable test code, thinking systemically about failure modes, and working side-by-side with developers to shift quality left. This role is not primarily about manual testing or test case management; it is about building reliable, code-driven automation at scale.

Key Responsibilities

Test Design & Implementation

• Design and implement automated test suites that span multiple layers of the application stack — from unit and integration tests through to end-to-end scenarios
• Build stable, maintainable tests for both frontend interfaces and backend services, using programming languages and frameworks appropriate to the technology stack
• Develop API and service-level tests that validate contracts, data flows, and business logic across distributed systems
• Implement resiliency and non-functional tests to validate system stability, reliability, and graceful degradation under failure conditions

Test Infrastructure & Strategy

• Create test harnesses, mocks, stubs, and test data strategies that enable reliable, repeatable automation
• Contribute to quality gates and automation standards within build and deployment pipelines to enable continuous testing
• Support test strategies for applications integrated with cloud-based services and infrastructure
• Diagnose and resolve test failures in collaboration with application engineers, improving signal quality and reducing flakiness

Engineering Collaboration

• Partner closely with application engineers to embed testing into feature development from the outset
• Influence engineering quality practices across teams, helping define standards and patterns for testability
• Continuously improve test coverage, execution speed, and overall feedback loop quality

What Success Looks Like (First 6–12 Months)

• Automated test coverage is measurably expanded across frontend and backend systems
• Continuous testing provides fast, reliable signal on code changes throughout the pipeline
• Defects are consistently detected earlier in the development lifecycle, reducing downstream cost
• End-to-end tests are stable, trusted, and actively maintained by the broader engineering team
• Application engineers are collaborating on and contributing to automated tests as a standard practice
• Production incidents attributable to regressions show a measurable decline over time

Minimum Qualifications

• Bachelor’s degree in computer science, Engineering, or a related field — or equivalent professional experience
• 3–6 years of hands-on experience in software quality engineering or test automation in a software product environment
• Strong programming proficiency in at least one modern, widely-adopted language; ability to write clean, maintainable test code
• Demonstrated experience building automated tests for backend APIs and services, including validation of request/response contracts and error handling
• Experience with automated testing of modern web-based frontend applications
• Familiarity with version control practices and collaborative software development workflows
• Ability to work closely with software engineers in Agile delivery teams, contributing directly to sprints and feature work

Preferred Qualifications

• Hands-on experience with end-to-end UI test automation, including strategies for managing test reliability and reducing flakiness
• Experience with API testing approaches including contract testing, schema validation, and service level verification
• Familiarity with component-level testing strategies and visual regression concepts for frontend systems
• Experience testing applications that integrate with cloud services, including awareness of infrastructure-related failure scenarios
• Exposure to performance, resiliency, or reliability testing — such as load testing or chaos engineering concepts
• Understanding of test automation design patterns, including mocking, test isolation, and test data management
• Familiarity with behaviour-driven development (BDD) practices or structured test management approaches is a plus, but not required