IT Systems Administrator (New York)

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs before responsibilities. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only when posting has real specific content. We have content: description about company, mission, etc. Could be "About the role" or maybe "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have responsibilities listed under "Key Responsibilities". So we can put that under

Responsibilities

with

• items. Requirements: "Key Requirements" and "Nice to Have". Could be Requirements section (mandatory) and maybe Skills? The nice-to-have could be Skills? Or Qualifications? The instruction includes Qualifications and Skills separate. We could put mandatory requirements under Requirements, nice-to-have under Skills, and maybe Qualifications could be degree etc. But we need to avoid filler sections. We have degree mention: "A degree in IT, Computer Science, or Information Systems is welcome; equivalent hands-on experience counts equally." That could go under Qualifications. We have Pay: "$100,000 - $120,000 a year". So we need a Pay section. Schedule: Not mentioned explicitly; it's Full-Time On-site. Could infer schedule? The posting says Full-Time. But we should not create Schedule unless posting actually states them. It says Full-Time, which is schedule type. Could we consider that as schedule? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Full-Time (which is schedule). So we can include Schedule section with "Full-Time, On-site". However we need to check if we should include Benefits: Not mentioned. So omit Benefits. We also have "We Believe" statements etc. That could be part of About the role or maybe a separate section like "About the company". But we only allowed headings list; we could put that under About the role (makes sense). Or we could create a separate section like "About the company" but not allowed. So we put under About the role. We need to remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes "Background Checks", "A Note on Recruiting Outreach". Those are legal/boilerplate; we should remove them. Also repeated "apply for this job" lines etc. Remove duplicates. We need to preserve all substantive information. So we keep the description about Lendbuzz mission, responsibilities, requirements, nice-to-have, pay, schedule (Full-Time On-site). Also maybe mention "You will be the only IT person on-site" etc is part of responsibilities. We need to format as HTML fragment only, no or . Use

  for headings,

  • for lists,

    for prose. We need to decide how to split content into sections. Potential sections: - About the role: includes company mission description and role overview (first paragraphs). Could be a

    with that text. - Responsibilities:

    Responsibilities

    with
    list items (maybe grouped by subheadings? But we can just list each bullet as
    • ). The responsibilities are described in paragraphs with bullet-like sentences. We'll extract each responsibility as a list item. - Requirements:

      Requirements

      with mandatory requirements list. - Qualifications: maybe degree etc. Could be

      Qualifications

      with list. - Skills:

      Skills

      with nice-to-have list. - Pay:

      Pay

      with

      $100,000 - $120,000 a year

      - Schedule:

      Schedule

      with

      Full-Time, On-site

      We must not repeat job title as heading. Not include Job ID. We must not include filler like "commensurate with experience". Not present. Now we need to extract the content precisely. Let's parse the posting. First paragraph: "At Lendbuzz, we believe financial opportunity should be more personalized and fair. We develop innovative technologies that provide underserved and overlooked borrowers with better access to credit. From our employees to our dealers, partners, and borrowers, we’ve built a company and a culture around a resolute belief in the promise and power of diversity. We value independent and critical thinking." Then: "We are hiring an IT Systems Administrator to own day-to-day IT for our New York office. You will be the only IT person on-site, which makes you the face of IT for everyone in the office. You are part of a global IT team reporting to IT leadership in Boston, who share tooling standards, escalation paths, and coverage." That's role overview. Then "Key Responsibilities" heading followed by paragraphs: - "Identity and Google Workspace administration Administer Google Workspace end-to-end (Gmail, Drive/shared drives, Calendar, Groups, Meet) plus core business/SaaS apps the NY office depends on user provisioning, access controls, and security settings coordinating with the global team on tenant-level configuration.Use Google Vault, the Security Investigation Tool, and Alert Center to support audits, security investigations, and eDiscovery requests.Own local access management: MFA enforcement, periodic user access reviews, device compliance, and least-privilege access, in line with global policy." That's a long sentence; we can split into bullet items: maybe separate responsibilities: Identity and Google Workspace administration; Endpoints and device management; Office infrastructure and AV; Service delivery and documentation. But the text includes headings within responsibilities: "Identity and Google Workspace administration", "Endpoints and device management", "Office infrastructure and AV", "Service delivery and documentation". Those are subheadings. We could keep them as part of list items or we could make subheadings? But only allowed headings are the specified ones; we cannot add extra headings like subheadings. So we should incorporate them into list items. Thus we can create list items each starting with the subheading maybe. Let's extract each responsibility block: 1. Identity and Google Workspace administration: - Administer Google Workspace end-to-end (Gmail, Drive/shared drives, Calendar, Groups, Meet) plus core business/SaaS apps the NY office depends on user provisioning, access controls, and security settings coordinating with the global team on tenant-level configuration. - Use Google Vault, the Security Investigation Tool, and Alert Center to support audits, security investigations, and eDiscovery requests. - Own local access management: MFA enforcement, periodic user access reviews, device compliance, and least-privilege access, in line with global policy. 2. Endpoints and device management: - Provision, troubleshoot, and repair macOS/Windows laptops, mobile devices, and peripherals. - Manage macOS in Jamf: enrollment, configuration profiles, software deployment, and compliance policies. - Run employee lifecycle processes (onboarding, offboarding, role changes) device prep, account setup, and access changes and maintain accurate asset records for laptops, accessories, licenses, ownership, and equipment status. 3. Office infrastructure and AV: - Maintain office network infrastructure (LAN/Wi-Fi, IP addressing, DNS/DHCP), coordinating with ISPs and network vendors on larger issues. - Set up and maintain Zoom Rooms/AV and conference rooms, keeping them reliably ready day to day to resolve printer connectivity/hardware issues. - Support desk setups, office moves, and new-space buildouts alongside the Workplace team. 4. Service delivery and documentation: - Track and resolve Jira tickets, keeping prioritization, response times, and communication consistent. - Find recurring tickets and remove the cause automate a provisioning step, fix the root issue, or document the fix. - Write and maintain SOPs and knowledge base docs so employees can self-serve and the global team can cover NY when you're out; partner with global IT, stakeholders, and vendors on escalations and process improvement. Now Requirements: "Key Requirements 4+ years in IT support, IT operations, systems administration, or SaaS administration. A degree in IT, Computer Science, or Information Systems is welcome; equivalent hands-on experience counts equally.Hands-on experience administering Google Workspace in a business environment.Experience supporting both macOS and Windows, with Jamf or another MDM platform.Working knowledge of networking fundamentals: LAN/Wi-Fi, DNS, DHCP, and IP addressing.Experience with a ticketing system such as Jira to manage and resolve support requests.Understanding of user access management, including account lifecycle and access review processes.Strong communication and customer service instincts — you can explain a fix to a non-technical colleague without making them feel foolish.Comfort as the sole on-site technical resource: you prioritize your own queue, know when to escalate, and stay steady when several things break at once." We can split into list items. Nice to Have: "Nice to Have Okta: SSO, MFA, provisioning, lifecycle management, and access policies.Apple Business Manager.Advanced Google Workspace features: Context-Aware Access, DLP, and OAuth app control.Scripting and automation — Google Apps Script, Bash, Python, or similar — to replace manual provisioning and reporting work.Exposure to security and compliance frameworks such as SOC 2, ISO 27001, or PCI DSS.Certifications in Google Workspace, Okta, Jamf, Apple, or general IT support." We can list each. Pay: "$100,000 - $120,000 a year" Schedule: The posting says "Full-Time / On-site". So schedule: Full-Time, On-site. Now About the role: We'll include the initial paragraphs about Lendbuzz mission and role overview. We also have "We Believe:" section after pay? Actually after pay there is "We Believe: Diversity is a competitive advantage..." etc. That's company values. Could be part of About the role or maybe a separate section but we don't have a heading for values. We could include under About the role as additional prose. Thus About the role will contain multiple paragraphs: mission, role overview, and We Believe statements. We need to ensure we don't include boilerplate like "Background Checks", "A Note on Recruiting Outreach", and repeated "apply for this job". Remove those. Now produce HTML. We'll need to escape any HTML special characters? Not needed. We'll output:

      About the role

      At Lendbuzz, we believe financial opportunity should be more personalized and fair. We develop innovative technologies that provide underserved and overlooked borrowers with better access to credit. From our employees to our dealers, partners, and borrowers, we’ve built a company and a culture around a resolute belief in the promise and power of diversity. We value independent and critical thinking.

      We are hiring an IT Systems Administrator to own day-to-day IT for our New York office. You will be the only IT person on-site, which makes you the face of IT for everyone in the office. You are part of a global IT team reporting to IT leadership in Boston, who share tooling standards, escalation paths, and coverage.

      We Believe: Diversity is a competitive advantage. We celebrate our differences, and are better when we have a variety of experiences, viewpoints, and backgrounds. Compassion is a strength. We care about our customers and look to build long-term relationships with them. Simplicity is a key feature. We work hard to make our forms and processes as painless and intuitive as possible. Honesty and transparency are non negotiable. We incorporate these traits in all of our interactions. Financial opportunity belongs to everyone. We work every day to improve lives by extending this opportunity. If you believe these things too then we would love to hear from you!

      Then Responsibilities:

      Responsibilities