logo

πŸ₯… GOAL OF THE GRADE SYSTEM

Increase level of developers in the company by making a transparent grade system that will answer the following questions: "What is my current level? What should I do to grow?"

βœ‹ THINGS TO AVOID

  1. No connection to real projects/problems
  2. Metric jerking
  3. Easy-cheesy - everybody is a senior
  4. Using hard-skills section as a detailed map (it should be treated as a compass)

🧬 Overall structure

1. Shared part

2. Separate part - hard skills

3. Add-ons

❓ FAQ

Will everyone be tested after rollout of the grade system?

  • No, there will be no testing. However, we do believe that everyone can check their level by themself or with the help of a teamleader and create an action plan to match the grade requirements within reasonable amount of time

Can I change something in the grade system?

  • Yes, you can make your suggestions. They will be reviewed by mainteners of this repo. You will find basic rules here

Can I skip some levels (e.g. become L3 Middle after L1 Intern)?

  • No, it is not possible, progress should be made step-by-step.

Are roles is continuation of grades?

  • No, roles are parallel to grades and more related to the particular project, and grades are more code-oriented

What are values?

  • They are basic behavioral concepts that show you the right demeanor at any engineering grade/role.

Is it necessarily to get one of the perks?

  • No, it's just an additional good things that couldn't been added straight to the grades' levels

πŸ‘πŸ‘πŸ‘ContributorsπŸ‘πŸ‘πŸ‘


Eduard Kovnatsky


Dmitry Derbenev


Mikhail Morozkov