https://github.com/financial-times/engineering-progression
Careers and progression for staff members in the Technology organisation at the FT.
https://github.com/financial-times/engineering-progression
Last synced: about 1 year ago
JSON representation
Careers and progression for staff members in the Technology organisation at the FT.
- Host: GitHub
- URL: https://github.com/financial-times/engineering-progression
- Owner: Financial-Times
- License: mit
- Created: 2019-02-14T10:47:27.000Z (over 7 years ago)
- Default Branch: main
- Last Pushed: 2025-03-04T10:46:44.000Z (over 1 year ago)
- Last Synced: 2025-03-31T14:43:02.770Z (about 1 year ago)
- Language: JavaScript
- Homepage: https://engineering-progression.ft.com/
- Size: 923 KB
- Stars: 118
- Watchers: 116
- Forks: 18
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# Engineering Progression
Job family and competencies for all roles in the Technology organisation at the FT.
---
- [Overview](#overview)
- [Competencies](#competencies)
- [Contributing](#contributing)
- [Licence](#licence)
## Overview
This repository holds the job family and competencies for all roles in the Technology organisation at the FT.
Keeping this framework in GitHub means we can use issues and pull requests to track and discuss changes to the competencies and job family descriptions. Storing it in this way also allows us to version it and release any changes.
This framework can be used in its raw form (YAML files), but it is also available via JSON endpoint, which means other things can be built off it (eg a Google Sheet)
## Competencies
Competencies are used to inform conversations about career progression between staff members and their manager. They are used for:
1. Defining a vacant or new role, writing a job description, evaluating candidates for a job
2. Setting and agreeing objectives designed to develop a staff member in their role
3. Tracking progress, managing performance and giving feedback, making expectations clear for each staff member
4. Evaluating readiness for a staff member to step up to the next level (e.g. through promotion)
There are several ways that you can read through these competencies and track progress:
- [Track and document progress using a Google Sheet](https://docs.google.com/spreadsheets/d/1V0LIbCQtJsi2iowfJnRTDr4Na4LhNAlJ_UHl9dDQs00/edit)
- [View all competencies on the website](https://engineering-progression.ft.com/competencies/)
- [Read the engineering competencies as YAML in this repository](data/job-families)
## Contributing
Anybody working for the Financial Times is welcome to suggest changes via a GitHub issue or pull request. We maintain a [contributing guide](CONTRIBUTING.md) to help people who are interested. There are many different ways you can contribute and help make this resource better for everyone:
- **Contribute to the Engineering Competencies**
Every engineer in the CTO organisation of the Financial Times can help shape these competencies. [A guide for adding or editing competencies is here](docs/competencies.md).
- **Contribute to the documentation and website**
It's important that the documentation in this repo and the Engineering Progression website is clear and easy to understand. [Get started maintaining the documentation](docs/documentation.md)
- **Contribute to the running of this repository**
This repository is the one source of truth for engineering careers and progression, and as such it's important that the code is maintained. It's also important that issues and pull requests are responded to quickly. [Get started contributing to the running of this repo](docs/repository.md)
## Licence
This software is published by the Financial Times under the [MIT licence](http://opensource.org/licenses/MIT).