Evidence
When assessing someone against the Develop Me responsibilities it is essential to have open and honest conversations regarding what level you believe someone is; there’s zero benefit to anyone in inflating a score. To help you have these honest conversations it’s a good idea to be able to provide clear examples of when and how a Developer has met obligations or exceeded expectations - we’ll call these examples evidence.
We collect evidence in order to satisfy the following criteria:
- Developer should be making a conscious effort to realise the values associated with a responsibility. Accidentally fixing a bug does not make you a master bug fixer, and there is an expectation that a real conscious application of skills should be required in order to prove your ability
- They should also be comfortable fulfilling the responsibility, in terms of effort / time / resources, and be relatively at ease with the impacts involved. Developers will occasionally be required to step outside of their comfort zone and operate at a higher level; this does not necessarily prove they are ready to progress - though it can indicate potential - and if the work places noticeable strain on the Developer, or their duties, then they may not yet be ready to progress
- There needs to be continuous proof of the characteristics necessary to fulfil a responsibility. Repeated demonstration is necessary in order to be satisfied that responsibilities have been fully incorporated into the working role
- We also expect to see repeated consistent realisation of the responsibility, ensuring that the Developer can be relied on to perform the specific duties
- Finally we need to be satisfied that all of the above has been carried out in a competent way that aligns with Trade Me values and quality measures. We can be consistently and consciously bad at a task so we need to ensure that a responsibility is carried out in a way that is deemed acceptable within the scope of the role
We’ll call this criteria the 5 C’s (there are many differing 5 C models out there for differing purposes, including Medium’s Engineering Growth Framework from which this is stolen based)
| Complexity of work - Level 4 | |
|---|---|
| You work on a range of complex and routine tasks applying a methodical approach to resolving issues | |
| Lesley has taken over support of the Plutonium Enrichment System and is responsible for ensuring continued operation within demanding SLAs | |
| Conscious | Has taken the time to get a deep understanding of the system, had read through the specs and done several deep dives through the codebase |
| Comfortable | Was able to remotely diagnose and resolve a recent P2 outage in the system and has been on hand to assist in various upgrade projects |
| Continuous | Has been involved in a number of 'war rooms' since March and frequently is called upon to give technical advice to other squads |
| Consistent | Is sought out by other groups to give technical advice and can be relied upon to be measured and thorough in responses |
| Competent | Has successfully resolved issues that other engineers have struggled to fix and is relied upon by others due to being able to resolve complex problems |