Cloud / DevOps Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information. So include responsibilities list, required qualifications list, desired qualifications list, overview paragraph, why work at noblis paragraph, total rewards paragraph (including benefits and compensation). Pay section: we have salary range.
We need to decide which sections to include: Responsibilities, Required Qualifications, Desired Qualifications, Overview, Why Work at Noblis, Total Rewards (maybe combine Benefits and Pay). But we need separate Pay section if salary range present. Also Benefits section if benefits described. The total rewards section includes benefits and compensation; we could split: Benefits (health, life, disability, financial, retirement, paid leave, professional development, tuition assistance, work-life programs) and Pay (salary range). However instruction: Prefer a few substantive sections over many thin ones. Could combine Benefits and Pay into Total Rewards section. But they said include a section ONLY when posting has real, specific content for it. The posting has "Total Rewards" heading with description of benefits and compensation. So we can make a section "Total Rewards". That covers benefits and compensation. However they also said never create Pay/Schedule/Benefits sections unless posting actually states them. Since they have a Total Rewards section, we can use that heading. But they also said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not mandatory to use exactly those; they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if appropriate. The posting has "Total Rewards". Could we map that to Benefits? Might be better to use "Benefits" heading and include the benefits description, and then a separate "Pay" heading for salary range. However they said prefer few substantive sections over many thin ones. But we have both benefits and pay; could combine into "Total Rewards". However they gave examples of headings but not required to stick to them. I'd choose to use "Total Rewards" as heading, as it's present in the posting. That seems faithful.
Thus sections: Responsibilities, Required Qualifications, Desired Qualifications, Overview, Why Work at Noblis, Total Rewards.
We need to extract content.
Responsibilities: The block starts with "Responsibilities Noblis is helping FAA..." then after that there is a paragraph about opportunity, then "Primary Responsibilities" list. We need to preserve all substantive info. So we should include the introductory paragraph as prose (
) and then the list as
- . The list items:
- Containerize application components (Docker/Podman) and create reproducible container images.
- Maintain Red Hat Enterprise Linux (RHEL) development/test hosts and follow hardening baselines.
- Support CI/CD jobs (Jenkins/GitLab CI/ArgoCD) by creating and updating pipeline scripts.
- Implement basic Infrastructure as Code (IaC) templates for test environments (Ansible, Terraform modules).
- Contribute to unit and integration testing, and assist with build troubleshooting.
- Participate in Agile ceremonies (daily standups, sprint planning, retrospectives).
- Assist with documentation (runbooks, deployment playbooks).
We should also include the earlier paragraph: "Noblis is helping FAA manage large and complex telecommunications and information management programs that use state of the art technologies to deliver enterprise infrastructure services essential to the safe and efficient operation of the largest, safest, and most complex aviation system in the world. We are seeking smart, passionate, and motivated people to join our proven team in a challenging and rewarding work environment where you will be actively engaged at the intersection of technology and operations enhancing our nation’s aviation system. If you want to be involved in acquiring, implementing, and managing the communications and information solutions to achieve our nation’s aviation vision, this is the job for you! This is an opportunity for an experienced, driven software solutions architect to join a dynamic team working to implement and manage the FAA’s highly-visible System Wide Information Management (SWIM) program as part of the NextGen transformation strategy. Support the SFDPS engineering team by implementing container builds, writing automation scripts, and operating services in Red Hat-based environments under mentor guidance. Work in Agile teams and follow CI/CD pipelines to enable migration to the FAA cloud platform."
That is all responsibilities prose.
Required Qualifications: list:
- Bachelor of Science degree and 6 years of relevant professional experience or Associates degree and 8 years of relevant professional experience
- Hands-on experience with Linux (preferably RHEL) and shell scripting (bash, Python).
- Software development experience with Java, Go, Python, or .Net
- Some exposure or coursework experience with C or C++programming is a plus
- Strong scripting skills with for automation tasks (maybe typo; keep as is)
- Familiarization with Java build tools and basic debugging techniques
- Experience building container images using Docker or Podman.
- Familiarity with Git and basic CI/CD concepts.
- Exposure to container orchestration (Kubernetes/OpenShift) or willingness to learn quickly.
- Comfortable working in Agile teams.
- Willingness and aptitude to learn and contribute to code refactoring and containerization of legacy Java/C/C++ components.
- U.S. Citizen or Green Card Permanent Resident (3+ years ouf of the last 5 years U.S. residency).
- Ability to obtain and maintain FAA Suitability
We should keep as list items.
Desired Qualifications: list:
- Experience with Ansible or Terraform.
- Basic cloud exposure (AWS/Azure/GCP or FedRAMP-authorized cloud).
- Coursera/edX or vendor certs in Linux, Docker, or Cloud Fundamentals.
- Any prior experience supporting FAA or federal systems (advantageous).
- Proven experience with at least one major message broker, such as Apache Kafka, RabbitMQ, IBM MQ, Solace, or NATS.
- Experience with data serialization formats, specifically JSON, XML, Avro, or Protobuf.
- Knowledge of messaging protocols like AMQP, MQTT, JMS, or STOMP.
- Understanding of asynchronous messaging patterns, pub-sub, and point-to-point queues.
- Experience with Cloud-based messaging services (e.g.AWS SNS/SQS, Azure Service Bus, Google Pub/Sub).
Overview: paragraph about Noblis and subsidiaries.
Why Work at Noblis: paragraph about passion, environment, etc.
Total Rewards: paragraph about health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs, award programs, eligibility, compensation determination, projected compensation range USD $86,800.00 - USD $135,625.00 /Yr. Also note about part-time adjustment.
We should not include boilerplate like "Commitment to Non-Discrimination", "EEO is the Law", etc. Also remove "Remote/hybrid status is subject to change..." maybe that's not boilerplate but could be considered metadata; but it's about remote/hybrid status. It's not a section heading; we could include it in Overview or Why Work at Noblis? It's a statement about remote/hybrid status subject to change. Might be considered minor metadata; we could fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is minor metadata about remote/hybrid status; we could include as a short p somewhere, maybe in Overview or Why Work at Noblis. But we could also drop it. Safer to drop it as it's not substantive. Also remove "Learn more and find opportunities at careers.noblis.org" maybe that's a link; could be considered minor metadata; drop.
Also remove "Other offerings may be provided for employees not within this category." That's part of Total Rewards; keep.
We must not include duplicated lines. Ensure we don't repeat.
Now craft HTML.
Structure:
Responsibilities
... prose ...
- ...
...
Required Qualifications
- ...
...
Desired Qualifications
- ...
...
Overview
...
Why Work at Noblis
...
Total Rewards
...
Make sure no extra whitespace at start.
Let's compose the prose exactly as in posting, but we can trim extra spaces.
Responsibilities prose:
"Noblis is helping FAA manage large and complex telecommunications and information management programs that use state of the art technologies to deliver enterprise infrastructure services essential to the safe and efficient operation of the largest, safest, and most complex aviation system in the world. We are seeking smart, passionate, and motivated people to join our proven team in a challenging and rewarding work environment where you will be actively engaged at the intersection of technology and operations enhancing our nation’s aviation system. If you want to be involved in acquiring, implementing, and managing the communications and information solutions to achieve our nation’s aviation vision, this is the job for you! This is an opportunity for an experienced, driven software solutions architect to join a dynamic team working to implement and manage the FAA’s highly-visible System Wide Information Management (SWIM) program as part of the NextGen transformation strategy. Support the SFDPS engineering team by implementing container builds, writing automation scripts, and operating services in Red Hat-based environments under mentor guidance. Work in Agile teams and follow CI/CD pipelines to enable migration to the FAA cloud platform."
Now list items as above.
Required Qualifications prose? Could be just list; no intro paragraph. We'll just list.
Desired Qualifications list.
Overview prose:
"Noblis and our wholly owned subsidiaries, Noblis ESI and Noblis MSD, take on some of the nation’s toughest challenges, delivering advanced solutions to our customers’ most critical missions. We bring together leading scientific, engineering, and management expertise in a culture grounded in objectivity and collaboration, ensuring our work creates lasting impact across federal missions. We work with a broad range of government agencies in the defense, intelligence, and federal civilian sectors."
Why Work at Noblis prose:
"At Noblis, we share a passion for excellence and innovation, and we create an environment where people can do meaningful work while maintaining the balance that keeps them energized and fulfilled. We seek out individuals with a natural curiosity and desire to collaborate and learn. We believe our people are our greatest strength, and we consistently seek exceptionally skilled, mission‑driven professionals who care deeply about doing work that enriches lives and makes our nation safer. Noblis has earned numerous workplace awards for our culture, our commitment to employee well‑being, and our dedication to meaningful, impactful work. We also maintain a drug‑free workplace."
Total Rewards prose:
"At Noblis we recognize and reward your contributions,
for prose. We must not repeat job title as heading. No Job ID. We must preserve all substantive information. So include responsibilities list, required qualifications list, desired qualifications list, overview paragraph, why work at noblis paragraph, total rewards paragraph (including benefits and compensation). Pay section: we have salary range. We need to decide which sections to include: Responsibilities, Required Qualifications, Desired Qualifications, Overview, Why Work at Noblis, Total Rewards (maybe combine Benefits and Pay). But we need separate Pay section if salary range present. Also Benefits section if benefits described. The total rewards section includes benefits and compensation; we could split: Benefits (health, life, disability, financial, retirement, paid leave, professional development, tuition assistance, work-life programs) and Pay (salary range). However instruction: Prefer a few substantive sections over many thin ones. Could combine Benefits and Pay into Total Rewards section. But they said include a section ONLY when posting has real, specific content for it. The posting has "Total Rewards" heading with description of benefits and compensation. So we can make a section "Total Rewards". That covers benefits and compensation. However they also said never create Pay/Schedule/Benefits sections unless posting actually states them. Since they have a Total Rewards section, we can use that heading. But they also said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not mandatory to use exactly those; they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if appropriate. The posting has "Total Rewards". Could we map that to Benefits? Might be better to use "Benefits" heading and include the benefits description, and then a separate "Pay" heading for salary range. However they said prefer few substantive sections over many thin ones. But we have both benefits and pay; could combine into "Total Rewards". However they gave examples of headings but not required to stick to them. I'd choose to use "Total Rewards" as heading, as it's present in the posting. That seems faithful.
Thus sections: Responsibilities, Required Qualifications, Desired Qualifications, Overview, Why Work at Noblis, Total Rewards.
We need to extract content.
Responsibilities: The block starts with "Responsibilities Noblis is helping FAA..." then after that there is a paragraph about opportunity, then "Primary Responsibilities" list. We need to preserve all substantive info. So we should include the introductory paragraph as prose (
) and then the list as
- . The list items:
- Containerize application components (Docker/Podman) and create reproducible container images.
- Maintain Red Hat Enterprise Linux (RHEL) development/test hosts and follow hardening baselines.
- Support CI/CD jobs (Jenkins/GitLab CI/ArgoCD) by creating and updating pipeline scripts.
- Implement basic Infrastructure as Code (IaC) templates for test environments (Ansible, Terraform modules).
- Contribute to unit and integration testing, and assist with build troubleshooting.
- Participate in Agile ceremonies (daily standups, sprint planning, retrospectives).
- Assist with documentation (runbooks, deployment playbooks).
We should also include the earlier paragraph: "Noblis is helping FAA manage large and complex telecommunications and information management programs that use state of the art technologies to deliver enterprise infrastructure services essential to the safe and efficient operation of the largest, safest, and most complex aviation system in the world. We are seeking smart, passionate, and motivated people to join our proven team in a challenging and rewarding work environment where you will be actively engaged at the intersection of technology and operations enhancing our nation’s aviation system. If you want to be involved in acquiring, implementing, and managing the communications and information solutions to achieve our nation’s aviation vision, this is the job for you! This is an opportunity for an experienced, driven software solutions architect to join a dynamic team working to implement and manage the FAA’s highly-visible System Wide Information Management (SWIM) program as part of the NextGen transformation strategy. Support the SFDPS engineering team by implementing container builds, writing automation scripts, and operating services in Red Hat-based environments under mentor guidance. Work in Agile teams and follow CI/CD pipelines to enable migration to the FAA cloud platform."
That is all responsibilities prose.
Required Qualifications: list:
- Bachelor of Science degree and 6 years of relevant professional experience or Associates degree and 8 years of relevant professional experience
- Hands-on experience with Linux (preferably RHEL) and shell scripting (bash, Python).
- Software development experience with Java, Go, Python, or .Net
- Some exposure or coursework experience with C or C++programming is a plus
- Strong scripting skills with for automation tasks (maybe typo; keep as is)
- Familiarization with Java build tools and basic debugging techniques
- Experience building container images using Docker or Podman.
- Familiarity with Git and basic CI/CD concepts.
- Exposure to container orchestration (Kubernetes/OpenShift) or willingness to learn quickly.
- Comfortable working in Agile teams.
- Willingness and aptitude to learn and contribute to code refactoring and containerization of legacy Java/C/C++ components.
- U.S. Citizen or Green Card Permanent Resident (3+ years ouf of the last 5 years U.S. residency).
- Ability to obtain and maintain FAA Suitability
We should keep as list items.
Desired Qualifications: list:
- Experience with Ansible or Terraform.
- Basic cloud exposure (AWS/Azure/GCP or FedRAMP-authorized cloud).
- Coursera/edX or vendor certs in Linux, Docker, or Cloud Fundamentals.
- Any prior experience supporting FAA or federal systems (advantageous).
- Proven experience with at least one major message broker, such as Apache Kafka, RabbitMQ, IBM MQ, Solace, or NATS.
- Experience with data serialization formats, specifically JSON, XML, Avro, or Protobuf.
- Knowledge of messaging protocols like AMQP, MQTT, JMS, or STOMP.
- Understanding of asynchronous messaging patterns, pub-sub, and point-to-point queues.
- Experience with Cloud-based messaging services (e.g.AWS SNS/SQS, Azure Service Bus, Google Pub/Sub).
Overview: paragraph about Noblis and subsidiaries.
Why Work at Noblis: paragraph about passion, environment, etc.
Total Rewards: paragraph about health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs, award programs, eligibility, compensation determination, projected compensation range USD $86,800.00 - USD $135,625.00 /Yr. Also note about part-time adjustment.
We should not include boilerplate like "Commitment to Non-Discrimination", "EEO is the Law", etc. Also remove "Remote/hybrid status is subject to change..." maybe that's not boilerplate but could be considered metadata; but it's about remote/hybrid status. It's not a section heading; we could include it in Overview or Why Work at Noblis? It's a statement about remote/hybrid status subject to change. Might be considered minor metadata; we could fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is minor metadata about remote/hybrid status; we could include as a short p somewhere, maybe in Overview or Why Work at Noblis. But we could also drop it. Safer to drop it as it's not substantive. Also remove "Learn more and find opportunities at careers.noblis.org" maybe that's a link; could be considered minor metadata; drop. Also remove "Other offerings may be provided for employees not within this category." That's part of Total Rewards; keep. We must not include duplicated lines. Ensure we don't repeat. Now craft HTML. Structure:
Responsibilities
... prose ...
- ... ...
Required Qualifications
- ... ...
Desired Qualifications
- ... ...
Overview
...
Why Work at Noblis
...
Total Rewards
...
Make sure no extra whitespace at start. Let's compose the prose exactly as in posting, but we can trim extra spaces. Responsibilities prose: "Noblis is helping FAA manage large and complex telecommunications and information management programs that use state of the art technologies to deliver enterprise infrastructure services essential to the safe and efficient operation of the largest, safest, and most complex aviation system in the world. We are seeking smart, passionate, and motivated people to join our proven team in a challenging and rewarding work environment where you will be actively engaged at the intersection of technology and operations enhancing our nation’s aviation system. If you want to be involved in acquiring, implementing, and managing the communications and information solutions to achieve our nation’s aviation vision, this is the job for you! This is an opportunity for an experienced, driven software solutions architect to join a dynamic team working to implement and manage the FAA’s highly-visible System Wide Information Management (SWIM) program as part of the NextGen transformation strategy. Support the SFDPS engineering team by implementing container builds, writing automation scripts, and operating services in Red Hat-based environments under mentor guidance. Work in Agile teams and follow CI/CD pipelines to enable migration to the FAA cloud platform." Now list items as above. Required Qualifications prose? Could be just list; no intro paragraph. We'll just list. Desired Qualifications list. Overview prose: "Noblis and our wholly owned subsidiaries, Noblis ESI and Noblis MSD, take on some of the nation’s toughest challenges, delivering advanced solutions to our customers’ most critical missions. We bring together leading scientific, engineering, and management expertise in a culture grounded in objectivity and collaboration, ensuring our work creates lasting impact across federal missions. We work with a broad range of government agencies in the defense, intelligence, and federal civilian sectors." Why Work at Noblis prose: "At Noblis, we share a passion for excellence and innovation, and we create an environment where people can do meaningful work while maintaining the balance that keeps them energized and fulfilled. We seek out individuals with a natural curiosity and desire to collaborate and learn. We believe our people are our greatest strength, and we consistently seek exceptionally skilled, mission‑driven professionals who care deeply about doing work that enriches lives and makes our nation safer. Noblis has earned numerous workplace awards for our culture, our commitment to employee well‑being, and our dedication to meaningful, impactful work. We also maintain a drug‑free workplace." Total Rewards prose: "At Noblis we recognize and reward your contributions,