As others mentioned, the junior/mid/senior are simply titles. In our company, we have junior, mid and senior level roles. The (unofficial) definition for these roles are,
Junior Developer: One who knows the basic coding blocks, familiar with at least one language (C, Java, Javascript) at least just enough to get around the code and understand what's going on, initially needs help/guidance in carrying out his day-to-day tasks and most of all, one who can listen and learn.
Mid Developer: One who is strong in at least one language/technology, can effectively work on his day-to-day tasks without any help from others, can collaborate with other developers in the team in implementing a solution.
Senior Developer: Person who not only understands the application which we works on, but also how it falls into the products and services offered by the company. He can coordinate teams and design/architect solutions, etc.,
Keeping in that mind, when we recruit we don't officially post that we want junior developers. We decide that after the technical interview.
As Kim Arnett mentioned earlier, number of years doesn't really justify the title. So even if a person puts on his resume as Senior developer based on his number of years, if the person doesn't have enough experience in the technology which the role requires (for ex. node.js) he would still be considered as Junior/Mid level developers.
My suggestion is to keep the role as generic and let them decide where you fit in.
As others mentioned, the junior/mid/senior are simply titles. In our company, we have junior, mid and senior level roles. The (unofficial) definition for these roles are,
Junior Developer: One who knows the basic coding blocks, familiar with at least one language (C, Java, Javascript) at least just enough to get around the code and understand what's going on, initially needs help/guidance in carrying out his day-to-day tasks and most of all, one who can listen and learn.
Mid Developer: One who is strong in at least one language/technology, can effectively work on his day-to-day tasks without any help from others, can collaborate with other developers in the team in implementing a solution.
Senior Developer: Person who not only understands the application which we works on, but also how it falls into the products and services offered by the company. He can coordinate teams and design/architect solutions, etc.,
Keeping in that mind, when we recruit we don't officially post that we want junior developers. We decide that after the technical interview.
As Kim Arnett mentioned earlier, number of years doesn't really justify the title. So even if a person puts on his resume as Senior developer based on his number of years, if the person doesn't have enough experience in the technology which the role requires (for ex. node.js) he would still be considered as Junior/Mid level developers.
My suggestion is to keep the role as generic and let them decide where you fit in.
Thanks for the advice. I found this extremely helpful!