Skip to content

Remote work and travel in FDE roles

3,315 postings · 1,376 companies · read

Stated in the posting

829 of 3,315 postings (25.0%) record on-site work.

25.0%829 postings

24.3%807 postings

21.0%697 postings

Not stated / unclear

29.6%982 postings

The arrangement stated in each posting, not a company-wide policy. Remote can include location restrictions, travel or conflicting office language.

Stated in the posting

Most postings say nothing about travel. Of the 1,403 that do, 826 state a maximum, and 723 cap it at 50% or less.

Share of the 1,403 postings that state it.

Explicitly no travel

0.6%9 postings

Up to 25%

24.8%348 postings

26–50%

26.7%375 postings

Over 50%

7.3%103 postings

Travel stated, no percentage

40.5%568 postings

1,912 postings say nothing.

A band is the maximum share of time the posting states. A posting that names travel without a percentage is counted on its own line, because no frequency is converted into a percentage. Silence is unknown, not zero travel. Conflicting terms are also unknown.

  • "Remote" can still limit the job to one state, region or country.
  • A travel percentage is the posting's stated maximum, not what the team did last quarter.
  • Ask what triggers a trip, how much notice people get, and whether the percentage counts conferences.
  • Missing language about location or travel means the condition is unknown, not that the job is remote or travel-free.

What to confirm with the employer

Confirm the eligible work location, the time zone, the office expectation, and whether customer visits are part of the job. A Veeam forward deployed engineer posting is one employer example, not a company-wide travel policy.

Locations and working arrangements here are read from the posting text, and those details change.

Employer postings · Download current counts · How to cite · How we read postings

Other posting data