CustomerGlu is looking to add a QA automation engineer in our team with at least 2 years of experience that can evolve existing QA processes for our platform:
- Take ownership of performing QA on platform and customer dashboard ensuring quality in releases. Working in a fast-paced, quality-focused environment, you will be involved in quality-assurance related activities throughout the entire development process, from planning to final release, while understanding the overall development process.
- Develop and execute test cases, scripts, plans and procedures (manual and automated).
- Evolve formal QA processes, ensuring that the team is using industry-accepted best practices.
- Developer QA/QC checklists for right stake holders in software delivery pipeline
- Maintain internal SLO and reduce customer outages/incidents with proactive QA
- Act as key point of contact for all QA aspects of releases, providing metrics, reports.
- QA experience in working within an Agile Scrum based development process
- 3 years+ experience testing smartphone apps and web apps (designing/implementing tests, test management, optimizing tests)
- Ability to communicate with PMs/engineers in development teams and members in QA teams to solve issues
- Experience in solving problems and improving processes in your team
- Experience in writing automated tests for UIs, APIs, Databases using Java language.
- Experience in development desktop or mobile web apps.
- Experience in performance testing, security testing, and internationalization testing
- Software development experience in a CI/CD environment
- Experience in quality analysis and reporting.
- Experience in Selenium, Serenity frameworks for testing in Java
**Our Ideal Candidate
- Motivation to provide a high-quality service for our users
- Capable of taking on bold challenges and learning from mistakes
- Capable of working independently and taking the initiative to lead the team to success
- Possesses a strong sense of responsibility and works hard to achieve their goals
- Capable of communicating proactively and producing output in a hybrid working environment.
Something looks off?