Is it reasonable to have multiple senior developers, but no juniors/mid-level developers?Importance (and flexibility) in Job Title Presented in Job-offerHow to title my last programming position?Less senior people are becoming more senior than myselfHow to win a promotion my mentor is interested in?

What happens when an outsider changes alignment?

How much can I change a NY cheesecakes recipe?

What principles should I follow when entering data into a complex relational database?

Life insurance as a lottery ticket

How to add new line between `ls -l` output

Huygens Lander: Why The Short Battery Life?

What are pros and cons around banning castling?

How does a common emitter amplifier work (intuitively)

Does saddle height needs to be changed when crank length changes?

Am I being exploited by my supervisor?

Would I still be able to cast conjure barrage if I was also using flame arrow?

My code seems to be a train wreck

tikz: place a mark on a straight line

One of my friends deposited £42 into my account that he had borrowed previously. Will it affect my UK visa application?

Encrypting email addresses in php

Should high school teachers say “real numbers” before teaching complex numbers?

Feasible explanation to the continued existence of dangerous magical creatures in a modern setting

How to resolve the transporter conundrum in a FTL spaceship?

Can airpod with wrong spelling on the case be original?

How good is Dust Devil?

Is Yoda made using CGI in the original Star Wars or is it practical effects?

Is it a complete sentence: "Caution murmured: it could be a trick, a lure, a trap."?

How much piloting did the Apollo astronauts actually do?

Should I perform my first oil change at 1000 miles, or when the manual says?



Is it reasonable to have multiple senior developers, but no juniors/mid-level developers?


Importance (and flexibility) in Job Title Presented in Job-offerHow to title my last programming position?Less senior people are becoming more senior than myselfHow to win a promotion my mentor is interested in?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









1


















I work in a company with 2 other developers. We typically don't work as a team, just independently on various projects. One developer has been here for 20 years and the other for 7. They both have the title of Senior Software Engineer.



I have been at this company for almost 3 years and have had 2 developer jobs prior to that, for a total of around 6 or 7 years of experience, and my own job title is just "Software Engineer". If I'm honest, I do look to these other two developers for guidance, but not actually in software development. I mainly ask questions about our specific systems since much of it is legacy stuff with little documentation. That being said, I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.



I enjoy my job, but due to the company being small, there isn't a lot of upward mobility. I can't have direct reports under me because there are no other developers. Would it be a strange request if I asked for a promotion, which would make the company have 3 "senior" developers with no mid-level/juniors. Or would I most likely be better off seeking out a larger company where I can have more responsibility?










share|improve this question

























  • What does "senior" mean? Is it related to "seniority" (as in years of experience) or do the junior developers report to the senior developers?

    – Juliana Karasawa Souza
    Oct 17 at 15:13











  • @JulianaKarasawaSouza In this case, I don't believe it's related to having direct reports because I was the first new developer for a long time prior to me joining this company. I think it's a combination of skill level and years of experience. Neither senior developer has any reports. I report directly to the CEO.

    – Jared
    Oct 17 at 15:16











  • It's hard to answer this question, because what a given title means (or what it takes to "earn" a title) is somewhat company-specific. If a company has a perception of what senior means, and all the work they're getting is legitimately senior-level - then sure, it makes perfect sense to only have senior developers.

    – dwizum
    Oct 17 at 15:31






  • 1





    @Bilkokuya Yes. All of us work directly with clients.

    – Jared
    Oct 17 at 15:32











  • If you want a pay increase. Don't be afraid to ask for both a pay increase. Asking for a better title sounds to me like you're afraid to ask for what you really want.

    – Stephan Branczyk
    Oct 19 at 6:31

















1


















I work in a company with 2 other developers. We typically don't work as a team, just independently on various projects. One developer has been here for 20 years and the other for 7. They both have the title of Senior Software Engineer.



I have been at this company for almost 3 years and have had 2 developer jobs prior to that, for a total of around 6 or 7 years of experience, and my own job title is just "Software Engineer". If I'm honest, I do look to these other two developers for guidance, but not actually in software development. I mainly ask questions about our specific systems since much of it is legacy stuff with little documentation. That being said, I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.



I enjoy my job, but due to the company being small, there isn't a lot of upward mobility. I can't have direct reports under me because there are no other developers. Would it be a strange request if I asked for a promotion, which would make the company have 3 "senior" developers with no mid-level/juniors. Or would I most likely be better off seeking out a larger company where I can have more responsibility?










share|improve this question

























  • What does "senior" mean? Is it related to "seniority" (as in years of experience) or do the junior developers report to the senior developers?

    – Juliana Karasawa Souza
    Oct 17 at 15:13











  • @JulianaKarasawaSouza In this case, I don't believe it's related to having direct reports because I was the first new developer for a long time prior to me joining this company. I think it's a combination of skill level and years of experience. Neither senior developer has any reports. I report directly to the CEO.

    – Jared
    Oct 17 at 15:16











  • It's hard to answer this question, because what a given title means (or what it takes to "earn" a title) is somewhat company-specific. If a company has a perception of what senior means, and all the work they're getting is legitimately senior-level - then sure, it makes perfect sense to only have senior developers.

    – dwizum
    Oct 17 at 15:31






  • 1





    @Bilkokuya Yes. All of us work directly with clients.

    – Jared
    Oct 17 at 15:32











  • If you want a pay increase. Don't be afraid to ask for both a pay increase. Asking for a better title sounds to me like you're afraid to ask for what you really want.

    – Stephan Branczyk
    Oct 19 at 6:31













1













1









1








I work in a company with 2 other developers. We typically don't work as a team, just independently on various projects. One developer has been here for 20 years and the other for 7. They both have the title of Senior Software Engineer.



I have been at this company for almost 3 years and have had 2 developer jobs prior to that, for a total of around 6 or 7 years of experience, and my own job title is just "Software Engineer". If I'm honest, I do look to these other two developers for guidance, but not actually in software development. I mainly ask questions about our specific systems since much of it is legacy stuff with little documentation. That being said, I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.



I enjoy my job, but due to the company being small, there isn't a lot of upward mobility. I can't have direct reports under me because there are no other developers. Would it be a strange request if I asked for a promotion, which would make the company have 3 "senior" developers with no mid-level/juniors. Or would I most likely be better off seeking out a larger company where I can have more responsibility?










share|improve this question














I work in a company with 2 other developers. We typically don't work as a team, just independently on various projects. One developer has been here for 20 years and the other for 7. They both have the title of Senior Software Engineer.



I have been at this company for almost 3 years and have had 2 developer jobs prior to that, for a total of around 6 or 7 years of experience, and my own job title is just "Software Engineer". If I'm honest, I do look to these other two developers for guidance, but not actually in software development. I mainly ask questions about our specific systems since much of it is legacy stuff with little documentation. That being said, I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.



I enjoy my job, but due to the company being small, there isn't a lot of upward mobility. I can't have direct reports under me because there are no other developers. Would it be a strange request if I asked for a promotion, which would make the company have 3 "senior" developers with no mid-level/juniors. Or would I most likely be better off seeking out a larger company where I can have more responsibility?







negotiation promotion raise






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 17 at 15:07









JaredJared

4271 gold badge2 silver badges5 bronze badges




4271 gold badge2 silver badges5 bronze badges















  • What does "senior" mean? Is it related to "seniority" (as in years of experience) or do the junior developers report to the senior developers?

    – Juliana Karasawa Souza
    Oct 17 at 15:13











  • @JulianaKarasawaSouza In this case, I don't believe it's related to having direct reports because I was the first new developer for a long time prior to me joining this company. I think it's a combination of skill level and years of experience. Neither senior developer has any reports. I report directly to the CEO.

    – Jared
    Oct 17 at 15:16











  • It's hard to answer this question, because what a given title means (or what it takes to "earn" a title) is somewhat company-specific. If a company has a perception of what senior means, and all the work they're getting is legitimately senior-level - then sure, it makes perfect sense to only have senior developers.

    – dwizum
    Oct 17 at 15:31






  • 1





    @Bilkokuya Yes. All of us work directly with clients.

    – Jared
    Oct 17 at 15:32











  • If you want a pay increase. Don't be afraid to ask for both a pay increase. Asking for a better title sounds to me like you're afraid to ask for what you really want.

    – Stephan Branczyk
    Oct 19 at 6:31

















  • What does "senior" mean? Is it related to "seniority" (as in years of experience) or do the junior developers report to the senior developers?

    – Juliana Karasawa Souza
    Oct 17 at 15:13











  • @JulianaKarasawaSouza In this case, I don't believe it's related to having direct reports because I was the first new developer for a long time prior to me joining this company. I think it's a combination of skill level and years of experience. Neither senior developer has any reports. I report directly to the CEO.

    – Jared
    Oct 17 at 15:16











  • It's hard to answer this question, because what a given title means (or what it takes to "earn" a title) is somewhat company-specific. If a company has a perception of what senior means, and all the work they're getting is legitimately senior-level - then sure, it makes perfect sense to only have senior developers.

    – dwizum
    Oct 17 at 15:31






  • 1





    @Bilkokuya Yes. All of us work directly with clients.

    – Jared
    Oct 17 at 15:32











  • If you want a pay increase. Don't be afraid to ask for both a pay increase. Asking for a better title sounds to me like you're afraid to ask for what you really want.

    – Stephan Branczyk
    Oct 19 at 6:31
















What does "senior" mean? Is it related to "seniority" (as in years of experience) or do the junior developers report to the senior developers?

– Juliana Karasawa Souza
Oct 17 at 15:13





What does "senior" mean? Is it related to "seniority" (as in years of experience) or do the junior developers report to the senior developers?

– Juliana Karasawa Souza
Oct 17 at 15:13













@JulianaKarasawaSouza In this case, I don't believe it's related to having direct reports because I was the first new developer for a long time prior to me joining this company. I think it's a combination of skill level and years of experience. Neither senior developer has any reports. I report directly to the CEO.

– Jared
Oct 17 at 15:16





@JulianaKarasawaSouza In this case, I don't believe it's related to having direct reports because I was the first new developer for a long time prior to me joining this company. I think it's a combination of skill level and years of experience. Neither senior developer has any reports. I report directly to the CEO.

– Jared
Oct 17 at 15:16













It's hard to answer this question, because what a given title means (or what it takes to "earn" a title) is somewhat company-specific. If a company has a perception of what senior means, and all the work they're getting is legitimately senior-level - then sure, it makes perfect sense to only have senior developers.

– dwizum
Oct 17 at 15:31





It's hard to answer this question, because what a given title means (or what it takes to "earn" a title) is somewhat company-specific. If a company has a perception of what senior means, and all the work they're getting is legitimately senior-level - then sure, it makes perfect sense to only have senior developers.

– dwizum
Oct 17 at 15:31




1




1





@Bilkokuya Yes. All of us work directly with clients.

– Jared
Oct 17 at 15:32





@Bilkokuya Yes. All of us work directly with clients.

– Jared
Oct 17 at 15:32













If you want a pay increase. Don't be afraid to ask for both a pay increase. Asking for a better title sounds to me like you're afraid to ask for what you really want.

– Stephan Branczyk
Oct 19 at 6:31





If you want a pay increase. Don't be afraid to ask for both a pay increase. Asking for a better title sounds to me like you're afraid to ask for what you really want.

– Stephan Branczyk
Oct 19 at 6:31










2 Answers
2






active

oldest

votes


















5




















Is it reasonable




It's just a job title. The company can give any title they want. I once worked in a place where every single person in the engineering department was a senior engineer, including the guy who drove us to sites and 2 guys with no qualifications at all.




I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.




Ask the boss, in practical terms it makes no difference to your role, so might be fine, unless there is a pay increase that goes with it. In which case there's still no harm asking, at least you will have information to make decisions with going forwards.






share|improve this answer




















  • 1





    I heard of a place that called their receptionist an "Executive Assistant".

    – Nelson
    Oct 18 at 3:13


















1



















According to the information provided, the titles are not linked to your position in the hierarchy, but to years of experience and technical expertise. There are also no department / reporting lines, since you report stright to the CEO.



This means that there is no organizational reason for having a ratio of junior x senior developers. There might be a monetary reason (a.k.a. "not in the budget")



That being said, you have 2 courses of action:



Stay in your current organization and apply for promotion



Understand what are the criteria for being elegible for a Senior Software Engineer position and what is the difference in scope of work between your Software Engineer position and the Senior Software Engineer.



Make an assessment on whether or not you meet the criteria and whether or not you can / will handle the different scope of work (if any). Set a personal target date for the eventual promotion to happen.



Talk to your boss about your intentions and to scout if there is a monetary reason behind this difference in titles, and whether or not they're willing to back your promotion. Understand if your boss' plans meet your target and the reason if don't.



Leave your organization



As you mentioned, your organization is quite flat for the moment, so there are not many positions with people leader responsibility. If you want to lead a team and have a different type of responsibility, you should look for another job unless there is a plan in the foreseeable future to expand the organization and create team lead type of positions that meets your personal timetable.



You should also be thinking about looking somewhere else if your boss' plan does not meet your personal target for promotion without a reasonable justification.






share|improve this answer




















  • 1





    Something to consider: The OP could interweave both actions - apply for promotion and get the 'senior' in front of his current title, hang around for a while (6-12 months) and then apply for a new job where he's actually getting a team to lead with the benefit of having the 'Senior Software Engineer' title already and the prospects of an increased compensation..

    – iLuvLogix
    Oct 17 at 16:41












  • @iLuvLogix yeah, that's the "set a personal timetable" part that connects the last sentence of both action plans :)

    – Juliana Karasawa Souza
    Oct 18 at 14:03












Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "423"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);














draft saved

draft discarded
















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f146633%2fis-it-reasonable-to-have-multiple-senior-developers-but-no-juniors-mid-level-de%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown


























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









5




















Is it reasonable




It's just a job title. The company can give any title they want. I once worked in a place where every single person in the engineering department was a senior engineer, including the guy who drove us to sites and 2 guys with no qualifications at all.




I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.




Ask the boss, in practical terms it makes no difference to your role, so might be fine, unless there is a pay increase that goes with it. In which case there's still no harm asking, at least you will have information to make decisions with going forwards.






share|improve this answer




















  • 1





    I heard of a place that called their receptionist an "Executive Assistant".

    – Nelson
    Oct 18 at 3:13















5




















Is it reasonable




It's just a job title. The company can give any title they want. I once worked in a place where every single person in the engineering department was a senior engineer, including the guy who drove us to sites and 2 guys with no qualifications at all.




I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.




Ask the boss, in practical terms it makes no difference to your role, so might be fine, unless there is a pay increase that goes with it. In which case there's still no harm asking, at least you will have information to make decisions with going forwards.






share|improve this answer




















  • 1





    I heard of a place that called their receptionist an "Executive Assistant".

    – Nelson
    Oct 18 at 3:13













5















5











5










Is it reasonable




It's just a job title. The company can give any title they want. I once worked in a place where every single person in the engineering department was a senior engineer, including the guy who drove us to sites and 2 guys with no qualifications at all.




I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.




Ask the boss, in practical terms it makes no difference to your role, so might be fine, unless there is a pay increase that goes with it. In which case there's still no harm asking, at least you will have information to make decisions with going forwards.






share|improve this answer















Is it reasonable




It's just a job title. The company can give any title they want. I once worked in a place where every single person in the engineering department was a senior engineer, including the guy who drove us to sites and 2 guys with no qualifications at all.




I'd like the title of Senior Software Engineer for my resume, future job prospects, and maybe a pay increase.




Ask the boss, in practical terms it makes no difference to your role, so might be fine, unless there is a pay increase that goes with it. In which case there's still no harm asking, at least you will have information to make decisions with going forwards.







share|improve this answer













share|improve this answer




share|improve this answer










answered Oct 17 at 18:26









KilisiKilisi

133k78 gold badges307 silver badges513 bronze badges




133k78 gold badges307 silver badges513 bronze badges










  • 1





    I heard of a place that called their receptionist an "Executive Assistant".

    – Nelson
    Oct 18 at 3:13












  • 1





    I heard of a place that called their receptionist an "Executive Assistant".

    – Nelson
    Oct 18 at 3:13







1




1





I heard of a place that called their receptionist an "Executive Assistant".

– Nelson
Oct 18 at 3:13





I heard of a place that called their receptionist an "Executive Assistant".

– Nelson
Oct 18 at 3:13













1



















According to the information provided, the titles are not linked to your position in the hierarchy, but to years of experience and technical expertise. There are also no department / reporting lines, since you report stright to the CEO.



This means that there is no organizational reason for having a ratio of junior x senior developers. There might be a monetary reason (a.k.a. "not in the budget")



That being said, you have 2 courses of action:



Stay in your current organization and apply for promotion



Understand what are the criteria for being elegible for a Senior Software Engineer position and what is the difference in scope of work between your Software Engineer position and the Senior Software Engineer.



Make an assessment on whether or not you meet the criteria and whether or not you can / will handle the different scope of work (if any). Set a personal target date for the eventual promotion to happen.



Talk to your boss about your intentions and to scout if there is a monetary reason behind this difference in titles, and whether or not they're willing to back your promotion. Understand if your boss' plans meet your target and the reason if don't.



Leave your organization



As you mentioned, your organization is quite flat for the moment, so there are not many positions with people leader responsibility. If you want to lead a team and have a different type of responsibility, you should look for another job unless there is a plan in the foreseeable future to expand the organization and create team lead type of positions that meets your personal timetable.



You should also be thinking about looking somewhere else if your boss' plan does not meet your personal target for promotion without a reasonable justification.






share|improve this answer




















  • 1





    Something to consider: The OP could interweave both actions - apply for promotion and get the 'senior' in front of his current title, hang around for a while (6-12 months) and then apply for a new job where he's actually getting a team to lead with the benefit of having the 'Senior Software Engineer' title already and the prospects of an increased compensation..

    – iLuvLogix
    Oct 17 at 16:41












  • @iLuvLogix yeah, that's the "set a personal timetable" part that connects the last sentence of both action plans :)

    – Juliana Karasawa Souza
    Oct 18 at 14:03















1



















According to the information provided, the titles are not linked to your position in the hierarchy, but to years of experience and technical expertise. There are also no department / reporting lines, since you report stright to the CEO.



This means that there is no organizational reason for having a ratio of junior x senior developers. There might be a monetary reason (a.k.a. "not in the budget")



That being said, you have 2 courses of action:



Stay in your current organization and apply for promotion



Understand what are the criteria for being elegible for a Senior Software Engineer position and what is the difference in scope of work between your Software Engineer position and the Senior Software Engineer.



Make an assessment on whether or not you meet the criteria and whether or not you can / will handle the different scope of work (if any). Set a personal target date for the eventual promotion to happen.



Talk to your boss about your intentions and to scout if there is a monetary reason behind this difference in titles, and whether or not they're willing to back your promotion. Understand if your boss' plans meet your target and the reason if don't.



Leave your organization



As you mentioned, your organization is quite flat for the moment, so there are not many positions with people leader responsibility. If you want to lead a team and have a different type of responsibility, you should look for another job unless there is a plan in the foreseeable future to expand the organization and create team lead type of positions that meets your personal timetable.



You should also be thinking about looking somewhere else if your boss' plan does not meet your personal target for promotion without a reasonable justification.






share|improve this answer




















  • 1





    Something to consider: The OP could interweave both actions - apply for promotion and get the 'senior' in front of his current title, hang around for a while (6-12 months) and then apply for a new job where he's actually getting a team to lead with the benefit of having the 'Senior Software Engineer' title already and the prospects of an increased compensation..

    – iLuvLogix
    Oct 17 at 16:41












  • @iLuvLogix yeah, that's the "set a personal timetable" part that connects the last sentence of both action plans :)

    – Juliana Karasawa Souza
    Oct 18 at 14:03













1















1











1









According to the information provided, the titles are not linked to your position in the hierarchy, but to years of experience and technical expertise. There are also no department / reporting lines, since you report stright to the CEO.



This means that there is no organizational reason for having a ratio of junior x senior developers. There might be a monetary reason (a.k.a. "not in the budget")



That being said, you have 2 courses of action:



Stay in your current organization and apply for promotion



Understand what are the criteria for being elegible for a Senior Software Engineer position and what is the difference in scope of work between your Software Engineer position and the Senior Software Engineer.



Make an assessment on whether or not you meet the criteria and whether or not you can / will handle the different scope of work (if any). Set a personal target date for the eventual promotion to happen.



Talk to your boss about your intentions and to scout if there is a monetary reason behind this difference in titles, and whether or not they're willing to back your promotion. Understand if your boss' plans meet your target and the reason if don't.



Leave your organization



As you mentioned, your organization is quite flat for the moment, so there are not many positions with people leader responsibility. If you want to lead a team and have a different type of responsibility, you should look for another job unless there is a plan in the foreseeable future to expand the organization and create team lead type of positions that meets your personal timetable.



You should also be thinking about looking somewhere else if your boss' plan does not meet your personal target for promotion without a reasonable justification.






share|improve this answer














According to the information provided, the titles are not linked to your position in the hierarchy, but to years of experience and technical expertise. There are also no department / reporting lines, since you report stright to the CEO.



This means that there is no organizational reason for having a ratio of junior x senior developers. There might be a monetary reason (a.k.a. "not in the budget")



That being said, you have 2 courses of action:



Stay in your current organization and apply for promotion



Understand what are the criteria for being elegible for a Senior Software Engineer position and what is the difference in scope of work between your Software Engineer position and the Senior Software Engineer.



Make an assessment on whether or not you meet the criteria and whether or not you can / will handle the different scope of work (if any). Set a personal target date for the eventual promotion to happen.



Talk to your boss about your intentions and to scout if there is a monetary reason behind this difference in titles, and whether or not they're willing to back your promotion. Understand if your boss' plans meet your target and the reason if don't.



Leave your organization



As you mentioned, your organization is quite flat for the moment, so there are not many positions with people leader responsibility. If you want to lead a team and have a different type of responsibility, you should look for another job unless there is a plan in the foreseeable future to expand the organization and create team lead type of positions that meets your personal timetable.



You should also be thinking about looking somewhere else if your boss' plan does not meet your personal target for promotion without a reasonable justification.







share|improve this answer













share|improve this answer




share|improve this answer










answered Oct 17 at 15:31









Juliana Karasawa SouzaJuliana Karasawa Souza

1,0445 silver badges14 bronze badges




1,0445 silver badges14 bronze badges










  • 1





    Something to consider: The OP could interweave both actions - apply for promotion and get the 'senior' in front of his current title, hang around for a while (6-12 months) and then apply for a new job where he's actually getting a team to lead with the benefit of having the 'Senior Software Engineer' title already and the prospects of an increased compensation..

    – iLuvLogix
    Oct 17 at 16:41












  • @iLuvLogix yeah, that's the "set a personal timetable" part that connects the last sentence of both action plans :)

    – Juliana Karasawa Souza
    Oct 18 at 14:03












  • 1





    Something to consider: The OP could interweave both actions - apply for promotion and get the 'senior' in front of his current title, hang around for a while (6-12 months) and then apply for a new job where he's actually getting a team to lead with the benefit of having the 'Senior Software Engineer' title already and the prospects of an increased compensation..

    – iLuvLogix
    Oct 17 at 16:41












  • @iLuvLogix yeah, that's the "set a personal timetable" part that connects the last sentence of both action plans :)

    – Juliana Karasawa Souza
    Oct 18 at 14:03







1




1





Something to consider: The OP could interweave both actions - apply for promotion and get the 'senior' in front of his current title, hang around for a while (6-12 months) and then apply for a new job where he's actually getting a team to lead with the benefit of having the 'Senior Software Engineer' title already and the prospects of an increased compensation..

– iLuvLogix
Oct 17 at 16:41






Something to consider: The OP could interweave both actions - apply for promotion and get the 'senior' in front of his current title, hang around for a while (6-12 months) and then apply for a new job where he's actually getting a team to lead with the benefit of having the 'Senior Software Engineer' title already and the prospects of an increased compensation..

– iLuvLogix
Oct 17 at 16:41














@iLuvLogix yeah, that's the "set a personal timetable" part that connects the last sentence of both action plans :)

– Juliana Karasawa Souza
Oct 18 at 14:03





@iLuvLogix yeah, that's the "set a personal timetable" part that connects the last sentence of both action plans :)

– Juliana Karasawa Souza
Oct 18 at 14:03


















draft saved

draft discarded















































Thanks for contributing an answer to The Workplace Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f146633%2fis-it-reasonable-to-have-multiple-senior-developers-but-no-juniors-mid-level-de%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown









Popular posts from this blog

Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

199年 目錄 大件事 到箇年出世嗰人 到箇年死嗰人 節慶、風俗習慣 導覽選單