Mixing
Pressured into doing a role I despise [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
I used to be a developer, which I did for 8 years. I started to really resent developing and came to loathe it. Therefore, I gave up that role and decided to retrain and work as DevOps.
My current employer is taking me into meetings almost weekly to pressure (almost harassing) me into working as a developer to help lighten the load of the other developers.
I decline each time stating that I am no longer a developer, and I came here to work as a DevOps. I really do not enjoy development, and developing makes me angry. The employer preaches that I do not have the company's best interests at heart.
So my real question is: How do I best handle this? Should I suck it up and just do what they want me to do, and feel like crap every day I am doing it.
Or do I continue to fight my corner, and if so, what would be the most reasonable way to present my thoughts?
team-role
edited Jul 8 '15 at 11:32
Jane S♦
40.8k17125159
asked Jul 8 '15 at 2:59
jshthornton
1116
closed as off-topic by gnat, user8365, Philipp, Roger, scaaahu Jul 9 '15 at 11:18
This question appears to be off-topic. The users who voted to close gave these specific reasons:
- "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." – Philipp, Roger, scaaahu
- "Real questions have answers. Rather than explaining why your situation is terrible, or why your boss/coworker makes you unhappy, explain what you want to do to make it better. For more information, click here." – gnat, Community
 |Â
show 7 more comments
up vote
1
down vote
favorite
I used to be a developer, which I did for 8 years. I started to really resent developing and came to loathe it. Therefore, I gave up that role and decided to retrain and work as DevOps.
My current employer is taking me into meetings almost weekly to pressure (almost harassing) me into working as a developer to help lighten the load of the other developers.
I decline each time stating that I am no longer a developer, and I came here to work as a DevOps. I really do not enjoy development, and developing makes me angry. The employer preaches that I do not have the company's best interests at heart.
So my real question is: How do I best handle this? Should I suck it up and just do what they want me to do, and feel like crap every day I am doing it.
Or do I continue to fight my corner, and if so, what would be the most reasonable way to present my thoughts?
team-role
edited Jul 8 '15 at 11:32
Jane S♦
40.8k17125159
asked Jul 8 '15 at 2:59
jshthornton
1116
closed as off-topic by gnat, user8365, Philipp, Roger, scaaahu Jul 9 '15 at 11:18
This question appears to be off-topic. The users who voted to close gave these specific reasons:
- "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." – Philipp, Roger, scaaahu
- "Real questions have answers. Rather than explaining why your situation is terrible, or why your boss/coworker makes you unhappy, explain what you want to do to make it better. For more information, click here." – gnat, Community
6
Well, the employer is correct. You put your own interests above the companies. Just like every employee they have ever hired. Do you have a specific question we could answer?
– nvoigt
Jul 8 '15 at 3:34
@nvoigt I have updated the question... to be a question.
– jshthornton
Jul 8 '15 at 4:01
4
You have missed the third option: you can quit.
– Dale M
Jul 8 '15 at 4:35
@DaleM Yes I could quit. But I do not think that is a viable option. I enjoy my work, I enjoy the people. This is literally the only gripe I have.
– jshthornton
Jul 8 '15 at 4:43
1
@LieRyan I outlined that I hate development (the bit they are pressuring me into doing) but love the current role (DevOps).
– jshthornton
Jul 8 '15 at 5:33
 |Â
show 7 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I used to be a developer, which I did for 8 years. I started to really resent developing and came to loathe it. Therefore, I gave up that role and decided to retrain and work as DevOps.
My current employer is taking me into meetings almost weekly to pressure (almost harassing) me into working as a developer to help lighten the load of the other developers.
I decline each time stating that I am no longer a developer, and I came here to work as a DevOps. I really do not enjoy development, and developing makes me angry. The employer preaches that I do not have the company's best interests at heart.
So my real question is: How do I best handle this? Should I suck it up and just do what they want me to do, and feel like crap every day I am doing it.
Or do I continue to fight my corner, and if so, what would be the most reasonable way to present my thoughts?
team-role
edited Jul 8 '15 at 11:32
Jane S♦
40.8k17125159
asked Jul 8 '15 at 2:59
jshthornton
1116
I used to be a developer, which I did for 8 years. I started to really resent developing and came to loathe it. Therefore, I gave up that role and decided to retrain and work as DevOps.
My current employer is taking me into meetings almost weekly to pressure (almost harassing) me into working as a developer to help lighten the load of the other developers.
I decline each time stating that I am no longer a developer, and I came here to work as a DevOps. I really do not enjoy development, and developing makes me angry. The employer preaches that I do not have the company's best interests at heart.
So my real question is: How do I best handle this? Should I suck it up and just do what they want me to do, and feel like crap every day I am doing it.
Or do I continue to fight my corner, and if so, what would be the most reasonable way to present my thoughts?
team-role
edited Jul 8 '15 at 11:32
Jane S♦
40.8k17125159
asked Jul 8 '15 at 2:59
jshthornton
1116
edited Jul 8 '15 at 11:32
Jane S♦
40.8k17125159
edited Jul 8 '15 at 11:32
Jane S♦
40.8k17125159
edited Jul 8 '15 at 11:32
Jane S♦
40.8k17125159
40.8k17125159
asked Jul 8 '15 at 2:59
jshthornton
1116
asked Jul 8 '15 at 2:59
jshthornton
1116
asked Jul 8 '15 at 2:59
jshthornton
1116
1116
closed as off-topic by gnat, user8365, Philipp, Roger, scaaahu Jul 9 '15 at 11:18
This question appears to be off-topic. The users who voted to close gave these specific reasons:
- "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." – Philipp, Roger, scaaahu
- "Real questions have answers. Rather than explaining why your situation is terrible, or why your boss/coworker makes you unhappy, explain what you want to do to make it better. For more information, click here." – gnat, Community
closed as off-topic by gnat, user8365, Philipp, Roger, scaaahu Jul 9 '15 at 11:18
This question appears to be off-topic. The users who voted to close gave these specific reasons:
- "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." – Philipp, Roger, scaaahu
- "Real questions have answers. Rather than explaining why your situation is terrible, or why your boss/coworker makes you unhappy, explain what you want to do to make it better. For more information, click here." – gnat, Community
6
Well, the employer is correct. You put your own interests above the companies. Just like every employee they have ever hired. Do you have a specific question we could answer?
– nvoigt
Jul 8 '15 at 3:34
@nvoigt I have updated the question... to be a question.
– jshthornton
Jul 8 '15 at 4:01
4
You have missed the third option: you can quit.
– Dale M
Jul 8 '15 at 4:35
@DaleM Yes I could quit. But I do not think that is a viable option. I enjoy my work, I enjoy the people. This is literally the only gripe I have.
– jshthornton
Jul 8 '15 at 4:43
1
@LieRyan I outlined that I hate development (the bit they are pressuring me into doing) but love the current role (DevOps).
– jshthornton
Jul 8 '15 at 5:33
 |Â
show 7 more comments
6
Well, the employer is correct. You put your own interests above the companies. Just like every employee they have ever hired. Do you have a specific question we could answer?
– nvoigt
Jul 8 '15 at 3:34
@nvoigt I have updated the question... to be a question.
– jshthornton
Jul 8 '15 at 4:01
4
You have missed the third option: you can quit.
– Dale M
Jul 8 '15 at 4:35
@DaleM Yes I could quit. But I do not think that is a viable option. I enjoy my work, I enjoy the people. This is literally the only gripe I have.
– jshthornton
Jul 8 '15 at 4:43
1
@LieRyan I outlined that I hate development (the bit they are pressuring me into doing) but love the current role (DevOps).
– jshthornton
Jul 8 '15 at 5:33
6
6
Well, the employer is correct. You put your own interests above the companies. Just like every employee they have ever hired. Do you have a specific question we could answer?
– nvoigt
Jul 8 '15 at 3:34
Well, the employer is correct. You put your own interests above the companies. Just like every employee they have ever hired. Do you have a specific question we could answer?
– nvoigt
Jul 8 '15 at 3:34
@nvoigt I have updated the question... to be a question.
– jshthornton
Jul 8 '15 at 4:01
@nvoigt I have updated the question... to be a question.
– jshthornton
Jul 8 '15 at 4:01
4
4
You have missed the third option: you can quit.
– Dale M
Jul 8 '15 at 4:35
You have missed the third option: you can quit.
– Dale M
Jul 8 '15 at 4:35
@DaleM Yes I could quit. But I do not think that is a viable option. I enjoy my work, I enjoy the people. This is literally the only gripe I have.
– jshthornton
Jul 8 '15 at 4:43
@DaleM Yes I could quit. But I do not think that is a viable option. I enjoy my work, I enjoy the people. This is literally the only gripe I have.
– jshthornton
Jul 8 '15 at 4:43
1
1
@LieRyan I outlined that I hate development (the bit they are pressuring me into doing) but love the current role (DevOps).
– jshthornton
Jul 8 '15 at 5:33
@LieRyan I outlined that I hate development (the bit they are pressuring me into doing) but love the current role (DevOps).
– jshthornton
Jul 8 '15 at 5:33
 |Â
show 7 more comments
5 Answers
5
active
oldest
votes
up vote
9
down vote
accepted
See other recent questions about being assigned work outside your original scope. Your job -- meaning what you will be evaluated on -- is whatever management tells you to do. If you have a formal written set of goals for the year that they have said you will be evaluated on, you can protest that other work interferes with those, but that's likely to just result in your assignment being officially rewritten.
In the end, if the request is at all reasonable, you can either pitch in, be evaluated as "not a team player", or really be not a team player and threaten to quit. Don't threaten unless you consider that an acceptable outcome.
Your best bet here might have been to have said "it isn't a job I like doing, but if I'm really needed I'll pitch in -- with the understanding that it's only for N weeks, and that this is a sacrifice for me and i'd like the extra effort reflected at year-end review time." You'd be doing development, but your boss would see you as being willing to make an extra effort when needed rather than as a "not my problem" slacker.
edited Jul 8 '15 at 5:44
panoptical
3,5761538
answered Jul 8 '15 at 3:47
keshlam
41.5k1267144
suggest improvements |Â
up vote
4
down vote
In many companies, predominantly small and medium sized, the boundary between development and devops is blurry - particularly if you take "development" to mean "any coding activity at all". An employer who sees someone in a devops role who is capable and not 100% utilised, but refuses to help out to the point where he has to go out and hire more developers instead, is going to see you as a liability. So your current course is going to be career-limiting, if not career-ending.
You could quit and find a large company that maintains strict siloing of work. Alternatively you could - and should anyway - take some time to actually understand yourself better and understand why development brings out anger, resentment and "feeling like crap" in you. Especially as you profess to love a closely related field. Is it development itself, or the individuals doing development at your company? You may not like dev work, fine, many don't, but it sounds like an irrationally strong reaction. I would certainly not recommend just "sucking it up" without a decent amount of introspection as it won't solve the underlying problem.
answered Jul 8 '15 at 7:55
Julia Hayward
12k53438
suggest improvements |Â
up vote
3
down vote
So my real question is. How do I best handle this. Should I suck it up
and just do what they want me to do, and feel like crap every day I am
doing it.
Or do I continue to fight my corner, and if so, what would be the most
reasonable way to present my thoughts.
I hope when you "decline each time" you have explained to your boss that you really don't want to be a developer.
Your best bet is to sit down with your boss (perhaps during a weekly one-on-one meeting), and explain how you really dislike developing, and that you were specifically hired as DevOps for that reason. Then you could ask "Is there some way we can lighten the load on the developers that doesn't require me to also do development?"
If your boss still insists that you must develop, then you will need to decide if this is the right company/job for you, or not - then act accordingly.
answered Jul 8 '15 at 10:46
Joe Strazzere
223k106656922
suggest improvements |Â
up vote
1
down vote
The right thing to do would be to say "I will pitch in until required but you will have to hire someone else quickly because such and such job makes the work I was hired to do suffer." That way you won't seem like you don't care about the company.
You could always quit if the situation doesn't change or gets worse in 1 year.
But saying no to work...whatever it may be is not the right way to go. You maybe hired for one reason but it is understood that you will do whatever it takes when your company is in need.
While liking what you do is important, there will always be a few things in your job that you dislike doing but still have to.
answered Jul 8 '15 at 8:01
Niyati
273
suggest improvements |Â
up vote
1
down vote
If you have a full-time job, and now they want you to do something else, something doesn't add up.
- Will someone else be doing your devops work?
- Is there not enough devops work for you to do on a full-time basis?
- Will you have to do both, i.e. work additional hours?
If you're required to work more hours, you should ask for more money. You may find yourself out of a job if there isn't enough for you to do or they have other people who can.
Can you work something out, so that there is an agreed upon limit to how long you'll need to do this. Sometimes it's easier to fight through something you don't like when you know there is an end in sight.
suggest improvements |Â
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
9
down vote
accepted
See other recent questions about being assigned work outside your original scope. Your job -- meaning what you will be evaluated on -- is whatever management tells you to do. If you have a formal written set of goals for the year that they have said you will be evaluated on, you can protest that other work interferes with those, but that's likely to just result in your assignment being officially rewritten.
In the end, if the request is at all reasonable, you can either pitch in, be evaluated as "not a team player", or really be not a team player and threaten to quit. Don't threaten unless you consider that an acceptable outcome.
Your best bet here might have been to have said "it isn't a job I like doing, but if I'm really needed I'll pitch in -- with the understanding that it's only for N weeks, and that this is a sacrifice for me and i'd like the extra effort reflected at year-end review time." You'd be doing development, but your boss would see you as being willing to make an extra effort when needed rather than as a "not my problem" slacker.
edited Jul 8 '15 at 5:44
panoptical
3,5761538
answered Jul 8 '15 at 3:47
keshlam
41.5k1267144
suggest improvements |Â
up vote
9
down vote
accepted
See other recent questions about being assigned work outside your original scope. Your job -- meaning what you will be evaluated on -- is whatever management tells you to do. If you have a formal written set of goals for the year that they have said you will be evaluated on, you can protest that other work interferes with those, but that's likely to just result in your assignment being officially rewritten.
In the end, if the request is at all reasonable, you can either pitch in, be evaluated as "not a team player", or really be not a team player and threaten to quit. Don't threaten unless you consider that an acceptable outcome.
Your best bet here might have been to have said "it isn't a job I like doing, but if I'm really needed I'll pitch in -- with the understanding that it's only for N weeks, and that this is a sacrifice for me and i'd like the extra effort reflected at year-end review time." You'd be doing development, but your boss would see you as being willing to make an extra effort when needed rather than as a "not my problem" slacker.
edited Jul 8 '15 at 5:44
panoptical
3,5761538
answered Jul 8 '15 at 3:47
keshlam
41.5k1267144
suggest improvements |Â
up vote
9
down vote
accepted
up vote
9
down vote
accepted
See other recent questions about being assigned work outside your original scope. Your job -- meaning what you will be evaluated on -- is whatever management tells you to do. If you have a formal written set of goals for the year that they have said you will be evaluated on, you can protest that other work interferes with those, but that's likely to just result in your assignment being officially rewritten.
In the end, if the request is at all reasonable, you can either pitch in, be evaluated as "not a team player", or really be not a team player and threaten to quit. Don't threaten unless you consider that an acceptable outcome.
Your best bet here might have been to have said "it isn't a job I like doing, but if I'm really needed I'll pitch in -- with the understanding that it's only for N weeks, and that this is a sacrifice for me and i'd like the extra effort reflected at year-end review time." You'd be doing development, but your boss would see you as being willing to make an extra effort when needed rather than as a "not my problem" slacker.
edited Jul 8 '15 at 5:44
panoptical
3,5761538
answered Jul 8 '15 at 3:47
keshlam
41.5k1267144
See other recent questions about being assigned work outside your original scope. Your job -- meaning what you will be evaluated on -- is whatever management tells you to do. If you have a formal written set of goals for the year that they have said you will be evaluated on, you can protest that other work interferes with those, but that's likely to just result in your assignment being officially rewritten.
In the end, if the request is at all reasonable, you can either pitch in, be evaluated as "not a team player", or really be not a team player and threaten to quit. Don't threaten unless you consider that an acceptable outcome.
Your best bet here might have been to have said "it isn't a job I like doing, but if I'm really needed I'll pitch in -- with the understanding that it's only for N weeks, and that this is a sacrifice for me and i'd like the extra effort reflected at year-end review time." You'd be doing development, but your boss would see you as being willing to make an extra effort when needed rather than as a "not my problem" slacker.
edited Jul 8 '15 at 5:44
panoptical
3,5761538
answered Jul 8 '15 at 3:47
keshlam
41.5k1267144
edited Jul 8 '15 at 5:44
panoptical
3,5761538
edited Jul 8 '15 at 5:44
panoptical
3,5761538
edited Jul 8 '15 at 5:44
panoptical
3,5761538
3,5761538
answered Jul 8 '15 at 3:47
keshlam
41.5k1267144
answered Jul 8 '15 at 3:47
keshlam
41.5k1267144
answered Jul 8 '15 at 3:47
keshlam
41.5k1267144
41.5k1267144
suggest improvements |Â
suggest improvements |Â
up vote
4
down vote
In many companies, predominantly small and medium sized, the boundary between development and devops is blurry - particularly if you take "development" to mean "any coding activity at all". An employer who sees someone in a devops role who is capable and not 100% utilised, but refuses to help out to the point where he has to go out and hire more developers instead, is going to see you as a liability. So your current course is going to be career-limiting, if not career-ending.
You could quit and find a large company that maintains strict siloing of work. Alternatively you could - and should anyway - take some time to actually understand yourself better and understand why development brings out anger, resentment and "feeling like crap" in you. Especially as you profess to love a closely related field. Is it development itself, or the individuals doing development at your company? You may not like dev work, fine, many don't, but it sounds like an irrationally strong reaction. I would certainly not recommend just "sucking it up" without a decent amount of introspection as it won't solve the underlying problem.
answered Jul 8 '15 at 7:55
Julia Hayward
12k53438
suggest improvements |Â
up vote
4
down vote
In many companies, predominantly small and medium sized, the boundary between development and devops is blurry - particularly if you take "development" to mean "any coding activity at all". An employer who sees someone in a devops role who is capable and not 100% utilised, but refuses to help out to the point where he has to go out and hire more developers instead, is going to see you as a liability. So your current course is going to be career-limiting, if not career-ending.
You could quit and find a large company that maintains strict siloing of work. Alternatively you could - and should anyway - take some time to actually understand yourself better and understand why development brings out anger, resentment and "feeling like crap" in you. Especially as you profess to love a closely related field. Is it development itself, or the individuals doing development at your company? You may not like dev work, fine, many don't, but it sounds like an irrationally strong reaction. I would certainly not recommend just "sucking it up" without a decent amount of introspection as it won't solve the underlying problem.
answered Jul 8 '15 at 7:55
Julia Hayward
12k53438
suggest improvements |Â
up vote
4
down vote
up vote
4
down vote
In many companies, predominantly small and medium sized, the boundary between development and devops is blurry - particularly if you take "development" to mean "any coding activity at all". An employer who sees someone in a devops role who is capable and not 100% utilised, but refuses to help out to the point where he has to go out and hire more developers instead, is going to see you as a liability. So your current course is going to be career-limiting, if not career-ending.
You could quit and find a large company that maintains strict siloing of work. Alternatively you could - and should anyway - take some time to actually understand yourself better and understand why development brings out anger, resentment and "feeling like crap" in you. Especially as you profess to love a closely related field. Is it development itself, or the individuals doing development at your company? You may not like dev work, fine, many don't, but it sounds like an irrationally strong reaction. I would certainly not recommend just "sucking it up" without a decent amount of introspection as it won't solve the underlying problem.
answered Jul 8 '15 at 7:55
Julia Hayward
12k53438
In many companies, predominantly small and medium sized, the boundary between development and devops is blurry - particularly if you take "development" to mean "any coding activity at all". An employer who sees someone in a devops role who is capable and not 100% utilised, but refuses to help out to the point where he has to go out and hire more developers instead, is going to see you as a liability. So your current course is going to be career-limiting, if not career-ending.
You could quit and find a large company that maintains strict siloing of work. Alternatively you could - and should anyway - take some time to actually understand yourself better and understand why development brings out anger, resentment and "feeling like crap" in you. Especially as you profess to love a closely related field. Is it development itself, or the individuals doing development at your company? You may not like dev work, fine, many don't, but it sounds like an irrationally strong reaction. I would certainly not recommend just "sucking it up" without a decent amount of introspection as it won't solve the underlying problem.
answered Jul 8 '15 at 7:55
Julia Hayward
12k53438
answered Jul 8 '15 at 7:55
Julia Hayward
12k53438
answered Jul 8 '15 at 7:55
Julia Hayward
12k53438
answered Jul 8 '15 at 7:55
Julia Hayward
12k53438
12k53438
suggest improvements |Â
suggest improvements |Â
up vote
3
down vote
So my real question is. How do I best handle this. Should I suck it up
and just do what they want me to do, and feel like crap every day I am
doing it.
Or do I continue to fight my corner, and if so, what would be the most
reasonable way to present my thoughts.
I hope when you "decline each time" you have explained to your boss that you really don't want to be a developer.
Your best bet is to sit down with your boss (perhaps during a weekly one-on-one meeting), and explain how you really dislike developing, and that you were specifically hired as DevOps for that reason. Then you could ask "Is there some way we can lighten the load on the developers that doesn't require me to also do development?"
If your boss still insists that you must develop, then you will need to decide if this is the right company/job for you, or not - then act accordingly.
answered Jul 8 '15 at 10:46
Joe Strazzere
223k106656922
suggest improvements |Â
up vote
3
down vote
So my real question is. How do I best handle this. Should I suck it up
and just do what they want me to do, and feel like crap every day I am
doing it.
Or do I continue to fight my corner, and if so, what would be the most
reasonable way to present my thoughts.
I hope when you "decline each time" you have explained to your boss that you really don't want to be a developer.
Your best bet is to sit down with your boss (perhaps during a weekly one-on-one meeting), and explain how you really dislike developing, and that you were specifically hired as DevOps for that reason. Then you could ask "Is there some way we can lighten the load on the developers that doesn't require me to also do development?"
If your boss still insists that you must develop, then you will need to decide if this is the right company/job for you, or not - then act accordingly.
answered Jul 8 '15 at 10:46
Joe Strazzere
223k106656922
suggest improvements |Â
up vote
3
down vote
up vote
3
down vote
So my real question is. How do I best handle this. Should I suck it up
and just do what they want me to do, and feel like crap every day I am
doing it.
Or do I continue to fight my corner, and if so, what would be the most
reasonable way to present my thoughts.
I hope when you "decline each time" you have explained to your boss that you really don't want to be a developer.
Your best bet is to sit down with your boss (perhaps during a weekly one-on-one meeting), and explain how you really dislike developing, and that you were specifically hired as DevOps for that reason. Then you could ask "Is there some way we can lighten the load on the developers that doesn't require me to also do development?"
If your boss still insists that you must develop, then you will need to decide if this is the right company/job for you, or not - then act accordingly.
answered Jul 8 '15 at 10:46
Joe Strazzere
223k106656922
So my real question is. How do I best handle this. Should I suck it up
and just do what they want me to do, and feel like crap every day I am
doing it.
Or do I continue to fight my corner, and if so, what would be the most
reasonable way to present my thoughts.
I hope when you "decline each time" you have explained to your boss that you really don't want to be a developer.
Your best bet is to sit down with your boss (perhaps during a weekly one-on-one meeting), and explain how you really dislike developing, and that you were specifically hired as DevOps for that reason. Then you could ask "Is there some way we can lighten the load on the developers that doesn't require me to also do development?"
If your boss still insists that you must develop, then you will need to decide if this is the right company/job for you, or not - then act accordingly.
answered Jul 8 '15 at 10:46
Joe Strazzere
223k106656922
answered Jul 8 '15 at 10:46
Joe Strazzere
223k106656922
answered Jul 8 '15 at 10:46
Joe Strazzere
223k106656922
answered Jul 8 '15 at 10:46
Joe Strazzere
223k106656922
223k106656922
suggest improvements |Â
suggest improvements |Â
up vote
1
down vote
The right thing to do would be to say "I will pitch in until required but you will have to hire someone else quickly because such and such job makes the work I was hired to do suffer." That way you won't seem like you don't care about the company.
You could always quit if the situation doesn't change or gets worse in 1 year.
But saying no to work...whatever it may be is not the right way to go. You maybe hired for one reason but it is understood that you will do whatever it takes when your company is in need.
While liking what you do is important, there will always be a few things in your job that you dislike doing but still have to.
answered Jul 8 '15 at 8:01
Niyati
273
suggest improvements |Â
up vote
1
down vote
The right thing to do would be to say "I will pitch in until required but you will have to hire someone else quickly because such and such job makes the work I was hired to do suffer." That way you won't seem like you don't care about the company.
You could always quit if the situation doesn't change or gets worse in 1 year.
But saying no to work...whatever it may be is not the right way to go. You maybe hired for one reason but it is understood that you will do whatever it takes when your company is in need.
While liking what you do is important, there will always be a few things in your job that you dislike doing but still have to.
answered Jul 8 '15 at 8:01
Niyati
273
suggest improvements |Â
up vote
1
down vote
up vote
1
down vote
The right thing to do would be to say "I will pitch in until required but you will have to hire someone else quickly because such and such job makes the work I was hired to do suffer." That way you won't seem like you don't care about the company.
You could always quit if the situation doesn't change or gets worse in 1 year.
But saying no to work...whatever it may be is not the right way to go. You maybe hired for one reason but it is understood that you will do whatever it takes when your company is in need.
While liking what you do is important, there will always be a few things in your job that you dislike doing but still have to.
answered Jul 8 '15 at 8:01
Niyati
273
The right thing to do would be to say "I will pitch in until required but you will have to hire someone else quickly because such and such job makes the work I was hired to do suffer." That way you won't seem like you don't care about the company.
You could always quit if the situation doesn't change or gets worse in 1 year.
But saying no to work...whatever it may be is not the right way to go. You maybe hired for one reason but it is understood that you will do whatever it takes when your company is in need.
While liking what you do is important, there will always be a few things in your job that you dislike doing but still have to.
answered Jul 8 '15 at 8:01
Niyati
273
answered Jul 8 '15 at 8:01
Niyati
273
answered Jul 8 '15 at 8:01
Niyati
273
answered Jul 8 '15 at 8:01
Niyati
273
273
suggest improvements |Â
suggest improvements |Â
up vote
1
down vote
If you have a full-time job, and now they want you to do something else, something doesn't add up.
- Will someone else be doing your devops work?
- Is there not enough devops work for you to do on a full-time basis?
- Will you have to do both, i.e. work additional hours?
If you're required to work more hours, you should ask for more money. You may find yourself out of a job if there isn't enough for you to do or they have other people who can.
Can you work something out, so that there is an agreed upon limit to how long you'll need to do this. Sometimes it's easier to fight through something you don't like when you know there is an end in sight.
suggest improvements |Â
up vote
1
down vote
If you have a full-time job, and now they want you to do something else, something doesn't add up.
- Will someone else be doing your devops work?
- Is there not enough devops work for you to do on a full-time basis?
- Will you have to do both, i.e. work additional hours?
If you're required to work more hours, you should ask for more money. You may find yourself out of a job if there isn't enough for you to do or they have other people who can.
Can you work something out, so that there is an agreed upon limit to how long you'll need to do this. Sometimes it's easier to fight through something you don't like when you know there is an end in sight.
suggest improvements |Â
up vote
1
down vote
up vote
1
down vote
If you have a full-time job, and now they want you to do something else, something doesn't add up.
- Will someone else be doing your devops work?
- Is there not enough devops work for you to do on a full-time basis?
- Will you have to do both, i.e. work additional hours?
If you're required to work more hours, you should ask for more money. You may find yourself out of a job if there isn't enough for you to do or they have other people who can.
Can you work something out, so that there is an agreed upon limit to how long you'll need to do this. Sometimes it's easier to fight through something you don't like when you know there is an end in sight.
If you have a full-time job, and now they want you to do something else, something doesn't add up.
- Will someone else be doing your devops work?
- Is there not enough devops work for you to do on a full-time basis?
- Will you have to do both, i.e. work additional hours?
If you're required to work more hours, you should ask for more money. You may find yourself out of a job if there isn't enough for you to do or they have other people who can.
Can you work something out, so that there is an agreed upon limit to how long you'll need to do this. Sometimes it's easier to fight through something you don't like when you know there is an end in sight.
answered Jul 8 '15 at 12:18
user8365
suggest improvements |Â
suggest improvements |Â
6
Well, the employer is correct. You put your own interests above the companies. Just like every employee they have ever hired. Do you have a specific question we could answer?
– nvoigt
Jul 8 '15 at 3:34
@nvoigt I have updated the question... to be a question.
– jshthornton
Jul 8 '15 at 4:01
4
You have missed the third option: you can quit.
– Dale M
Jul 8 '15 at 4:35
@DaleM Yes I could quit. But I do not think that is a viable option. I enjoy my work, I enjoy the people. This is literally the only gripe I have.
– jshthornton
Jul 8 '15 at 4:43
1
@LieRyan I outlined that I hate development (the bit they are pressuring me into doing) but love the current role (DevOps).
– jshthornton
Jul 8 '15 at 5:33