When someone tells you that they're a "Senior Software Developer @ XYZ Corp." , what do they really mean:
- They've done many jobs of that type before
- They're actually senior by age to other developers
- They just aced a really tough interview
When someone tells you that they're a "Senior Software Developer @ XYZ Corp." , what do they really mean:
That depends on the definition that the company he works for gives him, so it's subjective.
In our company, for someone to have earned this title, it means he's a seasoned developer with experience and a proven track record of being trusted, and good at what he does. The title has little to do with age or seniority, and more to do with skill and maturity.
It generally refers to a Software Developer that has a lot of experience (which can come with age) and differentiates the developer from a "Junior" developer. In larger companies/teams, people like to have differentiating job titles and show some kind of natural heriarchy. Most of the time Senior developers have earned that title through experience.
To me, it can be a combination of a few things:
But again, depending on the company they are working for, the job description will vary.
It means that their employer considers them either:
or all of the above.
It is all about the money, read this, find the place where you are, and decide if you are one of them :)
And this question should be community wiki, i believe.
The age of the developer itself does not make anyone 'Senior'. It may happen that someone is being a 'senior software engineer/developer' and someone else (a little bit older) is just a 'software developer'. The type of interview also should not make any difference. The difference should be experience. I think people usually are being considered as a senior software devs when having 5+ commercial (full-time) experience.
It means virtually NOTHING unless you know the context of the company they work for.
Typically, it is a prefix that matches pay scale or experience and starts at associate, to staff, to senior, to lead, to principle, to head.
Practically speaking, you can't expect to match it up with technical competence. Some people are really into titles but I would prefer fewer meaningless titles myself.
I think that in the best of all possible worlds, one's title would be one's name.
In general, it's meaningless. See The Senior System Administrators.
In some companies it may have very specific meanings, but you'd need to have a deep understanding of that particular company's corporate culture.