QA Automation

Our Automation QA employees are responsible for developing and executing exploratory and automated tests. Automation QA responsibilities also include designing and implementing tests, debugging and defining corrective actions to ensure the highest product quality. They also review system requirements and track quality assurance metrics (e.g. defect densities and open defect counts.)

This is a very important role in our company's product development process so they have an interface with a variety of teams. Our QAs conduct tests before the product's launch to ensure the software is running smoothly and meets our partner's needs while focusing on being cost-effective. Ultimately, they monitor all stages of software development to identify and resolve system malfunctions to meet quality standards and to automate the biggest amount of features and processes.

In order to progress in our development path and Level Up or Step Up, our QAs must:

• Meet the criteria of the Level & Step Chart for the chosen path (Individual Contributors Path or Management Path)
• Score at least a grade 4 in the KAI of the position in order to reach Level 3.
  

KAI of the position

General Knowledge

Concepts	Scrum
Frameworks	Scrum
Softwares/Tools/Platforms - Usage	Atlassian Bamboo
	Atlassian Bitbucket
	Atlassian Confluence
	Atlassian Jira
	BambooHR
	Docker Harbor
	Elastic Kibana
	Kamailio
	Libib
	OpenSTF
	Small Improvements
	Atlassian Jira SynapseRT
	Thycotic Passwordbox
Softwares/Tools/Platforms - Configuration	Docker Engine/Container
	Elasticsearch
Languages (Idioms)	Advanced English

Specific Knowledge

Concepts	Agile
	Application Lifecycle
	Balanced Scorecard
	Defect life cycle
	IDE
	Test Automation
Frameworks	JUnit
	PHPUnit
	Selenium
Languages	CasperJS
	JavaScript
Libraries	Espresso
Softwares/Tools/Platforms - Usage	Appium
	Countly
	Git
	Instabug
	Jenksins
	SQuirrel SQL client
Softwares/Tools/Platforms - Configuration	Apache Tomcat
	Microsoft Azure

IT Knowledge

System Administration
System Administration - Day to Day Ops
Networking concepts
Android Development
Programming

Secure Group Knowledge

The first item we require proficiency regarding our company is the Secure Group Management Model (yes, the content in this wiki!). Besides that, we also need our employees to understand our products in all aspects as described in the following table:

Secure Group Knowledge	What's Expected	Impact	Product	Minimum Grade
User Documentation	Good, user-level knowledge regarding the product and its functionalities. From the user documentation, all employees across the company are required to be well aware of our solutions’ core features and functions such as the Password Advisor or how to send an automatic crash report.	This knowledge helps us facilitate a user-centric approach internally, which we believe is essential to develop our business and solutions. The user documentation helps team members understand user behavior and needs more thoroughly and feel the impact of their everyday efforts.	Secure OS	4
			SAS	4
			Secure Chat	4
			Secure Email	4
			Secure Vault	4
			Secure Manager	4
Sales Documentation	Employees should gain significant knowledge regarding the business side of Secure Group. They need to be aware of commonly used concepts in our day-to-day activities such as our business and distribution model, value proposition, selling prices, key selling points, and target audience.	The information in the Sales Documentation supports employees in their daily routine. It conveys the overall business vision within the company. This documentation contributes to making employees aware of how our solutions are distributed, who are our key partners and target market to know exactly the people towards whom team members’ efforts should be aimed. Alignment on company-wide priorities is also achieved through clear communication of our value proposition and key selling points, helping everyone understand the things that matter most.	Secure OS	3
			SAS	3
			Secure Chat	3
			Secure Email	3
			Secure Vault	3
			Secure Manager	3
Support Documentation	People within the company need to be aware of commonly occurring problems with our solutions. From the Support Documentation, employees should also extract general level knowledge regarding support processes, the issues that we’re currently having product-wise, and the approach to troubleshooting them.	o The Support Documentation helps employees understand short-term priorities more clearly and communicate more openly why they’re needed. It also gives them general knowledge of how to spot and report a problem, which helps us facilitate a company-wide contribution to product development. Last but by no means least, it helps team members understand customers pains and behavioral patterns to strengthen our user-centric approach.	Secure OS	3
			SAS	3
			Secure Chat	3
			Secure Email	3
			Secure Vault	3
			Secure Manager	3
Functional Documentation	Through the Functional Documentation, employees should get a thorough understanding of the solutions and their multiple features. People that work closely with the products must understand exactly how they function, how users interact with them, how to configure different settings, and what’s the expected behavior of different software solutions.	o The information in the Functional Documentation helps employees whose work is closely connected with our solutions, to gain significant in-depth knowledge into their functionalities that far exceeds users‘ understanding. Such thorough product expertise helps us remain objective, evaluate market data more adequately, and constantly increase our internal expertise.	Secure OS	4
			SAS	4
			Secure Chat	4
			Secure Email	4
			Secure Vault	4
			Secure Manager	4
Technical Documentation	Employees concerned with the Technical Documentation and more concretely - software development, must gain complete mastery over all solutions. Such people are regarded as technical experts and need to be well aware of data structures, relational databases, algorithms, programming languages, models, etc.	The Technical Documentation is used to make sure people that are technically involved in product development have the required knowledge to perform their day-to-day tasks, optimize our solutions more easily, and support other teams with their in-depth expertise.	Secure OS	4
			SAS	4
			Secure Chat	4
			Secure Email	4
			Secure Vault	4
			Secure Manager	4

Salary Grid

Automation QA			Step
Level
	Individual Contributor Path	Management Path	1	2	3	4
	1: Automation QA Developer	-	1.500 lv	1.650 lv	1.800 lv	1.950 lv
	2: Sr. Automation QA Developer	-	2.500 lv	2.650 lv	2.800 lv	2.950 lv
	3: Automation QA Software Engineer	Manager	3.500 lv	3.650 lv	3.800 lv	3.950 lv
	4: Sr. Automation QA Software Engineer	Sr. Manager	4.500 lv	4.650 lv	4.800 lv	4.950 lv
	5: Automation QA Architect	Head of	5.500 lv	5.650 lv	5.800 lv	5.950 lv
	6: Sr. Automation QA Architect	Director	6.500 lv	6.650 lv	6.800 lv	6.950 lv
	-	Sr. Director	9.000 lv	9.400 lv	9.800 lv	10.200 lv
	-	Chief of	11.200 lv	11.600 lv	12.000 lv	12.400 lv
	-	VP	13.400 lv	13.800 lv	14.200 lv	14.600 lv