Cloud and Storage Engineer
for section headings. Use - for any list. Use
for prose.
We need to preserve all substantive information. Do not invent or summarize away detail. So we need to include all bullet points exactly as given? We can keep them as list items preserving text. Should we keep the dash at start? Probably we can keep the bullet text without leading dash.
We need to decide sections: About the role (paragraph). Responsibilities (maybe list of duties). Requirements (maybe experience/skills). Qualifications (education/experience). Skills (maybe technical skills). Benefits (list). Pay (paragraph). Schedule (paragraph). Ensure we don't create empty sections.
Let's extract content.
About the role: "CGS is seeking a Cloud and Storage Engineer to develop and implement full-scale Storage Area Network (SAN) architecture for a large EMC-based SAN infrastructure in support of a large federal agency. The ideal candidate will be able to excel in a fast-paced environment and successfully produce standards and implementation processes for storage configuration, optimization, replication, and storage security. 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 a big paragraph. Could split but it's okay as one
.
Now responsibilities: The bullet list under "Skills and attributes for success:" includes many items. Let's list them:
- Develops and implements full scale Storage Area Network (SAN) architecture for a large EMC-based SAN infrastructure in a multi-enterprise, complex, geographically dispersed solution; ranging from single servers to multi-tier, multi-platform solutions connected through fiber channel to multiple EMC Storage Arrays with petabytes of storage capacity.
- The SAN architecture considers the following aspects relating to SAN: performance, capacity, replication, disaster recovery, backup disk storage, and backup & recovery.
- Defines and sets a strategic direction for the SAN and backup environment.
- Designs and implements customer storage requirements into an enterprise solution that will be developed, installed, configured, and deployed in the environment.
- Provides overall storage and backup capacity planning, and utilization reporting.
- Produces standards and implementation processes for storage configuration, optimization, replication, virtualization, storage security, and disaster recovery.
- Troubleshoots complex SAN infrastructure issues and works with customers both internal and external to effectively resolve issues.
- Reviews, plans, and participates in executing regularly scheduled maintenances and/or projects on the storage infrastructure.
- Develops technical documentation, tiered storage and storage-as-a-service roadmaps, presentations, and cost models.
- Responsible for managing, maintaining, and developing the SAN infrastructure as part of a team to ensure 24/7/365 uptime.
- Architects and maintains private cloud environment. Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired.
- Performs security related tasks which include, but are not limited to, documentation, vulnerability scan review, assessment support, patch management, and auditing as required.
We could treat these as responsibilities. Some are more like skills (experience with Gov Cloud). But we can keep all under Responsibilities.
Now Requirements: maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's a desired skill, not requirement. But we could put under Skills.
Qualifications: Bachelor’s in computer science, business, or other relevant discipline. Eight (8) years of relevant work experience may be substituted for degree requirement. Must have significant, direct experience in Dell EMC products such as OneFile System (OneFS), MDS SAN switches, storage arrays (Unity, Isilon, VNS, and Data Domain), and RecoverPoint.
Skills: maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." Already mentioned.
But we also have "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's a skill.
Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." Already.
We could also include "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." as skill.
Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." is the only skill.
But we also have "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." Already.
Now Benefits: list: Health, Dental, and Vision; Life Insurance; 401k; Flexible Spending Account (Health, Dependent Care, and Commuter); Paid Time Off and Observance of State/Federal Holidays.
Pay: "$100,949.33 - $137,002.66 a year". The text includes "#CJ$100,949.33 - $137,002.66 a year". We'll output the range.
Schedule: "Full-Time". Could also mention Experienced but that's not schedule.
Now we need to avoid boilerplate: remove "Our Commitment:" paragraph? That's about values; maybe we can incorporate into About the role? But it's not required. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our Commitment:" paragraph is not boilerplate; it's about company values. Could keep as part of About the role? But we already have About the role paragraph. Might be redundant. However we need to preserve ALL substantive information. So we should include that info somewhere. Could add a section "About CGS" but not allowed headings list only includes specific headings. We could incorporate into About the role paragraph. But we must not invent headings. We could add another
under About the role? Actually we can just have multiple
elements; they don't need headings. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't forbid multiple
under a section. So we can have About the role section with multiple paragraphs: one about the role, another about CGS commitment.
Thus:
About the role
CGS is seeking a Cloud and Storage Engineer to develop and implement full-scale Storage Area Network (SAN) architecture for a large EMC-based SAN infrastructure in support of a large federal agency. The ideal candidate will be able to excel in a fast-paced environment and successfully produce standards and implementation processes for storage configuration, optimization, replication, and storage security. 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.
Our Commitment: Contact Government Services (CGS) strives to simplify and enhance government bureaucracy through the optimization of human, technical, and financial resources. We combine cutting-edge technology with world-class personnel to deliver customized solutions that fit our client’s specific needs. We are committed to solving the most challenging and dynamic problems. For the past seven years, we’ve been growing our government-contracting portfolio, and along the way, we’ve created valuable partnerships by demonstrating a commitment to honesty, professionalism, and quality work. Here at CGS we value honesty through hard work and self-awareness, professionalism in all we do, and to deliver the best quality to our consumers mending those relations for years to come. We care about our employees. Therefore, we offer a comprehensive benefits package.
Now Responsibilities: list of duties.
We'll create Responsibilities
with each bullet as - .
Now Requirements: maybe we can put education/experience substitution as Requirements? Actually qualifications includes education and experience. We'll make Qualifications section for education/experience substitution and specific product experience. Requirements could be maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." but that's desired not required. Could put under Skills.
Better: Requirements: maybe none specific besides the qualifications. But we need to include a section only if posting has real specific content. The posting has qualifications (education/experience) and specific product experience. So we can put those under Qualifications. Requirements could be omitted if no distinct content. However we have "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's a desired skill, not requirement. Could put under Skills.
Thus we may have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule.
Check if we need Requirements: maybe we can include "Eight (8) years of relevant work experience may be substituted for degree requirement." That's qualification. So Qualifications covers.
Now Skills: list desired experience with Gov Cloud/hybrid cloud. Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's it.
Now Benefits: list.
Pay: paragraph.
Schedule: paragraph.
Now ensure we don't repeat job title as heading. Good.
Now output HTML fragment.
Let's craft.
We need to escape any special characters? Not needed.
Make sure to
for prose. We need to preserve all substantive information. Do not invent or summarize away detail. So we need to include all bullet points exactly as given? We can keep them as list items preserving text. Should we keep the dash at start? Probably we can keep the bullet text without leading dash. We need to decide sections: About the role (paragraph). Responsibilities (maybe list of duties). Requirements (maybe experience/skills). Qualifications (education/experience). Skills (maybe technical skills). Benefits (list). Pay (paragraph). Schedule (paragraph). Ensure we don't create empty sections. Let's extract content. About the role: "CGS is seeking a Cloud and Storage Engineer to develop and implement full-scale Storage Area Network (SAN) architecture for a large EMC-based SAN infrastructure in support of a large federal agency. The ideal candidate will be able to excel in a fast-paced environment and successfully produce standards and implementation processes for storage configuration, optimization, replication, and storage security. 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 a big paragraph. Could split but it's okay as one
. Now responsibilities: The bullet list under "Skills and attributes for success:" includes many items. Let's list them: - Develops and implements full scale Storage Area Network (SAN) architecture for a large EMC-based SAN infrastructure in a multi-enterprise, complex, geographically dispersed solution; ranging from single servers to multi-tier, multi-platform solutions connected through fiber channel to multiple EMC Storage Arrays with petabytes of storage capacity. - The SAN architecture considers the following aspects relating to SAN: performance, capacity, replication, disaster recovery, backup disk storage, and backup & recovery. - Defines and sets a strategic direction for the SAN and backup environment. - Designs and implements customer storage requirements into an enterprise solution that will be developed, installed, configured, and deployed in the environment. - Provides overall storage and backup capacity planning, and utilization reporting. - Produces standards and implementation processes for storage configuration, optimization, replication, virtualization, storage security, and disaster recovery. - Troubleshoots complex SAN infrastructure issues and works with customers both internal and external to effectively resolve issues. - Reviews, plans, and participates in executing regularly scheduled maintenances and/or projects on the storage infrastructure. - Develops technical documentation, tiered storage and storage-as-a-service roadmaps, presentations, and cost models. - Responsible for managing, maintaining, and developing the SAN infrastructure as part of a team to ensure 24/7/365 uptime. - Architects and maintains private cloud environment. Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired. - Performs security related tasks which include, but are not limited to, documentation, vulnerability scan review, assessment support, patch management, and auditing as required. We could treat these as responsibilities. Some are more like skills (experience with Gov Cloud). But we can keep all under Responsibilities. Now Requirements: maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's a desired skill, not requirement. But we could put under Skills. Qualifications: Bachelor’s in computer science, business, or other relevant discipline. Eight (8) years of relevant work experience may be substituted for degree requirement. Must have significant, direct experience in Dell EMC products such as OneFile System (OneFS), MDS SAN switches, storage arrays (Unity, Isilon, VNS, and Data Domain), and RecoverPoint. Skills: maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." Already mentioned. But we also have "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's a skill. Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." Already. We could also include "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." as skill. Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." is the only skill. But we also have "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." Already. Now Benefits: list: Health, Dental, and Vision; Life Insurance; 401k; Flexible Spending Account (Health, Dependent Care, and Commuter); Paid Time Off and Observance of State/Federal Holidays. Pay: "$100,949.33 - $137,002.66 a year". The text includes "#CJ$100,949.33 - $137,002.66 a year". We'll output the range. Schedule: "Full-Time". Could also mention Experienced but that's not schedule. Now we need to avoid boilerplate: remove "Our Commitment:" paragraph? That's about values; maybe we can incorporate into About the role? But it's not required. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our Commitment:" paragraph is not boilerplate; it's about company values. Could keep as part of About the role? But we already have About the role paragraph. Might be redundant. However we need to preserve ALL substantive information. So we should include that info somewhere. Could add a section "About CGS" but not allowed headings list only includes specific headings. We could incorporate into About the role paragraph. But we must not invent headings. We could add another
under About the role? Actually we can just have multiple
elements; they don't need headings. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't forbid multiple
under a section. So we can have About the role section with multiple paragraphs: one about the role, another about CGS commitment.
Thus:
About the role
CGS is seeking a Cloud and Storage Engineer to develop and implement full-scale Storage Area Network (SAN) architecture for a large EMC-based SAN infrastructure in support of a large federal agency. The ideal candidate will be able to excel in a fast-paced environment and successfully produce standards and implementation processes for storage configuration, optimization, replication, and storage security. 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.
Our Commitment: Contact Government Services (CGS) strives to simplify and enhance government bureaucracy through the optimization of human, technical, and financial resources. We combine cutting-edge technology with world-class personnel to deliver customized solutions that fit our client’s specific needs. We are committed to solving the most challenging and dynamic problems. For the past seven years, we’ve been growing our government-contracting portfolio, and along the way, we’ve created valuable partnerships by demonstrating a commitment to honesty, professionalism, and quality work. Here at CGS we value honesty through hard work and self-awareness, professionalism in all we do, and to deliver the best quality to our consumers mending those relations for years to come. We care about our employees. Therefore, we offer a comprehensive benefits package.
Now Responsibilities: list of duties.
We'll create Responsibilities
with each bullet as - .
Now Requirements: maybe we can put education/experience substitution as Requirements? Actually qualifications includes education and experience. We'll make Qualifications section for education/experience substitution and specific product experience. Requirements could be maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." but that's desired not required. Could put under Skills.
Better: Requirements: maybe none specific besides the qualifications. But we need to include a section only if posting has real specific content. The posting has qualifications (education/experience) and specific product experience. So we can put those under Qualifications. Requirements could be omitted if no distinct content. However we have "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's a desired skill, not requirement. Could put under Skills.
Thus we may have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule.
Check if we need Requirements: maybe we can include "Eight (8) years of relevant work experience may be substituted for degree requirement." That's qualification. So Qualifications covers.
Now Skills: list desired experience with Gov Cloud/hybrid cloud. Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's it.
Now Benefits: list.
Pay: paragraph.
Schedule: paragraph.
Now ensure we don't repeat job title as heading. Good.
Now output HTML fragment.
Let's craft.
We need to escape any special characters? Not needed.
Make sure to
for prose. It doesn't forbid multiple
under a section. So we can have About the role section with multiple paragraphs: one about the role, another about CGS commitment. Thus:
About the role
CGS is seeking a Cloud and Storage Engineer to develop and implement full-scale Storage Area Network (SAN) architecture for a large EMC-based SAN infrastructure in support of a large federal agency. The ideal candidate will be able to excel in a fast-paced environment and successfully produce standards and implementation processes for storage configuration, optimization, replication, and storage security. 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.
Our Commitment: Contact Government Services (CGS) strives to simplify and enhance government bureaucracy through the optimization of human, technical, and financial resources. We combine cutting-edge technology with world-class personnel to deliver customized solutions that fit our client’s specific needs. We are committed to solving the most challenging and dynamic problems. For the past seven years, we’ve been growing our government-contracting portfolio, and along the way, we’ve created valuable partnerships by demonstrating a commitment to honesty, professionalism, and quality work. Here at CGS we value honesty through hard work and self-awareness, professionalism in all we do, and to deliver the best quality to our consumers mending those relations for years to come. We care about our employees. Therefore, we offer a comprehensive benefits package.
Now Responsibilities: list of duties. We'll createResponsibilities
- with each bullet as
- . Now Requirements: maybe we can put education/experience substitution as Requirements? Actually qualifications includes education and experience. We'll make Qualifications section for education/experience substitution and specific product experience. Requirements could be maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." but that's desired not required. Could put under Skills. Better: Requirements: maybe none specific besides the qualifications. But we need to include a section only if posting has real specific content. The posting has qualifications (education/experience) and specific product experience. So we can put those under Qualifications. Requirements could be omitted if no distinct content. However we have "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's a desired skill, not requirement. Could put under Skills. Thus we may have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Check if we need Requirements: maybe we can include "Eight (8) years of relevant work experience may be substituted for degree requirement." That's qualification. So Qualifications covers. Now Skills: list desired experience with Gov Cloud/hybrid cloud. Also maybe "Professional experience with Gov Cloud (AWS, Azure, etc.) and hybrid cloud architectures desired." That's it. Now Benefits: list. Pay: paragraph. Schedule: paragraph. Now ensure we don't repeat job title as heading. Good. Now output HTML fragment. Let's craft. We need to escape any special characters? Not needed. Make sure to