https://github.com/sdras/career-ladders
A sample of career ladders I use for my organization, open sourced for anyone.
https://github.com/sdras/career-ladders
career developer-advocacy documentation engineering guidance management
Last synced: 10 months ago
JSON representation
A sample of career ladders I use for my organization, open sourced for anyone.
- Host: GitHub
- URL: https://github.com/sdras/career-ladders
- Owner: sdras
- License: mit
- Created: 2021-04-07T15:48:54.000Z (almost 5 years ago)
- Default Branch: main
- Last Pushed: 2021-08-27T21:25:56.000Z (over 4 years ago)
- Last Synced: 2025-02-14T09:51:12.132Z (12 months ago)
- Topics: career, developer-advocacy, documentation, engineering, guidance, management
- Language: Vue
- Homepage: https://career-ladders.dev/
- Size: 3.92 MB
- Stars: 805
- Watchers: 17
- Forks: 63
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE.md
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Career Ladders
Site is here: [Career Ladders Site](https://career-ladders.dev/)
[I have an article about how I put these into practice in case it's helpful.](https://css-tricks.com/the-importance-of-career-laddering/) It's very important to not just put up career ladders and call it a day, but rather, put them into practice with a system that your employees can trust.
It's been more than a year since [I promised Sam Julien](https://twitter.com/samjulien/status/1265713280095531008?s=20) that I would open source the career laddering I've developed as an Engineering Manager and VP. The purpose of open sourcing them is _not_ to give the impression that this is the one true way to do career laddering, or that these are perfect and there's nothing to improve upon here. There is some value in sharing them, though, in that many folks have mentioned to me that they don't know where to start.
I'm open sourcing my career ladders so that people have a launching-off point. I do not have this all figured out, please feel free to iterate, or give feedback, or submit a PR. Full transparency, I don't have a ton of time for maintenance right now, and am maintaining a _lot_ of repos, so if your PR goes unnoticed for a while, that's why. I also may reject a PR if it's not the way I personally want to structure something, but that's ok! It's alright for us to have different ways of creating laddering, in fact, I would encourage one to make some changes depending on your org in particular, we don't have to all be the same, and probably shouldn't be.
Special thanks to Lauren Sell, Dizzy Smith, Jason Lengstorf, and Dalia Havens for always being around to bounce my ideas off of. Thanks to Chad Fowler for demonstrating a great example of career laddering while I was at Microsoft!
## Build Setup
```bash
# install dependencies
$ yarn install
# serve with hot reload at localhost:3000
$ yarn dev
# build for production and launch server
$ yarn build
$ yarn start
# generate static project
$ yarn generate
```
For detailed explanation on how things work, check out [Nuxt.js docs](https://nuxtjs.org).