21–24 of 24 posts
If you have 18 years of professional experience in anything, you are senior. It's not that complicated and at that point it doesn't matter what the company is.
Not that it automatically makes you a brilliant developer. But at that level of experience you can't consider someone as junior or mid. It's senior or above.
2) If you had to give an objective definition of a senior developer, it might be somebody that can design and plan out complicated product features on their own and who others turn to for guidance. That doesn't mean that seniors don't sometimes need to collaborate with others, but generally they can figure out how to solve most of their own problems without having their hand held.
It's supposes to mean years of exp and expertise but whatever
Earlier quoted context omitted.
Going in under-leveled but at the highest salary/total comp you qualify for could be beneficial. If its a large company that has a well known job title hierarchy you ideally want the maximum salary in the lowest job title in the hierarchy that has that salary in its range. Pretend your target salary is $100 (the numbers don't matter) and they have L1-L10 with L1 being the lowest and the ranges are: * L2: $80-110 * L3…
Yes, I suppose so but that assumes two things: 1. That you know the per-level salary bands before you join the company (this is often not public information) 2. That the salary bands overlap to a significant degree
All salary bands overlap, a company with a lot more people will have a lot more variation in salary per level/title.