What is a mid-level developer to you?
Photo credit Pexels.com, attribution isn't required but they are rad.
Story time. I had a recruiter reach out to me yesterday for the first time in ~9 months. After some conversation (possibly including self-assessment and salary topics) he admitted he had been passing over my name for mid-level positions, thinking I still considered myself to be junior. He suggested that I have another "tech assessment" phone call, implying "how much could have really changed?" when I feel he didn't really know me when we talked the first time around. (Not counting the degree I've been doing this ~4 years now.)
This got me wondering, how would a recruiter define the difference vs. how would a developer define the difference? without diving into unhealthy comparisons,
- Where do you draw your arbitrary line in the sand?
- Are there specific experiences you expect someone to have had before they can claim to be a mid-level developer?
- Are there specific languages/frameworks they must know or certain concepts they should be able to explain off-hand?
UPDATE: I did have that tech assessment, and I felt really good about it! As my final question I asked what a mid-level dev was to the interviewer, and the things he mentioned were all things I do day-to-day. Some examples he gave:
- Works with little to no supervision
- Is always learning and improving
- Does the work and documents as they go
- Knows when to reach out for help
- Helps more junior team members