Sr. QA Engineer

Sr. QA EngineerCollaborate closely with engineers, business analysts, product owners, and other team members to determine appropriate acceptance criteria for all changes (new features as well as updates).Responsibilities:Be responsible to review unit test coverage implemented by engineers so as to inform QE test strategyBe responsible to design and implement automated tests based on the agreed-upon acceptance criteria. The QE may work with other automated test engineers for thisBe responsible to set up the execution of automated tests as needed, via Continuous Integration (CI) toolsBe responsible to review the results of automated tests and take appropriate action (e.g. file defects, update test code/data/configuration, etc.)Be responsible to ensure that any areas not covered by automated tests are validated via alternate mechanismsBe responsible for generating and communicating test reports and metrics out to stakeholdersMentor other junior members of the teamAnalytical competence, which supports Test creation:Strong knowledge of AEM (Adobe Experience Manager) background and similar education technology applications, as well as the client's applications, supporting processes and test strategyActive participation in determining acceptance criteria of new features as well as changesDetermine appropriate test strategy for changesDetermine impact to test suite the need for new tests, maintenance to current tests, etc.Determine test data requirements for new testsTechnical competence, which supports Test Implementation:Experience with Acceptance Driven Development (ATDD) or Behavior Driven Development (BDD) approaches to developing and testing softwareExperience with Cucumber/Gherkin language to specify scenarios, or alternate tools in the same space such as Behat, Watir, etc.Knowledge of Java programming as applied to implement automated tests with REST services, Selenium, Databases, etc.Familiar with relational databases (e.g. Oracle, MySQL, etc.), as well as NoSQL databases (e.g. MongoDB, Cassandra, etc.)Familiar with modern version control systems such as Git, BitBucket or similarFamiliar with leveraging Continuous Integration tools such as Jenkins to set up tests to execute on schedule, on-demand or true CI (e.g. chained to code commits)Familiar with using tools such as SumoLogic, Loggly or other logging tools to correlate defects against other events of interestFamiliar with Fiddler, Charles, Postman, REST-Client, SOAP UI or similar tools to independently test REST endpoints to correlate and isolate defect causesAble to review code changes at a high level, understand unit test coverage and design automated tests that complement developer unit tests