29 ms·
Every place has its own names for things, but I often see "senior" refer to your interchangeable seniority in the field, not just in the one company/code base.
by sverhagen 9y ago
Every place has its own names for things, but I often see "senior" refer to your interchangeable seniority in the field, not just in the one company/code base. Then for people to grow into "lead" or "principal".
- johan_larson 9y agoSenior Developer is typically either a junior or intermediate title. In some places, the title progression for technical professionals is (dev, senior dev, staff dev, principal dev, arch, senior arch), meaning Senior is actually a junior title. In other places, the title progression is (dev I, dev II, senior dev, staff dev, senior staff dev, principal), meaning Senior is an intermediate title. There is of course some variability across companies, but it's safe to say that "Senior Developer" is never an actually senior position. People holding it are never in charge of big things.
- falcolas 9y agoIt's worth noting that most non-enterprise companies (i.e. not Microsoft, IBM, or Oracle) don't implement staff or principal prefixes, making senior the top of the list. I haven't had a principal prefix since I worked for Oracle (and got there via an acquisition where I was a senior), yet I'm always at or near the top of the development ladder for my department. As always, you need to ask questions, not make assumptions.
- deleted 9y ago[deleted]
- noway421 9y agoYeah, I think seniority in field means knowing the interchangeable parts of the stack. Even if the particular technology might be unknown to you, you still know the challenges each part might be representing and how to overcome them/what you should be aware of. It might be that I read the question wrong. OP says that the tech stack is unfamiliar, and I guess it comes down on whether they've been familiar with a similar tech stack or something is architecturely different.