{"id":19029419,"url":"https://github.com/guardian/engineering-performance-framework","last_synced_at":"2026-02-11T04:31:09.036Z","repository":{"id":46072583,"uuid":"318558856","full_name":"guardian/engineering-performance-framework","owner":"guardian","description":"The Guardian Engineering performance framework","archived":false,"fork":false,"pushed_at":"2025-01-23T08:19:06.000Z","size":110,"stargazers_count":48,"open_issues_count":0,"forks_count":4,"subscribers_count":36,"default_branch":"main","last_synced_at":"2025-02-13T16:56:30.819Z","etag":null,"topics":["documentation"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/guardian.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-12-04T15:35:20.000Z","updated_at":"2025-02-06T15:51:01.000Z","dependencies_parsed_at":"2024-04-29T09:41:07.072Z","dependency_job_id":"dc0b76fe-2840-469c-80ca-732ce12a2074","html_url":"https://github.com/guardian/engineering-performance-framework","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/guardian%2Fengineering-performance-framework","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/guardian%2Fengineering-performance-framework/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/guardian%2Fengineering-performance-framework/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/guardian%2Fengineering-performance-framework/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/guardian","download_url":"https://codeload.github.com/guardian/engineering-performance-framework/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240079637,"owners_count":19744725,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["documentation"],"created_at":"2024-11-08T21:14:10.577Z","updated_at":"2026-02-11T04:31:09.027Z","avatar_url":"https://github.com/guardian.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Engineering performance framework\n\nThis is the framework we use to assess the performance of engineers every 6\nmonths. Much like the software we write, this framework will never be perfect or finished.\n\nFor each role it is split into the same 3 categories:\n* 🚚 Delivery\n* ✨ Initiative \u0026 Influence.\n* 👩‍👨 People\n\nWhere the progression framework sets out high level expectations for a role, which may not be achievable every quarter,\nthe performance framework details everyday behaviours:\n  - Criteria labeled \"Meets\", we believe, contribute most to the department, and the expectation is that you consistently meet them \n  - Criteria labeled \"Exceeds\", we believe, are behaviours which contribute towards you growing and developing within your role\n\n#### Review\nEvery 6 months, at the end of Q1 and Q3, you and your manager will review your performance over the last 2 quarters using this framework.\n\nDuring a performance review, each criteria within each category will be assessed as 'met' or 'not-met':\n\nTaking an active role in your performance gives you the best chance of receiving a fair assessment and of getting the most out of your manager as they support your growth.\n\n#### Roles\n\n##### Individual Contributor\n\n* [Fellow and Associate Developer](#fellow-and-associate-developer)\n* [Software Developer](#software-developer)\n* [Senior Developer](#senior-developer)\n* [Staff Developer](#staff-developer)\n* [Principal Developer](#principal-developer)\n\n##### Engineering Management\n\n* [Associate Engineering Manager](./management/associate-engineering-manager.md)\n* [Engineering Manager](./management/engineering-manager.md)\n* [Senior Engineering Manager](./management/senior-engineering-manager.md)\n* [Head of Engineering](./management/head-of-engineering.md)\n\n\nSee the following [Indeed.com article for the difference between an \"Individual Contributor\" \u0026 \"Engineering Management\"](https://www.indeed.com/career-advice/finding-a-job/what-is-an-individual-contributor).\n\n#### Salary bands\n[Salary bands for each role](./salary-bands.md)\n\nFuther detail [here (staff only)](https://docs.google.com/document/d/1muN4pFqRhLFCELD9GS6aU1JaJRNG5tliEMlQVoX8bGE/edit).\n\n---\n\n### Fellow and Associate Developer\n\n#### 🚚 Delivery\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eDelivers small tasks independently.\u003c/li\u003e\n        \u003cli\u003eTakes on bigger pieces of work with support.\u003c/li\u003e\n        \u003cli\u003eTakes on PR feedback and improves their work.\u003c/li\u003e\n        \u003cli\u003eSeeks advice from more senior engineers when they are blocked.\u003c/li\u003e\n        \u003cli\u003eShows awareness of data privacy or security concerns where relevant.\u003c/li\u003e\n        \u003cli\u003eReviews PRs with helpful comments.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eBreaks down large problems into deliverable tasks.\u003c/li\u003e\n        \u003cli\u003eReliably delivers incremental changes with frequency.\u003c/li\u003e\n        \u003cli\u003eCan work mostly independently and unblocks their work when necessary by proactively reaching out to stakeholders, gathering data or provoking decisions/discussions.\u003c/li\u003e\n        \u003cli\u003eProvides delivery support to other engineers.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### ✨ Initiative and Influence\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eShares their work to the team or stream.\u003c/li\u003e\n        \u003cli\u003eSeeks to actively understand what they are being asked to do.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eSeeks to understand the why behind what they are being asked to do.\u003c/li\u003e\n        \u003cli\u003eActively explores new approaches in their own work.\u003c/li\u003e\n        \u003cli\u003eFocuses their learning and development plans to align with team goals.\u003c/li\u003e\n        \u003cli\u003eUses data to help with their or their team’s decision-making\u003c/li\u003e\n        \u003cli\u003eTakes opportunities to learn about wider department work through involvement in cross-team discussions or groups such as Accessibility Champions.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n\n#### 👩‍👨 People\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eProactively identifies opportunities to work with others.\u003c/li\u003e\n        \u003cli\u003eShows curiosity in others and their work.\u003c/li\u003e\n        \u003cli\u003eRegularly collaborates with their team on their work.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eEngages with departmental activities which uphold our departmental or engineering culture.\u003c/li\u003e\n        \u003cli\u003eGives useful feedback to their colleagues.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n---\n\n### Software Developer\n\n#### 🚚 Delivery\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eProvides delivery support to colleagues.\u003c/li\u003e\n        \u003cli\u003eBreaks down large problems into deliverable tasks.\u003c/li\u003e\n        \u003cli\u003eDelivers incremental changes frequently, reliably and with consistently good quality (e.g. readable code which adheres to team standards).\u003c/li\u003e\n        \u003cli\u003eTakes responsibility for their code from local testing to supporting it in production.\u003c/li\u003e\n        \u003cli\u003eCapable of independent delivery of most tasks.\u003c/li\u003e\n        \u003cli\u003eRegularly reviews team PRs providing helpful comments (e.g. constructive criticism / alternative approaches).\u003c/li\u003e\n        \u003cli\u003eRecognises when they’re near their limit and reaches out for help from others.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eIdentifies problems to solve and engages the team in scoping and prioritising their delivery.\u003c/li\u003e\n        \u003cli\u003eDemonstrates they can work to external schedule constraints and call out potential issues during estimation.\u003c/li\u003e\n        \u003cli\u003eEvaluates multiple options to solve technical problems (using data where relevant), and is trusted by the team to implement their recommended solution.\u003c/li\u003e\n        \u003cli\u003eOccasionally reviews PRs in projects where they have less context (e.g. outside their immediate team or dormant projects) with the same consideration.\u003c/li\u003e\n        \u003cli\u003eHelps to unblock their peers or shares responsibility for their tasks, in order to meet the team delivery goals.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### ✨ Initiative and Influence\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eAligns what they are working on to their team’s goals.\u003c/li\u003e\n        \u003cli\u003eRegularly gives useful feedback to more senior colleagues.\u003c/li\u003e\n        \u003cli\u003eSeeks to fully understand the end goal of the tasks they pick up, and is mindful of this throughout the delivery lifecycle.\u003c/li\u003e\n        \u003cli\u003eProvides input into architectural design choices.\u003c/li\u003e\n        \u003cli\u003eRegularly demos their work to the stream.\u003c/li\u003e\n        \u003cli\u003eUses relevant data and metrics to inform new ideas and make persuasive arguments.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eOccasionally introduces new technical approaches, which are adopted by the team, and make the team more effective.\u003c/li\u003e\n        \u003cli\u003eRegularly gives feedback to the team on improving their ways of working, and to team leads each quarter. Helps to implement some of these improvements by being an advocate for them.\u003c/li\u003e\n        \u003cli\u003eRegularly demos their work to the team, stream or stakeholders, and contextualises the impact of that work.\u003c/li\u003e\n        \u003cli\u003eSupports the team leads in making architectural design decisions (e.g. by writing options papers or architecture decision records).\u003c/li\u003e\n        \u003cli\u003eContributes towards maintaining code and product accessibility standards.\u003c/li\u003e\n        \u003cli\u003eRepresents the team in cross-team discussions and involves others when appropriate by sharing challenges and progress.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### 👩‍👨 People\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eEngages with departmental activities which uphold our departmental or engineering culture.\u003c/li\u003e\n        \u003cli\u003eProvides some mentoring or guidance to colleagues. This should not simply be contributing an opinion on a technical approach, but taking the time to introduce or improve someone’s working awareness of a topic in a supportive and encouraging way.\u003c/li\u003e\n        \u003cli\u003eDemonstrates inclusive behaviours as part of their everyday work.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eRegularly provides mentoring and guidance to colleagues.\u003c/li\u003e\n        \u003cli\u003eUndertakes departmental activities which uphold or improve our engineering culture or inclusivity.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n---\n\n### Senior Developer\n\n#### 🚚 Delivery\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eRegularly takes on more difficult tasks which require input from other teams or disciplines.\u003c/li\u003e\n        \u003cli\u003eDelivers reliably and with consistently good quality code (e.g. well tested and readable) which defines team standards.\u003c/li\u003e\n        \u003cli\u003eRegularly reviews team PRs providing constructive comments, or suggested alternative approaches.\u003c/li\u003e\n        \u003cli\u003eUses relevant data and metrics to support team delivery.\u003c/li\u003e\n        \u003cli\u003eDemonstrates working awareness that delivery goes beyond their individual contribution. (E.g. encourages others to improve their own delivery; manages dependencies on other projects and teams; balances short-term delivery with longer term objectives of own and other teams).\u003c/li\u003e\n        \u003cli\u003eCommitted to meeting their team’s objective and key results. (E.g. adapts delivery approach to meet the needs of the team, unblocks obstacles and supports the team in delivering its goals).\u003c/li\u003e\n        \u003cli\u003eCommunicates and documents their work thoroughly.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003ePlays a leading role in planning technical strategy for the team, or shaping the team’s delivery plans.\u003c/li\u003e\n        \u003cli\u003eMakes their team successful in meeting their objectives and key results.\u003c/li\u003e\n        \u003cli\u003eBalances risks to ensure team delivery.\u003c/li\u003e\n        \u003cli\u003eMonitors system and delivery pipeline health to ensure quality of service and team productivity.\u003c/li\u003e\n        \u003cli\u003eBrings the team or multiple teams together to maintain delivery pace and quality during periods of change and uncertainty.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### ✨ Initiative and Influence\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eDrives work activities to meet team goals, helping to define tasks, business outcomes, technical quality \u0026 OKRs.\u003c/li\u003e\n        \u003cli\u003eHelps keep the team focused on their long-term goals and values.\u003c/li\u003e\n        \u003cli\u003eGives regular feedback to the team and engineering manager and actively seeks to make improvements based on team and personal feedback.\u003c/li\u003e\n        \u003cli\u003eWorks with other engineers to determine the technical architecture within the stream.\u003c/li\u003e\n        \u003cli\u003eRegularly involved in cross-team discussions and uses their experience to influence outcomes (e.g. communicates own team’s context to improve shared understanding.)\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eIntroduces new technical approaches when appropriate, which are adopted by the team, and make the team more effective.\u003c/li\u003e\n        \u003cli\u003eDemonstrably moves the team’s key result scores as a result of the work they undertake.\u003c/li\u003e\n        \u003cli\u003eDemonstrates how the team can learn and improve from failures.\u003c/li\u003e\n        \u003cli\u003eAlways ensures plans and outcomes are well communicated to stakeholders and the wider business as appropriate.\u003c/li\u003e\n        \u003cli\u003eLeads work with other teams to solve cross-team challenges. Understands concerns of other teams and works to balance delivery across boundaries in order to deliver the best outcome overall.\u003c/li\u003e\n        \u003cli\u003eIs responsible for maintaining code and product accessibility standards.\u003c/li\u003e\n        \u003cli\u003eShares what they have learnt by tackling difficult technical and people problems.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### 👩‍👨 People\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eActively seeks to share knowledge with their colleagues, choosing communication method/styles that are appropriate to them and the situation.\u003c/li\u003e\n        \u003cli\u003eMakes a positive contribution to the inclusivity, atmosphere or culture of the department.\u003c/li\u003e\n        \u003cli\u003eRegularly advises or mentors others in a way that accelerates their personal development.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eSeeks to share knowledge beyond their team where useful/relevant (e.g. delegates learning opportunities).\u003c/li\u003e\n        \u003cli\u003eConsistently communicates the intention and outcomes from their work, leaving their work in a state where others can easily pick it up (e.g. produces well worded requirements, PRs, documentation, etc). Encourages this behaviour in others.\u003c/li\u003e\n        \u003cli\u003eEngages with departmental activities which improve our company or engineering culture and inclusivity.\u003c/li\u003e\n        \u003cli\u003eCoaches, mentors and supports their colleagues to perform better, share their opinions and insight, and be motivated by the work they undertake.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n---\n\n### Staff Developer\n\n#### 🚚 Delivery\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003ePlays a strategic role in the stream’s technical decision-making.\u003c/li\u003e\n        \u003cli\u003eProduces high quality code which defines stream standards, and inspires other engineers’ delivery.\u003c/li\u003e\n        \u003cli\u003eProvides feedback on important PRs and team’s solution design sessions.\u003c/li\u003e\n        \u003cli\u003eBalances short term goals and long term needs.\u003c/li\u003e\n        \u003cli\u003eFocuses on high impact and high value work.\u003c/li\u003e\n        \u003cli\u003eDemonstrates working awareness that delivery is more than just their individual contribution. (E.g. Promotes continuous improvement, delegates learning opportunities; encourages others to improve their own delivery; manages dependencies on other projects and teams).\u003c/li\u003e\n        \u003cli\u003eCommitted to meeting their team’s objective and key results.\u003c/li\u003e\n        \u003cli\u003eHelps to unblock obstacles and supports the team in delivering its goals.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eStaff Developers make successful delivery outcomes happen, for example by \u003cb\u003eeither\u003c/b\u003e:\n        \u003cul\u003e\n        \u003cli\u003eTech leading a significant engineering project which requires coordination with many other teams and disciplines within GNM.\u003c/li\u003e\n        \u003cli\u003eTurning around the delivery trajectory of a struggling team.\u003c/li\u003e\n        \u003cli\u003eContributing to the department’s technical and organisational decision-making and strategy.\u003c/li\u003e\n        \u003c/ul\u003e\n        \u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### ✨ Initiative and Influence\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eHosts department-wide forums where knowledge and experiences are shared.\u003c/li\u003e\n        \u003cli\u003eProvides a solid voice of technical authority when there is uncertainty that’s stalling engineering progress.\u003c/li\u003e\n        \u003cli\u003eHelps teams determine the right objectives and goals, and find an appropriate balance of health and maintenance alongside their delivery.\u003c/li\u003e\n        \u003cli\u003eHelps teams find technical solutions that fit within the department’s vision and culture.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eDemonstrates how the department can manage failure, fail fast, and learn and improve from such failures.\u003c/li\u003e\n        \u003cli\u003eChampions Guardian P\u0026E solutions, culture and values externally. For example by hosting external meet-ups, presenting at conferences, or writing blog posts.\u003c/li\u003e\n        \u003cli\u003eEnables software to be produced that can be used by, or benefits external communities and is widely accessible.\u003c/li\u003e\n        \u003cli\u003eWorks to reduce the likelihood that we will encounter high risk technical problems.\u003c/li\u003e\n        \u003cli\u003eDemonstrates deep engagement with and application of engineering or product data.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### 👩‍👨 People\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth style=\"width:50%;\"\u003eMeets Criteria\u003c/th\u003e\u003cth style=\"width:50%;\"\u003eExceeds Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eConstantly uses their knowledge and experience to raise the capabilities of their colleagues.\u003c/li\u003e\n        \u003cli\u003eLeads by example with the quality of their communication through appropriate means (e.g. exemplary requirements, PRs, documentation and presentations that could be understood with little context in the future).\u003c/li\u003e\n        \u003cli\u003eEmbodies a culture of respect that influences team processes and promotes empowerment of others - leading to more effective decision-making.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eIdentifies potential structural improvements to knowledge sharing, communication or culture of the department and acts on this to deliver improvements across the department.\u003c/li\u003e\n        \u003cli\u003eCoaches, mentors and supports all staff to perform better, share their opinions and insight, and be motivated by the work they undertake.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n---\n\n### Principal Developer\n\n\n#### 🚚 Delivery\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth width=\"100%\"\u003eCore Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eProvides technical guidance and oversight to the multiple development teams in your stream.\u003c/li\u003e\n        \u003cli\u003eEnsures sound technical architecture with technologies interoperating or connecting well to each other, enabling scale and flexibility to the business. \u003c/li\u003e\n        \u003cli\u003eFixes some issues when your help is requested or you see an organisational or technical value in resolving the problem.\u003c/li\u003e\n        \u003cli\u003eHelps define and review stream teams’ Service Levels Objectives (SLO), contributing to streams teams’ backlog prioritisation strategies to match them.\u003c/li\u003e\n        \u003cli\u003eLeads evaluation of new technologies and vendors, establishing key technical criterias for assessment, performing some of the technical assessments, and summarising clearly the benefits and drawbacks.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### ✨ Initiative and Influence\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth width=\"100%\"\u003eCore Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eAttends key meetings with Stakeholders and provide detailed technical views on the subject being discussed.\u003c/li\u003e\n        \u003cli\u003eAdvises, using data where relevant, on technical challenges and opportunities in conversations with Product Managers, sponsors and senior stakeholders.\u003c/li\u003e\n        \u003cli\u003eLeads collaborative discussions about evolving best practices (such as accessibility standards), defining our engineering standards.\u003c/li\u003e\n        \u003cli\u003eSeeks out systemic problems and opportunities, and presents proposals to the Head of Engineering on how to, respectively, remediate them and benefit from them.\u003c/li\u003e\n        \u003cli\u003eAdvises on new technology trials based on your previous experience, and mentor more junior developers in their technical discovery and technology intelligence.\u003c/li\u003e\n        \u003cli\u003eInspires action from colleagues and stakeholders.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n#### 👩‍👨 People\n\n\u003ctable\u003e\n  \u003ctr\u003e \u003cth width=\"100%\"\u003eCore Criteria\u003c/th\u003e\u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\n      \u003cul\u003e\n        \u003cli\u003eWorks with other Principal Engineers across the department to ensure their individual stream strategies align, and that common issues are resolved department wide and not stream-by-stream.\u003c/li\u003e\n        \u003cli\u003eShares knowledge across the department through technical presentations, writes articles, pairs with more junior colleagues, and other appropriate mechanisms.\u003c/li\u003e\n        \u003cli\u003eHelps to investigate complex technical issues and provides guidance for more junior developers when dealing with an incident.\u003c/li\u003e\n        \u003cli\u003eMentors Tech Leads and provides guidance on subject architectural choices review and prioritisation of technical debt.\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fguardian%2Fengineering-performance-framework","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fguardian%2Fengineering-performance-framework","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fguardian%2Fengineering-performance-framework/lists"}