****Please note: The interview and the job are conducted COMPLETELY in English.

We are looking for a super-smart Web tester/QC Engineer/Front-end Engineer to run manual UI testing and functional testing to ensure that our code is bug-free.

If you are looking to work with the latest in digital marketing, growth hacking, usability, AB testing, and conversion optimization, then this is the right job for you. You will have the opportunity to work with the world’s top experts on conversion optimization and UX!

We promise you three things:

• A lot of learning
• A lot of hard work
• A lot of fun

This work does NOT involve writing any automation testing. It involves validating the UI of the code we implement.

Who you should be (Qualifications):

• 2+ years of quality control experience.
• Deep understanding of QC principles, methodologies, and practices
• Having the ability to diagnose and resolve basic technical issues
• Experience with testing websites and web application
• Passionate about functional and UI testing
• Fluent in English and have great communication skills

Your responsibilities:

• Ability to analyze requirements and design test scenarios
• Create and execute test cases - you will ensure that sites work correctly on different types of devices.
• Defect/ Bugs Reporting and Prioritization. Re-testing and regression testing
•  Using issue-tracking tools
• UI/UX and Cross Browser Testing
• Verifying that the software works according to business requirements and specifications
• Providing a test summary report and recommendations for releases that reflect the quality attributes

Questions you should always be asking while testing:

• Does the UI use the correct styles / fit the style guide? Does it look like the mockups we provided – or if not, an acceptable proxy?
• Does the size, padding, font, and spacing match the design?
• Do the interactions and UX patterns fit with established patterns within your site? Does it fit general UX best practices?
• Does follow-up data show that your users are able to use the feature as intended, and are not confused or dropping off?
• Did the front-end developers use the correct style guide elements from CSS?