Test Automation Engineer

Who We Are

EdgeBeam is the world’s first Hybrid Network Operator (HNO)—a foundational layer at the edge enabling one-to-many data distribution for today’s wireless networks. We create & sell wireless services and solutions that solve edge connectivity challenges to connect people, data & devices through the untapped potential of broadcast networks.

Location & Work Dynamics

This position is headquartered in our Boston Seaport office and is a dedicated on-site role, not remote or hybrid. At this critical stage of EdgeBeam's growth, we believe that high-fidelity, in-person collaboration is essential to our success.

Role Overview

This role exists to make Edgebeam’s Playwright suite a reliable, gated part of the CI/CD pipeline — and to expand automation coverage as that pipeline matures. You will own the CI/CD side of the test platform (Playwright in GitHub Actions, smoke gates on pull requests, results integration with our test aggregation and case management systems) and increasingly write the API and UI automation tests that run through it. Early focus is making the pipeline trustworthy. Once it is, your day shifts toward authoring tests, expanding coverage, and partnering with engineering on test design for new features.

What You Will Do

• Own the CI/CD test pipeline: how Playwright runs in GitHub Actions, what gets gated at PR vs. nightly, and how results flow to the rest of the test platform.
• Define the test tag convention and runtime targets so PR feedback is fast and nightly coverage is broad.
• Integrate Playwright with the team’s test result aggregation platform (ReportPortal) and test case management system (Xray for Jira) — own the integration end; platform operations ownership sits elsewhere on the team.
• Enforce selector hygiene in every test — getByRole, getByLabel, getByTestId, never CSS classes — so UI tests survive visual and component refreshes.
• Write and maintain Playwright tests across API (primary today) and UI (BSS/OSS, stream analysis, refreshed screens). This share of the role grows as the CI/CD pipeline stabilizes and becomes a larger part of the week thereafter.
• Pair with engineering on Outside-In TDD for net-new features and push data-testid adoption into the code review checklist.
• Run the kill-the-flaky-test policy: auto-quarantine after three consecutive flaky runs, ticket the owner, fix-or-delete in seven days.
• Help formalize the AI-assisted triage workflow — prompting that reads the failure log plus the PR diff and proposes a hypothesis for human accept or reject.
• Set the bar for test quality as the test team scales from two to four; mentor by example.
  

What You Bring

• 5+ years writing and maintaining automated tests in production environments, including time spent owning a CI/CD test pipeline.
• Deep, hands-on Playwright (TypeScript or JavaScript) for both API and UI testing.
• Proven experience running Playwright at scale through CI/CD — sharding, parallelization, retries, artifact handling — in GitHub Actions (or comparable: GitLab CI, CircleCI).
• Familiarity with test result aggregation tooling (ReportPortal, Allure TestOps, Currents.dev, or equivalent) and test case management systems (Xray, Zephyr, TestRail, or equivalent) — enough to integrate cleanly, not necessarily to operate them.
• Selector strategy fluency: you write UI tests that survive a visual or component refresh.
• Strong opinions on flaky tests and the discipline to enforce a quarantine policy.
• Clear, written communication and the judgment to push back when scope or process slips.
• An AI first mindset and an ability to solve and implement using AI

Our Values

At EdgeBeam, we operate with a shared set of values:

• Customers First — We put our customers' objectives and pain points ahead of our own.
• Dig Deep — We are technically curious and thorough in execution. We don’t cream skim.
• Win Together — Collaboration is in our DNA.
• Disagree & Commit — We welcome constructive conflict. Once we have made a decision, we are behind that decision 100%.
• No Jerks — EdgeBeam is not a place for jerks.

What Success Looks Like

30 Days: Understand the current Playwright suite, the day-to-day triage workflow, the acceptance-criteria-to-test gap, and Edgebeam’s product lines (vector platform, agent, devices). Wire existing Playwright API tests into the test result aggregation pipeline.

90 Days: Tag convention defined; sharded GitHub Actions pipeline meets the runtime targets you set. Smoke job publishes PR status; nightly full run publishes aggregated results. First waves of API and UI tests authored against new BSS/OSS and stream analysis features.

180 Days: GitHub Actions smoke gate is a required check on every PR. Pass rate, flaky rate, and mean-time-to-fix are tracked weekly off the aggregated results. Test authoring is now the primary share of your week, expanding coverage across product lines. Kill-the-flaky-test policy is operating. AI-assisted triage workflow is live with the human review checkpoint.