Associate QA Engineer

About the role

This role defines and protects the Relay platform experience by validating features across user interfaces and device ecosystems. It targets recent graduates who bring foundational computer science knowledge and a drive to learn. The position operates from the Raleigh headquarters in a hybrid schedule.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Support end-to-end testing that covers Relay Devices and server-side components to validate integrated behavior.

Author test cases and acceptance tests that verify feature behavior before release.

Join Sprint planning and design sessions to clarify requirements and testing approaches.

Collaborate with project teams to understand requirements for new initiatives and align testing efforts.

Perform in-depth analysis by examining logs and querying data to isolate issues.

Rank test cases to achieve the strongest possible test coverage for each release.

Work effectively with cross-functional teammates in a small, fast-moving environment.

Investigate, communicate, and confirm defect resolutions so issues are fully resolved.

Record test methodologies, tools, and outcomes to create clear documentation for future reference.

Requirements

Hold a Bachelor's degree in Computer Science or Computer Engineering with a GPA of 3.2 or higher.

Apply an analytical approach to problem-solving when evaluating software behavior.

Explain Agile concepts and QA processes such as functional testing, regression testing, and smoke testing.

Use the Android Debug Bridge (ADB) and device logging tools to inspect runtime behavior.

Communicate clearly with developers and QA colleagues to understand features and defects and to share testing status.

Manage multiple tasks while identifying the next priority item to maintain progress.

Comfortably work in a Linux environment using file commands, grep, cat, bash, and vim.

Develop and debug automated test scripts to improve regression efficiency.

Leverage Python or other coding experience to support test automation when possible.

Show eagerness to learn and grow through feedback and structured development programs.

Bring 0-2 years of testing experience with Android, iOS, Web/Desktop, Networking, or similar domains.

Practical notes

Relay does not sponsor employment for this role.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

The platform captures large volumes of data weekly and uses AI tools for tasks such as noise suppression and translation.

Team members follow CHASE values and a learning framework aimed at continuous improvement.

The role is part of an engineering team that builds and tests complex tools used in real-world operations.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.