Front End QA

Frontend QA EngineerResponsibilities: Create test plans & test cases for assigned features and perform Primary focus is to validate FrontEnd applications Execute test cases & perform defect tracking/management Design & build automated regression tests from test cases using Cucumber framework Plan and run automation tests, integration tests, & regression tests Comfortable communicating with developers & other technical team members Participates in the full SDLC/Agile cycle engagements, including meetings, iterative development, estimations and design sessions Perform UAT / regression testing against APIs, Web Services using internal and external tools, Web portals and reports Perform UAT / regression testing for iOS and Android on emulators and hardware devices Develop and execute test plans, test cases and client use-case Identify and report QA issues, workflow issues and other project risks to development team Evaluate system performance, reproduce issues and work with development to resolve identified problems Tasks include evaluating daily test suites results, maintaining/updating automation tests, and improving regression tests/framework Review logs (via SPLUNK) and data analytics for the application Analyze live and historic data stored in DynamoDB, AWS RedShift, Aurora databases Skills: Ability to adapt within a rapidly changing environment and know when to ask for help Ability to work with browser developer tools e.g. Chrome developer tools (Console, Network, Session Storage, etc.) Strong analytical skills to differentiate issue whether it’s FrontEnd issue Strong experience in testing API calls from FrontEnd Experience working with automation testing frameworks (Selenium, Cucumber) and developing testing scripts Experience testing across multiple platforms (mobile, web, backend applications, etc.) Working knowledge of SQL, DynamoDB, AuroraDB, AWS RedShift, Splunk, JSON, XML files, Jmeter, Charles Proxy, Postman, Insomnia Experience in scripting/programming languages: JS, Python, JAVA Experience in testing enterprise level web applications, web services, databases Experience with Agile testing practices, SDLC process, Business Intelligence processes, Business Operations, Data Analytics Understands deployment pipeline, continuous integration, and code coverage Strong written & verbal communication skills Education and Experience: BA/BS or Master’s in Computer Science or quantitative or related field preferred At least 5+ years of combined experience as a quality assurance analyst/engineer, BI analyst/engineer including applications development and testing utilizing the complete software development life cycle 3 years of experience with manual/automation required 3 years of experience with Behavior Driven Design preferred Required Skills: MUST HAVE Java Coding experience, otherwise they will not pass the screening! Screening Topics: QA-SDET-Java QA-SDET-JavaScript Cucumber Selenium QA-API Testing "This is a UI testing position, but will consider a strong QA Automation Engineer or SDET. Candidates need to have deep understanding of API calls and how API interacts with UI once it has been called. Needs to understand browser UI networks and session storage. The client has a technical Code Challenge that they make everyone do as the first step of their interview process in Java, so without true coding/programming experience you candidate will fail." Must Haves: • Java • Cucumber • Selenium • API experience (API calls, not testing actual APIs) • Troubleshooting • Splunk or similar logging/alert tools Role Notes: • Their proprietary framework is Java/Cucumber/Selenium-based. Won't be building a framework from scratch, but will be contributing to the framework. • Looking for strong troubleshooting skills--not just running a test on the application, needs to be able to interpret the results and understand the implications as pertaining to the API or the UI-meets-API structure. Identify whether there's an issue in the API code/design or if it's something on the UI end preventing a successful call. Also need to be able to explain to developers very clearly what the issue is and how to fix it. Comes from deeper understanding of application architecture and development. • Deep understanding of API calls and how they relate to UI architecture and functionality • Splunk or other similar logging tool--just needs to be able to say "this is how I interpreted the logs and these are the steps I took to resolve"