Quality Engineer

Role Overview

We are looking for a Quality Engineer who treats quality as an engineering problem, not a manual one. You will build and own the testing infrastructure and frameworks that let every engineer ship small changes to production with confidence, in minutes, behind an automated quality gate. This is a hands-on role: you will stand up environments, write code, and design the regression suites that act as the release gate for the whole engineering org.

You share a great deal of skill set with our platform engineers when it comes to setting up infrastructure: provisioning sandbox environments, wiring tests into CI/CD, and operating them reliably. On top of that, you bring deep quality engineering: you design QA frameworks that all engineers contribute to, you write automated UI tests, and you treat the health of the test suite itself as a first-class, measured system.

Your near-term flagship deliverable is a Closed Box Regression Suite: an automated, owned, and continuously run set of tests that act as a quality gate for every release, run against a production-like sandbox, and designed so the same tests can eventually run in production with configuration changes alone.

About Localytics

Localytics is an AI-enablement firm for enterprise marketing organizations. We build, integrate, and operate marketing AI for modernizing teams.

We have been working inside CRM marketing for fifteen years. We have a long history of successfully supporting enterprise brands through our mobile analytics and engagement platform. Today, our mission is to help modernizing brands integrate the latest technologies across their marketing workflow, help them operate it, dramatically impacting outcomes.

Localytics is a lean, fast-growing team at an exciting juncture. We are building a work culture that values integrity, ownership, and impact. No matter your role, you'll have real responsibility, influence, and the opportunity to build things that matter.

What You'll Do

Own the Quality Gate

• Own the framework, conventions, reporting, and gate integration, while making it easy for every engineer to contribute coverage for the features they build
• Build automated gates that replace slow manual verification, so engineers stop waiting days for sign-off and start shipping small changes quickly
• Treat a change that is correct but materially slower or noisier as a regression worth blocking on, keeping behavior and performance both first-class

Keep the Gate Trustworthy

• Track flakiness, runtime, and coverage as first-class signals, because a slow or flaky gate gets bypassed and defeats its own purpose
• Reduce manual testing wherever possible and push meaningful verification left, out of production and into the gate

AI-Forward & Collaborative

• Use AI coding assistants to write and maintain tests faster, and build AI agents that extend the quality function
• Work closely with platform, product, and feature engineers to align quality standards with how the team actually ships

Capabilities You Bring

Professional Background

• 5+ years of professional experience in software quality engineering, test automation, or SDET roles, with meaningful time spent building frameworks rather than only writing test cases

Coding & Frameworks

• Strong hands-on coding ability in a language such as Python, Golang, or Java. Writes maintainable test code and tooling, not just scripts, and reads the application code being tested
• Proven experience designing and owning test frameworks that many engineers contribute to: shared conventions, fixtures, reporting, and the patterns that keep a growing suite trustworthy
• Experience testing systems at their public boundaries and contracts, the way a real client or SDK consumer experiences them, so tests stay durable across refactors

Test Automation Tooling

• Skilled with modern UI test automation tooling (Playwright, Cypress, Selenium, or similar) for dashboard and web application coverage
• Comfortable writing automated tests against APIs, services, and event-driven systems, asserting on observable behavior and performance
• Skilled in wiring test suites into CI/CD pipelines (GitHub Actions or similar) as required quality gates that block or promote releases

Environments & Infrastructure

• Hands-on experience provisioning and operating test environments on AWS, including containerized services (Docker, Kubernetes) and infrastructure as code (Terraform, CloudFormation)
• Understanding of why a sandbox must mirror production in components, topology, and realistic data, and experience reducing the gap between the two

Observability

• Familiarity with capturing execution time, latency, and error rates as part of a test run
• Comfortable with monitoring and logging tools (CloudWatch, Signoz, Prometheus, ELK)

Security & Resilience Testing

• Working knowledge of security and penetration testing concepts (OWASP Top 10, common web and API vulnerabilities)
• Experience with load testing and penetration testing as periodic checks against a production-like environment

Production Readiness

• Experience running tests safely against production, or designing suites that can be promoted from sandbox to production through configuration alone

Nice to Have

• Experience testing client SDKs and the applications that embed them, including mobile
• Familiarity with blue/green deployments and how a quality gate fits ahead of a production cutover
• Experience validating that AI agents are safe to deploy in production: testing guardrails and output constraints, checking for token explosion and runaway cost or latency, probing failure and fallback behavior, verifying agents stay within intended scope
• Experience putting AI agents to work inside the regression suite itself (e.g., a flaky-test agent that quarantines nondeterministic tests and opens a ticket, or a report agent that summarizes a run in plain language)

Outcomes You Will Deliver

Release Confidence

• Become the confidence engine that lets the team move from batched, cautious releases toward frequent, small, low-risk ones
• Measurably reduce the change failure rate of production deploys, catching behavior, performance, and security regressions in the gate before they reach customers

Adoption & Stability

• Drive broad adoption of the suite, with engineers across teams routinely contributing tests for the features they build and treating the gate as part of how they ship rather than an obstacle
• Own pre-production stability and fidelity, keeping the sandbox stable and production-like enough that the gate stays trustworthy and engineers are not blocked by environment flakiness

AI Quality

• Validate that AI agents built by the team, including those written by Forward Deployed Engineers for customer environments, are production-ready: guardrails hold, token cost and latency stay bounded, failure modes are handled, and agents stay within scope before they reach production
• Reduce manual quality overhead through agentic QA, deploying AI agents that scaffold tests, triage failures, and summarize results, freeing engineering time for higher-order quality work