Skip to content
Careers and progression for engineers in the CTO organisation
Branch: master
Clone or download
rowanmanning Add automated accessibility tests to the website (#123)
I've just been doing this work for the Origami website, and thought it
might be nice to run some automated accessibility tests on the
engineering progression website.

This now uses Pa11y CI to test some of the more obvious accessibility
issues. The build will fail if any are introduced.
Latest commit 9d4c6c2 Apr 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Add automated accessibility tests to the website (#123) Apr 15, 2019
data Fix typo on J->M Delivery: Works on most important task (#122) Apr 11, 2019
docs
script Add the full semantic version to the API (#119) Apr 10, 2019
site
test/schema Make the UUID regex more lenient (#31) Feb 26, 2019
.gitignore Deploy competency data to Google Sheets (#29) Feb 26, 2019
CONTRIBUTING.md Fix typo (#120) Apr 10, 2019
Gemfile Add a Jekyll site (#7) Feb 20, 2019
Gemfile.lock Add a Jekyll site (#7) Feb 20, 2019
LICENSE Initial commit Feb 14, 2019
Makefile Add automated accessibility tests to the website (#123) Apr 15, 2019
README.md Update places where competencies are viewable (#76) Mar 18, 2019
package-lock.json Add automated accessibility tests to the website (#123) Apr 15, 2019
package.json Add automated accessibility tests to the website (#123) Apr 15, 2019

README.md

Engineering Progression

Careers and progression for engineers in the CTO organisation.

⚠️ This project is currently in ALPHA, please do not use this to guide promotions decisions yet. We'll be publishing a BETA in the near future and helping to test this in a promotions round after that.


Overview

This repository is the single source of truth for the competencies and level definitions for Engineering roles in the CTO 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 role 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 availble via JSON endpoint, which means other things can be built off it (eg a Google Sheet)

Engineering Competencies

Engineering competencies are used to help identify when an engineer is ready for promotion. There are several ways that you can read through these competencies and track progress:

Contributing

Anybody working for the Financial Times is welcome to suggest changes via a GitHub issue or pull request. We maintain a contributing guide 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
    The Engineering competencies are used to help identify when an engineer is ready for promotion. Every engineer in the CTO organisation of the Financial Times can help shape these competencies. While they are in alpha and beta we are especially interested in contributions. A guide for adding or editing competencies is here.

  • Contribute to the documentation and website
    It's important that the documentation in this repo and the Engineering Progression website are clear and easy to understand. Get started maintaining the documentation

  • Build your own integration
    The competencies data is available through a JSON API, which means that engineers at the Financial Times can build their own integrations on top of it. Get started writing your own integrations

  • 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

Licence

This software is published by the Financial Times under the MIT licence.

You can’t perform that action at this time.