Field Deployment Analyst (CBP)

About Agile Defense

At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next.

Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests.

Title

: Field Deployment Analyst (CBP)

Clearance

: Active CBP Background Investigation (CBP BI) and EOD strongly preferred. We can begin processing for candidates who do not hold one.

Citizenship

: U.S. Citizenship required

Location

: Remote with Travel

Required Certification(s):

COMPTIA A+, Network+, Security+

Travel

: Extensive travel, up to 90%

The Role

U.S. Customs and Border Protection runs continuous operations across more than 300 land, air, and sea ports of entry, plus Border Patrol stations and the Air and Marine Operations Center. A lot of those sites are nowhere near anything. Equipment there still has to be installed, refreshed, repaired, and made to work, and no amount of remote tooling gets somebody's hands onto a rack three hours from the nearest office.

That is this job. You will travel to sites, install and turn up infrastructure and end-user equipment, fix what remote support could not, and hand the site back working. You will coordinate with network engineers, cloud and mobility teams, and the people who run the site you are standing in.

Two things are worth knowing before you apply. The site will not match the documentation, often enough that you should expect it rather than report it as a surprise. And you will frequently be the only person there who knows what the plan was, which means the decision about how to proceed is yours in the moment and explainable afterward. People who want a bridge line for every judgment call will find this uncomfortable.

What Success Looks Like

Objective 1: Leave each site working, not merely visited

What you installed gets verified in actual use before you leave, not just powered on and checked off.

Somebody at the site can operate what you put in and describe what it does.

You do not get called back for the same problem on the next trip.

The work holds up under the site's normal conditions, not only the conditions on the day you were standing there.

⠀Objective 2: Make the right call on site when the plan does not survive contact

You proceed, adapt, or stop based on what is actually in front of you, and can defend that choice afterward.

Escalation happens when a decision is genuinely above you, not when it is uncomfortable.

You arrive with what the job needs, because you thought in advance about what might be missing.

⠀Objective 3: Turn each trip into something the next person can use

As-built records match what is deployed, including every part that differs from the plan.

Site conditions that will complicate the next deployment get flagged before somebody else discovers them the hard way.

What you learned troubleshooting ends up somewhere searchable rather than in your own notes.

⠀Objective 4: Deploy without interrupting the operation you are deploying into

Work fits the site's operating rhythm instead of asking the site to fit yours.

Site leadership knows what you are doing and when, before you arrive.