Interviewing Questions Flashcards
Tell me about yourself
I’m working in QA for the past __ years, making sure that all works, looks, and feels good
mainly focusing on functional and UI testing, testing both Web and Mobile applications, Making sure that requirements are implemented and reporting issues in Jira. Working with iOS, Android, Windows, and Mac. I have a lot of experience with creating and maintaining QA documentation, using Testrail to create and execute test cases. Working with tools like Chrome Dev Tools, Xcode, Android Studio, ADB and Unix worked closely with Development and Product Management
….Well, that’s pretty much it…
Please feel free to ask if you have any particular questions.
When reporting issues in Jira?
Once I saw a mismatch between actual and expected behavior.
Used ADB and Unix
examples if they ask:
How did you use ADB?
- To install/uninstall apps on android (ADB install/uninstall)
- To create a log file for Android (ADB logcat)
How did you use Linux/Unix?
To search for errors/crashes/exceptions in the log file using “grep”
To run Linux/Unix command that we had in the steps of the test cases
* for example to clear cache and cookies on iOS devices, or to create files and folders on the device)
To make sure all looks good? yes, nothing is overlapped, misaligned, or truncated.
Tell me about yourself: (with recruiter)
Well, I work on Web and mobile applications, testing UI and Functionality,
Doing smoke and regression testing,
using chrome dev tool, ADB, Linux, Android Studio, and Xcode
Testing different browsers and platforms.
Testing iOS, Android, Windows, and mac.
Who exactly you are looking for?
Most important questions (recommended to learn by heart):
- Tell me about yourself
- How do you write a bug report?
- What you do if the developer tells you that it’s not a bug (or as designed)?
- What you do if the dev tells you it’s not reproducible?
- Which ADB commands did you use?
- Which Unix commands did you use?
- What is your weakness?
- Why did you choose to work in QA?
- How do you write test cases?
- Describe bug life cycle at your company
- If you need to complete 80 test cases in 5 days, but after the first day you completed 8 test cases, what will you do?
- How would you test a toaster? (understand the main idea)
- Which latest versions of iOS and Android did you work with ? which devices?
- Which file name was for iOS and Android apps ? (*.ipa/.apk)
- Tell me about your project
Call with a recruiter:
Recruiter: Hi Mr. X how are you doing?
You: Fine thank you, how are you?
Recruiter: Are you available on the market for new opportunities? Do you have a green card? citizenship? work authorization?
You: Yes, I’m looking for new opportunities.
Where is this position located? (remote?) and what is the maximum rate? Full Time or Contract? Is it manual testing or automation?
Recruiter: Yes, in your area. Manual. What’s your rate and availability?
You: I’m available for an interview anytime that works for you and can start the work in 2-3 weeks Notice, my rate is $35-40-45 (or 45-50) per hour if it’s a contract or 80-90K (or 90-100k) per year if it’s full-time.
Recruiter: W2 / corp to corp / 1099?
You: W2/1099, please send me the rate confirmation.
Recruiter: ok, I will send you the job description with rate confirmation (and rights to represent aka RTR), please, confirm the rate with your updated resume attached.
You: OK.
(reply mail with: “Confirmed”, and don’t apply twice [check job id] for the same position with another recruiter)
- I don’t give my personal details like date of birth or ID before the interview
- Regarding SSN tell them that you give SSN last digits only after you pass the onsite interview and receive an offer.
Why do you want to leave your current job and work with us?
Because of the crisis our company is laying off a lot of people and closing the office (I want to find a stable long term opportunity)
Don’t say any negative stuff.
Don’t say that you want more money.
If you need to complete 80 test cases in 5 days, but after the first day you completed 8 test cases, what will you do?
I will work according to the priorities, highest priority tickets first (Highest>High>Medium>low), also I will raise a concern to QA Manager that we might need more time or effort/resources to finish this testing on time if I see that the test cases are complicated and time-consuming.
What do you do if a developer reassigns a bug/ticket back to you and marks it as
“Can’t reproduce?”
I will try to reproduce on the reported device, will make sure that I’m following the right steps, using the right Environment, Device, Platform, Build.
I will try to reproduce on 1 or more other devices to make sure that it’s not device-related.
If not reproducible - I will close the ticket and leave a comment.
If reproducible - I will reopen the ticket and assign it back to the developer with my comment.
For your understanding:
*Don’t mention during the interview: You can let the developer know (using Slack) about it (depends on what is acceptable in your company) and offer to show on your devices. Message Example: “Bug-number, Reproducible on Device/s, Platform, Build” (if he would like he will come to see it on your device) but during the interview don’t mention it because you don’t want to show that you distract developers.
What would you do if a developer reassigns a ticket/bug back to you and marks it as “as-designed” / “not a bug”? (learn it!)
I will double-check the requirements if according to the requirements it’s expected behavior - I will close the bug and leave a comment,
BUT if it’s not expected according to requirements - I will reopen the bug, assign it back to the developer and leave a comment,
if the requirements are not clear or maybe missing, I will ask the product manager for clarifications.
And will close or reopen the ticket based on his answer.
Extra if they ask:
What kind of requirements did you work with?
PRD, Design
Where are the requirements located?
on Google Drive (shared with our team)
If they ask in which format was the document?
- It was a PDF with the PRD. (how all should work)
- And PDF with Design. (How all should look)
How many pages your PRD had? 25!
What kind of comments do you leave once it’s as expected?
“as designed” or “not a bug’
If it’s against the requirement the comment would be for example
“This is a valid bug according to the requirements page 27 line 7”
Reopen means: change the status to Open and assign back to the developer
*in real life if you are told that it’s not a bug you close the ticket and leave it alone;-) (don’t mention it during the interview, it’s for your understanding)
It is pretty often after SQA engineer enters a bug, the bug comes back as “not a bug”
List of reasons:
- As designed, cannot map to the requirement or test case
- Will not fix, the bug is a too low priority (P) and will not be addressed in the near future
- This is a story, not a bug (enhancement request)
- Soon this area is going to be redesigned and completely changed and developers don’t want to waste time on it
How did you write bug tickets? (learn it!)
you must answer very confidently and without going into details
I’m going to Jira. Creating a new ticket.
Choosing the correct project, choosing issue type which is a bug report.
Writing the Title
Description with steps to reproduce, actual and expected behavior,
Environment
Priority,
Attachments of the screenshots, videos and log files
Assignee
—————————————————————————————————————–
*Title - should be short and informative, should show what and where is the problem
*Extra in case you are asked for more: Link, Label
Linking (Link) relevant ticket if there is such (“related to” for example or “duplicate of”)
Label (any name of project/device/team/etc)
Examples when you add attachments:
Screenshot (if UI), (for example: if something is overlapped, misaligned or truncated)
videos (if it will help to better understand the bug)
log files (if for example crash of the app or any functional issue)
What are Bug Report components?
Project: Name
Issue Type: Bug
Title (informative and not long, what & where happens)
Description (Steps, Actual, Expected)
Priority (Highest, High, Medium, Low, Lowest)
Environment (Which device and platform, mac/win chrome/ff/ie, Android, iOS, Browser version)
Attachment (Screenshot, Video recording, Log file)
Assignee
Tell me about your current PROJECT: (examples) (MUST do the internship!)
no need to say the name of the app if they don’t ask
Project 1: (Sidekick)
Our team is developing a desktop and mobile application, it’s a browser that is designed for productivity and team working collaboration. Basically it’s a Chromium based browser with an extension that has a lot of management tools and makes the working process faster.
As a part of the QA team I test different platforms like windows and mac, sometimes I am required to perform testing on Linux. I use such tools as Chrome DevTools and UNIX commands, create and execute test cases in TestRail and file bugs in Jira following up until resolved.
I am always advocating the customers to make sure they get the best user experience.
Project 2: (e-gree)
The product I’m working on right now is a e-signature software. Basically it’s similar to DocuSign. Users can send custom documents to be electronically signed.
This product supports multiple platforms. One platform is web, a website where users can store agreements and share them with other users.
The second platform (our product developed for) is mobile. The application supports two operating systems, iOS and Android. The mobile version has very similar functionality to the web one where users can create, customize and send documents to be signed using their mobile devices.
Project 3: (Anybe)
I am working on a web application called Anybe which is a platform that makes it possible to try any job for a little while. Employers can post job offers which users can accept in order to get new work experience and do something completely different. This platform included two parts: testing it from the user’s side and as an employer.
Project 4: (Etabot)
Etabot is a plugin to JIRA Software. The purpose of this plugin is to predict how people work to help them perform more efficiently by collecting data from a task management system. The product makes planning more efficient, helps with collaboration, and deadline tracking.