This is a fully remote Automation Test Engineer role, open worldwide, paying $92,000 a year. The team ships code every day, and this position exists to ensure automated coverage keeps pace with that speed rather than falling behind. It's a full-time seat, not a contract gig, and it reports into the same engineering group that owns the product itself. The person who takes this on will have real ownership over how testing gets done, not just a queue of tickets handed down from someone else.
The product itself moves fast. New features land weekly, and the automation strategy has to flex around that pace rather than fight it. Anyone who's worked on a team where the test suite constantly lags behind the codebase will recognize the problem this role is meant to solve.
What This Role Actually Does
No fluff here, just the work.
- Build out new automated checks for features as they're developed, and keep the existing ones from going stale as the product changes underneath them
- Wire those tests into the CI/CD pipeline so they run on every build, not just before a release
- Dig through test results, separate real failures from noise, and get defects in front of developers early enough to actually matter
- Push for better testability in the product itself, since some bugs are easiest to prevent before a single line of test code gets written
Tests that fail for no real reason train people to stop trusting red builds, and once that trust is gone, an actual bug can slip through disguised as just another false alarm. Part of the job is keeping the suite honest: fast, reliable, and actually trusted by the team running it. That trust doesn't come automatically. It gets built one clean pipeline run at a time.
Tools and Skills You Need
- Selenium or a comparable browser automation tool, used in a real production setting rather than a training course
- Solid coding skills in Java or Python, enough to build and debug scripts independently without leaning on someone else
- Direct, hands-on experience getting automated checks running inside a CI/CD pipeline
- A sharp eye for what a test should actually verify, so the suite catches real problems instead of just running green
A four-year degree is the baseline for this one, and the field should be computer science or a closely related field. In terms of experience, the team wants at least 30 months of working with real automated coverage on a live, shipping product. Coursework projects and personal side scripts don't count toward that number; it needs to be work done where a missed bug had actual consequences. Someone sitting just under that mark with a genuinely strong portfolio shouldn't rule themselves out before even applying.
Nice-to-Haves
None of these are required, but they'll turn heads.
- Experience with a behavior-driven framework like Cucumber
- Some background in API testing, not just UI-level automation
- Time spent standing up or maintaining test infrastructure on AWS or Azure, rather than just reading about it
- Exposure to Docker or containerized test environments
A candidate who's touched even two or three of those will stand out from the pack. Nobody expects mastery across the board, and the team would rather see depth in one or two areas than a shallow pass through all four. Someone who's spent real time inside Docker but never opened Cucumber is in exactly the same boat as someone who's the reverse; either background works fine here.
Here's a real example from a recent sprint: a suite of checkout tests started failing intermittently in CI, but only on the pipeline's faster runners. It turned out a page was rendering its final state a beat after the test assumed it was ready, a timing bug that only showed up under load. Fixing it took more patience than cleverness, and that's fairly typical of the work. Debugging automation issues eats up real time some weeks, and this role expects someone comfortable with that rather than frustrated by it. Other weeks are quieter, mostly steady maintenance and small additions rather than chasing down a mystery. The ratio between those two kinds of weeks shifts with the release calendar, and it's rarely predictable more than a sprint or two out.
The Package
Salary is $92,000 a year, full-time, fully remote.
- Health insurance
- Paid time off
- 401(k) matching
- Remote-work flexibility, open to candidates anywhere
- Access to an employee assistance program for support outside of work, including mental health
That last one gets skipped over a lot in job listings, but Naukri Mitra includes it here because burnout in QA is real and quietly common, especially for people carrying an automation suite mostly on their own. Having a real support line matters more than a free lunch ever did, and it says something about how the team thinks about the people doing this work, not just the output they produce. Pay reviews happen on a set annual schedule too, so raises aren't something you have to fight for or bring up awkwardly in a one-on-one.
Next Steps
Send a resume plus a link to a repo or a sample test suite you've built, something that shows your actual code rather than a bullet point claiming you can write it. Rolling review, no fixed close date. Given the pay band and the worldwide eligibility, expect this one to draw serious interest, so a strong writing sample in the application goes a long way toward standing out early rather than getting lost in a pile. Anyone unsure whether their background lines up closely enough should still apply; the listed experience is a reasonable floor, not a hard cutoff, and a well-built sample project can say more than a resume line ever will. There's no separate coding test scheduled before the first conversation either, since the sample already does most of that work.
