Tax literacy
Geographic Arbitrage and Remote-Work Tax Residency Basics
Moving to a lower-cost-of-living or no-income-tax state as a remote engineer sounds simple. The tax-residency mechanics of actually making the move stick are not.
The idea is simple. Making the residency change stick is not.
Remote engineers who realize their salary is set independent of physical location, or close to it, often consider relocating to a lower-cost-of-living area or a state with no personal income tax to capture the resulting savings. The underlying financial logic is sound in principle — the same take-home pay stretches further, or a larger share of gross pay is retained, depending on the specific move. The part that trips people up is that changing your tax residency to actually capture those savings requires more than simply living somewhere else part of the time; it requires establishing genuine domicile under the specific rules of the states involved, and those rules are not uniform.
Domicile is about intent and connections, not just days present
Most states use some combination of a statutory residency test (commonly, spending more than a set number of days — frequently 183 — in the state during the year, sometimes combined with maintaining a permanent place of abode there) and a domicile test (your true, fixed, permanent home — the place you intend to return to, evidenced by factors like where you are registered to vote, hold a driver's license, register vehicles, maintain your primary healthcare providers, and spend the greater portion of your time). A remote engineer who claims to have moved to a no-income-tax state but keeps a driver's license, voter registration, primary residence, and the bulk of their actual time in their prior high-tax state has not necessarily changed their tax domicile in the eyes of that state's tax authority, regardless of a change-of-address form filed with an employer.
The "convenience of the employer" rule complicates remote work specifically
A number of states apply a "convenience of the employer" rule: if your employer is based in that state and you work remotely from another state for your own convenience rather than a genuine business necessity of the employer, the state where the employer is based can still claim the right to tax your income as though you worked there — regardless of where you actually performed the work. This rule varies significantly by state, has been the subject of ongoing legal disputes and legislative changes, and can create real double-taxation risk (though most states offer a credit for taxes paid to another state, which mitigates but does not always fully eliminate the friction) for remote engineers who assume their physical location alone determines their tax obligation.
A practical checklist for a residency change intended to be genuine and durable
- Change your driver's license, vehicle registration, and voter registration to the new state promptly, and keep records of the dates.
- Establish a genuine primary residence in the new state — purchase or a long-term lease, not a short-term arrangement that looks more like an extended stay than a home.
- Track actual days spent in each state carefully throughout the year, since statutory residency day-count tests are based on actual physical presence, not intent alone, and the burden of proof in an audit typically falls on the taxpayer.
- Sever or reduce ties to the prior state where practical — close or update accounts tied to the old address, move healthcare providers, and update professional and personal registrations.
- Check your specific employer's state and the convenience-of-the-employer rules that may apply, since this is the single most commonly overlooked complication for remote engineers specifically, as opposed to workers who simply live and work in the same single state throughout.
- File a part-year resident return for the year of the move in both states as applicable, and keep documentation supporting the domicile change date in case of a future residency audit — these audits do happen, particularly involving moves from high-tax states to no-income-tax states.
The takeaway
Geographic arbitrage as a remote engineer is a legitimate strategy, but capturing the tax benefit requires establishing genuine domicile — documented, dated, and consistent with actual behavior — not just a mailing address change. Understand your specific employer state's convenience-of-the-employer rules if applicable, and keep clear records supporting the residency change, since high-tax states have a direct financial incentive to scrutinize departures and do audit them.
Reciprocity agreements are a narrower, separate concept
A small number of neighboring states maintain reciprocity agreements that allow a resident of one state working in another to pay income tax only to their state of residence rather than filing and paying in both — a different mechanism entirely from the general geographic-arbitrage relocation scenario discussed above, and relevant mainly to engineers who live in one state and commute to a physical office in an adjacent state, rather than to fully remote engineers relocating to a state with no connection to their employer's location at all. Confirming whether a reciprocity agreement applies to your specific pair of states is worth doing directly rather than assuming general geographic-arbitrage guidance covers this narrower, state-pair-specific situation.
A short annual checklist review — current domicile documentation, current employer state's convenience rule status, and actual days-present tally for the year so far — is a reasonable habit for any remote engineer whose living situation involves more than one state, even years after an initial relocation is complete, since circumstances such as extended travel or a second residence can quietly shift the underlying facts over time.
Keeping a simple spreadsheet or calendar log of location by day, updated in real time rather than reconstructed retroactively, is the single most useful habit for any engineer whose year genuinely spans meaningful time in more than one state — reconstructing a year's travel pattern from memory during an audit inquiry is far harder, and far less convincing, than producing a contemporaneous record.
Disclosure
Important context
Is this personalized financial or tax advice?
No. These articles are general education for engineers and technical professionals, not personalized financial, tax, or legal advice. Equity plans, 401(k) plan documents, and tax rules vary by employer and change over time — verify specifics against your own plan documents and a licensed professional before acting.
Who publishes this content?
Engineer Financial is an independent editorial and tools property for software engineers and technical professionals. We are not a licensed financial advisor, broker-dealer, or investment adviser.
How do I go deeper on a topic covered here?
Use the calculators on /tools to model your own RSU, AMT, and allocation scenarios, or reach out via the contact form below to describe your situation. If your needs involve licensed advisory, structured intake can route you appropriately.
Contact
Talk with the Engineer Financial desk
Describe your situation and timeline. This form routes to the editorial team; licensing disclosures appear where regulated topics are discussed.
Build your personal financial system with the same precision you bring to work
STEM professionals accumulate equity, options, and deferred comp from multiple sources. An assumption-transparent plan shows every input, output, and sensitivity.
- RSU and options tax modeling (ISO, NSO, ESPP)
- Deferred comp and mega-backdoor Roth strategies
- FIRE scenario modeling with sensitivity analysis
- Multi-employer equity consolidation
Opens fenulwealthmanagement.com, our affiliated wealth-management firm · General education only · No fiduciary relationship formed on this page