Field Services Technician - Onsite Jeffersonville, KY & Clay City, KY
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings. Remove boilerplate etc. Preserve all substantive info.
We need to identify sections: About the role (description), Essential Job Functions (list), Basic Qualifications (list), Other Qualifications (list), Why DXC? / Life at DXC (maybe benefits?), Additional Information (maybe not needed), Pay range (but it's vague: "A reasonable estimate of the current compensation range for this position is - ." That's basically no actual range; it's placeholder. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Here pay range is not given (just dash). So we should not include Pay section. Schedule: they mention Monday to Friday Business hours (approximately 8:00 AM - 5:00 PM) Availability to work overtime during critical incidents or business emergencies. That's schedule info. So we can include a Schedule section with that content. Benefits: they mention DXC offers a comprehensive, flexible, and competitive benefits program which includes, but is not limited to, health, dental, and vision insurance coverage; employee wellness; life and disability insurance; a retirement savings plan, paid holidays, paid time off. That's substantive benefits. So include Benefits section.
We also have About DXC (intro) maybe not needed? The instruction: "Prefer a few substantive sections over many thin ones." We could include About the role (description), Responsibilities (Essential Job Functions), Requirements (Basic Qualifications + Other Qualifications maybe combined?), Benefits, Schedule. Could also include About the Team/Offering? Not much. The "About The Team/ Offering (Optional)" heading appears but no content after? Actually after that heading there is "About the Role". So we can ignore.
We need to ensure we don't repeat job title as heading. The job title is "Resident Field Support Technician". Not to be used as heading.
We need to preserve all substantive information. Let's extract:
About DXC paragraph: description of company. Might be considered boilerplate? It's about the company, not specific to role. Might be considered generic but could be kept? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About DXC is not exactly boilerplate but could be considered generic marketing. However it's substantive info about the company. Might be okay to keep as a short paragraph under maybe an "About DXC" heading? But they said prefer few substantive sections over many thin ones. Could combine into a brief intro paragraph before sections. The instruction: Output ONLY the HTML fragment. It didn't forbid having an introductory paragraph without heading. So we could start with a
containing the About DXC description. Then sections.
Let's list substantive content:
- About DXC: paragraph describing DXC helps global companies run mission-critical systems... (the first paragraph). Keep.
- About the Role: paragraph: "DXC Technology is seeking a Resident Field Support Technician to provide dedicated onsite IT support for a customer operating across two locations in Kentucky. This role requires a hands-on technical professional who will serve as the primary point of contact for end-user support, hardware troubleshooting, device deployments, and incident resolution while ensuring adherence to agreed service levels and customer satisfaction objectives. The technician will support both the Jeffersonville and Clay City sites and will travel between locations as needed."
- Location: "Jeffersonville, KY & Clay City, KY" and "The selected candidate will provide onsite support across both customer locations and must be able to travel between sites as required." Could be part of role description.
- Essential Job Functions: list of bullet points (the long list). We'll put under
Responsibilities
maybe. Use - .
- Basic Qualifications: list of items. Under
Requirements
maybe.
- Other Qualifications: list: Ability to travel between Jeffersonville and Clay City, Kentucky. Valid driver's license preferred. Reliable transportation may be required. Ability to perform occasional after-hours or overtime support for critical incidents. Monday to Friday Business hours (approximately 8:00 AM - 5:00 PM) Availability to work overtime during critical incidents or business emergencies.
But note schedule info appears also in Other Qualifications. We'll extract schedule: Monday to Friday Business hours (approximately 8:00 AM - 5:00 PM) Availability to work overtime during critical incidents or business emergencies.
We could put schedule in its own section.
- Why DXC? / Life at DXC: paragraph about DXC being employer of choice, culture, benefits program. We'll put under Benefits
maybe with list of benefits.
- Additional Information: includes EEO, ITAR, Pay range, Disability Accommodations, Recruitment fraud, etc. Many of those are boilerplate/legal. We should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the Additional Information section entirely (EEO, ITAR, Pay range, Disability Accommodations, Recruitment fraud). However note ITAR mentions that applicants must be US Citizens or Permanent Residents. That is a substantive requirement (citizenship). Should we keep? It's a requirement. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. ITAR is not EEO but a legal requirement for the role. Might be considered substantive. However it's also a legal statement. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". ITAR is legal. Might be considered boilerplate? It's a requirement for the job (must be US Citizen or Permanent Resident). That's substantive. But it's also a legal requirement. The instruction says remove legal boilerplate. However it's not exactly boilerplate; it's a specific requirement. I'd keep it as a requirement under Requirements maybe.
But the ITAR statement: "The client is in a controlled goods program environment and must comply with the International Traffic in Arms Regulations (ITAR), which mandates that all applicants be U.S. Citizens or Permanent Residents." That's a requirement. We'll include under Requirements.
Pay range: they say "A reasonable estimate of the current compensation range for this position is - ." That's no actual range, so we should not include Pay section.
Disability Accommodations and Recruitment fraud are boilerplate; remove.
Thus final sections:
- Intro paragraph: About DXC (maybe we can keep as ).
-
About the Role
with paragraph(s) describing role and locations.
- Responsibilities
with - list of essential job functions.
-
Requirements
with - list of basic qualifications + other qualifications (including travel, driver's license, after-hours, ITAR citizenship). Could separate Basic and Other but we can combine.
-
Benefits
with - list of benefits.
-
Schedule
with containing Monday to Friday Business hours (approximately 8:00 AM - 5:00 PM) Availability to work overtime during critical incidents or business emergencies.
We must not repeat job title as heading. We used About the Role, Responsibilities, Requirements, Benefits, Schedule. Good.
Check for duplicated lines: Ensure we don't duplicate any content.
Now craft HTML.
We need to ensure we use
for section headings. Use - for lists. Use
for prose.
Let's write:
DXC helps global companies run their mission-critical systems and operations while modernizing IT, optimizing data architectures and ensuring security and scalability across public, private and hybrid clouds. The world's largest companies and public sector organizations trust DXC to deploy services to drive new levels of performance, competitiveness, and customer experience across their IT estates. Our more than 125,000 people in 70-plus countries are entrusted by our customers to deliver transformative technologies to ensure the success, safety and well-being of businesses and people around the world. By combining strengths and expertise globally, we create solutions and deliver greater outcomes for customers across their entire IT estate.
About the Role
DXC Technology is seeking a Resident Field Support Technician to provide dedicated onsite IT support for a customer operating across two locations in Kentucky. This role requires a hands-on technical professional who will serve as the primary point of contact for end-user support, hardware troubleshooting, device deployments, and incident resolution while ensuring adherence to agreed service levels and customer satisfaction objectives. The technician will support both the Jeffersonville and Clay City sites and will travel between locations as needed.
Jeffersonville, KY & Clay City, KY. The selected candidate will provide onsite support across both customer locations and must be able to travel between sites as required.
Responsibilities
- Provide first-line onsite technical support to end users.
- Respond to incidents and service requests within agreed SLA targets.
- Troubleshoot and resolve hardware, software, and peripheral issues.
- Install, move, add, change, and dispose of IT equipment.
- Perform desktop, laptop, printer, and mobile device support.
- Support Microsoft 365 and Teams-related issues.
- Maintain accurate documentation within the ticketing system.
- Perform basic network troubleshooting.
- Configure and support workplace-connected devices.
- Assist with asset inventory and lifecycle management.
- Coordinate with remote support teams, vendors, and internal resolver groups.
- Execute maintenance, repairs, and equipment replacements.
- Ensure compliance with corporate security and operational policies.
- Escalate issues appropriately when required.
- Participate in continuous service improvement initiatives.
Requirements
- 2+ years of IT Support, Field Support, or Desktop Support experience.
- Strong customer service and communication skills.
- Ability to work independently in an onsite customer environment.
- Experience supporting enterprise users and infrastructure.
- Ability to prioritize multiple tasks in a fast-paced environment.
- Experience working under SLA and TTR commitments.
- Windows Operating Systems
- Microsoft 365
- Microsoft Teams
- Active Directory
- Hardware Break/Fix Support
- ITIL Foundation concepts
- Incident Management processes
- Service Request Management
- Knowledge of Azure, AWS, or GCP environments
- Ability to travel between Jeffersonville and Clay City, Kentucky.
- Valid driver's license preferred.
- Reliable transportation may be required.
- Ability to perform occasional after-hours or overtime support for critical incidents.
- The client is in a controlled goods program environment and must comply with the International Traffic in Arms Regulations (ITAR), which mandates that all applicants be U.S. Citizens or Permanent Residents.
Benefits
- Health, dental, and vision insurance coverage
- Employee wellness programs
- Life and disability insurance
- Retirement savings plan
- Paid holidays
- Paid time off
Schedule
Monday to Friday Business
for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings. Remove boilerplate etc. Preserve all substantive info. We need to identify sections: About the role (description), Essential Job Functions (list), Basic Qualifications (list), Other Qualifications (list), Why DXC? / Life at DXC (maybe benefits?), Additional Information (maybe not needed), Pay range (but it's vague: "A reasonable estimate of the current compensation range for this position is - ." That's basically no actual range; it's placeholder. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Here pay range is not given (just dash). So we should not include Pay section. Schedule: they mention Monday to Friday Business hours (approximately 8:00 AM - 5:00 PM) Availability to work overtime during critical incidents or business emergencies. That's schedule info. So we can include a Schedule section with that content. Benefits: they mention DXC offers a comprehensive, flexible, and competitive benefits program which includes, but is not limited to, health, dental, and vision insurance coverage; employee wellness; life and disability insurance; a retirement savings plan, paid holidays, paid time off. That's substantive benefits. So include Benefits section. We also have About DXC (intro) maybe not needed? The instruction: "Prefer a few substantive sections over many thin ones." We could include About the role (description), Responsibilities (Essential Job Functions), Requirements (Basic Qualifications + Other Qualifications maybe combined?), Benefits, Schedule. Could also include About the Team/Offering? Not much. The "About The Team/ Offering (Optional)" heading appears but no content after? Actually after that heading there is "About the Role". So we can ignore. We need to ensure we don't repeat job title as heading. The job title is "Resident Field Support Technician". Not to be used as heading. We need to preserve all substantive information. Let's extract: About DXC paragraph: description of company. Might be considered boilerplate? It's about the company, not specific to role. Might be considered generic but could be kept? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About DXC is not exactly boilerplate but could be considered generic marketing. However it's substantive info about the company. Might be okay to keep as a short paragraph under maybe an "About DXC" heading? But they said prefer few substantive sections over many thin ones. Could combine into a brief intro paragraph before sections. The instruction: Output ONLY the HTML fragment. It didn't forbid having an introductory paragraph without heading. So we could start with a
containing the About DXC description. Then sections. Let's list substantive content: - About DXC: paragraph describing DXC helps global companies run mission-critical systems... (the first paragraph). Keep. - About the Role: paragraph: "DXC Technology is seeking a Resident Field Support Technician to provide dedicated onsite IT support for a customer operating across two locations in Kentucky. This role requires a hands-on technical professional who will serve as the primary point of contact for end-user support, hardware troubleshooting, device deployments, and incident resolution while ensuring adherence to agreed service levels and customer satisfaction objectives. The technician will support both the Jeffersonville and Clay City sites and will travel between locations as needed." - Location: "Jeffersonville, KY & Clay City, KY" and "The selected candidate will provide onsite support across both customer locations and must be able to travel between sites as required." Could be part of role description. - Essential Job Functions: list of bullet points (the long list). We'll put under
Responsibilities
maybe. Use- .
- Basic Qualifications: list of items. Under
Requirements
maybe. - Other Qualifications: list: Ability to travel between Jeffersonville and Clay City, Kentucky. Valid driver's license preferred. Reliable transportation may be required. Ability to perform occasional after-hours or overtime support for critical incidents. Monday to Friday Business hours (approximately 8:00 AM - 5:00 PM) Availability to work overtime during critical incidents or business emergencies. But note schedule info appears also in Other Qualifications. We'll extract schedule: Monday to Friday Business hours (approximately 8:00 AM - 5:00 PM) Availability to work overtime during critical incidents or business emergencies. We could put schedule in its own section. - Why DXC? / Life at DXC: paragraph about DXC being employer of choice, culture, benefits program. We'll put underBenefits
maybe with list of benefits. - Additional Information: includes EEO, ITAR, Pay range, Disability Accommodations, Recruitment fraud, etc. Many of those are boilerplate/legal. We should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the Additional Information section entirely (EEO, ITAR, Pay range, Disability Accommodations, Recruitment fraud). However note ITAR mentions that applicants must be US Citizens or Permanent Residents. That is a substantive requirement (citizenship). Should we keep? It's a requirement. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. ITAR is not EEO but a legal requirement for the role. Might be considered substantive. However it's also a legal statement. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". ITAR is legal. Might be considered boilerplate? It's a requirement for the job (must be US Citizen or Permanent Resident). That's substantive. But it's also a legal requirement. The instruction says remove legal boilerplate. However it's not exactly boilerplate; it's a specific requirement. I'd keep it as a requirement under Requirements maybe. But the ITAR statement: "The client is in a controlled goods program environment and must comply with the International Traffic in Arms Regulations (ITAR), which mandates that all applicants be U.S. Citizens or Permanent Residents." That's a requirement. We'll include under Requirements. Pay range: they say "A reasonable estimate of the current compensation range for this position is - ." That's no actual range, so we should not include Pay section. Disability Accommodations and Recruitment fraud are boilerplate; remove. Thus final sections: - Intro paragraph: About DXC (maybe we can keep as). -
About the Role
with paragraph(s) describing role and locations. -Responsibilities
with- list of essential job functions.
-
Requirements
with- list of basic qualifications + other qualifications (including travel, driver's license, after-hours, ITAR citizenship). Could separate Basic and Other but we can combine.
-
Benefits
with- list of benefits.
-
Schedule
withcontaining Monday to Friday Business hours (approximately 8:00 AM - 5:00 PM) Availability to work overtime during critical incidents or business emergencies. We must not repeat job title as heading. We used About the Role, Responsibilities, Requirements, Benefits, Schedule. Good. Check for duplicated lines: Ensure we don't duplicate any content. Now craft HTML. We need to ensure we use
for section headings. Use
- for lists. Use
for prose. Let's write:
DXC helps global companies run their mission-critical systems and operations while modernizing IT, optimizing data architectures and ensuring security and scalability across public, private and hybrid clouds. The world's largest companies and public sector organizations trust DXC to deploy services to drive new levels of performance, competitiveness, and customer experience across their IT estates. Our more than 125,000 people in 70-plus countries are entrusted by our customers to deliver transformative technologies to ensure the success, safety and well-being of businesses and people around the world. By combining strengths and expertise globally, we create solutions and deliver greater outcomes for customers across their entire IT estate.
About the Role
DXC Technology is seeking a Resident Field Support Technician to provide dedicated onsite IT support for a customer operating across two locations in Kentucky. This role requires a hands-on technical professional who will serve as the primary point of contact for end-user support, hardware troubleshooting, device deployments, and incident resolution while ensuring adherence to agreed service levels and customer satisfaction objectives. The technician will support both the Jeffersonville and Clay City sites and will travel between locations as needed.
Jeffersonville, KY & Clay City, KY. The selected candidate will provide onsite support across both customer locations and must be able to travel between sites as required.
Responsibilities
- Provide first-line onsite technical support to end users.
- Respond to incidents and service requests within agreed SLA targets.
- Troubleshoot and resolve hardware, software, and peripheral issues.
- Install, move, add, change, and dispose of IT equipment.
- Perform desktop, laptop, printer, and mobile device support.
- Support Microsoft 365 and Teams-related issues.
- Maintain accurate documentation within the ticketing system.
- Perform basic network troubleshooting.
- Configure and support workplace-connected devices.
- Assist with asset inventory and lifecycle management.
- Coordinate with remote support teams, vendors, and internal resolver groups.
- Execute maintenance, repairs, and equipment replacements.
- Ensure compliance with corporate security and operational policies.
- Escalate issues appropriately when required.
- Participate in continuous service improvement initiatives.
Requirements
- 2+ years of IT Support, Field Support, or Desktop Support experience.
- Strong customer service and communication skills.
- Ability to work independently in an onsite customer environment.
- Experience supporting enterprise users and infrastructure.
- Ability to prioritize multiple tasks in a fast-paced environment.
- Experience working under SLA and TTR commitments.
- Windows Operating Systems
- Microsoft 365
- Microsoft Teams
- Active Directory
- Hardware Break/Fix Support
- ITIL Foundation concepts
- Incident Management processes
- Service Request Management
- Knowledge of Azure, AWS, or GCP environments
- Ability to travel between Jeffersonville and Clay City, Kentucky.
- Valid driver's license preferred.
- Reliable transportation may be required.
- Ability to perform occasional after-hours or overtime support for critical incidents.
- The client is in a controlled goods program environment and must comply with the International Traffic in Arms Regulations (ITAR), which mandates that all applicants be U.S. Citizens or Permanent Residents.
Benefits
- Health, dental, and vision insurance coverage
- Employee wellness programs
- Life and disability insurance
- Retirement savings plan
- Paid holidays
- Paid time off
Schedule
Monday to Friday Business
- for lists. Use
- list of benefits.
-
- list of basic qualifications + other qualifications (including travel, driver's license, after-hours, ITAR citizenship). Could separate Basic and Other but we can combine.
-
- list of essential job functions.
-