The problem of junior and senior
In the IT industry, we often refer to junior developers and senior developers. But what do those terms mean? Does it have to do with age? Or the duration of ones career? And what if an experienced React developer becomes a Magento 2 developer? And does an experienced senior Magento 2 developer suddenly know all about React as well? The terms junior and senior do not fit the actual knowledge that people have. Likewise, frontend, backend and full stack are also hardly descriptive. Our advice is to use a competency matrix or skill matrix instead.
Create your own competency matrix
We highly advise you to create a competency matrix yourself - you know your own people the best. However, we are happy to lend a helping hand:
- Create a new spreadsheet
- Download our CSV listing of skills
- Add the columns Category and Skill from the CSV file to your spreadsheet
- Remove skills that are irrelevant. Add additional skills that are relevant.
- Add the names of your employees.
- Add actions
Where can we help?
While drafting this mapping of skills and team members and after the skill matrix has been completed, we can help out:
- Run assessment sessions or brief interviews to check upon the skill level;
- Guide the people responsible for the matrix into which skills are most relevant and which are not;
- Train team members using all options available: Online training, on-demand content, on-site sessions;
This typically is an HR job, but the benefit of having Yireo jump in is because of our specific domain knowledge. Plus we can fullfill the actions needed to acquire skills, via training, materials and mentorship. This is also where our [/educational-subscription](Educational Subscriptions) come in.