Server Administrator
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the description.
Key content:
- Title: Server Patching Engineer (not used as heading)
- Description: Provide full-time proactive management on all servers and mission critical WINTEL based applications. Also day to day direction of server patching activities.
- Primary Responsibilities:
- Research, Download, Test and Deploy patches from Microsoft and other vendors.
- Working with business groups to establish and maintain outage windows for systems.
- Deploy patches within established windows on a monthly cycle.
- Mitigate issues with patches if possible.
- Escalate issues to other LMG teams if needed.
- Communicate activities during patching.
- Research trends in threats and vulnerabilities.
- Experience with Manage Engine Enterprise Patch Management for Servers is desired.
- MCSE or similar level Microsoft server experience is desired.
- Some early morning, late night and weekend work is required.
- Successful engineers who held this position in the past were very detail-oriented people who took pride in repeating the monthly processes with precision.
- Additional Skills & Qualifications:
- Need to have worked in a large enterprise environment.
- Experience Level Expert Level
- Job Type & Location: This is a Contract position based out of Louisville, KY.
- Pay And Benefits:
- Pay range $25.00 - $27.00/hr.
- Individual compensation offered within this range will depend on many factors...
- Eligibility requirements apply to some benefits and may depend on your job classification and length of employment.
- Benefits are subject to change and may be subject to specific elections, plan, or program terms.
- If eligible, the benefits available for this temporary role may include the following:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
- Workplace Type: This is a hybrid position in Louisville, KY.
- Application Deadline: This position is anticipated to close on Sep 25, 2026.
- About TEKsystems: description (multiple paragraphs). This is boilerplate? It's about the company. Might be considered boilerplate but it's substantive about the employer. The instructions say remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" sections are not exactly boilerplate but could be considered company description. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the About TEKsystems content? It's not a required section heading like About the role, but we could include it under a heading like "About the company" but not in the list of allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings where appropriate. The "About TEKsystems" could go under "About the role"? Actually "About the role" is for role description. The initial description about the role could be placed there. The "About TEKsystems" is about the company, not the role. There's no heading for company info. We could either omit it (if considered boilerplate) or incorporate into a paragraph under "About the role"? But that would be mixing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" is not exactly those categories, but it's still boilerplate-ish company description. However, they said preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive info about the employer. Should we keep it? Possibly yes, but we need to fit into allowed headings. There's no "About the company" heading allowed. Could we create a
without a heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says use for section headings (e.g. ...). It doesn't forbid other headings, but suggests we should use those headings for sections. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could have a section with heading "About TEKsystems" if we want, but it's not in the examples. However, the examples are just examples; we could still use other headings if needed. But they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings. Probably they want us to map content to those headings only. So we should omit the company description if it doesn't fit. However, we could incorporate some of it into "About the role" as a brief note about the company? But that would be mixing.
Better to follow the instruction: Use those headings for sections. So we will create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
- About the role: summary of the role: "Provide full-time proactive management on all servers and mission critical WINTEL based applications. In addition, this person will be responsible for day to day direction of the server patching activities." Also maybe mention contract, location, hybrid, etc. But location and job type could go under Requirements or Qualifications? Usually location is separate but not a heading. Could put in About the role.
- Responsibilities: list of duties (the bullet list). Use - .
- Requirements: maybe "Experience with Manage Engine Enterprise Patch Management for Servers is desired. MCSE or similar level Microsoft server experience is desired. Some early morning, late night and weekend work is required." Also "Need to have worked in a large enterprise environment." Also "Experience Level Expert Level". Also "Job Type & Location: This is a Contract position based out of Louisville, KY." Could be part of Requirements.
- Qualifications: maybe similar to Requirements; but we can combine. However we need to avoid thin sections. Perhaps we can have Requirements and Qualifications combined? But we need to decide.
- Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Research trends in threats and vulnerabilities." Also "Communicate activities during patching." Also "Mitigate issues with patches if possible. Escalate issues to other LMG teams if needed." But those are more responsibilities.
- Benefits: list of benefits.
- Pay: pay range.
- Schedule: maybe mention hybrid, early morning/late night/weekend work required. Also mention monthly cycle.
We need to avoid filler like "commensurate with experience". Not present.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must remove application instructions (like "Application Deadline" maybe considered application instruction? It's a deadline; could be considered part of posting but not application instruction. The instruction says remove application instructions. The deadline is not exactly an instruction to apply, but it's info about when it closes. Might be okay to keep? It's not a section heading; we could put it in a paragraph under About the role or Schedule? Probably better to include it as a short paragraph under About the role or maybe under Schedule? It's not schedule. Could be under About the role.
We also need to remove duplicated lines: there are duplicated "About TEKsystems" and "The company is an equal opportunity employer..." etc. We'll remove those.
Now craft HTML.
We'll start with
About the role
then ...
Then Responsibilities
- ...
Then Requirements
- ...
Then Qualifications
maybe we can put "Experience Level Expert Level" and "Need to have worked in a large enterprise environment." But those are similar to requirements. Could combine but we need to avoid thin sections. Perhaps we can have only Requirements and Qualifications combined? But we need to follow instruction: include a section only when posting has real specific content for it. If we put both, they'd have content. Could we merge Requirements and Qualifications into one section called "Requirements & Qualifications"? Not in allowed headings but maybe okay. However they gave examples; we could still use other headings but they said use for section headings (e.g. ...). It doesn't forbid others, but to be safe, we stick to those.
We could put Requirements: includes experience, certifications, work hours, enterprise environment, expert level, contract location. Qualifications: maybe "Detail-oriented, able to repeat monthly processes with precision." That's more a skill. Could put under Skills.
Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Research trends in threats and vulnerabilities." Also "Communicate activities during patching." Also "Mitigate issues with patches if possible. Escalate issues to other LMG teams if needed." But those are responsibilities.
Better to allocate:
- About the role: role summary + location + job type + hybrid + deadline.
- Responsibilities: the bullet list of patching duties.
- Requirements: technical experience (Manage Engine, MCSE), enterprise environment, expert level, work hours (early morning/late night/weekend).
- Qualifications: maybe "Detail-oriented, able to repeat monthly processes with precision." (though could be skill). But we can put under Skills.
- Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Ability to research threats/vulnerabilities." Also "Communication skills." But we can keep simple.
- Benefits: list.
- Pay: pay range.
- Schedule: maybe mention hybrid, monthly cycle, work hours.
We need to avoid thin sections: each should have substantive content.
Let's draft.
About the role paragraph: "Provide full-time proactive management on all servers and mission critical WINTEL based applications, including day-to-day direction of server patching activities. This is a contract position based in Louisville, KY, with a hybrid workplace arrangement. The position is anticipated to close on Sep 25, 2026."
Responsibilities ul: items:
- Research, download, test, and deploy patches from Microsoft and other vendors.
- Work with business groups to establish and maintain outage windows for systems.
- Deploy patches within established windows on a monthly cycle.
- Mitigate issues with patches when possible.
- Escalate issues to other LMG teams as needed.
- Communicate activities during patching.
- Research trends in threats and vulnerabilities.
Requirements ul:
- Experience with Manage Engine Enterprise Patch Management for Servers (desired).
- MCSE or equivalent Microsoft server experience (desired).
- Experience working in a large enterprise environment.
- Expert level experience.
- Availability for early morning, late night
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the description. Key content: - Title: Server Patching Engineer (not used as heading) - Description: Provide full-time proactive management on all servers and mission critical WINTEL based applications. Also day to day direction of server patching activities. - Primary Responsibilities: - Research, Download, Test and Deploy patches from Microsoft and other vendors. - Working with business groups to establish and maintain outage windows for systems. - Deploy patches within established windows on a monthly cycle. - Mitigate issues with patches if possible. - Escalate issues to other LMG teams if needed. - Communicate activities during patching. - Research trends in threats and vulnerabilities. - Experience with Manage Engine Enterprise Patch Management for Servers is desired. - MCSE or similar level Microsoft server experience is desired. - Some early morning, late night and weekend work is required. - Successful engineers who held this position in the past were very detail-oriented people who took pride in repeating the monthly processes with precision. - Additional Skills & Qualifications: - Need to have worked in a large enterprise environment. - Experience Level Expert Level - Job Type & Location: This is a Contract position based out of Louisville, KY. - Pay And Benefits: - Pay range $25.00 - $27.00/hr. - Individual compensation offered within this range will depend on many factors... - Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. - Benefits are subject to change and may be subject to specific elections, plan, or program terms. - If eligible, the benefits available for this temporary role may include the following: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) - Workplace Type: This is a hybrid position in Louisville, KY. - Application Deadline: This position is anticipated to close on Sep 25, 2026. - About TEKsystems: description (multiple paragraphs). This is boilerplate? It's about the company. Might be considered boilerplate but it's substantive about the employer. The instructions say remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" sections are not exactly boilerplate but could be considered company description. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the About TEKsystems content? It's not a required section heading like About the role, but we could include it under a heading like "About the company" but not in the list of allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings where appropriate. The "About TEKsystems" could go under "About the role"? Actually "About the role" is for role description. The initial description about the role could be placed there. The "About TEKsystems" is about the company, not the role. There's no heading for company info. We could either omit it (if considered boilerplate) or incorporate into a paragraph under "About the role"? But that would be mixing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" is not exactly those categories, but it's still boilerplate-ish company description. However, they said preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive info about the employer. Should we keep it? Possibly yes, but we need to fit into allowed headings. There's no "About the company" heading allowed. Could we create a
without a heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says use for section headings (e.g. ...). It doesn't forbid other headings, but suggests we should use those headings for sections. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could have a section with heading "About TEKsystems" if we want, but it's not in the examples. However, the examples are just examples; we could still use other headings if needed. But they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings. Probably they want us to map content to those headings only. So we should omit the company description if it doesn't fit. However, we could incorporate some of it into "About the role" as a brief note about the company? But that would be mixing.
Better to follow the instruction: Use those headings for sections. So we will create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
- About the role: summary of the role: "Provide full-time proactive management on all servers and mission critical WINTEL based applications. In addition, this person will be responsible for day to day direction of the server patching activities." Also maybe mention contract, location, hybrid, etc. But location and job type could go under Requirements or Qualifications? Usually location is separate but not a heading. Could put in About the role.
- Responsibilities: list of duties (the bullet list). Use - .
- Requirements: maybe "Experience with Manage Engine Enterprise Patch Management for Servers is desired. MCSE or similar level Microsoft server experience is desired. Some early morning, late night and weekend work is required." Also "Need to have worked in a large enterprise environment." Also "Experience Level Expert Level". Also "Job Type & Location: This is a Contract position based out of Louisville, KY." Could be part of Requirements.
- Qualifications: maybe similar to Requirements; but we can combine. However we need to avoid thin sections. Perhaps we can have Requirements and Qualifications combined? But we need to decide.
- Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Research trends in threats and vulnerabilities." Also "Communicate activities during patching." Also "Mitigate issues with patches if possible. Escalate issues to other LMG teams if needed." But those are more responsibilities.
- Benefits: list of benefits.
- Pay: pay range.
- Schedule: maybe mention hybrid, early morning/late night/weekend work required. Also mention monthly cycle.
We need to avoid filler like "commensurate with experience". Not present.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must remove application instructions (like "Application Deadline" maybe considered application instruction? It's a deadline; could be considered part of posting but not application instruction. The instruction says remove application instructions. The deadline is not exactly an instruction to apply, but it's info about when it closes. Might be okay to keep? It's not a section heading; we could put it in a paragraph under About the role or Schedule? Probably better to include it as a short paragraph under About the role or maybe under Schedule? It's not schedule. Could be under About the role.
We also need to remove duplicated lines: there are duplicated "About TEKsystems" and "The company is an equal opportunity employer..." etc. We'll remove those.
Now craft HTML.
We'll start with
About the role
then ...
Then Responsibilities
- ...
Then Requirements
- ...
Then Qualifications
maybe we can put "Experience Level Expert Level" and "Need to have worked in a large enterprise environment." But those are similar to requirements. Could combine but we need to avoid thin sections. Perhaps we can have only Requirements and Qualifications combined? But we need to follow instruction: include a section only when posting has real specific content for it. If we put both, they'd have content. Could we merge Requirements and Qualifications into one section called "Requirements & Qualifications"? Not in allowed headings but maybe okay. However they gave examples; we could still use other headings but they said use for section headings (e.g. ...). It doesn't forbid others, but to be safe, we stick to those.
We could put Requirements: includes experience, certifications, work hours, enterprise environment, expert level, contract location. Qualifications: maybe "Detail-oriented, able to repeat monthly processes with precision." That's more a skill. Could put under Skills.
Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Research trends in threats and vulnerabilities." Also "Communicate activities during patching." Also "Mitigate issues with patches if possible. Escalate issues to other LMG teams if needed." But those are responsibilities.
Better to allocate:
- About the role: role summary + location + job type + hybrid + deadline.
- Responsibilities: the bullet list of patching duties.
- Requirements: technical experience (Manage Engine, MCSE), enterprise environment, expert level, work hours (early morning/late night/weekend).
- Qualifications: maybe "Detail-oriented, able to repeat monthly processes with precision." (though could be skill). But we can put under Skills.
- Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Ability to research threats/vulnerabilities." Also "Communication skills." But we can keep simple.
- Benefits: list.
- Pay: pay range.
- Schedule: maybe mention hybrid, monthly cycle, work hours.
We need to avoid thin sections: each should have substantive content.
Let's draft.
About the role paragraph: "Provide full-time proactive management on all servers and mission critical WINTEL based applications, including day-to-day direction of server patching activities. This is a contract position based in Louisville, KY, with a hybrid workplace arrangement. The position is anticipated to close on Sep 25, 2026."
Responsibilities ul: items:
- Research, download, test, and deploy patches from Microsoft and other vendors.
- Work with business groups to establish and maintain outage windows for systems.
- Deploy patches within established windows on a monthly cycle.
- Mitigate issues with patches when possible.
- Escalate issues to other LMG teams as needed.
- Communicate activities during patching.
- Research trends in threats and vulnerabilities.
Requirements ul:
- Experience with Manage Engine Enterprise Patch Management for Servers (desired).
- MCSE or equivalent Microsoft server experience (desired).
- Experience working in a large enterprise environment.
- Expert level experience.
- Availability for early morning, late night
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings. Probably they want us to map content to those headings only. So we should omit the company description if it doesn't fit. However, we could incorporate some of it into "About the role" as a brief note about the company? But that would be mixing.
Better to follow the instruction: Use those headings for sections. So we will create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
- About the role: summary of the role: "Provide full-time proactive management on all servers and mission critical WINTEL based applications. In addition, this person will be responsible for day to day direction of the server patching activities." Also maybe mention contract, location, hybrid, etc. But location and job type could go under Requirements or Qualifications? Usually location is separate but not a heading. Could put in About the role.
- Responsibilities: list of duties (the bullet list). Use - .
- Requirements: maybe "Experience with Manage Engine Enterprise Patch Management for Servers is desired. MCSE or similar level Microsoft server experience is desired. Some early morning, late night and weekend work is required." Also "Need to have worked in a large enterprise environment." Also "Experience Level Expert Level". Also "Job Type & Location: This is a Contract position based out of Louisville, KY." Could be part of Requirements.
- Qualifications: maybe similar to Requirements; but we can combine. However we need to avoid thin sections. Perhaps we can have Requirements and Qualifications combined? But we need to decide.
- Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Research trends in threats and vulnerabilities." Also "Communicate activities during patching." Also "Mitigate issues with patches if possible. Escalate issues to other LMG teams if needed." But those are more responsibilities.
- Benefits: list of benefits.
- Pay: pay range.
- Schedule: maybe mention hybrid, early morning/late night/weekend work required. Also mention monthly cycle.
We need to avoid filler like "commensurate with experience". Not present.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must remove application instructions (like "Application Deadline" maybe considered application instruction? It's a deadline; could be considered part of posting but not application instruction. The instruction says remove application instructions. The deadline is not exactly an instruction to apply, but it's info about when it closes. Might be okay to keep? It's not a section heading; we could put it in a paragraph under About the role or Schedule? Probably better to include it as a short paragraph under About the role or maybe under Schedule? It's not schedule. Could be under About the role.
We also need to remove duplicated lines: there are duplicated "About TEKsystems" and "The company is an equal opportunity employer..." etc. We'll remove those.
Now craft HTML.
We'll start with
About the role
then ...
Then Responsibilities
- ...
Then Requirements
- ...
Then Qualifications
maybe we can put "Experience Level Expert Level" and "Need to have worked in a large enterprise environment." But those are similar to requirements. Could combine but we need to avoid thin sections. Perhaps we can have only Requirements and Qualifications combined? But we need to follow instruction: include a section only when posting has real specific content for it. If we put both, they'd have content. Could we merge Requirements and Qualifications into one section called "Requirements & Qualifications"? Not in allowed headings but maybe okay. However they gave examples; we could still use other headings but they said use for section headings (e.g. ...). It doesn't forbid others, but to be safe, we stick to those.
We could put Requirements: includes experience, certifications, work hours, enterprise environment, expert level, contract location. Qualifications: maybe "Detail-oriented, able to repeat monthly processes with precision." That's more a skill. Could put under Skills.
Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Research trends in threats and vulnerabilities." Also "Communicate activities during patching." Also "Mitigate issues with patches if possible. Escalate issues to other LMG teams if needed." But those are responsibilities.
Better to allocate:
- About the role: role summary + location + job type + hybrid + deadline.
- Responsibilities: the bullet list of patching duties.
- Requirements: technical experience (Manage Engine, MCSE), enterprise environment, expert level, work hours (early morning/late night/weekend).
- Qualifications: maybe "Detail-oriented, able to repeat monthly processes with precision." (though could be skill). But we can put under Skills.
- Skills: maybe "Detail-oriented, able to repeat monthly processes with precision." Also "Ability to research threats/vulnerabilities." Also "Communication skills." But we can keep simple.
- Benefits: list.
- Pay: pay range.
- Schedule: maybe mention hybrid, monthly cycle, work hours.
We need to avoid thin sections: each should have substantive content.
Let's draft.
About the role paragraph: "Provide full-time proactive management on all servers and mission critical WINTEL based applications, including day-to-day direction of server patching activities. This is a contract position based in Louisville, KY, with a hybrid workplace arrangement. The position is anticipated to close on Sep 25, 2026."
Responsibilities ul: items:
- Research, download, test, and deploy patches from Microsoft and other vendors.
- Work with business groups to establish and maintain outage windows for systems.
- Deploy patches within established windows on a monthly cycle.
- Mitigate issues with patches when possible.
- Escalate issues to other LMG teams as needed.
- Communicate activities during patching.
- Research trends in threats and vulnerabilities.
Requirements ul:
- Experience with Manage Engine Enterprise Patch Management for Servers (desired).
- MCSE or equivalent Microsoft server experience (desired).
- Experience working in a large enterprise environment.
- Expert level experience.
- Availability for early morning, late night
About the role
then...
ThenResponsibilities
- ...
Requirements
- ...