At a Glance
- Tasks: Join our team to test and improve web software for grocery essentials.
- Company: Be part of Amazon's innovative GEET QA team, focused on quality assurance.
- Benefits: Enjoy a flexible work environment with opportunities for growth and learning.
- Why this job: Make a real impact by ensuring top-notch customer experiences through testing.
- Qualifications: Experience in test planning and execution is essential; MShop testing preferred.
- Other info: We value diversity and provide accommodations for applicants with disabilities.
The predicted salary is between 36000 - 60000 £ per year.
GEET (Grocery and Everyday Essentials Tech) QA team is looking for QAEs who are passionate about testing and breaking Web Software.
The candidate must have the skills to identify software bugs quickly, describe the bugs know concepts like testing for boundary values, creating a traceability matrix for large projects, analysing a code change and identifying the right set of test cases to run, etc.
Key job responsibilities
Create test plans, write test cases for new features.
Regression test and sign off on various partner team testing requests.
Be the Customer Representative and advocate for them in Bug Triage and other meetings.
Build Domain Knowledge and understanding of the Product under test.
Regularly communicate testing status and identify risks to Program launch dates.
Follow SOPs, identify gaps, outdated information and update it.
Perform manual testing of services and UI features on desktop browsers, mobile browsers and mobile shopping application
A day in the life
You will own end-to-end testing of various customer-facing features. You will write test plan, review it with stakeholders. You will own test execution, Bug Triage, QA Status communication. You will develop deep understanding of the program and have opportunity to understand how various Systems at Amazon work. You will also work with Operations teams to execute specific test scenarios. You will drive User Acceptance Testing (UAT) and lastly update our regression test suite with relevant set of test cases
About the team
The GEET (Grocery and Everyday Essentials Tech) QA team owns end to end testing of Fresh Program (including CX and Fulfilment) , Pharmacy and Quick Commerce.
BASIC QUALIFICATIONS
– Experience in Test Planning and Execution.
PREFERRED QUALIFICATIONS
– MShop Testing
Our inclusive culture empowers Amazonians to deliver the best results for our customers. If you have a disability and need a workplace accommodation or adjustment during the application and hiring process, including support for the interview or onboarding process, please visit https://amazon.jobs/content/en/how-we-hire/accommodations for more information. If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner.
Amazon is an equal opportunity employer and does not discriminate on the basis of protected veteran status, disability, or other legally protected status.
#J-18808-Ljbffr
Quality Assurance Engineer II, GEET QA employer: Amazon
Contact Detail:
Amazon Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land Quality Assurance Engineer II, GEET QA
✨Tip Number 1
Familiarise yourself with the specific tools and technologies used in Quality Assurance, especially those related to web software testing. Understanding the common frameworks and methodologies can give you an edge during discussions with the team.
✨Tip Number 2
Brush up on your knowledge of test planning and execution. Being able to articulate your experience with creating test plans and writing test cases will demonstrate your capability to handle the responsibilities of the role effectively.
✨Tip Number 3
Prepare to discuss your approach to bug triage and how you advocate for customers. Sharing specific examples of how you've represented user interests in past projects can showcase your commitment to quality and customer satisfaction.
✨Tip Number 4
Engage with the QA community online or through local meetups to stay updated on best practices and trends in testing. Networking can provide insights into the role and may even lead to valuable connections within the industry.
We think you need these skills to ace Quality Assurance Engineer II, GEET QA
Some tips for your application 🫡
Understand the Role: Before applying, make sure you fully understand the responsibilities of a Quality Assurance Engineer II. Familiarise yourself with key concepts like test planning, regression testing, and bug triage, as these will be crucial in your application.
Tailor Your CV: Highlight relevant experience in your CV that aligns with the job description. Emphasise your skills in test planning, execution, and any specific tools or methodologies you've used in previous roles.
Craft a Strong Cover Letter: In your cover letter, express your passion for quality assurance and testing. Mention specific examples of how you've successfully identified bugs or improved testing processes in past projects.
Showcase Your Technical Skills: If you have experience with MShop Testing or similar technologies, make sure to include this in your application. Providing concrete examples of your technical skills will help you stand out.
How to prepare for a job interview at Amazon
✨Understand the Testing Process
Familiarise yourself with the entire testing process, from test planning to execution. Be prepared to discuss how you create test plans and write test cases, as well as your experience with regression testing.
✨Showcase Your Bug Identification Skills
Be ready to demonstrate your ability to identify and describe software bugs. You might be asked about specific examples where you successfully found and reported bugs, so have a few stories in mind.
✨Know Your Tools and Techniques
Brush up on the tools and techniques used in Quality Assurance, especially those related to boundary value testing and traceability matrices. Being able to discuss these concepts confidently will impress your interviewers.
✨Communicate Effectively
Since you'll need to regularly communicate testing status and risks, practice articulating your thoughts clearly. Prepare to explain complex technical details in a way that non-technical stakeholders can understand.