On-Site vs Remote FDE Work: Travel Realities and Building Trust in Person

The standard “remote vs. on-site” debate fails the Forward Deployed Engineer. You aren’t a fully distributed developer pushing commits from a cabin, and you aren’t a resident employee swiping a badge at HQ every morning. You exist in a third state—a high-trust hybrid where travel is a feature, not a bug. This piece breaks down the real cadences, the economics, and the specific moments that force you onto a plane.

The FDE Spectrum: It’s Not a Binary

Most FDE roles fall into one of three operational models. The model dictates your compensation structure, your relationship with the customer, and your burnout threshold.

Pure remote FDE roles are rare at the entry level. A customer paying seven figures for a platform expects the engineer to sit in their SCIF or boardroom at least once during the deployment phase. The question isn’t “can I work remotely,” but “what is the minimum viable presence to unblock the deal?”

The Trust Architecture: Why You Fly

Travel isn’t about optics; it’s about information asymmetry. In a remote call, the customer sees a 1080p grid of faces. They hide the sticky note on the monitor that says “Check with legal before sharing this schema.” On-site, you see the sticky note. You read the room.

You fly for three specific engineering signals that Slack cannot transmit:

1. The Schema Revelation: You need to map their legacy Oracle monstrosity. They won’t send the 200MB CSV over email. You sit next to their DBA, look at the screen together, and sketch the JOINs on a whiteboard.
2. The Political Unblock: Two VP stakeholders refuse to agree on a workflow in a Google Doc. You facilitate a two-hour conference room session where you wireframe the UI in real-time using a dummy endpoint. Alignment happens in the room, not in the thread.
3. The Air-Gap Bridge: The production environment has no outbound internet. You physically carry a hardened appliance (or a laptop with a one-time pad) to install the on-prem edge runtime. This is still the reality in defense, finance, and critical infrastructure.

Travel Realities: A Typical Quarter

Let’s look at a concrete Q2 for a hybrid FDE supporting two enterprise accounts.

• Week 1 (Remote): Prep sprint. You’re building a custom ingestion connector for a client’s REST API. You host a 30-minute Loom walkthrough for their engineering team.
• Week 2 (On-Site, Client A): Fly out Monday morning. You’re in their Chicago office Tuesday-Thursday. Goal: integrate the connector into their staging environment and run a live data reconciliation against 1M rows. Fly back Thursday red-eye.
• Week 3 (Remote): Bug fixes, documentation, internal product feedback. You advocate for a feature that Client A needs, writing a technical spec for core engineering.
• Week 4 (On-Site, Client B): Fly to New York. This is a QBR (Quarterly Business Review) prep. You aren’t coding much; you’re building a dashboard to prove ROI to the economic buyer. You present on Friday.

The Per-Diem Economics

Travel comp is where FDEs either get rich slowly or bleed money. Know the mechanics.

• M&IE (Meals & Incidental Expenses): Federal GSA rates are the baseline. Domestic travel to a Tier 1 city (NYC/SF) pays roughly $79/day. Companies often pay this as a flat cash per-diem on your paycheck. If you eat grocery store salads and keep the $79, you pocket the delta. This is tax-free to you.
• Lodging: Never pay out-of-pocket for the hope of reimbursement. Corporate cards or direct-bill hotels are standard. Points and status are yours to keep (this is a non-trivial compensation perk—Marriott Titanium/Hyatt Globalist status translates to significant personal vacation value).
• The “Road Warrior” Trap: A $150k base + $30k travel uplift sounds great until you calculate the hourly rate of a 60-hour week that includes a Sunday night flight. Value your time. If the travel uplift doesn’t cover the hours lost, you’re taking a pay cut.

Remote Work That Actually Works

When you are remote, you aren’t just “working from home.” You are running a remote engineering outpost. The standard corporate remote playbook fails because you lack the internal network’s context. You must over-index on artifact creation.

The Async Artifact Stack:

• Decision Logs: For every customer call, write a 5-bullet summary in a shared Notion/Confluence. State the decision, the alternatives considered, and the customer’s exact words. This prevents the “I thought we agreed on X” email three weeks later. This aligns with the portfolio methodology we drill in The FDE Portfolio: Shipped Artifacts and Decision Logs to Get Hired.
• Loom > Live Calls: Never schedule a 30-minute call to show a bug fix. Record a 4-minute Loom. They can watch it at 2x speed. Your calendar remains yours.
• Local Simulation: Before you fly, you replicate their environment locally. If they have a weird Kubernetes distribution, you build a kind cluster that mimics it. You don’t debug infrastructure on a customer’s laptop while they watch you sweat.

Building Trust Without a Badge

Trust is the currency of the FDE. On-site, trust is built through shared meals and hallway conversations. Remote, you must manufacture trust through reliability and transparency.

1. The “No Surprises” SLA: If you hit a blocker at 2 PM, the customer knows by 2:15 PM. You don’t sit on bad news.
2. Screen Share the Mess: When a query takes 30 seconds, don’t hide it. Share your screen. Show the EXPLAIN ANALYZE. Show them you are digging into the heap dump. They trust engineers who show their work, even when it’s failing.
3. The Internal Advocate: The highest-leverage remote activity is fighting the internal product team on the customer’s behalf. When the customer sees a feature ship in the core platform because you filed a ruthless ticket with reproducible steps, they trust you more than the sales rep.

For those looking to break in, the interview process specifically tests for this narrative of ownership. You can’t just grind Leetcode; you need to demonstrate the signal of a builder who ships. We cover this in detail in The FDE Interview Loop: Preparing for Signal Over Leetcode Memorization.

FAQ: On-Site vs Remote FDE Work and Travel Realities

Is it better to work remotely or on-site as an FDE?

It depends on the engagement phase. For initial discovery and air-gapped deployments, on-site is non-negotiable. For maintenance, scaling, and internal advocacy, remote is more productive. The “better” state is the one that unblocks the current technical bottleneck. High-performing FDEs optimize for the ability to switch modes instantly, not for a permanent remote setup.

Is remote work going away in 2026 for FDEs?

No, but “remote” is being redefined. It no longer means “never travels.” It means “travels with extreme intentionality.” Companies are cutting discretionary travel (internal summits) but increasing customer-facing travel. The FDE role is the last mile of enterprise software; that last mile often requires a physical footprint. The trend is toward shorter, higher-intensity on-site bursts (3 days instead of 5) rather than a return to 5-day office mandates.

How to make $1000 a week remotely?

While this is a common search query, it’s the wrong framing for an FDE. FDE total compensation is typically salary + equity + per-diem. Per-diem alone can net $500-$700/week tax-free during travel weeks. However, chasing short-term cash misses the point. The FDE track builds the skill of translating raw engineering into revenue. This skill compounds into Solutions Architecture leadership or CTO roles at startups, where equity returns dwarf weekly cash. Focus on the skill acquisition; the cash follows.

What is the difference between on-site and remote for an FDE?

On-site is synchronous, high-bandwidth, and politically charged. You are debugging people and systems simultaneously. Remote is asynchronous, high-focus, and artifact-driven. You are building code, writing decision logs, and automating the repetitive parts of the deployment. The FDE role is the oscillation between these two states. If you only do one, you are either a consultant or a staff engineer, not an FDE.

How do I prepare for the travel demands of an FDE role?

Build systems for your life, not just your code. Automate your personal finances (see our guide on building a personal finance categorizer from bank CSVs with Gemini and Supabase). Master the art of the single-bag travel setup (one backpack, no checked luggage). Protect your health (airport lounges are not gyms). The physical resilience to handle a red-eye and debug a production incident at 9 AM is a competitive advantage.