Senior Test Engineer, Performance & Automation

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 onsite 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

We’re building a real test platform under a team that’s about to double, expanding from API-only into UI testing, and shifting toward agentic development workflows. This senior role has two jobs running in parallel: stand up performance testing as a new discipline at Edgebeam — tooling, baselines, and gates — and materially expand automated functional coverage across the vector platform and device software. You’ll work alongside the existing Playwright-based automation effort and the incoming ReportPortal + Xray stack, and you’ll set the bar for how performance and load testing are done here.

What You Will Do

• Build out the performance test system from scratch — tooling selection, environment, baselines, and the workflow that gets results back to engineering.
• Author and maintain performance, load, soak, and stress tests against the vector platform APIs and device software using K6 (preferred) and/or JMeter.
• Expand automated functional test coverage in Playwright across the vector platform and device software, with disciplined selector hygiene and Jira-linked test cases.
• Integrate performance tests into GitHub Actions and ReportPortal; define the SLOs and the regression thresholds that trip a build.
• Partner with engineering on data-testid conventions, AC-driven test design, and Outside-In TDD on net-new features (stream analyzer first).
• Triage performance regressions and functional failures, working with dev to root-cause and close the loop.
• Mentor junior testers on automation patterns, test strategy, and performance fundamentals.
• Help shape the team’s adoption of AI-assisted test authoring and triage, with a human-in-the-loop review discipline.
  
  

What You Bring

• 7+ years of test engineering experience, with at least 3 years focused on performance and load testing of distributed backend systems.
• Hands-on expertise with K6 (preferred) and JMeter — scripting, parameterization, results interpretation, CI integration.
• Strong automation chops in Playwright (or comparable modern framework) for API and UI testing; JavaScript/TypeScript fluency.
• Solid understanding of HTTP, REST, WebSockets, and the kinds of failure modes that show up under load (connection pool exhaustion, GC pressure, tail latency, backpressure).
• Experience defining SLOs, baselining, and gating builds on performance regressions.
• Comfort working in AWS and observing systems through logs, metrics, and traces.
• Git, GitHub Actions, and a working knowledge of Jira and test case management.
• Wireless, broadcast, telecom, or embedded device test experience is a plus.
• 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: Ramped on the vector platform, device software, and the existing Playwright suite. Performance tool selection (K6 vs. JMeter, or both) decided with a written rationale. First performance test running end-to-end against a non-prod environment, even if narrow.

90 Days:  Performance test suite covers the top 3–5 critical paths on the vector platform with baselines and pass/fail thresholds. Functional automation coverage measurably up — concrete number of new Playwright tests landed, all Jira-linked. Performance results flowing into ReportPortal and visible to engineering. Owning the perf review for at least one release.

180 Days: Performance gating in CI for critical paths. A trend dashboard that surfaces regressions before they ship. Device software covered with both functional and performance tests. Documented performance testing playbook the rest of the team can run against. Mentoring at least one junior tester on automation strategy.