5 ms·

> Supporting the services you are developing feels like natural part of the job. Paying fairly your employees for providing the support outside business hours

by gggsre 3y ago

> Supporting the services you are developing feels like natural part of the job. Paying fairly your employees for providing the support outside business hours also feels like natural part of the job. Unfortunately, surprisingly few companies do this.

zdragnar 3y ago
If you want to charge different rates based on hour of the day, you should consider contract work rather than salaried. The whole point of taking a salary is to have a predictable income, which cuts both ways.
- gggsre 3y ago
  > If you want to charge different rates based on hour of the day, you should consider contract work rather than salaried. What I'm saying is I don't want to do unpaid overtime and heroically sacrifice my weekends for oncall. > The whole point of taking a salary is to have a predictable income, which cuts both ways. Unsure what point about "cuts both ways" are you trying to make here. I think the company can pretty easily calculate how many non-business-hours are there within a month and allocate some money to compensate people doing oncall.
  - zdragnar 3y ago
    > unpaid overtime There's no such thing for salaried positions. I previously worked for a company that handed out "production bonuses" to people who worked >40 hours a week, calculated based off of your annual salary and hours worked. They were very clear to never call it overtime, because that has a very different meaning (legally). > Unsure what point about "cuts both ways" are you trying to make here Unlike a contractor, you don't have to look for another job after a defined period. You have a regular, fixed income (and benefits) so long as both you and your employer are happy. "40 hours per week" is a convention, not a requirement, though. Most companies are pretty good at picking 40 hours as a reasonable work-life balance mark. Some (notably startups and people mills like Amazon) push for more. That said, if you want a guarantee, stick to contracting paid hourly.
- mullingitover 3y ago
  The only caveat I would add to this is: if you begin the position without the expectation of on-call being made up front, and then it's pushed on you without any extra comp, that's not exactly fair. However, as long as that's made clear from the outset, yes, your salary covers you performing your expected duties whenever they need to be performed. It's not like salaried engineers aren't compensated well.
- ipaddr 3y ago
  Office full time work is 40 hours per week during the day for most. If you are working in the evenings you probably are a contractor or a newbie.
- justinclift 3y ago
  It seems to be fairly common for the on-call part of (salaried) jobs to be paid extra. For example, if you're rostered to be on call - whether or not you actually need to do anything - for a given week, then you'll be paid some $$$ for the inconvenience. Likewise, if you do actually need to do some after hours work during that on-call time (eg: some servers went down unexpectedly, find out what/why/etc + fix) then you'll be paid for that time as well. At least, this is how it's been at my last few roles.

by gggsre 3y ago

zdragnar 3y ago

If you want to charge different rates based on hour of the day, you should consider contract work rather than salaried. The whole point of taking a salary is to have a predictable income, which cuts both ways.

gggsre 3y ago
> If you want to charge different rates based on hour of the day, you should consider contract work rather than salaried. What I'm saying is I don't want to do unpaid overtime and heroically sacrifice my weekends for oncall. > The whole point of taking a salary is to have a predictable income, which cuts both ways. Unsure what point about "cuts both ways" are you trying to make here. I think the company can pretty easily calculate how many non-business-hours are there within a month and allocate some money to compensate people doing oncall.
- zdragnar 3y ago
  > unpaid overtime There's no such thing for salaried positions. I previously worked for a company that handed out "production bonuses" to people who worked >40 hours a week, calculated based off of your annual salary and hours worked. They were very clear to never call it overtime, because that has a very different meaning (legally). > Unsure what point about "cuts both ways" are you trying to make here Unlike a contractor, you don't have to look for another job after a defined period. You have a regular, fixed income (and benefits) so long as both you and your employer are happy. "40 hours per week" is a convention, not a requirement, though. Most companies are pretty good at picking 40 hours as a reasonable work-life balance mark. Some (notably startups and people mills like Amazon) push for more. That said, if you want a guarantee, stick to contracting paid hourly.
mullingitover 3y ago
The only caveat I would add to this is: if you begin the position without the expectation of on-call being made up front, and then it's pushed on you without any extra comp, that's not exactly fair. However, as long as that's made clear from the outset, yes, your salary covers you performing your expected duties whenever they need to be performed. It's not like salaried engineers aren't compensated well.
ipaddr 3y ago
Office full time work is 40 hours per week during the day for most. If you are working in the evenings you probably are a contractor or a newbie.
justinclift 3y ago
It seems to be fairly common for the on-call part of (salaried) jobs to be paid extra. For example, if you're rostered to be on call - whether or not you actually need to do anything - for a given week, then you'll be paid some $$$ for the inconvenience. Likewise, if you do actually need to do some after hours work during that on-call time (eg: some servers went down unexpectedly, find out what/why/etc + fix) then you'll be paid for that time as well. At least, this is how it's been at my last few roles.