Network Manager
Softheon · Stony Brook, NY · 2 days ago
RemoteRemoteInformation Technology$122k–$140k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Job Title: Network Manager Team: Infrastructure Job Location: Remote About Us ... (culture etc). About The Role: description. Requirements: includes "You Will:" with many bullet-like paragraphs. Actually the "Requirements" section includes many responsibilities and tasks. Then later "You Have Education", "Experience", "Required Certifications", "Preferred Certifications", "Knowledge", "Skills", "Attributes". Then "Benefits". Also "Pay" is mentioned: base pay $122,000- $140,000 plus equity etc. Schedule: Not explicitly given except mention of remote, 2 times per year in-person, 10% travel, must reside in Eastern/Central time zone, must be located in certain states. Also mention "Please note that the requirements of this role are beyond the 9am - 6pm scope. It is expected that all leaders are available to the organization when needed." That's schedule info.
We need sections: About the role (we have About The Role). Responsibilities (we have many tasks under Requirements? Actually the "You Will:" includes responsibilities. Could treat that as Responsibilities. Requirements (education, experience, certifications). Qualifications maybe combine? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if content exists.
We have About The Role content.
Responsibilities: we can extract from "You Will:" bullet points (the long list). That includes network operations, team leadership, security, projects, vendor management, talent management, additional responsibilities.
Requirements: education, experience, certifications required.
Qualifications: maybe we could put "Preferred Certifications" and "Knowledge" as Qualifications? But Qualifications heading maybe for preferred qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have Skills section explicitly: "Skills". Also "Attributes". Could treat Attributes as part of Skills? But we have separate Skills heading; we could put Skills content there, and maybe Attributes could go under Skills or maybe under Qualifications? However we should not invent sections; we can include Skills heading with content from Skills and Attributes? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Skills and Attributes under Skills heading. But we need to preserve all substantive info; we can include both under Skills as list items.
Benefits: we have Benefits section.
Pay: we have base pay range.
Schedule: we have info about beyond 9-6, on-call, travel, in-person 2 times per year, time zone, state restrictions.
We must not include boilerplate like EEO etc. At end there is EEO statement; we must remove.
We must not include duplicated lines.
We must not include application instructions.
We must not include navigation/cookie/legal.
We must not include "About Us" maybe? The instruction says include section only when posting has real specific content for it. About Us is not in the list of allowed headings; we cannot create About Us heading. So we should omit About Us and Our Company Culture etc. However we might need to preserve substantive info? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. But we cannot create headings not in list. However we could embed that info under About the role? Probably not appropriate. The About Us is not required headings; maybe we can drop it because it's not part of allowed headings and not essential to the role? But it's substantive info about company. The instruction says preserve ALL substantive information; but also says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g. those). It might be okay to include other headings if needed, but they gave examples. Safer to stick to those headings only. However we could include About Us under About the role? Not ideal.
Maybe we can treat "About Us" as part of About the role? But About the role already has its own heading. Could we add a paragraph after About the role heading describing company? The About The Role section currently includes description of role only. We could add a brief paragraph about company under About the role? But that would mix.
Better to follow instruction: only use those headings. So we will omit About Us and culture.
We must still preserve substantive information from the posting that is relevant to the role: responsibilities, requirements, qualifications, skills, benefits, pay, schedule. The company mission etc may be considered substantive but not required headings; maybe we can drop as it's not in allowed headings. The instruction says preserve ALL substantive information; but also says "include a section ONLY when the posting has real, specific content for it". It doesn't say we cannot omit sections not in list. It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. I'd include only those headings.
Thus we will output:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g. those). It might be okay to include other headings if needed, but they gave examples. Safer to stick to those headings only. However we could include About Us under About the role? Not ideal.
Maybe we can treat "About Us" as part of About the role? But About the role already has its own heading. Could we add a paragraph after About the role heading describing company? The About The Role section currently includes description of role only. We could add a brief paragraph about company under About the role? But that would mix.
Better to follow instruction: only use those headings. So we will omit About Us and culture.
We must still preserve substantive information from the posting that is relevant to the role: responsibilities, requirements, qualifications, skills, benefits, pay, schedule. The company mission etc may be considered substantive but not required headings; maybe we can drop as it's not in allowed headings. The instruction says preserve ALL substantive information; but also says "include a section ONLY when the posting has real, specific content for it". It doesn't say we cannot omit sections not in list. It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. I'd include only those headings.
Thus we will output:
About the role
... (the About The Role paragraph)
Responsibilities
- ... each responsibility item
Requirements
- ... education, experience, required certifications
Qualifications
- ... preferred certifications, knowledge
Skills
- ... skills and attributes
Benefits
- ... benefits
Pay
... base pay range etc
Schedule
- ... schedule details