Network Security Administrator
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include sections that have real specific content. The posting does not mention Benefits, Pay, Schedule. So we should not include those headings. We need to map content to appropriate headings: "About the role" could be Position Summary. "Responsibilities" could be Essential Functions. "Requirements" could be the overall Requirements section, but we also have subheadings like Qualifications, Skills, etc. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings as appropriate. We should not repeat the job title as heading. We need to preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. Also remove duplicated lines. There's some duplication: "Ensures network equipment, software, and traffic is operating at optimal levels." appears twice? Actually appears once in Essential Functions list and later again? Let's check: In Essential Functions list: "Configures, installs, maintains, and supports various network devices and services, such as, but not limited to, routers, switches, firewalls, VLAN’s, etc. Ensures network equipment, software, and traffic is operating at optimal levels. Performs network maintenance and upgrades. Maintains network security, reliability, and integrity. Ensures network equipment, components, and software is up to date per vendor and regulatory requirements. Monitors and evaluates network resources and systems performance. Responds to network troubleshooting issues. Assists Information Technology Director, and Information Technology Manager with network compliance requirements (PCI, etc.). Performs all duties in accordance with Chinook Winds Casino Resort customer service standards. Provides input or recommendations for improvements and changes in processes or services. All other duties as assigned." There's duplication of "Ensures network equipment, software, and traffic is operating at optimal levels." appears only once? Actually there is also later "Ensures network equipment, components, and software is up to date per vendor and regulatory requirements." That's different. So no duplication.
We need to format lists with - . For prose use
. For headings use
. We need to decide which sections to include.
We have Position Summary -> About the role.
Essential Functions -> Responsibilities.
Requirements -> we could have a heading Requirements and then sub-sections like Qualifications, Skills, Education, Experience, Certificates & Licenses, Physical Demands, Work Environment, Working Conditions. But the instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. So we could have Qualifications
etc. But we also need to include Requirements maybe as a heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Requirements as a heading and then inside we could have subheadings? But they didn't forbid subheadings; they just gave examples. We could just use Requirements as a heading and then list the content as paragraphs/lists. However they also said "Prefer a few substantive sections over many thin ones." So maybe we should combine similar items into broader sections: About the role, Responsibilities, Requirements (which includes Qualifications, Skills, Education, Experience, Certificates, Physical Demands, Work Environment, Working Conditions). That seems reasonable.
We must not include headings with filler text like "commensurate with experience". Not present.
We need to preserve all substantive information. So we need to include all details: Position Summary, Essential Functions list, Competency Statements list, Education, Experience, Computer Skills, Certificates & Licenses, Physical Demands (with table-like list), Work Environment, Working Conditions.
We need to format lists with - . For Competency Statements, it's a list of bullet points: Communication Skills - Ability..., Customer Oriented..., Enthusiastic..., Interpersonal... So we can make
- Communication Skills - Ability to communicate effectively with others verbally.
etc.
Education: "High School Diploma or GED. Bachelor’s degree with emphasis in computer studies preferred." That's prose; could be .
Experience: "3 years of network engineer/administrator experience with demonstrated competency in network infrastructure and backbone configuration, support, and maintenance."
.
Computer Skills: "Experience with HP PCM preferred. Administrator level knowledge of network equipment and software required."
.
Certificates & Licenses: "Industry network certification preferred. Required to obtain Siletz Tribal Gaming License."
.
Physical Demands: This is a detailed list with categories: Lift/Carry, Stand, Walk, Sit, Handling/Fingering, Reach Outward, Reach Above Shoulder, Push/Pull, Climb, Crawl, Squat or Kneel, Bend, etc. Each with frequency and weight. We need to preserve all. Could format as
- Lift/Carry: Stand Frequently 10 lbs or less Frequently ...
but that seems messy. Better to keep as preserving the original text? The instruction says use
- for any list of duties/requirements/benefits. Physical Demands is a list of items, so we should use
- . Each line could be a list item.
We need to parse the Physical Demands block:
"Physical Demands Physical Demands Lift/Carry Stand Frequently 10 lbs or less Frequently Walk Frequently 11-20 lbs Frequently Sit Constantly 21-50 lbs Occasionally Handling/Fingering Constantly 51-100 lbs Occasionally Reach Outward Constantly Over 100 lbs Not Applicable Reach Above Shoulder Occasionally Push/Pull Climb Not Applicable 12 lbs or less Frequently Crawl Occasionally 13-25 lbs Occasionally Squat or Kneel Occasionally 26-40 lbs Occasionally Bend Frequently 41-100 lbs Occasionally Not Applicable- Activity is not applicable to this occupation. Occasionally- Occupation requires this activity up to 33% of the time (0-2.5+ hours/day. Frequently- Occupation requires this activity from 33%-66% of the time (2.5-5.5+ hours/day. Constantly- Occupation requires this activity more than 66% of the time (5.5+ hours/day."
There's duplication of "Physical Demands". We need to preserve all substantive info but remove duplicated lines. So we should have one "Physical Demands" heading? Actually we are not using heading for Physical Demands; it's inside Requirements section. We'll just list items.
We need to clean up duplication: The block starts with "Physical Demands Physical Demands". We'll treat as one heading maybe not needed. We'll just list the items after that.
Let's extract items:
- Lift/Carry Stand Frequently 10 lbs or less Frequently
- Walk Frequently 11-20 lbs Frequently
- Sit Constantly 21-50 lbs Occasionally
- Handling/Fingering Constantly 51-100 lbs Occasionally
- Reach Outward Constantly Over 100 lbs Not Applicable
- Reach Above Shoulder Occasionally
- Push/Pull Climb Not Applicable 12 lbs or less Frequently
- Crawl Occasionally 13-25 lbs Occasionally
- Squat or Kneel Occasionally 26-40 lbs Occasionally
- Bend Frequently 41-100 lbs Occasionally
- Not Applicable- Activity is not applicable to this occupation.
- Occasionally- Occupation requires this activity up to 33% of the time (0-2.5+ hours/day.
- Frequently- Occupation requires this activity from 33%-66% of the time (2.5-5.5+ hours/day.
- Constantly- Occupation requires this activity more than 66% of the time (5.5+ hours/day.
We need to ensure we keep the definitions of Occasionally, Frequently, Constantly.
We'll format each as
- .
Work Environment: "Work will take place in a small office environment with occasional exposure to a busy resort and gaming environment with multiple distractions. Some work may take place in sensitive areas including the gaming floor. The noise level in the work environment is usually quite to moderate. Occasionally the work environment will be in locations exposed to smoke and the associate effects." We'll put as
.
Working Conditions: "Conditions of employment include passing a pre-employment drug screen, a background investigation, and completing a 180-day introductory period."
.
Now we need to ensure we don't include headings for Benefits, Pay, Schedule.
We'll output:
About the role
Responsible for administering, monitoring, and maintaining a growing resort-wide network infrastructure and backbone, and all associated equipment and software. Assists Information Technology Director, and Information Technology Manager in assuring that all networks and associated activities are fully operational and performing in accordance with company requirements.
Responsibilities
- Configures, installs, maintains, and supports various network devices and services, such as, but not limited to, routers, switches, firewalls, VLAN’s, etc.
- Ensures network equipment, software, and traffic is operating at optimal levels.
- Performs network maintenance and upgrades.
- Maintains network security, reliability, and integrity.
- Ensures network equipment, components, and software is up to date per vendor and regulatory requirements.
- Monitors and evaluates network resources and systems performance.
- Responds to network troubleshooting issues.
- Assists Information Technology Director, and Information Technology Manager with network compliance requirements (PCI, etc.).
- Performs all duties in accordance with Chinook Winds Casino Resort customer service standards.
- Provides input or recommendations for improvements and changes in processes or services.
- All other duties as assigned.
Requirements
Position Qualifications
maybe we shouldn't use h4 because only h3 allowed? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but to be safe we could avoid other heading levels and just use
for sub-sections. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we could use those exact headings. So we could have Qualifications
etc. But we already have a Requirements heading; we could then have subheadings like Qualifications, Skills, Education, Experience, Certificates & Licenses, Physical Demands, Work Environment, Working Conditions as as well? That would be many headings. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we should keep Requirements as one section and include all details inside as paragraphs and lists, without further headings. That would be fewer sections.
Thus we will have:
About the role
...
Responsibilities
...
Requirements
Position Qualifications: Workers in this position must be 21 or older.
Competency Stat
- . For prose use
. For headings use
. We need to decide which sections to include. We have Position Summary -> About the role. Essential Functions -> Responsibilities. Requirements -> we could have a heading Requirements and then sub-sections like Qualifications, Skills, Education, Experience, Certificates & Licenses, Physical Demands, Work Environment, Working Conditions. But the instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. So we could have
Qualifications
etc. But we also need to include Requirements maybe as a heading? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Requirements as a heading and then inside we could have subheadings? But they didn't forbid subheadings; they just gave examples. We could just use Requirements as a heading and then list the content as paragraphs/lists. However they also said "Prefer a few substantive sections over many thin ones." So maybe we should combine similar items into broader sections: About the role, Responsibilities, Requirements (which includes Qualifications, Skills, Education, Experience, Certificates, Physical Demands, Work Environment, Working Conditions). That seems reasonable. We must not include headings with filler text like "commensurate with experience". Not present. We need to preserve all substantive information. So we need to include all details: Position Summary, Essential Functions list, Competency Statements list, Education, Experience, Computer Skills, Certificates & Licenses, Physical Demands (with table-like list), Work Environment, Working Conditions. We need to format lists with
- . For Competency Statements, it's a list of bullet points: Communication Skills - Ability..., Customer Oriented..., Enthusiastic..., Interpersonal... So we can make
- Communication Skills - Ability to communicate effectively with others verbally. etc. Education: "High School Diploma or GED. Bachelor’s degree with emphasis in computer studies preferred." That's prose; could be
- Lift/Carry: Stand Frequently 10 lbs or less Frequently ... but that seems messy. Better to keep as
- for any list of duties/requirements/benefits. Physical Demands is a list of items, so we should use
- . Each line could be a list item. We need to parse the Physical Demands block: "Physical Demands Physical Demands Lift/Carry Stand Frequently 10 lbs or less Frequently Walk Frequently 11-20 lbs Frequently Sit Constantly 21-50 lbs Occasionally Handling/Fingering Constantly 51-100 lbs Occasionally Reach Outward Constantly Over 100 lbs Not Applicable Reach Above Shoulder Occasionally Push/Pull Climb Not Applicable 12 lbs or less Frequently Crawl Occasionally 13-25 lbs Occasionally Squat or Kneel Occasionally 26-40 lbs Occasionally Bend Frequently 41-100 lbs Occasionally Not Applicable- Activity is not applicable to this occupation. Occasionally- Occupation requires this activity up to 33% of the time (0-2.5+ hours/day. Frequently- Occupation requires this activity from 33%-66% of the time (2.5-5.5+ hours/day. Constantly- Occupation requires this activity more than 66% of the time (5.5+ hours/day." There's duplication of "Physical Demands". We need to preserve all substantive info but remove duplicated lines. So we should have one "Physical Demands" heading? Actually we are not using heading for Physical Demands; it's inside Requirements section. We'll just list items. We need to clean up duplication: The block starts with "Physical Demands Physical Demands". We'll treat as one heading maybe not needed. We'll just list the items after that. Let's extract items: - Lift/Carry Stand Frequently 10 lbs or less Frequently - Walk Frequently 11-20 lbs Frequently - Sit Constantly 21-50 lbs Occasionally - Handling/Fingering Constantly 51-100 lbs Occasionally - Reach Outward Constantly Over 100 lbs Not Applicable - Reach Above Shoulder Occasionally - Push/Pull Climb Not Applicable 12 lbs or less Frequently - Crawl Occasionally 13-25 lbs Occasionally - Squat or Kneel Occasionally 26-40 lbs Occasionally - Bend Frequently 41-100 lbs Occasionally - Not Applicable- Activity is not applicable to this occupation. - Occasionally- Occupation requires this activity up to 33% of the time (0-2.5+ hours/day. - Frequently- Occupation requires this activity from 33%-66% of the time (2.5-5.5+ hours/day. - Constantly- Occupation requires this activity more than 66% of the time (5.5+ hours/day. We need to ensure we keep the definitions of Occasionally, Frequently, Constantly. We'll format each as
- .
Work Environment: "Work will take place in a small office environment with occasional exposure to a busy resort and gaming environment with multiple distractions. Some work may take place in sensitive areas including the gaming floor. The noise level in the work environment is usually quite to moderate. Occasionally the work environment will be in locations exposed to smoke and the associate effects." We'll put as
. Working Conditions: "Conditions of employment include passing a pre-employment drug screen, a background investigation, and completing a 180-day introductory period."
. Now we need to ensure we don't include headings for Benefits, Pay, Schedule. We'll output:
About the role
Responsible for administering, monitoring, and maintaining a growing resort-wide network infrastructure and backbone, and all associated equipment and software. Assists Information Technology Director, and Information Technology Manager in assuring that all networks and associated activities are fully operational and performing in accordance with company requirements.
Responsibilities
- Configures, installs, maintains, and supports various network devices and services, such as, but not limited to, routers, switches, firewalls, VLAN’s, etc.
- Ensures network equipment, software, and traffic is operating at optimal levels.
- Performs network maintenance and upgrades.
- Maintains network security, reliability, and integrity.
- Ensures network equipment, components, and software is up to date per vendor and regulatory requirements.
- Monitors and evaluates network resources and systems performance.
- Responds to network troubleshooting issues.
- Assists Information Technology Director, and Information Technology Manager with network compliance requirements (PCI, etc.).
- Performs all duties in accordance with Chinook Winds Casino Resort customer service standards.
- Provides input or recommendations for improvements and changes in processes or services.
- All other duties as assigned.
Requirements
Position Qualifications
maybe we shouldn't use h4 because only h3 allowed? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but to be safe we could avoid other heading levels and just use
for sub-sections. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we could use those exact headings. So we could have
Qualifications
etc. But we already have a Requirements heading; we could then have subheadings like Qualifications, Skills, Education, Experience, Certificates & Licenses, Physical Demands, Work Environment, Working Conditions asas well? That would be many headings. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we should keep Requirements as one section and include all details inside as paragraphs and lists, without further headings. That would be fewer sections. Thus we will have:
About the role
...
Responsibilities
- ...
Requirements
Position Qualifications: Workers in this position must be 21 or older.
Competency Stat
. Experience: "3 years of network engineer/administrator experience with demonstrated competency in network infrastructure and backbone configuration, support, and maintenance."
. Computer Skills: "Experience with HP PCM preferred. Administrator level knowledge of network equipment and software required."
. Certificates & Licenses: "Industry network certification preferred. Required to obtain Siletz Tribal Gaming License."
. Physical Demands: This is a detailed list with categories: Lift/Carry, Stand, Walk, Sit, Handling/Fingering, Reach Outward, Reach Above Shoulder, Push/Pull, Climb, Crawl, Squat or Kneel, Bend, etc. Each with frequency and weight. We need to preserve all. Could format as
preserving the original text? The instruction says use
- . For Competency Statements, it's a list of bullet points: Communication Skills - Ability..., Customer Oriented..., Enthusiastic..., Interpersonal... So we can make