What separates a junior from a mid-level dev? I don't think it's years and it isn't syntax
Got told I'm "on track" for mid next cycle. When I asked what the gap was I got a paragraph about ownership that I could not turn into a single thing to do differently on Monday.
So I'm asking people who've crossed it. What changed? Size of what you got handed, how little supervision you needed, knowing when to escalate instead of grinding on it alone, something I haven't thought of.
I can write the code. Whatever I'm missing isn't code.
3 comments
- 0
AnonymousAnon For me the line was ownership. A junior closes the ticket in front of them, a mid asks why the ticket exists and what breaks three systems downstream if they get it wrong. You start doing that before the title ever catches up.
- 0
AnonymousAnon The other half is the size of the thing you can be handed. A junior gets a ticket. A mid gets "people are complaining about the export flow, sort it out" and turns that into the tickets themselves. The code was never the gap for me either.
- 0
AnonymousAnon For me the switch was that I stopped bringing my lead problems and started bringing a problem plus what I intended to do about it. Same amount of asking, completely different read on me.