MTDV Achievements
Good morning, dear Patrons!
We are happy to release MTDV Achievements to you today. 

Soon, it will be available publicly through our blog. But feel free to share it with your friends anytime (with some explanations from your side, as this things is quite complex).

Any feedback is welcomed! 

What is it? 

MTDV Achievements is a set of measurable deliberate practices with exponential level of challenge growth.

This matrix will be used to rate mentors for MTDV platform.

Also, in the future we will most probably track your personal progress (level) based on this matrix as well. It does not mean that you need to compete with each other on the basis of this matrix. 

This is a tool to help you with your personal mastery growth with explicit and measurable steps.

Every achievement will give you 1 points to the compound level. As of today, the maximum level is 64.

How was it designed?

The design goal for this matrix was to collect a set of practices in distinct skill sets for T-shaped professional, which will maximise the career flexibility.

Think this: if you achieve most of those things you can work in any company, related to software development industry, in the world. Also, you are competent to create your own projects/businesses.

Also, it correlates with career growth of several high-profile people in our industry and is based on some well-known insights. If you want to dive a bit deeper, you can read "Growing as Software Engineer". MTDV Achievements is the next generation of this matrix.


Every row represents a set of challenges with growing complexity in a distinct isolated skill set. You are supposed to start with the lowest level of challenge (the leftmost cell) and proceed to the highest level step by step. This way the challenge will grow naturally and you won't be stressed a lot.


Every column represent a similar level of challenge for different skill sets. Also, it shows the perfect position you need to be to efficiently deal with the challenge. For example, "Mentor someone to help them reach a better position in tech" is easier to do if you are a senior engineer, as mentoring junior developers will probably be in your work responsibilities.


This matrix can also help your answer the questions "Am I good enough to be at my current position?"  If you reached half of the achievements of a given level, it's probably a good idea to take more responsibility.  For example, if you are a Mid-Level Engineer and you have reached all Level 1 achievements and eight Level 2 achievements, then it's a very good idea to get a promotion to Senior Engineer at your workplace.

On the other hand, we would recommend to try and gather all achievements in a single column anyway to create a better T-shaped foundation. So, if you are a Senior Engineer, do not rush immediately to Lead position and spend some time to finish the Level 2 achievements.


Reaching the top level (64, all achievements) does not mean your career has come to an end. It means that you have reached the state where you must take full control of your career and figure out how to multiply your influence.
At this point you will definitely be in top 1% of the field (one of a 200000 programmers world-wide), though it is speculative.

It is possible to reach level 64 in 5 years of deliberate career growth, though we would not recommend it, as you will probably need to sacrifice health or relationships if you are not in the ideal situation (or not privileged enough).

How do I use it?

You can use the matrix in several ways:

  • Figure out what to do next to get a promotion easier
  • Use the matrix as a basis for salary negotiations
  • Figure out what next step you can take to ramp up your skills
  • Give feedback to your peers and mentees based on the matrix


On lower levels, you can start several challenges in parallel. On higher levels, we would advice to focus on a couple of challenges at the same time to make it more efficient.


A special note should be given on reiterations: it is necessary to reiterate with those achievements. It's not generally enough to just achieve something once. 

We use a simple test to measure mastery:  Have you achieved something several times in different contexts?

Reiteration allows you to better understand details and subtle nuances of the challenge and grows your confidence. This is basically what people call "experience".