Customer Support Specialist (Technical)
for each heading only if there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About Peraton (company overview) - maybe not needed? It's generic but could be part of About the role? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should create sections only if content exists. Likely we will have About the role (the paragraph describing role). Responsibilities (list of duties). Qualifications (basic and desired). Skills maybe part of qualifications? Could separate Skills if present. Benefits (Benefits Statement). Pay (Target Salary Range). Schedule (Core Work Schedule, training schedule, remote etc). Also maybe location? Not required heading.
We must not create sections with filler like "commensurate with experience". We have actual schedule info: "Core Work Schedule: TBD, must be flexible for 1st, 2nd and 3rd shift." That's TBD but also says must be flexible for shifts. It's somewhat vague but still specific? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD", "varies", "TBD"). Since schedule includes TBD, we might avoid Schedule section if it's just TBD? However they also give details: training program schedule, shift requirements, remote possibility. So we can include Schedule with those specifics, ignoring the TBD phrase? We could include schedule details but not mention TBD? The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". If we include the schedule heading, we must not have placeholder text as the only content. We can include the schedule details (training program, shift flexibility, remote). The TBD phrase is part of the content but we could still include it? Might be considered filler. Safer to include schedule details but maybe omit the TBD phrase? However we must preserve ALL substantive information; we cannot invent or summarize away detail. If we remove TBD, we are altering info. But TBD is placeholder; maybe we can keep it but it's placeholder. The rule says never emit a heading followed by filler/placeholder text. If we include TBD as part of content, that is filler. So maybe we should not include Schedule section at all because the only schedule info includes TBD. However there is also substantive schedule info: training program Monday-Friday 7am-3:30pm, after training work assigned shift at least four days per week, remote possible fifth day. That's substantive. So we could include schedule section with those details, and maybe we can keep the TBD phrase but it's still filler. The rule says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include filler text within the section; it says heading followed by filler/placeholder text (i.e., the section content is just filler). If we have other substantive content, it's okay. So we can include schedule section with the substantive details, and we can keep the TBD phrase as part of the content (though it's filler). Might be okay.
Similarly Pay: we have Target Salary Range: $51,000 - $82,000. That's specific, not filler. So Pay section okay.
Benefits: we have Benefits Statement with list. So Benefits section okay.
About the role: we have paragraphs describing role. So About the role section.
Responsibilities: we have a long list of day-to-day roles and responsibilities. So Responsibilities section.
Qualifications: we have Basic Qualifications and Desired Qualifications. So Qualifications section.
Skills: maybe we could extract skills from qualifications? But we could also not create Skills section if not explicitly present. The posting includes skills like troubleshooting, communication, etc. But we could treat them as part of Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine Skills into Qualifications. So we may not create separate Skills heading.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We need to use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, application statements, etc. Also remove "Application Statements:" etc. Also remove "EEO:" line.
Also remove "Details" heading? Not needed.
We need to preserve all substantive information: company overview? Might be considered substantive but not under a heading. Could be placed in a
before sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other
content outside sections. But we could include a brief intro about Peraton as a
before the first heading. However the instruction says "Use
for section headings (e.g. About the role, ...)". It doesn't say we must wrap everything in those headings. So we can have a
for company overview then
About the role
etc.
But we must not repeat job title as heading. The job title is "Customer Support Specialist (CSS)". Not used as heading.
Let's extract content.
Company overview: first paragraph about Peraton: "About Peraton Peraton is a next-generation national security company..." We'll keep as .
Program Overview: "Peraton provides the customer with enterprise infrastructure support to plan, engineer, implement, enhance, maintain and operate the global consular affairs IT environment." Could be part of About the role? Might be separate but we can incorporate into About the role
.
About The Role: The paragraph after "About The Role". We'll put that as content under About the role heading.
Responsibilities: The "Day to Day Roles and Responsibilities:" list. We'll turn each sentence into
- maybe. It's a long list separated by periods. We'll split into items.
Qualifications: Basic Qualifications and Desired Qualifications. We'll make
with items.
Benefits: Benefits Statement: list of benefits. We'll make .
Pay: Target Salary Range sentence. We'll put as .
Schedule: Core Work Schedule, training program, shift details. We'll make
maybe with
for details? Could be prose.
Let's extract exact text.
Company overview paragraph:
"About Peraton Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure."
We'll keep as one .
Program Overview sentence:
"Peraton provides the customer with enterprise infrastructure support to plan, engineer, implement, enhance, maintain and operate the global consular affairs IT environment."
We could add as another
before About the role.
Now About the role heading content: The paragraph after "About The Role". Let's copy:
"Peraton is seeking a Customer Support Specialist (CSS) to join our team of qualified and diverse professionals supporting the Department of State (DOS) Bureau of Diplomatic Technology (DT) Consular Affairs Enterprise Infrastructure Operations (CAEIO) Program. The CAEIO Program provides global IT Operations and Maintenance services supporting the modernization, availability, reliability, and security of legacy networks, applications, databases, and enterprise services supporting Consular Affairs operations. The CSS is a member of the Service Desk team supporting the CA Service Center. The Service Desk serves as the central point of coordination for IT service events affecting the CA IT infrastructure and user community. The CSS provides technical support and service management functions across the enterprise, requiring the ability to independently assess user-reported issues, analyze available information, determine appropriate resolution or escalation paths, and coordinate with technical support organizations to restore services and fulfill customer requirements. The CSS is expected to apply established IT service management practices, technical knowledge, and independent judgment to resolve incidents and requests, maintain service quality, identify recurring issues, and contribute to continuous improvement of Service Desk operations. The position interacts regularly with CAEIO technical teams, DOS leadership, customers, and other stakeholders to support effective service delivery and compliance with established service-level objectives."
We'll put that as
under About the role.
Now Responsibilities: The list after "Day to Day Roles and Responsibilities:" We'll split each sentence (separated by periods). Let's extract sentences:
1. Provide technical analysis and remote support for enterprise software, desktop computing, network connectivity, mobile devices, and related IT services through telephone, email, chat, and enterprise service management platforms.
2. Assess reported incidents and service requests, gather relevant technical and customer information, determine appropriate troubleshooting and resolution approaches, and implement or coordinate corrective actions within established procedures.
3. Diagnose and resolve common technical issues using documented procedures, knowledge management resources, technical documentation, and established IT service management practices.
4. Determine when incidents require escalation based on technical complexity, business impact, security considerations, service-level requirements, or available support capabilities, and coordinate escalation with appropriate technical organizations.
5. Maintain ownership of assigned incidents and service requests through resolution or appropriate escalation, ensuring customers receive timely updates and that required actions are documented.
6. Communicate directly with customers to clarify technical issues, gather diagnostic information, provide status updates, explain resolutions, and confirm successful restoration of service.
7. Analyze incident information and recurring issues to identify trends, knowledge gaps, or opportunities to improve service delivery and first-contact resolution.
8. Create and maintain accurate technical documentation, incident records, troubleshooting information, and knowledge articles supporting Service Desk operations.
9. Contribute to the development and improvement of Knowledge Base content by documenting effective troubleshooting techniques, solutions, workarounds, and lessons learned.
10. Apply ITIL-based Incident Management and Request Fulfillment practices to assigned work while ensuring compliance with applicable government policies, procedures, security requirements, SLAs, and SLOs.
11. Monitor ServiceNow dashboards and operational queues to identify unassigned, aging, pending, or otherwise at-risk incidents and requests and take appropriate action to facilitate timely resolution.
12. Analyze ticket status, workload, aging, and service-level information to identify potential risks to customer service and escalate concerns to appropriate Service Desk leadership.
13. Participate in shift turnover activities by communicating significant incidents, unresolved issues, service impacts, operational concerns, and other information necessary to maintain continuity of service.
14. Prepare and communicate scheduled operational reports and shift deliverables, ensuring information is complete, accurate, and submitted within established requirements.
15. Coordinate with Service Desk colleagues, CAEIO technical teams, and other stakeholders to facilitate incident resolution, service restoration, and fulfillment of customer requests.
16. Maintain working knowledge of Service Desk processes, enterprise applications, support procedures, and operational responsibilities sufficient to provide effective technical support and provide backup coverage across Service Desk functions.
17. Identify opportunities to improve processes, procedures, knowledge resources, and customer support practices and provide recommendations to Service
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, application statements, etc. Also remove "Application Statements:" etc. Also remove "EEO:" line.
Also remove "Details" heading? Not needed.
We need to preserve all substantive information: company overview? Might be considered substantive but not under a heading. Could be placed in a
before sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other
content outside sections. But we could include a brief intro about Peraton as a
before the first heading. However the instruction says "Use
for section headings (e.g. About the role, ...)". It doesn't say we must wrap everything in those headings. So we can have a
for company overview then
About the role
etc.
But we must not repeat job title as heading. The job title is "Customer Support Specialist (CSS)". Not used as heading.
Let's extract content.
Company overview: first paragraph about Peraton: "About Peraton Peraton is a next-generation national security company..." We'll keep as .
Program Overview: "Peraton provides the customer with enterprise infrastructure support to plan, engineer, implement, enhance, maintain and operate the global consular affairs IT environment." Could be part of About the role? Might be separate but we can incorporate into About the role
.
About The Role: The paragraph after "About The Role". We'll put that as content under About the role heading.
Responsibilities: The "Day to Day Roles and Responsibilities:" list. We'll turn each sentence into
- maybe. It's a long list separated by periods. We'll split into items.
Qualifications: Basic Qualifications and Desired Qualifications. We'll make
with items.
Benefits: Benefits Statement: list of benefits. We'll make .
Pay: Target Salary Range sentence. We'll put as .
Schedule: Core Work Schedule, training program, shift details. We'll make
maybe with
for details? Could be prose.
Let's extract exact text.
Company overview paragraph:
"About Peraton Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure."
We'll keep as one .
Program Overview sentence:
"Peraton provides the customer with enterprise infrastructure support to plan, engineer, implement, enhance, maintain and operate the global consular affairs IT environment."
We could add as another
before About the role.
Now About the role heading content: The paragraph after "About The Role". Let's copy:
"Peraton is seeking a Customer Support Specialist (CSS) to join our team of qualified and diverse professionals supporting the Department of State (DOS) Bureau of Diplomatic Technology (DT) Consular Affairs Enterprise Infrastructure Operations (CAEIO) Program. The CAEIO Program provides global IT Operations and Maintenance services supporting the modernization, availability, reliability, and security of legacy networks, applications, databases, and enterprise services supporting Consular Affairs operations. The CSS is a member of the Service Desk team supporting the CA Service Center. The Service Desk serves as the central point of coordination for IT service events affecting the CA IT infrastructure and user community. The CSS provides technical support and service management functions across the enterprise, requiring the ability to independently assess user-reported issues, analyze available information, determine appropriate resolution or escalation paths, and coordinate with technical support organizations to restore services and fulfill customer requirements. The CSS is expected to apply established IT service management practices, technical knowledge, and independent judgment to resolve incidents and requests, maintain service quality, identify recurring issues, and contribute to continuous improvement of Service Desk operations. The position interacts regularly with CAEIO technical teams, DOS leadership, customers, and other stakeholders to support effective service delivery and compliance with established service-level objectives."
We'll put that as
under About the role.
Now Responsibilities: The list after "Day to Day Roles and Responsibilities:" We'll split each sentence (separated by periods). Let's extract sentences:
1. Provide technical analysis and remote support for enterprise software, desktop computing, network connectivity, mobile devices, and related IT services through telephone, email, chat, and enterprise service management platforms.
2. Assess reported incidents and service requests, gather relevant technical and customer information, determine appropriate troubleshooting and resolution approaches, and implement or coordinate corrective actions within established procedures.
3. Diagnose and resolve common technical issues using documented procedures, knowledge management resources, technical documentation, and established IT service management practices.
4. Determine when incidents require escalation based on technical complexity, business impact, security considerations, service-level requirements, or available support capabilities, and coordinate escalation with appropriate technical organizations.
5. Maintain ownership of assigned incidents and service requests through resolution or appropriate escalation, ensuring customers receive timely updates and that required actions are documented.
6. Communicate directly with customers to clarify technical issues, gather diagnostic information, provide status updates, explain resolutions, and confirm successful restoration of service.
7. Analyze incident information and recurring issues to identify trends, knowledge gaps, or opportunities to improve service delivery and first-contact resolution.
8. Create and maintain accurate technical documentation, incident records, troubleshooting information, and knowledge articles supporting Service Desk operations.
9. Contribute to the development and improvement of Knowledge Base content by documenting effective troubleshooting techniques, solutions, workarounds, and lessons learned.
10. Apply ITIL-based Incident Management and Request Fulfillment practices to assigned work while ensuring compliance with applicable government policies, procedures, security requirements, SLAs, and SLOs.
11. Monitor ServiceNow dashboards and operational queues to identify unassigned, aging, pending, or otherwise at-risk incidents and requests and take appropriate action to facilitate timely resolution.
12. Analyze ticket status, workload, aging, and service-level information to identify potential risks to customer service and escalate concerns to appropriate Service Desk leadership.
13. Participate in shift turnover activities by communicating significant incidents, unresolved issues, service impacts, operational concerns, and other information necessary to maintain continuity of service.
14. Prepare and communicate scheduled operational reports and shift deliverables, ensuring information is complete, accurate, and submitted within established requirements.
15. Coordinate with Service Desk colleagues, CAEIO technical teams, and other stakeholders to facilitate incident resolution, service restoration, and fulfillment of customer requests.
16. Maintain working knowledge of Service Desk processes, enterprise applications, support procedures, and operational responsibilities sufficient to provide effective technical support and provide backup coverage across Service Desk functions.
17. Identify opportunities to improve processes, procedures, knowledge resources, and customer support practices and provide recommendations to Service
for prose. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, application statements, etc. Also remove "Application Statements:" etc. Also remove "EEO:" line. Also remove "Details" heading? Not needed. We need to preserve all substantive information: company overview? Might be considered substantive but not under a heading. Could be placed in a
before sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other
content outside sections. But we could include a brief intro about Peraton as a
before the first heading. However the instruction says "Use
for section headings (e.g. About the role, ...)". It doesn't say we must wrap everything in those headings. So we can have a
for company overview then
About the role
etc. But we must not repeat job title as heading. The job title is "Customer Support Specialist (CSS)". Not used as heading. Let's extract content. Company overview: first paragraph about Peraton: "About Peraton Peraton is a next-generation national security company..." We'll keep as. Program Overview: "Peraton provides the customer with enterprise infrastructure support to plan, engineer, implement, enhance, maintain and operate the global consular affairs IT environment." Could be part of About the role? Might be separate but we can incorporate into About the role
. About The Role: The paragraph after "About The Role". We'll put that as content under About the role heading. Responsibilities: The "Day to Day Roles and Responsibilities:" list. We'll turn each sentence into
- with items.
Benefits: Benefits Statement: list of benefits. We'll make
- .
Pay: Target Salary Range sentence. We'll put as
. Schedule: Core Work Schedule, training program, shift details. We'll make
maybe with
- for details? Could be prose.
Let's extract exact text.
Company overview paragraph:
"About Peraton Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure."
We'll keep as one
. Program Overview sentence: "Peraton provides the customer with enterprise infrastructure support to plan, engineer, implement, enhance, maintain and operate the global consular affairs IT environment." We could add as another
before About the role. Now About the role heading content: The paragraph after "About The Role". Let's copy: "Peraton is seeking a Customer Support Specialist (CSS) to join our team of qualified and diverse professionals supporting the Department of State (DOS) Bureau of Diplomatic Technology (DT) Consular Affairs Enterprise Infrastructure Operations (CAEIO) Program. The CAEIO Program provides global IT Operations and Maintenance services supporting the modernization, availability, reliability, and security of legacy networks, applications, databases, and enterprise services supporting Consular Affairs operations. The CSS is a member of the Service Desk team supporting the CA Service Center. The Service Desk serves as the central point of coordination for IT service events affecting the CA IT infrastructure and user community. The CSS provides technical support and service management functions across the enterprise, requiring the ability to independently assess user-reported issues, analyze available information, determine appropriate resolution or escalation paths, and coordinate with technical support organizations to restore services and fulfill customer requirements. The CSS is expected to apply established IT service management practices, technical knowledge, and independent judgment to resolve incidents and requests, maintain service quality, identify recurring issues, and contribute to continuous improvement of Service Desk operations. The position interacts regularly with CAEIO technical teams, DOS leadership, customers, and other stakeholders to support effective service delivery and compliance with established service-level objectives." We'll put that as
under About the role. Now Responsibilities: The list after "Day to Day Roles and Responsibilities:" We'll split each sentence (separated by periods). Let's extract sentences: 1. Provide technical analysis and remote support for enterprise software, desktop computing, network connectivity, mobile devices, and related IT services through telephone, email, chat, and enterprise service management platforms. 2. Assess reported incidents and service requests, gather relevant technical and customer information, determine appropriate troubleshooting and resolution approaches, and implement or coordinate corrective actions within established procedures. 3. Diagnose and resolve common technical issues using documented procedures, knowledge management resources, technical documentation, and established IT service management practices. 4. Determine when incidents require escalation based on technical complexity, business impact, security considerations, service-level requirements, or available support capabilities, and coordinate escalation with appropriate technical organizations. 5. Maintain ownership of assigned incidents and service requests through resolution or appropriate escalation, ensuring customers receive timely updates and that required actions are documented. 6. Communicate directly with customers to clarify technical issues, gather diagnostic information, provide status updates, explain resolutions, and confirm successful restoration of service. 7. Analyze incident information and recurring issues to identify trends, knowledge gaps, or opportunities to improve service delivery and first-contact resolution. 8. Create and maintain accurate technical documentation, incident records, troubleshooting information, and knowledge articles supporting Service Desk operations. 9. Contribute to the development and improvement of Knowledge Base content by documenting effective troubleshooting techniques, solutions, workarounds, and lessons learned. 10. Apply ITIL-based Incident Management and Request Fulfillment practices to assigned work while ensuring compliance with applicable government policies, procedures, security requirements, SLAs, and SLOs. 11. Monitor ServiceNow dashboards and operational queues to identify unassigned, aging, pending, or otherwise at-risk incidents and requests and take appropriate action to facilitate timely resolution. 12. Analyze ticket status, workload, aging, and service-level information to identify potential risks to customer service and escalate concerns to appropriate Service Desk leadership. 13. Participate in shift turnover activities by communicating significant incidents, unresolved issues, service impacts, operational concerns, and other information necessary to maintain continuity of service. 14. Prepare and communicate scheduled operational reports and shift deliverables, ensuring information is complete, accurate, and submitted within established requirements. 15. Coordinate with Service Desk colleagues, CAEIO technical teams, and other stakeholders to facilitate incident resolution, service restoration, and fulfillment of customer requests. 16. Maintain working knowledge of Service Desk processes, enterprise applications, support procedures, and operational responsibilities sufficient to provide effective technical support and provide backup coverage across Service Desk functions. 17. Identify opportunities to improve processes, procedures, knowledge resources, and customer support practices and provide recommendations to Service