Cloud Systems Architect
for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's parse the posting. Job title: Cloud Systems Architect. Not to repeat as heading. We have: Employment Type: Full-Time, Mid-level Department: Information Technology. Could be metadata; we can fold into a short
maybe. We have description: "We are seeking a Cloud Systems Architect with experience with cloud infrastructure to engineer and support public, private and hybrid clouds. The ideal candidate will be proficient in a variety of cloud hosts including Amazon Web Services and Microsoft Azure at a minimum. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities." That's about the role / company. Could be "About the role" or "About CGS". We'll use "About the role". Then we have "Skills and attributes for success:" with bullet points (starting with hyphens). Those are responsibilities? They describe duties: knowledge of updates, advisor, work with IT Security team, engineering on customer premise applications, designs and defines system architecture, determines systems specifications, coordinates design of subsystems, identifies, analyzes, resolves program support deficiencies, develops and recommends corrective actions, may provide technical guidance for DBAs and developers. Those are responsibilities/duties. Then "Qualifications:" with bullet list: Experience with and a complete understanding of the technology required for cloud computing, experience with skills to migrate applications to the cloud, ability to build relationships, ability to integrate services and tools, ability to implement SIEM, experience with meeting or exceeding requirements of cloud provider SLAs, experience with AWS and Azure, knowledge of programming languages (Python, PHP, Java, Node, Ruby on Rails), Typically a Bachelor's Degree and 6 years work experience or equivalent experience. Then "Our Commitment:" paragraph about CGS mission, values, benefits: "We care about our employees. Therefore, we offer a comprehensive benefits package.- Health, Dental, and Vision- Life Insurance- 401k- Flexible Spending Account (Health, Dependent Care, and Commuter)- Paid Time Off and Observance of State/Federal Holidays". That's benefits. Then there is salary: "#CJ$167,032.32 - $226,686.72 a year". That's pay. No schedule info. We must not include boilerplate like EEO, contact info, application instructions, etc. Remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to include a section only when posting has real specific content for it. So we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly Skills? The "Skills and attributes for success" could be considered Skills section, but we already have Responsibilities covering those bullet points. However the bullet points include both skills and responsibilities. The instruction says use headings for sections like Skills, Responsibilities, etc. We could split: Skills and attributes for success as Skills section, and then maybe Responsibilities separate? But the bullet list seems to be a mix. The posting says "Skills and attributes for success:" then bullet list. Then later "Qualifications:" bullet list. So we can treat the first bullet list as Skills (or Responsibilities). Since they are more like skills/attributes, we can put under
Skills
. Then we might also have a Responsibilities section? The posting does not have a separate responsibilities list besides that. However some of those bullet points are responsibilities (e.g., "Designs and defines system architecture..."). Could still be considered responsibilities. But we need to avoid thin sections. Perhaps combine them under one heading "Skills and Responsibilities". But the instruction says use headings like Skills, Responsibilities. We could create both but ensure they have content. If we split, we need to decide which bullet points go where. Could separate: Skills: knowledge of updates, advisor, work with IT Security team, ability to build relationships, ability to integrate services, ability to implement SIEM, knowledge of programming languages. Responsibilities: engineer and support clouds, designs and defines system architecture, determines systems specs, coordinates design of subsystems, identifies/resolves deficiencies, develops corrective actions, may provide technical guidance, experience with migrating apps, experience with meeting SLAs, experience with AWS/Azure. But that seems arbitrary.
Better to keep one section: maybe "Responsibilities and Skills". But the instruction says use headings like Skills, Responsibilities. It didn't forbid combining? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not strict that we must use those exact headings; we can use others? Probably we should stick to those headings when appropriate. Since we have both skills and responsibilities content, we could make two sections: Skills and Responsibilities, each with appropriate bullet points.
Let's extract bullet points from "Skills and attributes for success:":
- The candidate will be knowledgeable of the most recent updates and developments and act as an advisor to our customer in reference to the cloud management strategies to be employed to take advantage of the benefits offered by cloud computing such as being able to function without any restrictions to the workload, initiate as many workstations as necessary per time period and pay only for what they actually use.
- The candidate will also work with the IT Security team to manage and maintain cloud systems security of the data and network resources.
- The candidate will also be responsible for engineering on customer premise applications and systems interconnected to cloud resources.
- Designs and defines system architecture for new or existing complex computer systems.
- Determines systems specifications, input/output processes, and working parameters for hardware/software compatibility and maintenance of system security.
- Coordinates design of subsystems and integration of total system. Identifies, analyzes, and resolves program support deficiencies.
- Develops and recommends corrective actions.
- May provide technical guidance for database administrators and software developers.
Now "Qualifications:" bullet list:
- Experience with and a complete understanding of the technology required for cloud computing.
- Experience with the skills to migrate applications to the cloud.
- Be able to build relationships between the customers and the team members.
- The ability and the knowledge to integrate services and tools to any and all areas to be used such as networks and data processing.
- The ability and the knowledge to implement security information and event management to keep the customer's assets safe.
- Experience with meeting or exceeding the requirements of cloud provider service-level agreements
- Experience with AWS and Azure.
- Knowledge of a multitude of programming languages including Python, PHP, Java, Node and Ruby on Rails.
- Typically a Bachelor's Degree and 6 years work experience or equivalent experience.
Note some overlap: building relationships, integrate services, implement SIEM appear in both lists. We need to preserve all substantive information; we can keep duplicates? Might be okay but could be redundant. However we should not invent or summarize away detail; we can keep them as they appear in each section. If we split into Skills and Qualifications, duplicates may appear in both; that's okay as they are from original.
But we also have a paragraph about the role at start; we can put that under About the role.
Benefits: list.
Pay: salary.
We have no schedule.
We must not include boilerplate like EEO, contact info, application instructions, etc. Also remove duplicated lines like "Contact Government Services (CGS) strives..." maybe part of Our Commitment; we can keep that as part of About the role or maybe a separate section "About CGS". But we already have About the role; we could incorporate that paragraph there.
Let's craft HTML:
About the role
We are seeking a Cloud Systems Architect with experience with cloud infrastructure to engineer and support public, private and hybrid clouds. The ideal candidate will be proficient in a variety of cloud hosts including Amazon Web Services and Microsoft Azure at a minimum. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities.
Maybe also include employment type and department as a short p: "Employment Type: Full-Time, Mid-level | Department: Information Technology". Could be included in About the role paragraph or separate small p. We'll add a p after the heading.
Then Skills:
Skills
- The candidate will be knowledgeable of the most recent updates and developments and act as an advisor to our customer in reference to the cloud management strategies to be employed to take advantage of the benefits offered by cloud computing such as being able to function without any restrictions to the workload, initiate as many workstations as necessary per time period and pay only for what they actually use.
- The candidate will also work with the IT Security team to manage and maintain cloud systems security of the data and network resources.
- The candidate will also be responsible for engineering on customer premise applications and systems interconnected to cloud resources.
- Designs and defines system architecture for new or existing complex computer systems.
- Determines systems specifications, input/output processes, and working parameters for hardware/software compatibility and maintenance of system security.
- Coordinates design of subsystems and integration of total system. Identifies, analyzes, and resolves program support deficiencies.
- Develops and recommends corrective actions.
- May provide technical guidance for database administrators and software developers.
Then Responsibilities? Actually the above could be considered responsibilities. But we already used Skills. We could rename this section to "Responsibilities". However the bullet list includes skills like knowledge of updates, advisor, etc. Might be better to call it "Responsibilities". But the instruction says we can use Skills heading. Let's decide: We'll use "Responsibilities" for the bullet list that describes duties, and "Skills" for the qualifications list? But qualifications list includes experience, education, etc. Actually qualifications list is more about required experience and education. So we could have:
- Responsibilities: bullet list from "Skills and attributes for success:" (since they describe what the candidate will do).
- Qualifications: bullet list from "Qualifications:" (experience, education, etc.)
- Skills: maybe not needed separately.
But we have both "Skills and attributes for success" and "Qualifications". The qualifications list includes skills like ability to integrate services, implement SIEM, knowledge of programming languages, etc. So there is overlap.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine Skills and Qualifications into one section called "Qualifications and Skills". But we need to follow heading examples; we could use "Qualifications" as heading and include both experience and skills. That would be acceptable.
Thus we have sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
Let's assign:
About the role: introductory paragraph + employment type/department.
Responsibilities: bullet list from "Skills and attributes for success:" (the duties).
Qualifications: bullet list from "Qualifications:" (experience, education, etc.)
Benefits: list from benefits.
Pay: salary.
Now ensure we don't include boilerplate: remove "Our Commitment:" paragraph? Actually we used part of it for benefits; the earlier paragraph about CGS mission could be considered part of About the role. We'll incorporate
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to include a section only when posting has real specific content for it. So we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly Skills? The "Skills and attributes for success" could be considered Skills section, but we already have Responsibilities covering those bullet points. However the bullet points include both skills and responsibilities. The instruction says use headings for sections like Skills, Responsibilities, etc. We could split: Skills and attributes for success as Skills section, and then maybe Responsibilities separate? But the bullet list seems to be a mix. The posting says "Skills and attributes for success:" then bullet list. Then later "Qualifications:" bullet list. So we can treat the first bullet list as Skills (or Responsibilities). Since they are more like skills/attributes, we can put under
Skills
. Then we might also have a Responsibilities section? The posting does not have a separate responsibilities list besides that. However some of those bullet points are responsibilities (e.g., "Designs and defines system architecture..."). Could still be considered responsibilities. But we need to avoid thin sections. Perhaps combine them under one heading "Skills and Responsibilities". But the instruction says use headings like Skills, Responsibilities. We could create both but ensure they have content. If we split, we need to decide which bullet points go where. Could separate: Skills: knowledge of updates, advisor, work with IT Security team, ability to build relationships, ability to integrate services, ability to implement SIEM, knowledge of programming languages. Responsibilities: engineer and support clouds, designs and defines system architecture, determines systems specs, coordinates design of subsystems, identifies/resolves deficiencies, develops corrective actions, may provide technical guidance, experience with migrating apps, experience with meeting SLAs, experience with AWS/Azure. But that seems arbitrary. Better to keep one section: maybe "Responsibilities and Skills". But the instruction says use headings like Skills, Responsibilities. It didn't forbid combining? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not strict that we must use those exact headings; we can use others? Probably we should stick to those headings when appropriate. Since we have both skills and responsibilities content, we could make two sections: Skills and Responsibilities, each with appropriate bullet points.
Let's extract bullet points from "Skills and attributes for success:":
- The candidate will be knowledgeable of the most recent updates and developments and act as an advisor to our customer in reference to the cloud management strategies to be employed to take advantage of the benefits offered by cloud computing such as being able to function without any restrictions to the workload, initiate as many workstations as necessary per time period and pay only for what they actually use.
- The candidate will also work with the IT Security team to manage and maintain cloud systems security of the data and network resources.
- The candidate will also be responsible for engineering on customer premise applications and systems interconnected to cloud resources.
- Designs and defines system architecture for new or existing complex computer systems.
- Determines systems specifications, input/output processes, and working parameters for hardware/software compatibility and maintenance of system security.
- Coordinates design of subsystems and integration of total system. Identifies, analyzes, and resolves program support deficiencies.
- Develops and recommends corrective actions.
- May provide technical guidance for database administrators and software developers.
Now "Qualifications:" bullet list:
- Experience with and a complete understanding of the technology required for cloud computing.
- Experience with the skills to migrate applications to the cloud.
- Be able to build relationships between the customers and the team members.
- The ability and the knowledge to integrate services and tools to any and all areas to be used such as networks and data processing.
- The ability and the knowledge to implement security information and event management to keep the customer's assets safe.
- Experience with meeting or exceeding the requirements of cloud provider service-level agreements
- Experience with AWS and Azure.
- Knowledge of a multitude of programming languages including Python, PHP, Java, Node and Ruby on Rails.
- Typically a Bachelor's Degree and 6 years work experience or equivalent experience.
Note some overlap: building relationships, integrate services, implement SIEM appear in both lists. We need to preserve all substantive information; we can keep duplicates? Might be okay but could be redundant. However we should not invent or summarize away detail; we can keep them as they appear in each section. If we split into Skills and Qualifications, duplicates may appear in both; that's okay as they are from original.
But we also have a paragraph about the role at start; we can put that under About the role.
Benefits: list.
Pay: salary.
We have no schedule.
We must not include boilerplate like EEO, contact info, application instructions, etc. Also remove duplicated lines like "Contact Government Services (CGS) strives..." maybe part of Our Commitment; we can keep that as part of About the role or maybe a separate section "About CGS". But we already have About the role; we could incorporate that paragraph there.
Let's craft HTML:
About the role
We are seeking a Cloud Systems Architect with experience with cloud infrastructure to engineer and support public, private and hybrid clouds. The ideal candidate will be proficient in a variety of cloud hosts including Amazon Web Services and Microsoft Azure at a minimum. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities.
Maybe also include employment type and department as a short p: "Employment Type: Full-Time, Mid-level | Department: Information Technology". Could be included in About the role paragraph or separate small p. We'll add a p after the heading. Then Skills:Skills
- The candidate will be knowledgeable of the most recent updates and developments and act as an advisor to our customer in reference to the cloud management strategies to be employed to take advantage of the benefits offered by cloud computing such as being able to function without any restrictions to the workload, initiate as many workstations as necessary per time period and pay only for what they actually use.
- The candidate will also work with the IT Security team to manage and maintain cloud systems security of the data and network resources.
- The candidate will also be responsible for engineering on customer premise applications and systems interconnected to cloud resources.
- Designs and defines system architecture for new or existing complex computer systems.
- Determines systems specifications, input/output processes, and working parameters for hardware/software compatibility and maintenance of system security.
- Coordinates design of subsystems and integration of total system. Identifies, analyzes, and resolves program support deficiencies.
- Develops and recommends corrective actions.
- May provide technical guidance for database administrators and software developers.