Negotiating Relocation in a Distributed Tech Team?
Looking for some honest advice from people in tech who may have navigated something similar.
I recently received a software engineering offer from a company I’m genuinely excited about. The compensation and growth opportunity are incredible, and the hiring manager/team conversations went really well. The team itself is geographically distributed across multiple offices/time zones, and the hiring manager described the work as operating very collaboratively over Slack/Zoom/travel.
The challenge is around relocation. Leadership/recruiting strongly prefer DC residency long term, even though there’s also an office in my current city (Atlanta). My hiring manager seemed operationally open to phased onboarding/travel flexibility, but the written offer still formally requires relocation within a few months.
I’m not trying to avoid collaboration or ask for permanent “never come onsite” remote work. I’m fully open to travel, onboarding onsite, and regular in-person collaboration. The difficult part is that I currently have significant family/home obligations in Atlanta, and I’m trying to realistically figure out whether phased transitions like this tend to work in practice at fast-growing tech companies or whether I’m setting myself up for long-term instability.
For those who’ve worked in distributed orgs/startups:
\- Have you seen flexibility evolve after someone proves themselves?
\- How much do direct managers vs leadership/HR influence these situations operationally?
\- Would you personally take a high-upside opportunity with some uncertainty around long-term location expectations?
I’m trying to approach this thoughtfully and professionally, not emotionally, and would really appreciate honest perspectives from people who’ve navigated similar decisions.