
I run a five level job levelling framework across AI and software engineering, design, project management and business development at Kreeda Labs. When someone is hired at one level rather than the next, or moves up, I am in that decision.
Most people at one to five years are working hard on the wrong things. They are getting better at the job they already have, which is exactly what keeps them in it.
Forty five minutes on what the next level actually requires in your discipline and how far away you are. Which of your current strengths have stopped earning you anything. The two or three behaviours that separate the people who move from the people who stay. And how to raise it with your manager without it sounding like a demand.
We also cover the uncomfortable version. Sometimes the honest answer is that there is no level above you here worth having, and the move is out rather than up. I will say so if that is what the evidence looks like.
Who this is for: software engineers, QA, designers, data and AI people, analysts, coordinators and junior PMs at one to five years who have been at the same level long enough to start wondering why.
What you leave with: the specific gap, written down, and what to do about it this quarter.