| Job title | L1. Junior | L2. Middle | L3. Senior | L4. Lead | L5. Chief |
|---|---|---|---|---|---|
| Development experience and knowledge | Some experience of programming languages | At least 1 year of relevant development experience | At least 3 years of relevant development experience, including UML, Modeling and Design skills | At least 5 years of relevant development experience, including UML, Modeling and Design skills, and expert knowledge of at least one technical area | At least 7 years of relevant development experience, including UML, Modeling and Design skills, expert knowledge of at least one technical area, and ability to coach and train other developers |
| Software process knowledge | Not expected to have knowledge or experience of the software development processes | Expected to be able to follow a defined software development process | Expected to be able to follow and understand a defined software development process | Expected to be able to follow, understand, and enhance a defined software development process | Expected to be able to follow, understand, and actively influence and enhance a defined software development process |
| Design and documentation skills | Able to read and understand project and requirement documentation | Able to read and understand project and requirement documentation; able to create documentation describing his/her code. | Able to read and understand project and requirement documentation; able to create design, technical and project documentation including high-quality documentation of his/her code | Able to read and understand project and requirement documentation; able to create high-quality design, technical and project documentation including documentation of his/her code; able to write high-quality non-functional requirement specifications and audit documentation | Able to read and understand project and requirement documentation; able to create high-quality design, technical and project documentation including documentation of his/her code; able to write high-quality use cases and audit documentation |
| Roles played on a project | Plays the Developer role | Plays the Developer role | Plays the Key Developer and Software Architect roles. May sometimes play Development Team Lead and Project Coordinator role | Plays the Key Developer and Software Architect roles, and usually also performs a Development Team Lead, Project Coordinator, Reviewer or Auditor role | Can play any role, typically a senior position. Responsibilities can include Development Team Lead, Project Coordinator, Software Architect, Reviewer, Auditor, Technical Trainer |
| Reliability | Expected to work effectively under supervision | Expected to implement functionality without direct supervision | Expected to be self-managing, implement functionality without supervision and test his/her work thoroughly using test cases | Expected to be self-managing, take technical responsibility for a subsystem or a whole project, work without supervision and test his/her work thoroughly using test cases.Expected to have proven experience in evaluating theoretical knowledge and practical (on-the-job) skills and the seniority level of candidates and providing actionable feedback and recommendations on positions/projects matching. | Expected to be self-managing, take technical responsibility for a subsystem or a whole project, work without supervision and test his/her work thoroughly using test cases.Expected to have proven experience in evaluating theoretical knowledge and practical (on-the-job) skills and the seniority level of candidates and providing actionable feedback and recommendations on positions/projects matching. |
| Quality | No specific expectations regarding quality | Must show a sense of responsibility for the quality of the code written by him/her | Creates deliverables in good quality | Must be a role model for colleagues; creates deliverables in high quality | Must be a role model for colleagues, on a par with the best industry standards; creates deliverables in excellent-quality |
| Customer relations | Not expected to deal directly with customers | Not expected to deal directly with customers | Expected to participate in phone conferences; be interviewed by customers; visit customers with supervision | Expected to participate in phone conferences; be interviewed by customers; be involved in customer workshops and presentations; visit customers without supervision | Expected to have good customer relationship skills; participate in phone conferences; be interviewed by customers; be involved in customer workshops and presentations; visit customers without supervision |
| English | B1 | B1 | B2 | B2 | B2 |
| Skills in customer negotioations | Able to read and understand the Customer’s Communication Language | Able to read and write the Customer’s Communication Language and have some speaking ability | Comfortably able to read and write and speak the Customer’s Communication Language | Comfortably able to read, write and speak the Customer’s Communication Language; able to write high-quality unambiguous texts | Totally fluent in the spoken and written variants of the Customer’s Communication Language; able to write high-quality unambiguous texts |
This repository has been archived by the owner on Jan 23, 2022. It is now read-only.