Hard to say, especially If I think, I seen recently in Sweden a bunch of senior with like 2-3 years of experience and leads and cto-s with 5-6 years of experience....
IMHO,
a junior supposed to understand a few basic principle, and supposed to know several keyword, and probably played around a lot with things.
A mid-level/developer, I believe is a mixed rank. Have the knowledge of several principle, things, code snippets, tricks, environment, also has a few project behind, understand other non-essential things. E.g.: has experience, but only focused on his area.
A senior can understand not just the things what he/she need to work, but the connected technologies and can see a project on a higher level, can understand requirements and how to ship different parts.
A lead more like a politician. Normally, they does not code anymore, but they understand the tech perspective, has higher view, more information from a project. Can decide direction since has vision where it shall lead. Also, has understanding on low level also, and by architecture or has the knowledge, who to talk to.
An architect is less development, more devop/sysop and understanding of connections, interactions, correlations and possibilities. At many company an "architect" basically a sysop/devop, who more like a cloud/aws/gcloud... manager and has the responsiblity to make hw & sw on bottom layer works.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hard to say, especially If I think, I seen recently in Sweden a bunch of senior with like 2-3 years of experience and leads and cto-s with 5-6 years of experience....
IMHO,
a junior supposed to understand a few basic principle, and supposed to know several keyword, and probably played around a lot with things.
A mid-level/developer, I believe is a mixed rank. Have the knowledge of several principle, things, code snippets, tricks, environment, also has a few project behind, understand other non-essential things. E.g.: has experience, but only focused on his area.
A senior can understand not just the things what he/she need to work, but the connected technologies and can see a project on a higher level, can understand requirements and how to ship different parts.
A lead more like a politician. Normally, they does not code anymore, but they understand the tech perspective, has higher view, more information from a project. Can decide direction since has vision where it shall lead. Also, has understanding on low level also, and by architecture or has the knowledge, who to talk to.
An architect is less development, more devop/sysop and understanding of connections, interactions, correlations and possibilities. At many company an "architect" basically a sysop/devop, who more like a cloud/aws/gcloud... manager and has the responsiblity to make hw & sw on bottom layer works.