Position: Test Automation Engineer (С#)
Company: AllSTARSIT
Category: QA Automation
Experience required: 3y
English level: intermediate

Specialization - Cybersecurity
Headquarters - New York, NY
Years on the market - 15
Team size and structure - Up to 2000 employees worldwide. Eastern Europe – 5 departments, up to 50 employees
Current technology stack - C#, SQL DB, NUnit, MStest, Junit, Docker, CI/CD, Rest AP

Required skills:
 - At least 4 years of experience in the software testing field
- Deep understanding of QA methodologies and processes
- Deep understanding of QA testing types/scenarios and flows
- Experience in designing and developing (C#) product’s automation
- Experience working with SQL DB
- Knowledge of at least one test framework: NUnit, MStest, Junit
- Experience with Docker
- Experience working with CI/CD
- Experience with Rest API
- Fast technology adaptation
- Ability to work on multiple projects under tight deadlines
- Good interpersonal skills
- Good English (reading/writing)

Advantages:
- Experience with multithreaded programming
- Experience with microservice architecture
- Experience with RabbitMQ
- Experience with Cloud environments: AWS/Azure
- Degree in Computer Sciences, Engineering or related

Scope of work:
- will be a part of a DEV team and will be in charge on the automation pipeline, written in C# and focused-on backend side (not UI)
- will need to be a member of a Team (currently 4 Dev and 2 IT Deployment) that is working in Agile SCRUM (iteration of 3 weeks including all Agile ceremonies and work along with them on usual working hours)
- will need to take full ownership on Edge automation and check their status every morning. If there are failures, he will need to investigate them and open bugs for the person responsible on them
during the sprint, He/She will need to estimate risks and efforts of automation PBIs and advise the DEV team about their testing and create automation infra for them where missing
- will need to create new automation infrastructures (places that we have a gap, like working with security vendors API instead of recorded logs)
- will need to do “Release readiness” and “Release Hardening” checklists (some manually, some can be automated)
- will need to do some manual QA (For places we are not covering yet with automation) and plan to automate them in the future where possible
will need to learn to work with Docker/Kubernetes and such