JavaScript required
We’re sorry, but Coda doesn’t work properly without JavaScript enabled.
Skip to content
Gallery
Software Quality Assurance Engineer
Overview
Software Quality Assurance Engineer
Learning
Products
More
Share
Explore
Software Quality Assurance Engineer
[For Review]Your Responsibilities
Gather is our Office
Always acknowledge messages that you are tagged in. May it be as a team or as an individual.
Add an emoji or respond to the message to let the sender know that you have read their message.
Remind your recipient to acknowledge your message the same way you acknowledge the messages of others.
Give a timeframe in case you can’t respond to the question right away.
I’ll get back to you in X hours
Let me check first then I’ll get back to you before EOD (End of Day)
I’ll have it done on Monday next week.
Respect other peoples time
If you agreed to a meeting schedule, make sure to be there on time.
Check the calendar of the person that you need to set a meeting first before putting the invite.
In case you’ll miss the meeting, notify the other participants prior the meeting.
Clients are our lifeline
Without them we’ll be jobless so take care of our clients.
Always put our client’s best interest
in what you do.
Never allow bugs to be seen by our clients especially the critical ones.
Know your product like the back of your hand
If you can’t explain it then, you don’t know it.
Know your actors and what are their roles in the product.
Understand why are we doing the features. (Needs more emphasis on this one)
Ask questions. More questions.
Never assume something is working
Make sure to see it with your own eyes before accepting a ticket.
If you need more time to test a feature let the Product —
All things created by man are bound to have an error.
Follow proper documentation process
Screenshots are your best friends.
Always document your testing.
Do voice overs when attaching video clips so that it can be easily understood.
Requesting a change on the ticket? Put a screenshot.
Accepting a ticket? Put a screenshot.
Steps are meant to be detailed to guide the devs to debug the issues.
Over-communicate
Raise any suggestions during standups.
Keep your standups updated.
We are a team so everyone’s voice matters.
Respect everyone’s opinion.
Seek help if you need.
Never stop learning
We are here to support you and help you grow so always take the opportunity.
Ask your teammates to teach you.
Request training sessions.
Stay curious.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
Ctrl
P
) instead.