Full Stack Web Development: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 357: | Line 357: | ||
!rowspan="6"|Support Documentation | !rowspan="6"|Support Documentation | ||
|rowspan="6"|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. | |rowspan="6"|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. | ||
|rowspan="6"| | |rowspan="6"|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 | |Secure OS | ||
|3 | |3 | ||
Line 378: | Line 378: | ||
!rowspan="6"|Functional Documentation | !rowspan="6"|Functional Documentation | ||
|rowspan="6"|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. | |rowspan="6"|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. | ||
|rowspan="6"| | |rowspan="6"|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 | |Secure OS | ||
|4 | |4 |
Revision as of 12:50, 6 November 2020
The job of Web Developers is to plan, build, test and maintain internet sites and applications. Some relevant part of their work is customer-oriented: either when designing new applications or when suggesting improvements in existent projects. This work-relationship can be very delicate and requires a broad view of the market, business management processes, marketing, and other necessary skills.
A developer needs to master several technologies and in different layers. Let's take a brief look at some of them:
In the presentation layer, we have HTML, CSS, and Javascript as required technologies. They should also be familiar with other optional technologies such as Actionscripting (Flash), Silverlight, among others. Knowing HTML and CSS is the minimum possible hard skill to have in order to start being effectively productive in Secure Group
In the business rule layer, the PHP language and ASP.NET technology are the starting points. There are, however, several technologies such as JSP, ColdFusion, Ruby on Rails, CGI, among others that can be very useful as well. Of course, to master any of these languages it's required knowledge of programming logic in order to minimize time and effort and maximize results.
In the data layer, knowledge of the SQL language and some of the most commonly used databases on the web, such as MySQL and SQL Server, is indispensable.
In order to progress in our development path and Level Up or Step Up, our Web Developers 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.
Salary Grid
All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.
Web Development | Step | ||||
---|---|---|---|---|---|
Level | |||||
Individual Contributor Path | 1 | 2 | 3 | 4 | |
Full Stack Web Developer | 4.500 | 4.650 | 4.800 | 4.950 | |
Sr. Full Stack Web Developer Level 2 | 5.500 | 5.650 | 5.800 | 5.950 | |
Sr. Full Stack Developer Level 3 | 6.500 | 6.650 | 6.800 | 6.950 | |
Sr. Full Stack Developer Level 4 | 7.500 | 7.650 | 7.800 | 7.950 | |
Sr. Full Stack Architect Level 5 | 8.500 | 8.650 | 8.800 | 8.950 | |
Sr. Full Stack Architect Level 6 | 9.500 | 9.650 | 9.800 | 9.950 |
KAI of the position
General Knowledge
Concepts | Balanced Scorecard |
---|---|
Scrum | |
Frameworks | Scrum |
Languages | Perl |
Softwares/Tools/Platforms - Usage | Atlassian Bamboo |
Atlassian Bitbucket | |
Atlassian Confluence | |
Atlassian Jira | |
BambooHR | |
Combain | |
Countly | |
Crowdin | |
Docker Harbor | |
Docker Swarm | |
Elastic Kibana | |
Elastic Logstash | |
Jetbrains PhpStorm | |
Kamailio | |
Kubernetes | |
Libib | |
MS Exchange | |
OpenSTF | |
Small Improvements | |
Idaptive | |
Unwired Labs | |
Softwares/Tools/Platforms - Configuration | Atlassian Bitbucket |
Countly | |
Docker Engine/Container | |
Docker Harbor | |
Docker Swarm | |
Elasticsearch | |
Elastic Kibana | |
Elastic Logstash | |
Kamailio | |
Kubernetes | |
Softwares/Tools/Platforms - Server Administration | Elasticsearch |
Kubernetes | |
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
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. | 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. | 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 |