Scientific Programmer

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay, Schedule. We need to include only sections with real content. From posting: - Job Title: Scientific Programmer (not heading) - Clearance Required: Public Trust (metadata) - Work Location: Remote (metadata) - About the role: description after "Alpha Omega is seeking...". We'll put that under

About the role

with paragraph(s). - Key Responsibilities: list items. We'll put

Responsibilities

with

• ... each. - Experience/Skills: Required Qualifications and Preferred Qualifications. Could combine into Requirements and Skills sections. The instruction: use headings for Requirements, Qualifications, Skills. We need to decide. Probably we can have

  Requirements

  for required qualifications, and

  Preferred Qualifications

  maybe under Skills? But they said use headings for Requirements, Qualifications, Skills. Could combine required and preferred under Requirements? Or have Requirements (required) and Skills (preferred). Let's interpret: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which content goes where. We have required qualifications (2 years experience, programming, cloud, web tech, DB, version control, API). Preferred qualifications (data stewardship, legacy migration, agile, system security). Education also. We could put Required Qualifications under

  Requirements

  . Preferred Qualifications under

  Qualifications

  (or Skills). But Skills heading could be for technical skills list. However we already have skills in required. Might be redundant. Better: Use Requirements for required experience/skills, Qualifications for education/preferred, Skills for maybe technical skills? But we already listed technical skills in required. Could still put them under Skills. Let's design: - About the role: paragraph summarizing role. - Responsibilities: list of key responsibilities. - Requirements: required qualifications (2 years experience, programming & scripting, cloud infrastructure, web technologies, database management, version control & DevOps, API development). Could be list. - Qualifications: preferred qualifications (data stewardship, legacy migration, agile methodology, system security) plus education (BS/BA degree...). Could be list. - Skills: maybe we could list specific technical skills: Python, Bash, AWS Lambda, serverless, React, TypeScript, PL/SQL, Git, GitLab CI/CD, RESTful APIs. But that duplicates. However we can still include as a concise list. - Benefits: list of benefits from "Joining The Alpha Omega Team Entitles You To Participate In All Retirement Benefits..." and bullet list. - Pay: salary range $60,000 - $62,000. - Schedule: not mentioned; remote location but no schedule. So we should NOT include Schedule section. - Also include clearance and work location maybe as a short paragraph under About the role or separate? Could fold minor metadata into a short

  or drop it. We'll include a short paragraph after About the role maybe: "Clearance: Public Trust. Work Location: Remote." But we must not repeat job title as heading. We must remove boilerplate: navigation, legal, EEO, etc. Remove "Application Deadline: December 7, 2026" (that's application instruction? It's a deadline, but instruction says remove application instructions. So drop that. Also remove "Joining The Alpha Omega Team Entitles You To Participate In All Retirement Benefits..." we keep benefits but not the sentence? We can keep benefits list. We need to preserve all substantive information. So we need to keep the description of Alpha Omega, company description, culture and values? That's substantive but maybe not needed for sections; we could include under About the role or a separate section like "About the Company". But headings list does not include About the Company. Could we add a section? The instruction says use headings for those specific headings; but we could still add other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could add About the Company as a section if needed. However we already have About the role; we could incorporate company description there. We must not invent or summarize away detail. So we need to keep the company description text. We'll include it as a paragraph under About the role maybe after role description. Let's extract substantive content: Job Details Description (ignore). Job Title: Scientific Programmer (ignore heading). Clearance Required: Public Trust. Work Location: Remote. Alpha Omega is seeking a qualified Scientific Programmer in support of our NOAA National Centers for Environmental Information (NCEI) Data Stewardship Division (DSD) customer. This division works in partnership with NOAA and the broader community to develop and maintain a robust and efficient infrastructure of hardware, software, and processes to support the ingest, long-term preservation, and delivery of environmental data products spanning the depths of the ocean to the surface of the sun. In this role, this individual will be responsible for stewardship of our nation’s environmental data. Key Responsibilities: - Infrastructure Modernization: Drive the transition of legacy systems to modern architectures. - System Maintenance: Proactively monitor and maintain aging infrastructure to ensure high availability and performance. - Development & Integration: Design and implement scalable solutions using serverless technologies and robust backend scripting. - Documentation & Quality Control: Maintain rigorous documentation standards by utilizing Pull Requests (PRs) to record architectural changes, code updates, and completed tasks. - CI/CD Management: Oversee automated deployment pipelines to ensure code quality and streamlined delivery cycles. Experience/Skills: Required Qualifications: - 2 years of experience. - Programming & Scripting: Proficiency in Python and Bash for automation and data processing. - Cloud Infrastructure: Hands-on experience with AWS Lambda and serverless architecture. - Web Technologies: Strong understanding of React and TypeScript for front-end interface management. - Database Management: Experience writing and optimizing PL/SQL queries and managing relational databases. - Version Control & DevOps: Advanced knowledge of Git and GitLab CI/CD workflows. - API Development: Experience building and consuming RESTful APIs. Preferred Qualifications: - Data Stewardship: Previous experience working within data-heavy contracts or meteorological data formats. - Legacy Migration: Proven track record of successfully "lifting and shifting" or refactoring aging infrastructure into cloud-native environments. - Agile Methodology: Experience working in an Agile/Scrum environment with a focus on iterative delivery. - System Security: Familiarity with implementing security best practices within AWS environments. Education: BS/BA Degree in an IT/IS field, such as Computer Science, Information Systems, Software Engineering or a related field, or equivalent bootcamp/self-taught experience. Salary And Benefit Information: The likely salary range for this position is $60,000 - $62,000. This is not, however, a guarantee of compensation or salary. There are multiple factors that are considered in determining final pay for a position, including, but not limited to, relevant work experience, skills, certifications and competencies that align to the specified role, education and certifications as well as contract provisions regarding labor categories that are specific to the position and could fall outside of this range. Application Deadline: December 7, 2026 (remove) Joining The Alpha Omega Team Entitles You To Participate In All Retirement Benefits, Plans Of Deferred Compensation, Health And Insurance Benefits, And Other Such Benefits As Set Forth In The Company’s Policy And Benefits Manuals. See Below, To Name a Few: - 15 days PTO including paid parental, military, and bereavement leave - Eleven (11) paid Federal holidays, five of which are floating holidays (as designated by the company’s holiday schedule each year) - Health and Dental Insurance (including 100% employer paid premiums for employee coverage under the HDHP health plan) - Life Insurance, STD/LTD term disability coverage, with employer paid premiums - 401 (k) plan with a match that is 100% vested after you complete two years of service - FSA/DFSA/HSA flexible benefit plans - Annual Tuition & Professional Development Reimbursement benefit We regularly review our Total Rewards package to ensure our offerings are competitive and reflect what our employees have told us they value most. Our Company: Alpha Omega is an award-winning solutions provider dedicated to delivering mission-enabling technology and strategic solutions for our customers. Since our founding in 2016, we have grown to over 700 employees nationwide consisting of former operators, technologists, and strategists who bring decades of government and industry experience. They are united by one purpose: ensuring our nation’s continued global leadership. We have a unified operating model providing technical capabilities and solutions for customers across two main business units: National Security – supporting agencies such as the Department of Homeland Security (DHS), Navy, Air Force, Army, and the Department of State (DOS). National Resilience – supporting agencies such as Federal Deposit Insurance Corporation (FDIC), Treasury, Health & Human Services (HHS), National Institutes of Health (NIH), National Oceanic and Atmospheric Administration (NOAA) and the United States Department of Agriculture (USDA) Through strategic partnerships, intellectual property, and relentless drive for innovation, Alpha Omega is shaping the future of government technology. We are proud to be a Virginia Best Places to Work 8 times, an Inc. 5000 honoree 7 times, and a Washington Post Top Workplaces 4 times. Join us in driving transformation that secures the nation's future. Culture And Values: Guided by our core values—Harmony, Engagement, Accountability, Resourcefulness, and Tenacity (HEART)— we foster a culture of innovation, collaboration, and continuous learning and are committed to delivering high-impact solutions. We recognize and reward hard work. Alpha Omega's culture is driven by our values and mission. We invest in top talent through mentorship, growth, and meaningful work. We value individuality, reward integrity, and foster a diverse, high-performing team united by purpose-at work, in service, and in the community. Alpha Omega Integration, LLC (Alpha Omega) is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or veteran status, or any other protected class. #dice (remove EEO etc.) We need to remove EEO/equal-opportunity boilerplate. So remove the last paragraph about EEO and the "#dice". Also remove "Application Deadline". Also remove "Salary And Benefit Information:" maybe keep as heading Pay. We need to keep salary range. Now construct HTML. We'll have:

  About the role

  Alpha Omega is seeking a qualified Scientific Programmer in support of our NOAA National Centers for Environmental Information (NCEI) Data Stewardship Division (DSD) customer. This division works in partnership with NOAA and the broader community to develop and maintain a robust and efficient infrastructure of hardware, software, and processes to support the ingest, long-term preservation, and delivery of environmental data products spanning the depths of the ocean to the surface of the sun. In this role, this individual will be responsible for stewardship of our nation’s environmental data.

  Clearance: Public Trust. Work Location: Remote.

  Maybe we can include clearance and location as a short paragraph.

  Responsibilities

  • Infrastructure Modernization: Drive the transition of legacy systems to modern architectures.
  • System Maintenance: Proactively monitor and maintain aging infrastructure to ensure high availability and performance.