[kfcm]

Always a tough choice. And only one you can make.

Here's my thoughts:

1) People/teammates make all the difference in the world. You love working with your current team; you've enjoyed working with the Other Company's (OC) IT Director before. But will you like the OC's team you'll be working with? Will you be seen by them as capable, or as a buddy being brought in to shove "architecture" down their throats?

2) Vacation. This is a negotiation. Tell them you have three weeks now (and have proof) and tell them you want the match. That shouldn't be too difficult, but I've actually seen companies balk and walk away over this (Even as far as telling senior people with X weeks vacation they'll be treated like entry-level and start with none for the first six months, etc). Sure sign of bureaucracy, and being tied to processes.

3) WFH. Kind of unclear. I'm assuming you can WFH pretty regularly now, and with OC you'll lose a lot of that. Again, negotiate. If most of OC team is in another city, what difference does it make if you're in the office, or at home on the corporate VPN--like they are.

4) Commute. WFH could make a lot of difference here too. But adding 15 minutes each way is 30 minutes a day, 2.5 hours a week, 10 hours a month, 120 a year. What could you do with that spare time if you didn't have the commute? Not to mention costs in gas, mileage on tires and car, etc.

5) Boredom. You're bored in your current job, which is never a good thing. But are you relevant? Meaning, are you doing useful things, listened to, etc? If you jump over to OC, will you still be relevant? Or will remote team ignore you and do their own things? Irrelevance and boredom are never good apart, and torture together.

[midwestdev]

Thanks for the feedback!

1) While I can't be sure, I believe that I would be able to be seen as capable. I consider myself a strong mobile developer, and I have many years of shipping some very popular apps. It is my understanding that the remote mobile team is somewhat more on the junior side. If I made changes to the team (introduce formal code review, spin up build servers and nightly/CI builds, etc) it would be done gradually and with their input.

2) This is basically what I was thinking. If they don't budge on vacation, or are unwilling to even consider it, it isn't a good sign.

3) Their rationale has been that while yes, the mobile team is in another city, part of my role in this position is somewhat of a liaison between the mobile team and the rest of the IT in my current city. As new features are requested of the app that have service dependencies, it would require me to interface with the team in my city. Still though, IMO, this doesn't require 5 days a week face to face. I've never had problems doing this in my current role. I honestly just think this comes down to the company here not being used to people regularly WFH. When I first joined my current company, it wasn't an option at all, but it was added a year after I joined.

4) Commute does worry me some. Although, I know many people with MUCH longer commutes. I think that ~40 minute commute is on the max of what I would consider bearable. This commute falls under that. Although, another consideration is that this job is further away from my child's daycare. So, on certain days, my effective commute may be longer still.

5) I feel like I'm listened to and that I am relevant. At most places I have worked, I feel like I have the respect of my peers and management. I work very hard. But in the past 2 years, I have spun up 2 completely new, relatively large apps for my current company. Once they are released, the development cycle seems to slow a lot. The number of new features that need to be developed go way down. I'm in one of those maintenance modes now and can lead to me being bored.

[midwestdev]

I also fear that my current liberal WFH policy is becoming a form of golden handcuffs.

It is something that isn't offered by as many companies around here, and I've started to grow very used to it.