<aside> 🌍 This page has been made public for all engineering candidates. 🙂
</aside>
In the beginning of December, I started working on a career path to introduce at Luminovo. As I hope you’ve noticed, the focus within Product & Engineering has fully shifted to shipping, shipping, and more shipping over the last weeks, so I paused this endeavor for now.
However, for @magnus jahnen 360 degree feedback, I replaced the normal performance objectives with a new format, based on the preparation work I was doing for our career paths. You can find the dimensions, we used to query feedback for Magnus below.
The idea is not that every single engineer excels in every single dimension, but the dimensions should give you an idea in which areas you can still grow. When giving feedback on the different dimensions, you shouldn’t worry about answering every last question. Instead you should focus your feedback on what a Luminerd does best and worst.
My original plan was to refine this more before writing the first RfC, but perfect is the enemy of the good, so voila.
<aside> 👉 What do I want from you? Read through the dimensions below. Does this reflect your understanding what a good software engineer should be doing at Luminovo? Is something unclear? Is something missing for you? And most importantly: would this help you guide feedback conversations about personal development and career trajectories that you have with your manager, directs and peers?
</aside>
You can skip this part, but if you’re interested, I outlined some of the principles that can help you understand what distinguishes a good from a bad career path.