Mixing
In software development, do employers demand more from hourly employees? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
Here in the USA, employees who are software developers are typically paid an annual salary, or less often, an hourly salary. Here, I'm referring to W-2 employees, not contractors.
As well-paid employees, employers expect software developers to deliver the goods.
I would like to ask those of you who have worked under both annual salary and hourly salary pay schedules, does working under one schedule or the other affect expectations from employers? Does it affect the work in any other meaningful way?
My thought is that if I were a hiring manager, for better or for worse, I would look at employees' cost and productivity differently.
software-industry salary
asked Feb 22 '13 at 16:04
Daniel Allen Langdon
35936
closed as not constructive by jcmeloni, Mark Booth, IDrinkandIKnowThings, gnat, JB King Feb 22 '13 at 22:30
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
0
down vote
favorite
Here in the USA, employees who are software developers are typically paid an annual salary, or less often, an hourly salary. Here, I'm referring to W-2 employees, not contractors.
As well-paid employees, employers expect software developers to deliver the goods.
I would like to ask those of you who have worked under both annual salary and hourly salary pay schedules, does working under one schedule or the other affect expectations from employers? Does it affect the work in any other meaningful way?
My thought is that if I were a hiring manager, for better or for worse, I would look at employees' cost and productivity differently.
software-industry salary
asked Feb 22 '13 at 16:04
Daniel Allen Langdon
35936
closed as not constructive by jcmeloni, Mark Booth, IDrinkandIKnowThings, gnat, JB King Feb 22 '13 at 22:30
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.
2
From the FAQ: You should only ask practical, answerable questions based on actual problems that you face. Chatty, open-ended questions diminish the usefulness of our site. If your motivation for asking the question is “I would like to participate in a discussion about ______â€Â, then you should not be asking here.
– IDrinkandIKnowThings
Feb 22 '13 at 19:39
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Here in the USA, employees who are software developers are typically paid an annual salary, or less often, an hourly salary. Here, I'm referring to W-2 employees, not contractors.
As well-paid employees, employers expect software developers to deliver the goods.
I would like to ask those of you who have worked under both annual salary and hourly salary pay schedules, does working under one schedule or the other affect expectations from employers? Does it affect the work in any other meaningful way?
My thought is that if I were a hiring manager, for better or for worse, I would look at employees' cost and productivity differently.
software-industry salary
asked Feb 22 '13 at 16:04
Daniel Allen Langdon
35936
Here in the USA, employees who are software developers are typically paid an annual salary, or less often, an hourly salary. Here, I'm referring to W-2 employees, not contractors.
As well-paid employees, employers expect software developers to deliver the goods.
I would like to ask those of you who have worked under both annual salary and hourly salary pay schedules, does working under one schedule or the other affect expectations from employers? Does it affect the work in any other meaningful way?
My thought is that if I were a hiring manager, for better or for worse, I would look at employees' cost and productivity differently.
software-industry salary
asked Feb 22 '13 at 16:04
Daniel Allen Langdon
35936
asked Feb 22 '13 at 16:04
Daniel Allen Langdon
35936
asked Feb 22 '13 at 16:04
Daniel Allen Langdon
35936
asked Feb 22 '13 at 16:04
Daniel Allen Langdon
35936
35936
closed as not constructive by jcmeloni, Mark Booth, IDrinkandIKnowThings, gnat, JB King Feb 22 '13 at 22:30
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as not constructive by jcmeloni, Mark Booth, IDrinkandIKnowThings, gnat, JB King Feb 22 '13 at 22:30
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.
2
From the FAQ: You should only ask practical, answerable questions based on actual problems that you face. Chatty, open-ended questions diminish the usefulness of our site. If your motivation for asking the question is “I would like to participate in a discussion about ______â€Â, then you should not be asking here.
– IDrinkandIKnowThings
Feb 22 '13 at 19:39
add a comment |Â
2
From the FAQ: You should only ask practical, answerable questions based on actual problems that you face. Chatty, open-ended questions diminish the usefulness of our site. If your motivation for asking the question is “I would like to participate in a discussion about ______â€Â, then you should not be asking here.
– IDrinkandIKnowThings
Feb 22 '13 at 19:39
2
2
From the FAQ: You should only ask practical, answerable questions based on actual problems that you face. Chatty, open-ended questions diminish the usefulness of our site. If your motivation for asking the question is “I would like to participate in a discussion about ______â€Â, then you should not be asking here.
– IDrinkandIKnowThings
Feb 22 '13 at 19:39
From the FAQ: You should only ask practical, answerable questions based on actual problems that you face. Chatty, open-ended questions diminish the usefulness of our site. If your motivation for asking the question is “I would like to participate in a discussion about ______â€Â, then you should not be asking here.
– IDrinkandIKnowThings
Feb 22 '13 at 19:39
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
Most hourly workers get overtime, most companies don't want to pay it, so they don't get asked to work it unless it is actually critical. They have fewer compunctions about asking salaried workers to work more than 40 hours.
answered Feb 22 '13 at 18:23
HLGEM
133k25227489
I have heard this before. I was wondering if employers may be more demanding of hourly employees in terms of what they expect them to accomplish during their hourly work.
– Daniel Allen Langdon
Feb 22 '13 at 21:04
Daniel, I think most managers have no idea who on a team is contributing what in terms of moving a feature or product forward. For instance, one team member may write many features in a short period of time, but they're all buggy and hard to maintain, whereas another team member may be the one who goes in and cleans all that up. Who accomplished more? So I think many managers shy away from making comparisons between team members.
– Amy Blankenship
Feb 23 '13 at 3:00
add a comment |Â
up vote
2
down vote
That is a really difficult question to answer because the answers is simply "it depends." It will vary greatly from company to company, department to department, manager to manager, and even down to the colleague you're sitting next to.
As somebody who has worked as a consultant on both salary and hourly basis, I can be the first to tell you it makes no difference between whether I worked salary or hourly, it all came down to the project manager and the company culture.
You will feel more pressure if you have a crappy project manager (PM), you will feel less pressure if you're working with a PM who knows his/her stuff. Any project manager worth his/her salt will know how to properly estimate development of any given feature and consequences of such features based on their development methodology, historical develvery experience, and team capabilities. Most people forget to allocate enough testing time, and if they do, they don't allocate enough time to fix the problems found during testing. Thus, finding project managers who are aware of these problems are far and few inbetween unfortunatley.
If a reputable company hires you hourly, chances are you're going to end up with a good project manager since they probably have already (accurately) estimated how much time a project will take to complete, and did a cost-benefit analysis and decided to pick you up hourly. In most cases, it means less developmental hurdles than salary actually. However, if a reputable company hires you hourly, and you're finding that you're working overtime constantly, consider looking inwards for a problem.
answered Feb 22 '13 at 21:52
Magnum
1212
I have found the worst estimators are the ones who want a daily hour long meeting with the whole team on a long-term project and then forget to factor all those hours into the estimate. 10 people * 5 hours per week* 26 weeks is a lot of hours to miss in your estimate. This is often the bigger cause than misestimating the testing time.
– HLGEM
Mar 22 '17 at 21:04
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Most hourly workers get overtime, most companies don't want to pay it, so they don't get asked to work it unless it is actually critical. They have fewer compunctions about asking salaried workers to work more than 40 hours.
answered Feb 22 '13 at 18:23
HLGEM
133k25227489
I have heard this before. I was wondering if employers may be more demanding of hourly employees in terms of what they expect them to accomplish during their hourly work.
– Daniel Allen Langdon
Feb 22 '13 at 21:04
Daniel, I think most managers have no idea who on a team is contributing what in terms of moving a feature or product forward. For instance, one team member may write many features in a short period of time, but they're all buggy and hard to maintain, whereas another team member may be the one who goes in and cleans all that up. Who accomplished more? So I think many managers shy away from making comparisons between team members.
– Amy Blankenship
Feb 23 '13 at 3:00
add a comment |Â
up vote
3
down vote
accepted
Most hourly workers get overtime, most companies don't want to pay it, so they don't get asked to work it unless it is actually critical. They have fewer compunctions about asking salaried workers to work more than 40 hours.
answered Feb 22 '13 at 18:23
HLGEM
133k25227489
I have heard this before. I was wondering if employers may be more demanding of hourly employees in terms of what they expect them to accomplish during their hourly work.
– Daniel Allen Langdon
Feb 22 '13 at 21:04
Daniel, I think most managers have no idea who on a team is contributing what in terms of moving a feature or product forward. For instance, one team member may write many features in a short period of time, but they're all buggy and hard to maintain, whereas another team member may be the one who goes in and cleans all that up. Who accomplished more? So I think many managers shy away from making comparisons between team members.
– Amy Blankenship
Feb 23 '13 at 3:00
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Most hourly workers get overtime, most companies don't want to pay it, so they don't get asked to work it unless it is actually critical. They have fewer compunctions about asking salaried workers to work more than 40 hours.
answered Feb 22 '13 at 18:23
HLGEM
133k25227489
Most hourly workers get overtime, most companies don't want to pay it, so they don't get asked to work it unless it is actually critical. They have fewer compunctions about asking salaried workers to work more than 40 hours.
answered Feb 22 '13 at 18:23
HLGEM
133k25227489
answered Feb 22 '13 at 18:23
HLGEM
133k25227489
answered Feb 22 '13 at 18:23
HLGEM
133k25227489
answered Feb 22 '13 at 18:23
HLGEM
133k25227489
133k25227489
I have heard this before. I was wondering if employers may be more demanding of hourly employees in terms of what they expect them to accomplish during their hourly work.
– Daniel Allen Langdon
Feb 22 '13 at 21:04
Daniel, I think most managers have no idea who on a team is contributing what in terms of moving a feature or product forward. For instance, one team member may write many features in a short period of time, but they're all buggy and hard to maintain, whereas another team member may be the one who goes in and cleans all that up. Who accomplished more? So I think many managers shy away from making comparisons between team members.
– Amy Blankenship
Feb 23 '13 at 3:00
add a comment |Â
I have heard this before. I was wondering if employers may be more demanding of hourly employees in terms of what they expect them to accomplish during their hourly work.
– Daniel Allen Langdon
Feb 22 '13 at 21:04
Daniel, I think most managers have no idea who on a team is contributing what in terms of moving a feature or product forward. For instance, one team member may write many features in a short period of time, but they're all buggy and hard to maintain, whereas another team member may be the one who goes in and cleans all that up. Who accomplished more? So I think many managers shy away from making comparisons between team members.
– Amy Blankenship
Feb 23 '13 at 3:00
I have heard this before. I was wondering if employers may be more demanding of hourly employees in terms of what they expect them to accomplish during their hourly work.
– Daniel Allen Langdon
Feb 22 '13 at 21:04
I have heard this before. I was wondering if employers may be more demanding of hourly employees in terms of what they expect them to accomplish during their hourly work.
– Daniel Allen Langdon
Feb 22 '13 at 21:04
Daniel, I think most managers have no idea who on a team is contributing what in terms of moving a feature or product forward. For instance, one team member may write many features in a short period of time, but they're all buggy and hard to maintain, whereas another team member may be the one who goes in and cleans all that up. Who accomplished more? So I think many managers shy away from making comparisons between team members.
– Amy Blankenship
Feb 23 '13 at 3:00
Daniel, I think most managers have no idea who on a team is contributing what in terms of moving a feature or product forward. For instance, one team member may write many features in a short period of time, but they're all buggy and hard to maintain, whereas another team member may be the one who goes in and cleans all that up. Who accomplished more? So I think many managers shy away from making comparisons between team members.
– Amy Blankenship
Feb 23 '13 at 3:00
add a comment |Â
up vote
2
down vote
That is a really difficult question to answer because the answers is simply "it depends." It will vary greatly from company to company, department to department, manager to manager, and even down to the colleague you're sitting next to.
As somebody who has worked as a consultant on both salary and hourly basis, I can be the first to tell you it makes no difference between whether I worked salary or hourly, it all came down to the project manager and the company culture.
You will feel more pressure if you have a crappy project manager (PM), you will feel less pressure if you're working with a PM who knows his/her stuff. Any project manager worth his/her salt will know how to properly estimate development of any given feature and consequences of such features based on their development methodology, historical develvery experience, and team capabilities. Most people forget to allocate enough testing time, and if they do, they don't allocate enough time to fix the problems found during testing. Thus, finding project managers who are aware of these problems are far and few inbetween unfortunatley.
If a reputable company hires you hourly, chances are you're going to end up with a good project manager since they probably have already (accurately) estimated how much time a project will take to complete, and did a cost-benefit analysis and decided to pick you up hourly. In most cases, it means less developmental hurdles than salary actually. However, if a reputable company hires you hourly, and you're finding that you're working overtime constantly, consider looking inwards for a problem.
answered Feb 22 '13 at 21:52
Magnum
1212
I have found the worst estimators are the ones who want a daily hour long meeting with the whole team on a long-term project and then forget to factor all those hours into the estimate. 10 people * 5 hours per week* 26 weeks is a lot of hours to miss in your estimate. This is often the bigger cause than misestimating the testing time.
– HLGEM
Mar 22 '17 at 21:04
add a comment |Â
up vote
2
down vote
That is a really difficult question to answer because the answers is simply "it depends." It will vary greatly from company to company, department to department, manager to manager, and even down to the colleague you're sitting next to.
As somebody who has worked as a consultant on both salary and hourly basis, I can be the first to tell you it makes no difference between whether I worked salary or hourly, it all came down to the project manager and the company culture.
You will feel more pressure if you have a crappy project manager (PM), you will feel less pressure if you're working with a PM who knows his/her stuff. Any project manager worth his/her salt will know how to properly estimate development of any given feature and consequences of such features based on their development methodology, historical develvery experience, and team capabilities. Most people forget to allocate enough testing time, and if they do, they don't allocate enough time to fix the problems found during testing. Thus, finding project managers who are aware of these problems are far and few inbetween unfortunatley.
If a reputable company hires you hourly, chances are you're going to end up with a good project manager since they probably have already (accurately) estimated how much time a project will take to complete, and did a cost-benefit analysis and decided to pick you up hourly. In most cases, it means less developmental hurdles than salary actually. However, if a reputable company hires you hourly, and you're finding that you're working overtime constantly, consider looking inwards for a problem.
answered Feb 22 '13 at 21:52
Magnum
1212
I have found the worst estimators are the ones who want a daily hour long meeting with the whole team on a long-term project and then forget to factor all those hours into the estimate. 10 people * 5 hours per week* 26 weeks is a lot of hours to miss in your estimate. This is often the bigger cause than misestimating the testing time.
– HLGEM
Mar 22 '17 at 21:04
add a comment |Â
up vote
2
down vote
up vote
2
down vote
That is a really difficult question to answer because the answers is simply "it depends." It will vary greatly from company to company, department to department, manager to manager, and even down to the colleague you're sitting next to.
As somebody who has worked as a consultant on both salary and hourly basis, I can be the first to tell you it makes no difference between whether I worked salary or hourly, it all came down to the project manager and the company culture.
You will feel more pressure if you have a crappy project manager (PM), you will feel less pressure if you're working with a PM who knows his/her stuff. Any project manager worth his/her salt will know how to properly estimate development of any given feature and consequences of such features based on their development methodology, historical develvery experience, and team capabilities. Most people forget to allocate enough testing time, and if they do, they don't allocate enough time to fix the problems found during testing. Thus, finding project managers who are aware of these problems are far and few inbetween unfortunatley.
If a reputable company hires you hourly, chances are you're going to end up with a good project manager since they probably have already (accurately) estimated how much time a project will take to complete, and did a cost-benefit analysis and decided to pick you up hourly. In most cases, it means less developmental hurdles than salary actually. However, if a reputable company hires you hourly, and you're finding that you're working overtime constantly, consider looking inwards for a problem.
answered Feb 22 '13 at 21:52
Magnum
1212
That is a really difficult question to answer because the answers is simply "it depends." It will vary greatly from company to company, department to department, manager to manager, and even down to the colleague you're sitting next to.
As somebody who has worked as a consultant on both salary and hourly basis, I can be the first to tell you it makes no difference between whether I worked salary or hourly, it all came down to the project manager and the company culture.
You will feel more pressure if you have a crappy project manager (PM), you will feel less pressure if you're working with a PM who knows his/her stuff. Any project manager worth his/her salt will know how to properly estimate development of any given feature and consequences of such features based on their development methodology, historical develvery experience, and team capabilities. Most people forget to allocate enough testing time, and if they do, they don't allocate enough time to fix the problems found during testing. Thus, finding project managers who are aware of these problems are far and few inbetween unfortunatley.
If a reputable company hires you hourly, chances are you're going to end up with a good project manager since they probably have already (accurately) estimated how much time a project will take to complete, and did a cost-benefit analysis and decided to pick you up hourly. In most cases, it means less developmental hurdles than salary actually. However, if a reputable company hires you hourly, and you're finding that you're working overtime constantly, consider looking inwards for a problem.
answered Feb 22 '13 at 21:52
Magnum
1212
answered Feb 22 '13 at 21:52
Magnum
1212
answered Feb 22 '13 at 21:52
Magnum
1212
answered Feb 22 '13 at 21:52
Magnum
1212
1212
I have found the worst estimators are the ones who want a daily hour long meeting with the whole team on a long-term project and then forget to factor all those hours into the estimate. 10 people * 5 hours per week* 26 weeks is a lot of hours to miss in your estimate. This is often the bigger cause than misestimating the testing time.
– HLGEM
Mar 22 '17 at 21:04
add a comment |Â
I have found the worst estimators are the ones who want a daily hour long meeting with the whole team on a long-term project and then forget to factor all those hours into the estimate. 10 people * 5 hours per week* 26 weeks is a lot of hours to miss in your estimate. This is often the bigger cause than misestimating the testing time.
– HLGEM
Mar 22 '17 at 21:04
I have found the worst estimators are the ones who want a daily hour long meeting with the whole team on a long-term project and then forget to factor all those hours into the estimate. 10 people * 5 hours per week* 26 weeks is a lot of hours to miss in your estimate. This is often the bigger cause than misestimating the testing time.
– HLGEM
Mar 22 '17 at 21:04
I have found the worst estimators are the ones who want a daily hour long meeting with the whole team on a long-term project and then forget to factor all those hours into the estimate. 10 people * 5 hours per week* 26 weeks is a lot of hours to miss in your estimate. This is often the bigger cause than misestimating the testing time.
– HLGEM
Mar 22 '17 at 21:04
add a comment |Â
2
From the FAQ: You should only ask practical, answerable questions based on actual problems that you face. Chatty, open-ended questions diminish the usefulness of our site. If your motivation for asking the question is “I would like to participate in a discussion about ______â€Â, then you should not be asking here.
– IDrinkandIKnowThings
Feb 22 '13 at 19:39