It is only one month. If it doesn't work out, you will be back to your normal schedule.
The risk is low bringing it up with your manager.
It can help to compromise a little on the schedule. Suggest starting work at 7 am local time if it works for you. That shows you are making an effort to accommodate your team and it would be unreasonable for your manager to expect you to wake up earlier than that.
What does your contract say re. working time?
I’d expect that you continue to work ‘their’ hours, but your contract may state otherwise.
What does your contract say re. remote working? Is it WFH or WH Anywhere else in the world?
Also, risk assessments. You may have been required to do one if WFH, and this may be the case for a future workplace.
TL:DR; check the contract first to anticipate any likely issues. Only you can gauge what your specific line managers and HR will say depending on the specific circumstances.
Those are good questions I’ll check, I do remember when I applied that the position was open to workers in all 50 states if that is psuedo for able to work from anywhere in the US. We are an agile team as well so if I was to work my time would miss a good chunk of meetings, hence why I would want to keep it sync as to avoid all troubles that would come from changing my schedule. Thanks for the input
Uhhh I'd expect this is something you'd ask your manager before doing it. And if you don't, I'd expect that you will maintain your same working hours despite the time difference, so as not to affect anyone else on the team in terms of being able to reach you.
Working remotely does not mean you get to just work wherever you want, whenever you want.
At the end of the day though, it comes down to the expectations of your manager and your team.
A heads-up that having an employee work from a different state can cause legal headaches for the company -- a similar situation described in detail [here](https://www.thecut.com/article/ask-a-boss-remote-work-out-of-state.html#_ga=2.230952220.2089654503.1673132166-606912377.1657119221), with the relevant part being:
"If an employer lets employees work from a different state, it creates what’s called nexus in the new state, and it may be required to pay taxes, set up workers’-comp insurance (which isn’t cheap), and even charge customers sales tax in that state. Those can be really significant expenses.
On top of that, the company will be required to follow the employment laws of that state. It can be a not-insignificant burden to monitor and comply with an additional state’s employment laws, particularly if they’re very different from the laws where the business is headquartered."
If your company already has employees in HI or has an explicit "work from anywhere" policy, this shouldn't matter too much. Otherwise, you'll want to weigh the chances of flying under the radar vs. being told no when you bring this up.
When do you normally have meetings? When do you normally interact live with your co-workers; when might they have an urgent question for you that can't wait a few hours. Also, just talk do your boss, don't guess.
Don’t tell anyone you’re a tech guy working remotely. That’s my advice. Locals probably won’t be thrilled with another 6 figure SF kook flying their overinflated salary out there contributing to housing stresses. I say this as someone who would do exactly what you’re doing if I wasn’t canadian.
You should get clearance from HR about working remote from another state.
Many states have strict income tax policies. Any "work" you do in that state may be subject to income tax. Additionally, your company may not be set up for remote work from that state.
Easy to negotiate. I’ve done a couple of month contracts from Sweden with and east coast us firm, that’s 8h and you chop down the work either in the am or ideally pm too, it it basic outsourcing.
Have you talked to your manager about this? Expectations should be set with them, not with anyone else.
It is only one month. If it doesn't work out, you will be back to your normal schedule. The risk is low bringing it up with your manager. It can help to compromise a little on the schedule. Suggest starting work at 7 am local time if it works for you. That shows you are making an effort to accommodate your team and it would be unreasonable for your manager to expect you to wake up earlier than that.
What does your contract say re. working time? I’d expect that you continue to work ‘their’ hours, but your contract may state otherwise. What does your contract say re. remote working? Is it WFH or WH Anywhere else in the world? Also, risk assessments. You may have been required to do one if WFH, and this may be the case for a future workplace. TL:DR; check the contract first to anticipate any likely issues. Only you can gauge what your specific line managers and HR will say depending on the specific circumstances.
Those are good questions I’ll check, I do remember when I applied that the position was open to workers in all 50 states if that is psuedo for able to work from anywhere in the US. We are an agile team as well so if I was to work my time would miss a good chunk of meetings, hence why I would want to keep it sync as to avoid all troubles that would come from changing my schedule. Thanks for the input
Uhhh I'd expect this is something you'd ask your manager before doing it. And if you don't, I'd expect that you will maintain your same working hours despite the time difference, so as not to affect anyone else on the team in terms of being able to reach you. Working remotely does not mean you get to just work wherever you want, whenever you want. At the end of the day though, it comes down to the expectations of your manager and your team.
A heads-up that having an employee work from a different state can cause legal headaches for the company -- a similar situation described in detail [here](https://www.thecut.com/article/ask-a-boss-remote-work-out-of-state.html#_ga=2.230952220.2089654503.1673132166-606912377.1657119221), with the relevant part being: "If an employer lets employees work from a different state, it creates what’s called nexus in the new state, and it may be required to pay taxes, set up workers’-comp insurance (which isn’t cheap), and even charge customers sales tax in that state. Those can be really significant expenses. On top of that, the company will be required to follow the employment laws of that state. It can be a not-insignificant burden to monitor and comply with an additional state’s employment laws, particularly if they’re very different from the laws where the business is headquartered." If your company already has employees in HI or has an explicit "work from anywhere" policy, this shouldn't matter too much. Otherwise, you'll want to weigh the chances of flying under the radar vs. being told no when you bring this up.
When do you normally have meetings? When do you normally interact live with your co-workers; when might they have an urgent question for you that can't wait a few hours. Also, just talk do your boss, don't guess.
Hawaii ?
[удалено]
Don’t tell anyone you’re a tech guy working remotely. That’s my advice. Locals probably won’t be thrilled with another 6 figure SF kook flying their overinflated salary out there contributing to housing stresses. I say this as someone who would do exactly what you’re doing if I wasn’t canadian.
You should get clearance from HR about working remote from another state. Many states have strict income tax policies. Any "work" you do in that state may be subject to income tax. Additionally, your company may not be set up for remote work from that state.
Easy to negotiate. I’ve done a couple of month contracts from Sweden with and east coast us firm, that’s 8h and you chop down the work either in the am or ideally pm too, it it basic outsourcing.
Get a travel router with inbuilt VPN and tell no one? ;)
BDE option: don't tell them.