Cloud Engineers, Senior Engineers, Architects & Automation Specialists (CBP)

• Services you deploy survive their first real peak without emergency intervention.
• The failure of one component degrades the service rather than stopping it.
• Someone on call at two in the morning can tell what broke from the telemetry, without calling you to interpret it.
• Capacity and cost decisions get made before somebody escalates them.
• Environments get rebuilt from code, and the code matches what is actually running.
• Deployments that used to need a person watching them now run unattended.
• When automation fails, it fails visibly and leaves a trail somebody else can follow.
• Engineers stop keeping private scripts, because the shared tooling does the job.
• Security controls are designed in rather than retrofitted after a review finds them missing.
• Evidence for control assessments comes out of the pipeline instead of a documentation sprint before every deadline.
• You can explain to a security reviewer what a change does and why it is safe, in terms that answer their question rather than yours.

• Automation Specialist. You own the pipelines and tooling the rest of the team builds on. You decide how something gets automated, and when a manual step is not yet worth the cost of removing.
• Cloud Engineer. You own a service, an environment, or a workload. You make routine build and configuration calls yourself and bring the consequential ones to a review.
• Senior Cloud Engineer. You take the problems that arrive without a clear answer, including the ones that cross into network or security. Other engineers check their approach with you before they commit to it.
• Cloud Architect. You set the patterns others build against, and you are accountable when a pattern meets an operational or accreditation reality it did not anticipate.

• You have run production workloads in a government cloud environment where an outage cost something beyond a missed sprint.
• You have written infrastructure as code that other people used without needing you in the room to explain it.
• You have taken a system through a federal authorization process and can say what you would do differently the next time.
• You have integrated cloud services with legacy systems you could not replace, and can describe the compromises you made.
• 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 work comfortably in more than one platform's tooling and are not dependent on a single vendor's console.
• Cloud platform and security certifications are useful, but they are not a substitute for having done the work.

A note on timing

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