Full Stack Engineer / Software Developer (CBP)

About the role

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: Full Stack Engineer / Software Developer (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: Ashburn, VA - Hybrid

Salary Range: [Pending]

Travel: Rare, as needed

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. The infrastructure behind that work is only half the story. Somebody still has to build the applications and services that run on top of it, and build them so they hold up inside a federal accreditation process rather than in spite of one.

You will design, build, and maintain software across the stack, working alongside cloud engineers, automation specialists, and security staff who own the environment your code runs in. This is a development role, not an infrastructure role. You are writing the application, not standing up the platform underneath it.

Two things are worth knowing before you apply. Security is not a phase that happens after the code works, it is part of what "working" means here, so you will spend real time on things a purely commercial shop might treat as somebody else's job. And this program does not have the luxury of a green field. Some of what you build has to fit around systems that predate the current approach, and pretending otherwise produces software that looks good in a demo and fails in production.

What Success Looks Like

Objective 1: Ship software that survives its first real contact with production

- Code you write passes review without repeated rounds over the same category of issue.

- Features work the way they were specified, and where the specification was wrong, you caught it before users did.

- What you build integrates cleanly with the pipelines and environments the cloud and automation teams maintain, instead of working around them.

⠀Objective 2: Build security in rather than bolt it on

- Common vulnerability classes get caught in your own review, not in a scan somebody else runs later.

- You can explain a security finding in your own code and fix it without waiting to be told exactly what is wrong.