Full Stack Engineer / Software Developer

The Role

What Success Looks Like

• 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.

• 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.
• Secrets, credentials, and sensitive configuration never end up somewhere they should not be, because you built the habit rather than relying on a gate to catch it.

• Someone who did not write a piece of code can extend it without reverse engineering your intent first.
• Tests exist for the logic that would be expensive to get wrong, and they catch real regressions rather than just existing.
• Technical debt gets named and tracked instead of quietly accumulating under a working feature.

• Documentation and evidence needed for a security or compliance review come out of your normal development process rather than a separate effort before a deadline.
• You can explain what a change does and why it is safe in terms a non-developer reviewer can act on.

What You Bring

• You have built and shipped production software in a government or highly regulated environment, not only in a commercial setting with fewer constraints.
• You have written code that had to pass a security review, and can describe what you changed because of it.
• You are comfortable across the stack rather than deep in only the frontend or only the backend.
• You have worked inside a CI/CD pipeline as a contributor, not just as someone whose code gets deployed by it.
• You hold an active CBP BI, a fitness determination at another DHS component, or an active DoD clearance. Any of these shortens your start date.
• You have integrated new software with a legacy system you could not replace, and can describe the tradeoffs you made.

A note on timing

Employee Benefits

• Happy - Be Infectious. Happiness multiplies and creates a positive and connected environment where motivation and satisfaction have an outsized effect on everything we do.
• Helpful - Be Supportive. Being helpful is the foundation of teamwork, resulting in a supportive atmosphere where collaboration flourishes, and collective success is celebrated.
• Honest - Be Trustworthy. Honesty serves as our compass, ensuring transparent communication and ethical conduct, essential to who we are and the complex domains we support.
• Humble - Be Grounded. Success is not achieved alone, humility ensures a culture of mutual respect, encouraging open communication, and a willingness to learn from one another and take on any task.
• Hungry - Be Eager. Our hunger for excellence drives an insatiable appetite for innovation and continuous improvement, propelling us forward in the face of new and unprecedented challenges.
• Hustle - Be Driven. Hustle is reflected in our relentless work ethic, where we are each committed to going above and beyond to advance the mission and achieve success.