Lead Mobile QA Engineer

Role :  Lead Mobile QA Engineer

Location :   [San Francisco, CA, 94102] (Onsite,)

 

 

 

 

 

 

Note: Need Local and at least 12+ years of exp

Job Description:-

Mobile QA Experience: At least 5 years’ experience with QA for mobile applications working closely with Engineering, Product and UX teams. React Native app testing is aplus. SME areas for the overall QA team (not expecting one person to know all of this, however, we need experts in the team to cover these areas):

  • Experience with mobile app payments and promos (Apple Pay, Google Pay)
  • Experience with marketing tools like AppsFlyer and surveys (ex: Medallia)
  • Experience with app rater
  • Experience with Firebase

 

● QA Tooling: Experience with the following QA tools and mobile platforms – TestFlight, Apple Connect, Google Play Console, Firebase, GA, Jira/Confluence, Browerstack.

● Proactive & Ownership: Ability to proactively find issues in mobile applications, surface to the cross-functional team, and take ownership to drive the matter to closure.

Demonstrates opinionated view based on experience in questioning/pushing back on requirements, UX design and engineering implementation.

 

Lead qualifications:

 Deliver overall test plan for each release based on requirements, UX, Q&A/feedback and not just tickets defined by Product Management. The QA lead should be able to “play back” the key features from a user journey and key outcomes standpoint.

 Personally running sanity tests on the key features in each release and highlighting risk areas (ex: first run through feature and it is not working), creating P0 bugs based on user journey testing of features and not just the original tickets defined by Product Management

● Ability to distill a complex problem and communicate effectively with the cross-functional team to drive shared understanding of the issue.

● Critical thinking to fully understand multiple user journeys within a mobile application and understand how they interact with each other, both from the user-facing perspective and the backend system perspective, Test full flows not just what is written in a ticket

 

Thanks and Regards.

Pratik Kumar

Senior Technical Specialist

[email protected]

Email

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Most Voted
Newest Oldest
Inline Feedbacks
View all comments