Always a tough choice.  And only one you can make.<p>Here&#x27;s my thoughts:<p>1) People&#x2F;teammates make all the difference in the world.  You love working with your current team; you&#x27;ve enjoyed working with the Other Company&#x27;s (OC) IT Director before.  But will you like the OC&#x27;s team you&#x27;ll be working with? Will you be seen by them as capable, or as a buddy being brought in to shove &quot;architecture&quot; down their throats?<p>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&#x27;t be too difficult, but I&#x27;ve actually seen companies balk and walk away over this (Even as far as telling senior people with X weeks vacation they&#x27;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.<p>3) WFH.  Kind of unclear.  I&#x27;m assuming you can WFH pretty regularly now, and with OC you&#x27;ll lose a lot of that.  Again, negotiate.  If most of OC team is in another city, what difference does it make if you&#x27;re in the office, or at home on the corporate VPN--like they are.<p>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&#x27;t have the commute?  Not to mention costs in gas, mileage on tires and car, etc.<p>5) Boredom.  You&#x27;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.