Product Owner

In order to progress in our development path and Level Up or Step Up, our Product Owners 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	Agile
	Balanced Scorecard
	Planning
	Product Demo
	Software Roadmap
	Technical Writing
Frameworks	Android Components
	Android SDK
	API
	Kanban
	Scrum
Languages	JQL
Protocols	XMPP
	SIP
Softwares/Tools/Platforms - Usage	Android Studio
	Atlassian Bamboo
	Atlassian Bitbucket
	Atlassian Confluence
	Atlassian Jira
	BambooHR
	Big Picture
	Countly
	Crowdin
	Docker Engine
	Gerrit
	Instabug
	OpenSTF
	Small Improvements
	Workable
Softwares/Tools/Platforms - Configuration	Atlassian Bamboo
	Atlassian Confluence
	Atlassian Jira
	Crowdin
Softwares/Tools/Platforms - Server Administration	Atlassian Jira
	Languages (Idioms)	Advanced English

Specific Knowledge

Concepts	Design Patterns
	Version Control via Git
	Highload projects
	IDE
	OOP
	CMS
	REST
	Web Performance Experience
	Web Security
Frameworks	Bootstrap
	PHPUnit
	Selenium
	Symfony
	Vue.js
	Yii
Languages	Bash Script
	CasperJS
	CSS
	HTML
	JavaScript
	JSON
	Less
	PHP
	Python
	SASS
	SCSS
	SQL
	XML
Libraries	Ajax
	Faker
	Guzzle
	JQuery
	React.js
	Twig
Protocols	Oauth2
	JWT
Softwares/Tools/Platforms - Usage	Docker Compose
	MySQL
	NGINX
Softwares/Tools/Platforms - Configuration	Apache Tomcat
	Microsoft Azure
	MySQL
	NGINX
Softwares/Tools/Platforms - Server Administration	MySQL
	NGINX

IT Knowledge

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

Secure Group Knowledge

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

Web Development			Step
Level
	Individual Contributor Path	Management Path	1	2	3	4
	1: Web Developer	-	2.000 lv	2.150 lv	2.300 lv	2.450 lv
	2: Sr. Web Developer	-	3.000 lv	3.150 lv	3.300 lv	3.450 lv
	3: Software Engineer	Manager	4.000 lv	4.150 lv	4.300 lv	4.450 lv
	4: Sr. Software Engineer	Sr. Manager	5.000 lv	5.150 lv	5.300 lv	5.450 lv
	5: System Architect	Head of	6.000 lv	6.150 lv	6.300 lv	6.450 lv
	6: Sr. System Architect	Director	7.000 lv	7.150 lv	7.300 lv	7.450 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