Technical Support Representative Senior
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: - "This position is not eligible for visa sponsorship, now or in the future. Candidates must be a US Citizen or valid Green Card Holder. This position is hybrid 3 days per week in the following office locations: Cincinnati, OH" -> This is metadata: visa, citizenship, hybrid schedule, location. Should be folded into a short
maybe. - "Ready to take your career global? Make your mark at one of the biggest names in payments. We’re looking for a Technical Support Representative to join our ever-evolving Workstation Asset Management team and help shape the future of global commerce." -> This is intro. - "Schedule: Sunday-Tuesday and every other Wednesday 8am-8pm ET" -> schedule info. - "What You’ll Own" bullet list: Providing technical support regarding network infrastructure, internal desktops and clients, servers, and software. Performing account management that includes adding and deleting users, creating new user accounts, and modifying accounts. Maintaining passwords, data integrity, and file system security. Communicating highly technical information in layman terms to non-technical users. Recommending hardware and software solutions. - "What You’ll Bring": Experience providing end-user LAN/WAN support for Windows XP/Vista/7, and MS Office 2003/2007/2010/2013. Expertise with anti-virus and backups. We prefer experience supporting Windows 2003/2008/2008R2 and a background troubleshooting MS Exchange and supporting Citrix. A bachelor’s in CIS, Business, or related field, or three years of equivalent experience. - "About The Team": paragraph about inclusive global teams. - "What makes a Globalpayer? ..." paragraph. - "Does this sound like you? Then you sound like a Globalpayer. Apply now to take your career global." -> application instruction, should be removed. We need to produce sections: maybe "About the role" (intro), "Responsibilities" (What You’ll Own), "Requirements" (What You’ll Bring), "Qualifications" (maybe education/experience), "Skills" (maybe technical skills), "Schedule" (the schedule), maybe "Benefits" not present, "Pay" not present. Also "About the Team" could be a section but not in list; we could treat as "About the Team" but not in allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use others? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings; but we can also include other headings if needed? Safer to stick to those. We have content for About the role (intro), Responsibilities, Requirements, Qualifications, Skills, Schedule. Benefits and Pay not present, so omit.
We need to decide what goes where.
- About the role: intro paragraph(s) about role, team, mission. Could combine the first paragraphs: "Ready to take your career global? Make your mark at one of the biggest names in payments. We’re looking for a Technical Support Representative to join our ever-evolving Workstation Asset Management team and help shape the future of global commerce." plus maybe the team description? But team description could be separate but we don't have a heading for About the Team. Could include in About the role.
- Responsibilities: the "What You’ll Own" list.
- Requirements: maybe the "What You’ll Bring" list (experience, expertise, preferences). Could also include citizenship/visa requirement? That is metadata; could be placed in a short
before sections. - Qualifications: education requirement (bachelor's or equivalent). Could be separate. - Skills: technical skills list (LAN/WAN support, anti-virus, backups, Windows versions, MS Exchange, Citrix). Could be separate. - Schedule: the schedule line. We need to preserve all substantive information, not invent or summarize away detail. So we must keep all details. Let's extract details: Metadata: - Not eligible for visa sponsorship, now or in the future. - Candidates must be a US Citizen or valid Green Card Holder. - Hybrid 3 days per week in Cincinnati, OH. Intro: - Ready to take your career global? Make your mark at one of the biggest names in payments. - We’re looking for a Technical Support Representative to join our ever-evolving Workstation Asset Management team and help shape the future of global commerce. Team description (maybe part of About the role): - Our inclusive and global teams win together every day. We’re proud to have the best minds in the industry, who you can learn from as you grow your career. The people, the energy, the connections – it’s unmatched. Come and be part of an ever-evolving company and get dynamic opportunities that go beyond borders. - What makes a Globalpayer? Globalpayers think like a client, act like an owner and win as one team. We’re curious and innovative – always finding better ways to deliver impact. We empower each other to make decisions, and it’s our passion that drives excellence in everything we set out to do. - Does this sound like you? Then you sound like a Globalpayer. Apply now to take your career global. (Remove application instruction.) But we must remove application instructions: "Apply now to take your career global." So we should drop that sentence. Also "Does this sound like you? Then you sound like a Globalpayer." Could be considered a call to action; maybe we keep as part of team description? It's not exactly application instruction but it's encouraging to apply. Might be considered boilerplate? The instruction says remove application instructions. That sentence is encouraging to apply; likely considered application instruction. Safer to remove both "Does this sound like you? Then you sound like a Globalpayer." and "Apply now to take your career global." However, the preceding sentences about Globalpayer are descriptive of culture; we can keep those. Thus keep: - What makes a Globalpayer? Globalpayers think like a client, act like an owner and win as one team. We’re curious and innovative – always finding better ways to deliver impact. We empower each other to make decisions, and it’s our passion that drives excellence in everything we set out to do. Now responsibilities list: - Providing technical support regarding network infrastructure, internal desktops and clients, servers, and software. - Performing account management that includes adding and deleting users, creating new user accounts, and modifying accounts. - Maintaining passwords, data integrity, and file system security. - Communicating highly technical information in layman terms to non-technical users. - Recommending hardware and software solutions. Requirements list (What You’ll Bring): - Experience providing end-user LAN/WAN support for Windows XP/Vista/7, and MS Office 2003/2007/2010/2013. - Expertise with anti-virus and backups. - We prefer experience supporting Windows 2003/2008/2008R2 and a background troubleshooting MS Exchange and supporting Citrix. - A bachelor’s in CIS, Business, or related field, or three years of equivalent experience. We could split qualifications: education requirement (bachelor's or equivalent) as Qualifications. Skills: technical skills (LAN/WAN support, MS Office, anti-virus, backups, Windows 2003/2008/2008R2, MS Exchange, Citrix). Experience: maybe part of Requirements. But we need to avoid duplication. Let's decide: Section "About the role": intro + team description + Globalpayer description (without apply). Also include metadata? Could include metadata in a short p before sections. Section "Responsibilities": the What You’ll Own list. Section "Requirements": the experience and expertise statements (maybe combine). Could include the preferred experience and the bachelor's requirement? But we have Qualifications separate. Section "Qualifications": bachelor's or equivalent. Section "Skills": technical skills list (LAN/WAN support, MS Office, anti-virus, backups, Windows 2003/2008/2008R2, MS Exchange, Citrix). Might also include account management? That's responsibility. Section "Schedule": the schedule line. We must not repeat content. Ensure all substantive info appears somewhere. Let's list all substantive info: Metadata: - Not eligible for visa sponsorship, now or in the future. - Candidates must be a US Citizen or valid Green Card Holder. - Hybrid 3 days per week in Cincinnati, OH. Intro: - Ready to take your career global? Make your mark at one of the biggest names in payments. - We’re looking for a Technical Support Representative to join our ever-evolving Workstation Asset Management team and help shape the future of global commerce. Team description: - Our inclusive and global teams win together every day. - We’re proud to have the best minds in the industry, who you can learn from as you grow your career. - The people, the energy, the connections – it’s unmatched. - Come and be part of an ever-evolving company and get dynamic opportunities that go beyond borders. Globalpayer description: - What makes a Globalpayer? Globalpayers think like a client, act like an owner and win as one team. - We’re curious and innovative – always finding better ways to deliver impact. - We empower each other to make decisions. - It’s our passion that drives excellence in everything we set out to do. Responsibilities: - Providing technical support regarding network infrastructure, internal desktops and clients, servers, and software. - Performing account management that includes adding and deleting users, creating new user accounts, and modifying accounts. - Maintaining passwords, data integrity, and file system security. - Communicating highly technical information in layman terms to non-technical users. - Recommending hardware and software solutions. Experience/Requirements: - Experience providing end-user LAN/WAN support for Windows XP/Vista/7, and MS Office 2003/2007/2010/2013. - Expertise with anti-virus and backups. - We prefer experience supporting Windows 2003/2008/2008R2 and a background troubleshooting MS Exchange and supporting Citrix. - A bachelor’s in CIS, Business, or related field, or three years of equivalent experience. Schedule: - Sunday-Tuesday and every other Wednesday 8am-8pm ET. Now we need to map to sections. About the role: Could include intro, team description, Globalpayer description. Also maybe mention hybrid location? But that's metadata; we could put metadata in a short p before sections. Let's create a short p for metadata: "This position is not eligible for visa sponsorship; candidates must be a US Citizen or valid Green Card Holder. The role is hybrid (3 days per week) in Cincinnati, OH." Then About the role: combine intro + team + Globalpayer. Responsibilities: list. Requirements: maybe the experience statements (excluding education). Could include the experience with LAN/WAN, MS Office, anti-virus, backups, preferred Windows, MS Exchange, Citrix. Qualifications: bachelor's or equivalent. Skills: maybe we could combine with Requirements? But we need to avoid thin sections. Could merge Requirements and Skills into one? But we have to follow instruction: prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into a single "Requ