Automation Test Engineer Job Description and KRAs

An Automation Test Engineer writes and maintains automated tests that check software works correctly on every build. At the entry level they build test scripts for web or API, run suites, report failures and help keep the automation stable under the guidance of senior QA. A good automation tester writes reliable scripts, understands what to check and tells a real failure from a flaky one. The role sits in the QA or engineering team and reports to a QA lead or senior QA engineer, delivering assigned automation and learning the framework.

Detail	For this role
Department	Information Technology
Level	Entry level
Reports to	QA Lead
Direct reports	None
Experience	Fresher or up to 2 years in test automation

Automation Test Engineer job description template

Copy this job description, replace the text in square brackets and post it on your careers page or a job portal.

Job title: Automation Test Engineer

Department: Information Technology

Reports to: QA Lead

Location: [City], [office, branch or site]

About the role

Key responsibilities

Write automated test scripts for web or API features using the team's framework.
Convert manual test cases into stable, repeatable automated tests.
Run automated suites on new builds and report failures with clear evidence.
Investigate failures to tell a real defect from a flaky or environment issue.
Maintain and refactor existing scripts as the application changes.
Set up and manage test data needed for automated runs.
Help integrate tests into the CI pipeline so they run on every build.
Log defects with clear steps to reproduce and track them to closure.
Improve coverage for the areas most likely to break.
Learn the framework, tools and testing practices with support from seniors.

Requirements

Graduate in computer science, IT or engineering
Working knowledge of an automation tool and a programming language
ISTQB foundation certification is an advantage
Fresher or up to 2 years in test automation

KRAs and KPIs for a Automation Test Engineer

Key result areas for the appraisal form, each with a KPI you can measure every month or quarter.

Key result area	How to measure it
Automation delivery	Assigned test scripts delivered within sprint estimates
Suite stability	Flaky tests in owned scripts kept below the agreed level
Coverage growth	Automated coverage for the module grown to the target each quarter
Defect quality	Logged defects accepted as valid without missing steps
CI health	Automated runs kept green with failures triaged same day
Learning	New automation skills picked up each quarter

Skills and tools

Test automation scriptingSelenium or PlaywrightAPI testing with PostmanProgramming basicsTest case designCI basicsDefect loggingAttention to detailWillingness to learn

Tools used day to day: Selenium, Playwright, Postman, Java or Python, Git, Jenkins.

Reporting line and career path

Moves up from: Manual Tester, Software Trainee, QA Engineer
Next roles: Senior QA Engineer, SDET, Automation Lead

Interview questions for a Automation Test Engineer

What makes an automated test reliable rather than flaky?
How do you decide which manual test cases to automate first?
Walk me through automating a login and a form submission.
A test passes locally but fails in CI. How do you investigate?
How do you handle test data for automated runs?
What is the difference between UI and API testing?

Managing a Automation Test Engineer in ZeniaHR

AttendanceOffice or hybrid on a general shift, with extended hours near a release. Web punch on the approved office network covers office days, and mobile app punch with a location check covers work from home days set in the work terms policy.LeaveAn entry level tester is often on probation, so track the probation end through the probation queue. Reporting manager then HR approve leave, and the leave calendar helps the QA team keep test cover during a release cycle.Performance and KRAsSet the KRAs above as goals in a review cycle and use the probation review rated 1 to 5 by the manager to confirm the tester. After confirmation hold the formal review each quarter and check automation delivery and suite stability monthly.

Hire and manage your information technology team in one place

Post the role, onboard the new hire, and track attendance, leave and KRAs in ZeniaHR. Free for your first 50 employees.

Book a free demo See pricing

Frequently asked questions

What does an automation test engineer do?

An automation test engineer writes and maintains automated tests that check software on every build. They turn manual test cases into scripts, run suites, report failures and keep the automation stable. At the entry level they deliver assigned scripts, log defects clearly and learn the framework with support from senior QA engineers.

What is the difference between a manual tester and an automation tester?

A manual tester runs tests by hand and is strong at exploring and finding unexpected issues. An automation tester writes code to run repeatable checks fast, especially for regression. Both matter, and many testers do both. Automation needs programming skill, while manual testing needs sharp test design and curiosity.

Do you need coding for automation testing?

Yes, some coding is needed. You should be comfortable writing scripts in a language such as Java or Python and using a framework like Selenium or Playwright. You do not need to be a full developer, but you must read code, handle logic and debug scripts. Strong test design skills matter just as much.