Service Desk Analyst

We need to output HTML fragment with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Remove boilerplate, duplicate lines, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About ECI: description of company. Could be "About the role"? Actually "About ECI" is company overview. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for company overview? Usually "About the role" is about the job. But we have "About ECI" describing company. Could treat as "About the role"? Might be okay. However they said do NOT repeat the job title as a heading. Not relevant. We need sections: maybe "About the role" (company overview), "Responsibilities", "Required Skills & Experience" (could be Requirements or Qualifications), "Preferred / Nice-to-Have" (maybe Skills), "What Success Looks Like" (maybe Qualifications?), "Why Join ECI?" (maybe Benefits?), "Working Conditions" (maybe Schedule? but schedule not given). There's no explicit Pay or Schedule. So we should not create Pay or Schedule sections unless posting actually states them. It does not mention pay or schedule specifics. So omit those. Benefits: posting mentions "Competitive compensation and benefits." Also "Love your job. Share your passion for technology. Create your future at ECI." Also "ECI also offers a competitive compensation package and so much more!" That's vague. Not specific benefits like health insurance etc. Should we include Benefits section? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting says "Competitive compensation and benefits." That's generic but still states benefits exist. Is that considered specific? It's vague but mentions benefits. Might be okay to include Benefits section with that statement. However they said prefer a few substantive sections over many thin ones. Could combine benefits into Why Join ECI? But Why Join ECI? includes "Competitive compensation and benefits." plus other points. So we could have a Benefits section with that line. But we also have "Working Conditions" which is not in the list of allowed headings. The allowed headings are limited to those examples. We should not create a heading not in list unless we think it's needed? 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 could use other headings? Probably we should stick to those. Working Conditions could be placed under Responsibilities? Not really. Could be omitted? But we must preserve ALL substantive information. Working Conditions is substantive. We could incorporate it into Responsibilities or maybe a separate section but not in allowed list. However we could treat it as "Requirements"? Not appropriate. Maybe we can create a section "Working Conditions" as a heading despite not being in examples? The instruction says use those for section headings (e.g. ...). It might be okay to use other headings if needed, but they gave examples. Safer to stick to given headings and fold Working Conditions into Responsibilities or Requirements? Could be under Responsibilities as part of what you will do? It's about physical demands, not duties. Could be under "Requirements"? Not exactly. Could be under "Qualifications"? Not. Maybe we can create a section "Working Conditions" as a heading, but risk violating instruction. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings; but not strictly prohibited to use others. However they also say "Prefer a few substantive sections over many thin ones." So we could combine Working Conditions into Responsibilities as a bullet? Might be okay. Let's extract substantive content: Company overview (About ECI): two paragraphs duplicated but we need to preserve all info without duplication. We'll combine unique info. From text: "ECI is the leading global provider of managed services, cybersecurity, and business transformation for mid-market financial services organizations across the globe. From its unmatched range of services, ECI provides stability, security and improved business performance, freeing clients from technology concerns and enabling them to focus on running their businesses. More than 1,000 customers worldwide with over $3 trillion of assets under management put their trust in ECI. At ECI, we believe success is driven by passion and purpose. Our passion for technology is only surpassed by our commitment to empowering our employees around the world." Then later: "About ECI ECI is a leading global provider of managed services, cybersecurity, and business transformation for the financial services industry. We support more than 1,000 clients worldwide, representing over $3 trillion in assets under management. Our mission is to provide stability, security, and operational excellence—so our clients can focus on running their businesses. At ECI, our passion for technology is matched by our commitment to our people. We foster a culture of accountability, continuous improvement, and client-first thinking." Combine: leading global provider of managed services, cybersecurity, business transformation for mid-market financial services organizations (or financial services industry). Over 1,000 clients worldwide, over $3 trillion AUM. Provides stability, security, improved business performance, operational excellence. Passion for technology, commitment to employees, culture of accountability, continuous improvement, client-first thinking. We'll produce a paragraph. Opportunity / The Opportunity: description of role: seeking Service Desk Analysts, ideal for technologists, fast-paced managed services environment, solving complex end-user problems, delivering world-class support, front line for clients, Level 1 and Level 2 support across modern Microsoft-centric ecosystems, identify trends, reduce repeat issues, contribute to continuous improvement. Work model: Onsite role based in New York office (with potential flexibility based on business needs). We'll put that under "About the role" maybe? Actually "About the role" could include opportunity description. We'll use "About the role" heading for role description. Responsibilities: bullet list from "What You Will Do". Provide Level 1 and Level 2 end-user support for Windows-based environments across multiple client locations. Deliver exceptional client experience, particularly during high-impact or VIP incidents. Triage, diagnose, resolve incidents and service requests using ITIL-aligned practices. Support and troubleshoot issues related to: Microsoft 365 (Outlook, Teams, OneDrive, SharePoint); Exchange Online and email security; Endpoint performance, OS issues, application errors; File access, permissions, restores, print services; Remote access technologies (Cloud PC, AVD, Citrix, VPN); Perform user and access administration in Active Directory and Azure AD (Entra ID); Support endpoint management and security tooling, including Microsoft Intune and MDM/MAM platforms; Use ServiceNow and remote support tools to manage workload and meet SLA commitments; Collaborate with Engineering, Network, Security, and Client Success teams to drive timely resolution and escalation; Participate in project work such as new-hire onboarding, hardware refreshes, Microsoft 365 migrations, and cloud adoption initiatives; Identify recurring issues, document known errors, contribute to service improvement initiatives. We'll make a

with each as
• . Required Skills & Experience: list under "Requirements" or "Qualifications". We'll use "Requirements". Items: Experience providing end-user IT support in a corporate or MSP environment (early-career candidates considered). Strong working knowledge of: Windows 11; Microsoft 365 and Office applications; Azure AD (Entra ID), Exchange Online, OneDrive, SharePoint, Teams; Hands-on experience with endpoint and device management tools (e.g., Microsoft Intune); Familiarity with identity and access concepts including MFA and conditional access; Basic PowerShell usage for administrative tasks; Experience supporting mobile devices (iOS and Android); Foundational networking knowledge (TCP/IP, DNS, DHCP); Working knowledge of cybersecurity fundamentals; Experience with a service management platform (ServiceNow preferred); Strong communication skills and ability to work in a high-volume support environment. We'll make a
  . Preferred / Nice-to-Have: could be under "Skills" or "Qualifications". We'll use "Skills". Items: Experience working within a Managed Service Provider (MSP); Familiarity with ITIL v4 concepts; Exposure to Azure; Experience supporting Apple/Mac-based environments; Experience supporting financial services or alternative investment clients; Familiarity with Bloomberg, Refinitiv, or FactSet; Relevant certifications (MS-900, AZ-900, ITIL 4 Foundation). We'll make a
  . What Success Looks Like: could be under "Qualifications"? Actually it's about performance expectations. Could be its own section but not in list. Could be under "Requirements"? Not exactly. Could be under "Qualifications"? Might be okay to create a section "Qualifications" for this. But we already used Qualifications? Not yet. We have Requirements and Skills. We could use Qualifications for success metrics. Let's use "Qualifications" heading for What Success Looks Like. Items: High client satisfaction and positive client feedback; Consistent achievement of SLA and quality targets; Reduction in repeat incidents through strong troubleshooting and documentation; Effective collaboration with peers and escalation teams; Continued growth in technical depth and ownership. We'll make a
  . Why Join ECI?: could be under "Benefits". Items: Support mission-critical financial services clients globally; Exposure to modern cloud, security, and automation technologies; Clear career development pathways; Competitive compensation and benefits; A culture that values accountability, teamwork, and continuous improvement; Love your job. Share your passion for technology. Create your future at ECI. We'll make a
  . Working Conditions: we need to preserve. Could be under "Responsibilities"? Not ideal. Could be under "Requirements"? Not. Could be under "Skills"? Not. Could be under "Benefits"? Not. Could be under "Qualifications"? Not. Perhaps we can create a section "Working Conditions" despite not being in list, but risk. However we could incorporate into Responsibilities as a bullet about physical demands? Might be okay to add a bullet under Responsibilities: "Ability to work under a moderate noise level...", etc. But those are not duties but working conditions. Still we can include as bullet under Responsibilities? Might be okay. Alternatively we could create a section "Working Conditions" as

  and hope it's acceptable. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. I'd lean to include Working Conditions as its own heading because it's substantive and not covered elsewhere. The risk is minor. I'll include it. We must not include boilerplate like EEO, legal, etc. Not present. We must not repeat job title. Not present. We must not include application instructions. Not present. We must not include duplicated lines. We'll deduplicate. Now produce HTML fragment. Structure:

  About the role

  ... company overview + opportunity description? Actually we separated company overview and opportunity. Could combine both under About the role. Let's do that: About the role includes company overview and opportunity description. Paragraph: combine company overview and opportunity. Let's craft: ECI is a leading global provider of managed services, cybersecurity,