Senior Software Engineer, TS/SCI w/Poly
About the role
maybe we can put the program overview and about the role combined? Actually "About the role" heading expects description of role. We'll put the description from "About The Role" and maybe also program overview? Program overview is more about the program. Could be part of "About the role" or separate? Since we only have headings list, we could put program overview under About the role as part of description. Better: Have sections: - About the role (includes program overview and role description) - Responsibilities (maybe we can extract bullet list from the role description? The role description is a paragraph with many responsibilities; we could split into- items. But instruction: Use
- for any list of duties/requirements/benefits. The role description is not a list but prose; we can keep as
. However we could also break into list for clarity but not required. Safer to keep as
. - Requirements: maybe we can separate qualifications into Requirements (education/experience) and Skills (technical). The posting has "Qualifications" heading with experience, degree, substitution, then list of tech skills and clearance. We could split: Requirements: experience and education; Skills: technical skills and clearance. - Benefits: include enhanced benefits statement and benefits statement. - Pay: include target salary range. - Schedule: not present, so omit. We must not create sections with filler like "not specified". So omit Schedule. Now produce HTML. We need to ensure we don't repeat job title. No headings for job title. Let's craft:
About the role
Program Overview: Provides IC data management support to modernize mega data repositories, dataflow management, data provenance and compliance validation, and streaming solutions.
About The Role: Designs, develops, and implements secure cloud-based solutions that support scalable, resilient, and mission-critical environments. Architects cloud infrastructure, develops detailed technical plans, and defines specifications to support the deployment of modern cloud platforms and services. Collaborates closely with product managers, engineers, and stakeholders to define requirements and develop specifications for new cloud-based products, services, applications, and enterprise solutions. Leads the deployment and integration of cloud management platforms, continuously evaluating system performance and implementing enhancements to improve reliability, scalability, and operational efficiency. Supports the development and expansion of a cloud services portfolio, including value-added capabilities that enhance enterprise infrastructure and mission support. Develops solution recommendations and prepares Basis of Estimate (BOE) documentation for cloud initiatives. Conducts cost-benefit analyses comparing cloud solutions with alternatives such as virtual private networks, dedicated hosting, or on-premises infrastructure to identify optimal deployment strategies and areas of highest return on investment. Performs operations and maintenance of secure managed cloud platforms, ensuring system availability, performance, and compliance with security requirements. Implements automation to improve operational efficiency, including monitoring, alerting, and automated remediation of system events. Designs, develops, and maintains infrastructure as code (IaC) and leverages CI/CD pipelines to enable consistent, repeatable deployments and streamlined platform management. Supports the development of RESTful services within a Java development environment. This API serves as the source system for the ingestion and transformation of cost and usage information associated with the cloud services used within MPO. The system pushes data to several critical follow-on systems used for assessment and decision-making by corporate management and leadership.
Now Responsibilities: maybe we could extract bullet list from the role description but we already have it in About the role. Could we avoid duplication? The instruction: Use- for any list of duties/requirements/benefits. The role description is not a list; it's prose. So we can keep as
. If we want a Responsibilities section, we could reuse same content but that would duplicate. Better to not have a separate Responsibilities section if it's same as About the role. But we need to follow headings list only when posting has real specific content for it. The posting does have responsibilities described; we could put them under Responsibilities heading and omit About the role heading. However we also have program overview which is not exactly responsibilities. Could combine program overview under About the role heading and responsibilities under Responsibilities heading (splitting). Let's split: About the role: program overview + brief role purpose. Responsibilities: the detailed list. Thus:
About the role
Program Overview: Provides IC data management support to modernize mega data repositories, dataflow management, data provenance and compliance validation, and streaming solutions.
The role designs, develops, and implements secure cloud-based solutions that support scalable, resilient, and mission‑critical environments.
Then Responsibilities: list of duties. We need to extract duties from the long sentence. Could break into bullet list. Let's list duties: - Architects cloud infrastructure, develops detailed technical plans, and defines specifications to support the deployment of modern cloud platforms and services. - Collaborates closely with product managers, engineers, and stakeholders to define requirements and develop specifications for new cloud‑based products, services, applications, and enterprise solutions. - Leads the deployment and integration of cloud management platforms, continuously evaluating system performance and implementing enhancements to improve reliability, scalability, and operational efficiency. - Supports the development and expansion of a cloud services portfolio, including value‑added capabilities that enhance enterprise infrastructure and mission support. - Develops solution recommendations and prepares Basis of Estimate (BOE) documentation for cloud initiatives. - Conducts cost‑benefit analyses comparing cloud solutions with alternatives such as virtual private networks, dedicated hosting, or on‑premises infrastructure to identify optimal deployment strategies and areas of highest return on investment. - Performs operations and maintenance of secure managed cloud platforms, ensuring system availability, performance, and compliance with security requirements. - Implements automation to improve operational efficiency, including monitoring, alerting, and automated remediation of system events. - Designs, develops, and maintains infrastructure as code (IaC) and leverages CI/CD pipelines to enable consistent, repeatable deployments and streamlined platform management. - Supports the development of RESTful services within a Java development environment. This API serves as the source system for the ingestion and transformation of cost and usage information associated with the cloud services used within MPO. The system pushes data to several critical follow‑on systems used for assessment and decision‑making by corporate management and leadership. We can put each as - .
Now Requirements: education/experience.
From Qualifications: Twenty (20) years' experience as a SWE in programs and contracts of similar scope, type, and complexity is required. Bachelor's degree in computer science or related discipline from an accredited college or university is required. Four (4) years of additional SWE experience on projects with similar software processes may be substituted for a bachelor's degree.
We can put as
- ... etc.
Now Skills: Java, Spring Boot, PostgreSQL. Experience with Angular UI is a plus. Experience with deployments using Docker and/or Podman containers. Active TS/SCI clearance with polygraph clearance is required.
We can list as
- .
Now Benefits: Enhanced benefits: heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan. Plus Benefits Statement list: medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays.
We can combine into a
- list.
Now Pay: Target Salary Range: $176,000 - $282,000. plus note about determination factors. We can keep as
. Now Schedule: none. Now ensure we removed boilerplate: removed company overview fluff? Actually we kept program overview and role purpose. The initial "About Peraton" paragraph is company description; we could omit as not required heading. It's not under any heading; we could keep as a
before sections? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs not under headings. But better to keep only relevant sections. The company overview is not under a heading; could be omitted as not required. However it's substantive info about company; but not under any heading list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other content outside headings, but we should aim to follow the structure. I'd include a brief intro maybe as
but not under heading. However to be safe, we can include it under a heading like "About Peraton" but that's not in allowed list. Better to omit. Thus final HTML:
About the role
Program Overview: Provides IC data management support to modernize mega data repositories, dataflow management, data provenance and compliance validation, and streaming solutions.
The role designs, develops, and implements secure cloud-based solutions that support scalable, resilient, and mission‑critical environments.
Responsibilities
- Architects cloud infrastructure, develops detailed technical plans, and defines specifications to support the deployment of modern cloud platforms and services.
- Collaborates closely with product managers, engineers, and stakeholders to define requirements and develop specifications for new cloud‑based products, services, applications, and enterprise solutions.
- Leads the deployment and integration of cloud management platforms, continuously evaluating system performance and implementing enhancements to improve reliability, scalability, and operational efficiency.
- Supports the development and expansion of a cloud services portfolio, including value‑added capabilities that enhance enterprise infrastructure and mission support.
- Develops solution recommendations and prepares Basis of Estimate (BOE) documentation for cloud initiatives.
- Conducts cost‑benefit analyses comparing cloud solutions with alternatives such as virtual private networks, dedicated hosting, or on‑premises infrastructure to identify optimal deployment strategies and areas of highest return on investment.
- Performs operations and maintenance of secure managed cloud platforms, ensuring system availability, performance, and compliance with security requirements.
- Implements automation to improve operational efficiency, including monitoring
- list.
Now Pay: Target Salary Range: $176,000 - $282,000. plus note about determination factors. We can keep as
- .
Now Benefits: Enhanced benefits: heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan. Plus Benefits Statement list: medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays.
We can combine into a
- ... etc.
Now Skills: Java, Spring Boot, PostgreSQL. Experience with Angular UI is a plus. Experience with deployments using Docker and/or Podman containers. Active TS/SCI clearance with polygraph clearance is required.
We can list as
- for any list of duties/requirements/benefits. The role description is not a list; it's prose. So we can keep as
- for any list of duties/requirements/benefits. The role description is not a list but prose; we can keep as