Position: Key Quality Engineer with Java
Company: EPAM
Experience required: 3y
English level: upper

**Product Overview: **
There are several systems that help court staff in their daily activity. All of them work with court cases in various ways. Litigation Analytics Infrastructure project is a bridge between systems – it is ETL process that helps to collect and modify data according to customer needs. 

**Project\Stream Overview: **
Project currently in the phase of migration from on premise infrastructure to cloud (AWS). 
QA team is responsible for: tests migration to cloud, new tests creation, on prem vs cloud test results comparison. In all stages need to work with variety of data – xmls, jsons, parquet Data Frames, object files. One of responsibility is preparing test data and creating golden data. 
Possibly to dig into AWS services. Test design improvements are welcomed. 
Team: 9 dev, 3 QA, plus related streams 
VDI is used as working env. 
Commitment required: 1.5 years 

**Requirements: **
Strong Senior Automation QA\SET who wish lead a team of 4ppl \or Lead Automation QA\SET 
AWS background: s3, pipelines, Lambdas, step functions 
Experience with creating Automated Testing Frameworks from scratch 
Experienced in Java 8 and above, Maven, XML, SQL, REST 
Testing mind set for capturing complete coverage of complex testing scenarios 
Familiar with Agile methodology 
Good oral and written communication skills. Good English - direct communication with customer is required. 

**Nice to have: **
Python 
Experience in Spark, Hadoop, Big Data 
Microsoft TFS 

**Key Responsibilities** (on a day-to-day basis):  
Participation in Agile processes including daily stand-up, iteration planning, story tasking, and iteration retrospective. 
Review business requirements to prepare testing scope. 
Tracking team progress. 
Develop test scripts\infrastructure for AWS migration, on prem tests creation\support. 
Perform code review. 
Regression runs review. 
Report test results and monitor defects and their resolution. 
Effectively contribute and implement new ideas on improving the software testing process. 
Interact with developers, related test streams QA teams. 
Clear and concise English communications, including verbal, instant messenger, e-mail, and written documentation.