Mixing
Advancing to Senior positions [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
2
down vote
favorite
I've been working as a Software Engineer for 8 years. I have not specialized on any language or technology, as I've been unlucky with my assigned projects and almost all of them used different languages. I could consider myself a Senior regarding general experience, but maybe not regarding technologies. Right now I'm looking for positions as Software Engineer.
My question is, with my experience, is it good to aim for a Senior position as my next step? Or maybe a better question, do you think someone with my experience would be fit for a Senior position?
job-search career-development careers
edited May 8 '15 at 10:12
EAlvarado
31
asked May 7 '15 at 21:56
Edo
141
closed as off-topic by scaaahu, gnat, IDrinkandIKnowThings, keshlam, DJClayworth May 10 '15 at 5:41
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – scaaahu, gnat, IDrinkandIKnowThings, keshlam, DJClayworth
suggest improvements |Â
up vote
2
down vote
favorite
I've been working as a Software Engineer for 8 years. I have not specialized on any language or technology, as I've been unlucky with my assigned projects and almost all of them used different languages. I could consider myself a Senior regarding general experience, but maybe not regarding technologies. Right now I'm looking for positions as Software Engineer.
My question is, with my experience, is it good to aim for a Senior position as my next step? Or maybe a better question, do you think someone with my experience would be fit for a Senior position?
job-search career-development careers
edited May 8 '15 at 10:12
EAlvarado
31
asked May 7 '15 at 21:56
Edo
141
closed as off-topic by scaaahu, gnat, IDrinkandIKnowThings, keshlam, DJClayworth May 10 '15 at 5:41
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – scaaahu, gnat, IDrinkandIKnowThings, keshlam, DJClayworth
4
Whether you're a fit for a senior position depends on how good you are, not how many years you've done at the grindstone.
– Philip Kendall
May 7 '15 at 22:19
@PhilipKendall this answer seems to suggest that it's not as straightforward "Most companies want to hire people that have had their failures paid for by previous companies, that is why they require N+ years of experience..."
– gnat
May 8 '15 at 10:11
2
"Senior" is an unbelievably squishy term when it comes to this field. I'm out looking for a new position myself and have run across openings where it means more than two, five, ten or 15 or 20 years. Disregard the title and look at the requirements.
– Blrfl
May 8 '15 at 11:14
@PhilipKendall, If only that were true in all cases. Try working in defence contracting, where education/experience requirements for each engineering 'level' is very specifically laid out.
– James Adam
May 8 '15 at 13:30
suggest improvements |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I've been working as a Software Engineer for 8 years. I have not specialized on any language or technology, as I've been unlucky with my assigned projects and almost all of them used different languages. I could consider myself a Senior regarding general experience, but maybe not regarding technologies. Right now I'm looking for positions as Software Engineer.
My question is, with my experience, is it good to aim for a Senior position as my next step? Or maybe a better question, do you think someone with my experience would be fit for a Senior position?
job-search career-development careers
edited May 8 '15 at 10:12
EAlvarado
31
asked May 7 '15 at 21:56
Edo
141
I've been working as a Software Engineer for 8 years. I have not specialized on any language or technology, as I've been unlucky with my assigned projects and almost all of them used different languages. I could consider myself a Senior regarding general experience, but maybe not regarding technologies. Right now I'm looking for positions as Software Engineer.
My question is, with my experience, is it good to aim for a Senior position as my next step? Or maybe a better question, do you think someone with my experience would be fit for a Senior position?
job-search career-development careers
edited May 8 '15 at 10:12
EAlvarado
31
asked May 7 '15 at 21:56
Edo
141
edited May 8 '15 at 10:12
EAlvarado
31
edited May 8 '15 at 10:12
EAlvarado
31
edited May 8 '15 at 10:12
EAlvarado
31
31
asked May 7 '15 at 21:56
Edo
141
asked May 7 '15 at 21:56
Edo
141
asked May 7 '15 at 21:56
Edo
141
141
closed as off-topic by scaaahu, gnat, IDrinkandIKnowThings, keshlam, DJClayworth May 10 '15 at 5:41
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – scaaahu, gnat, IDrinkandIKnowThings, keshlam, DJClayworth
closed as off-topic by scaaahu, gnat, IDrinkandIKnowThings, keshlam, DJClayworth May 10 '15 at 5:41
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – scaaahu, gnat, IDrinkandIKnowThings, keshlam, DJClayworth
4
Whether you're a fit for a senior position depends on how good you are, not how many years you've done at the grindstone.
– Philip Kendall
May 7 '15 at 22:19
@PhilipKendall this answer seems to suggest that it's not as straightforward "Most companies want to hire people that have had their failures paid for by previous companies, that is why they require N+ years of experience..."
– gnat
May 8 '15 at 10:11
2
"Senior" is an unbelievably squishy term when it comes to this field. I'm out looking for a new position myself and have run across openings where it means more than two, five, ten or 15 or 20 years. Disregard the title and look at the requirements.
– Blrfl
May 8 '15 at 11:14
@PhilipKendall, If only that were true in all cases. Try working in defence contracting, where education/experience requirements for each engineering 'level' is very specifically laid out.
– James Adam
May 8 '15 at 13:30
suggest improvements |Â
4
Whether you're a fit for a senior position depends on how good you are, not how many years you've done at the grindstone.
– Philip Kendall
May 7 '15 at 22:19
@PhilipKendall this answer seems to suggest that it's not as straightforward "Most companies want to hire people that have had their failures paid for by previous companies, that is why they require N+ years of experience..."
– gnat
May 8 '15 at 10:11
2
"Senior" is an unbelievably squishy term when it comes to this field. I'm out looking for a new position myself and have run across openings where it means more than two, five, ten or 15 or 20 years. Disregard the title and look at the requirements.
– Blrfl
May 8 '15 at 11:14
@PhilipKendall, If only that were true in all cases. Try working in defence contracting, where education/experience requirements for each engineering 'level' is very specifically laid out.
– James Adam
May 8 '15 at 13:30
4
4
Whether you're a fit for a senior position depends on how good you are, not how many years you've done at the grindstone.
– Philip Kendall
May 7 '15 at 22:19
Whether you're a fit for a senior position depends on how good you are, not how many years you've done at the grindstone.
– Philip Kendall
May 7 '15 at 22:19
@PhilipKendall this answer seems to suggest that it's not as straightforward "Most companies want to hire people that have had their failures paid for by previous companies, that is why they require N+ years of experience..."
– gnat
May 8 '15 at 10:11
@PhilipKendall this answer seems to suggest that it's not as straightforward "Most companies want to hire people that have had their failures paid for by previous companies, that is why they require N+ years of experience..."
– gnat
May 8 '15 at 10:11
2
2
"Senior" is an unbelievably squishy term when it comes to this field. I'm out looking for a new position myself and have run across openings where it means more than two, five, ten or 15 or 20 years. Disregard the title and look at the requirements.
– Blrfl
May 8 '15 at 11:14
"Senior" is an unbelievably squishy term when it comes to this field. I'm out looking for a new position myself and have run across openings where it means more than two, five, ten or 15 or 20 years. Disregard the title and look at the requirements.
– Blrfl
May 8 '15 at 11:14
@PhilipKendall, If only that were true in all cases. Try working in defence contracting, where education/experience requirements for each engineering 'level' is very specifically laid out.
– James Adam
May 8 '15 at 13:30
@PhilipKendall, If only that were true in all cases. Try working in defence contracting, where education/experience requirements for each engineering 'level' is very specifically laid out.
– James Adam
May 8 '15 at 13:30
suggest improvements |Â
1 Answer
1
active
oldest
votes
up vote
8
down vote
The major difference between a senior and junior developer isn't the number of years, nor is it the specialisation in any given technology. It is the ability to analyse the problem you are facing, break it down, perform whatever research you need and resolve it yourself. You don't have to go a more experienced person to solve it for you.
This doesn't mean you can't go talk to an expert in a given technology if you need their input, but they aren't solving the problem for you. YOU are doing the analysis, identifying the potential solutions.
You are the person that people come to talk to if they can't solve their problems. Does this happen, title notwithstanding? Most people have become senior developers in reality before they ever get allocated the title. That's what moves you into the more senior roles - a demonstrated capacity to act as a senior developer.
answered May 7 '15 at 23:06
Jane S♦
40.8k17125159
1
Yep. This sums it up nicely. In my case, I was hired in and intermediate-senior capacity right out of college since I had been doing FOSS C/C++ development since childhood and had already managed some small projects. If you can convince people you really know what you're doing, are self driven, eager to learn new things on your own without being asked, and can pass that knowledge on to others, you're well ahead of the competition.
– DevNull
May 7 '15 at 23:33
1
I think number of years is also a requirement though 8 years is about the minimum to get the sort of experience to have a chance to be considered a senior. More realistically unless you are the super star 10-12 years is more likely just to get the breadth of experience needed for a senior position. That said I got my first senior position with just 4 years experience. I was not really ready for it and it showed. 10 years later it is evident to me why.
– IDrinkandIKnowThings
May 8 '15 at 12:39
suggest improvements |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
The major difference between a senior and junior developer isn't the number of years, nor is it the specialisation in any given technology. It is the ability to analyse the problem you are facing, break it down, perform whatever research you need and resolve it yourself. You don't have to go a more experienced person to solve it for you.
This doesn't mean you can't go talk to an expert in a given technology if you need their input, but they aren't solving the problem for you. YOU are doing the analysis, identifying the potential solutions.
You are the person that people come to talk to if they can't solve their problems. Does this happen, title notwithstanding? Most people have become senior developers in reality before they ever get allocated the title. That's what moves you into the more senior roles - a demonstrated capacity to act as a senior developer.
answered May 7 '15 at 23:06
Jane S♦
40.8k17125159
1
Yep. This sums it up nicely. In my case, I was hired in and intermediate-senior capacity right out of college since I had been doing FOSS C/C++ development since childhood and had already managed some small projects. If you can convince people you really know what you're doing, are self driven, eager to learn new things on your own without being asked, and can pass that knowledge on to others, you're well ahead of the competition.
– DevNull
May 7 '15 at 23:33
1
I think number of years is also a requirement though 8 years is about the minimum to get the sort of experience to have a chance to be considered a senior. More realistically unless you are the super star 10-12 years is more likely just to get the breadth of experience needed for a senior position. That said I got my first senior position with just 4 years experience. I was not really ready for it and it showed. 10 years later it is evident to me why.
– IDrinkandIKnowThings
May 8 '15 at 12:39
suggest improvements |Â
up vote
8
down vote
The major difference between a senior and junior developer isn't the number of years, nor is it the specialisation in any given technology. It is the ability to analyse the problem you are facing, break it down, perform whatever research you need and resolve it yourself. You don't have to go a more experienced person to solve it for you.
This doesn't mean you can't go talk to an expert in a given technology if you need their input, but they aren't solving the problem for you. YOU are doing the analysis, identifying the potential solutions.
You are the person that people come to talk to if they can't solve their problems. Does this happen, title notwithstanding? Most people have become senior developers in reality before they ever get allocated the title. That's what moves you into the more senior roles - a demonstrated capacity to act as a senior developer.
answered May 7 '15 at 23:06
Jane S♦
40.8k17125159
1
Yep. This sums it up nicely. In my case, I was hired in and intermediate-senior capacity right out of college since I had been doing FOSS C/C++ development since childhood and had already managed some small projects. If you can convince people you really know what you're doing, are self driven, eager to learn new things on your own without being asked, and can pass that knowledge on to others, you're well ahead of the competition.
– DevNull
May 7 '15 at 23:33
1
I think number of years is also a requirement though 8 years is about the minimum to get the sort of experience to have a chance to be considered a senior. More realistically unless you are the super star 10-12 years is more likely just to get the breadth of experience needed for a senior position. That said I got my first senior position with just 4 years experience. I was not really ready for it and it showed. 10 years later it is evident to me why.
– IDrinkandIKnowThings
May 8 '15 at 12:39
suggest improvements |Â
up vote
8
down vote
up vote
8
down vote
The major difference between a senior and junior developer isn't the number of years, nor is it the specialisation in any given technology. It is the ability to analyse the problem you are facing, break it down, perform whatever research you need and resolve it yourself. You don't have to go a more experienced person to solve it for you.
This doesn't mean you can't go talk to an expert in a given technology if you need their input, but they aren't solving the problem for you. YOU are doing the analysis, identifying the potential solutions.
You are the person that people come to talk to if they can't solve their problems. Does this happen, title notwithstanding? Most people have become senior developers in reality before they ever get allocated the title. That's what moves you into the more senior roles - a demonstrated capacity to act as a senior developer.
answered May 7 '15 at 23:06
Jane S♦
40.8k17125159
The major difference between a senior and junior developer isn't the number of years, nor is it the specialisation in any given technology. It is the ability to analyse the problem you are facing, break it down, perform whatever research you need and resolve it yourself. You don't have to go a more experienced person to solve it for you.
This doesn't mean you can't go talk to an expert in a given technology if you need their input, but they aren't solving the problem for you. YOU are doing the analysis, identifying the potential solutions.
You are the person that people come to talk to if they can't solve their problems. Does this happen, title notwithstanding? Most people have become senior developers in reality before they ever get allocated the title. That's what moves you into the more senior roles - a demonstrated capacity to act as a senior developer.
answered May 7 '15 at 23:06
Jane S♦
40.8k17125159
answered May 7 '15 at 23:06
Jane S♦
40.8k17125159
answered May 7 '15 at 23:06
Jane S♦
40.8k17125159
answered May 7 '15 at 23:06
Jane S♦
40.8k17125159
40.8k17125159
1
Yep. This sums it up nicely. In my case, I was hired in and intermediate-senior capacity right out of college since I had been doing FOSS C/C++ development since childhood and had already managed some small projects. If you can convince people you really know what you're doing, are self driven, eager to learn new things on your own without being asked, and can pass that knowledge on to others, you're well ahead of the competition.
– DevNull
May 7 '15 at 23:33
1
I think number of years is also a requirement though 8 years is about the minimum to get the sort of experience to have a chance to be considered a senior. More realistically unless you are the super star 10-12 years is more likely just to get the breadth of experience needed for a senior position. That said I got my first senior position with just 4 years experience. I was not really ready for it and it showed. 10 years later it is evident to me why.
– IDrinkandIKnowThings
May 8 '15 at 12:39
suggest improvements |Â
1
Yep. This sums it up nicely. In my case, I was hired in and intermediate-senior capacity right out of college since I had been doing FOSS C/C++ development since childhood and had already managed some small projects. If you can convince people you really know what you're doing, are self driven, eager to learn new things on your own without being asked, and can pass that knowledge on to others, you're well ahead of the competition.
– DevNull
May 7 '15 at 23:33
1
I think number of years is also a requirement though 8 years is about the minimum to get the sort of experience to have a chance to be considered a senior. More realistically unless you are the super star 10-12 years is more likely just to get the breadth of experience needed for a senior position. That said I got my first senior position with just 4 years experience. I was not really ready for it and it showed. 10 years later it is evident to me why.
– IDrinkandIKnowThings
May 8 '15 at 12:39
1
1
Yep. This sums it up nicely. In my case, I was hired in and intermediate-senior capacity right out of college since I had been doing FOSS C/C++ development since childhood and had already managed some small projects. If you can convince people you really know what you're doing, are self driven, eager to learn new things on your own without being asked, and can pass that knowledge on to others, you're well ahead of the competition.
– DevNull
May 7 '15 at 23:33
Yep. This sums it up nicely. In my case, I was hired in and intermediate-senior capacity right out of college since I had been doing FOSS C/C++ development since childhood and had already managed some small projects. If you can convince people you really know what you're doing, are self driven, eager to learn new things on your own without being asked, and can pass that knowledge on to others, you're well ahead of the competition.
– DevNull
May 7 '15 at 23:33
1
1
I think number of years is also a requirement though 8 years is about the minimum to get the sort of experience to have a chance to be considered a senior. More realistically unless you are the super star 10-12 years is more likely just to get the breadth of experience needed for a senior position. That said I got my first senior position with just 4 years experience. I was not really ready for it and it showed. 10 years later it is evident to me why.
– IDrinkandIKnowThings
May 8 '15 at 12:39
I think number of years is also a requirement though 8 years is about the minimum to get the sort of experience to have a chance to be considered a senior. More realistically unless you are the super star 10-12 years is more likely just to get the breadth of experience needed for a senior position. That said I got my first senior position with just 4 years experience. I was not really ready for it and it showed. 10 years later it is evident to me why.
– IDrinkandIKnowThings
May 8 '15 at 12:39
suggest improvements |Â
4
Whether you're a fit for a senior position depends on how good you are, not how many years you've done at the grindstone.
– Philip Kendall
May 7 '15 at 22:19
@PhilipKendall this answer seems to suggest that it's not as straightforward "Most companies want to hire people that have had their failures paid for by previous companies, that is why they require N+ years of experience..."
– gnat
May 8 '15 at 10:11
2
"Senior" is an unbelievably squishy term when it comes to this field. I'm out looking for a new position myself and have run across openings where it means more than two, five, ten or 15 or 20 years. Disregard the title and look at the requirements.
– Blrfl
May 8 '15 at 11:14
@PhilipKendall, If only that were true in all cases. Try working in defence contracting, where education/experience requirements for each engineering 'level' is very specifically laid out.
– James Adam
May 8 '15 at 13:30