Senior IT Administrator

We need to output HTML fragment with sections: About the role? The job details include a description about IonQ and role description. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - About IonQ (company description) maybe "About the role"? Actually "About the role" could be the introductory paragraph describing the role: "We are seeking a highly motivated and versatile Senior IT Administrator to be the dedicated on-site IT presence for our College Park office and the primary technical resource for two nearby satellite lab locations. This critical role involves providing hands-on support across the entire IT spectrum, including end-user helpdesk, A/V management, networking, and critical project work." That is substantive. - Responsibilities: we have a big list under "Responsibilities" heading with subpoints. - Requirements/Qualifications/Skills: The posting has "You Would Be a Good Fit With" and "You Would Be a Great Fit With". Those are qualifications/skills. We need to decide how to split: maybe "Qualifications" for required (Good Fit) and "Skills" for preferred (Great Fit) or combine. The instruction says use headings like Requirements, Qualifications, Skills. We can choose to have "Qualifications" for required and "Preferred Qualifications" maybe but not required. However we should not create sections with filler. We have content for both. We also have Location, Travel, Salary (Pay), Benefits. - Pay: "The approximate base salary range for this position is $107,123 - $140,251." Also mentions total compensation includes base, bonus, equity. That's substantive. So we can include Pay section. - Benefits: "Our benefits include comprehensive medical, dental, and vision plans, matching 401(k), unlimited PTO and paid holidays, parental/adoption leave, legal insurance, and a home technology stipend." That's substantive. So Benefits section. - Schedule: Not explicitly mentioned except maybe "may require after-hours support." Not a schedule. Could be considered schedule but not explicit. Probably we should not create Schedule section because no explicit schedule like full-time, part-time, shift. There's mention "must be able to work on-site full-time". That's schedule: full-time on-site. Could be considered schedule. But we have location and travel. The instruction says only create Schedule if posting actually states them. It does state "must be able to work on-site full-time". That's a schedule detail. So we could include Schedule section with that. But we also have Location: "Location: This role will be based in our College Park office and may require after-hours support." That's location info. Could be part of a short paragraph maybe under a heading "Location". However the allowed headings list does not include Location. They only gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fold location into maybe About the role or a short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Location is minor metadata? Could be folded into a short p. Probably we can include location in a paragraph after About the role. Travel: "Travel: Up to 10%". That's also minor metadata; could be folded. We need to preserve all substantive information. So we need to include location and travel info somewhere, maybe in a

after About the role. We must not include boilerplate like EEO, export control, etc. Remove those. We need to output only HTML fragment, no /, no markdown fences. Thus structure:

About the role

We are seeking a highly motivated and versatile Senior IT Administrator to be the dedicated on-site IT presence for our College Park office and the primary technical resource for two nearby satellite lab locations. This critical role involves providing hands-on support across the entire IT spectrum, including end-user helpdesk, A/V management, networking, and critical project work. Location: College Park, Maryland office; may require after-hours support. Travel: up to 10%.

Then Responsibilities:

Responsibilities

• ...
...

We need to capture all responsibilities bullet points from the posting. Let's extract responsibilities: Under "Responsibilities" heading: - Onsite IT Operations and End-User Support - Primary Technical Liaison: Serve as the dedicated, primary technical point of contact for the main College Park office, providing scheduled, expert support visits to two satellite lab locations in the region. - Helpdesk & Desktop Support: Deliver hands-on Level 2 support, specializing in the timely diagnosis and resolution of all hardware, software, connectivity, and printer issues for local staff. - Asset Lifecycle Management: Own the complete local IT inventory lifecycle, including the provisioning, maintenance, and retirement of all end-user hardware (laptops, monitors, peripherals), while ensuring continuous stocking of essential IT supplies. - Lab Equipment Support: Provide dedicated operational and technical support for IT equipment within critical laboratory environments. - A/V Management: Manage the setup, operation, and ongoing support of all conference room A/V equipment and provide reliable, on-the-spot support for meetings and occasional company-wide events. - Lab Infrastructure & Configuration Management (SDE/Automation Focus) - Lab Workstation Management: Serve as the primary contact for lab IT support. This includes setting up new lab workstations (imaging and baseline), deploying standard configurations via playbooks, and maintaining a test workstation for pre-production changes. - Data Access & Networking: Set up permissions for lab workstations to securely access IonQ data (e.g., shared drive, Confluence). Assist with deploying necessary lab network services (e.g., DNS server, Synology/shared drive configuration). - Routine Maintenance: Coordinate and perform routine maintenance, including monthly software updates and reboots for lab workstations, in coordination with research teams. - Documentation: Update and write guides for recurring lab IT tasks (e.g., remote connection, SSH, file sharing). - Network and Infrastructure Assistance - Local Network Troubleshooting: Perform foundational network troubleshooting for common issues related to VPNs, switches, firewalls, and wireless access points (APs). - Escalation & Liaison: Serve as the local technical liaison, escalating complex network issues to the core engineering teams and coordinating local efforts. - Physical Deployment: Assist the network engineering team with the physical installation and de-installation of networking gear (e.g., racking/stacking switches, and deploying APs). - Strategic Projects and M&A Integration - Corporate Projects: Actively participate in assigned internal corporate IT projects, such as system upgrades, security initiatives, and documentation/process standardization improvements. - Remote Site Deployment: Travel occasionally to new or acquired satellite locations to execute the foundational installation of desktops, networking gear and audio/visual equipment. We need to preserve all that. We'll put each as

. Could group under subheadings? Not allowed; only

for section headings. We could keep bullet list flat. Now Qualifications/Requirements/Skills. We have "You Would Be a Good Fit With" (required) and "You Would Be a Great Fit With" (preferred). We could split into two sections: "Qualifications" (required) and "Skills" (preferred) or "Preferred Qualifications". The instruction allows Qualifications, Skills headings. We'll do:

Qualifications

• 6+ years of experience in a System Administrator, Desktop Support, or Helpdesk role.
• Demonstrable experience providing hands-on, end-user technical support in a corporate environment.
• Proficiency with Windows, Linux, and macOS operating systems.
• Experience administering SAML-based SaaS Apps (Okta, Entra, Jumpcloud).
• Supporting cloud-based productivity applications (M365, Google Workspace).
• Solid understanding of basic networking concepts (TCP/IP, DHCP, DNS) and experience with basic troubleshooting of network devices (switches, firewalls, Wi-Fi).
• Experience with A/V setup and support for modern video conferencing solutions (e.g., Zoom Rooms, Google Meets, Microsoft Teams Rooms).
• Strong organizational skills and experience with inventory management and asset tracking.
• Excellent written and verbal communication skills, with a focus on customer service and clear technical documentation.
• Must be able to work on-site full-time in the College Park office.

Then

Skills

(preferred):

• Experience in a rapidly growing environment or a technology-focused company.
• Certifications such as CompTIA Network+, CompTIA Security+, or Cisco Certified Network Associate (CCNA) are a plus.
• Demonstrable experience with Configuration Management tools (e.g., Ansible, Puppet, Chef) or scripting/automation (e.g., Python, Bash).
• Experience in a rapidly growing, technology-focused company or lab environment.
• Prior experience supporting research or engineering teams with custom lab software.
• Keep lab playbooks up to date and evaluate replacements for existing Ansible playbooks used for setting up new workstations and developer desktops.
• Interface with the security team to ensure compliance.
• Prior experience with IT support for M&A activity.

Note there is some duplication: "Experience in a rapidly growing environment or a technology-focused company." appears twice; we can keep both but maybe deduplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate the repeated line. It appears twice: once in Good Fit? Actually first appears under Good Fit? Let's check: Under Good Fit: "Experience in a rapidly growing environment or a technology-focused company." Under Great Fit: also "Experience in a rapidly growing, technology-focused company or lab environment." Slightly different but similar. Not exact duplicate. The line "Experience in a rapidly growing environment or a technology-focused company." appears only once under Good Fit. The Great Fit has "Experience in a rapidly growing, technology-focused company or lab environment." Slightly different. So not duplicate. But there is also "Experience in a rapidly growing, technology-focused company or lab environment." under Great Fit. That's similar but not identical. We'll keep both as they are distinct. Now Pay section:

Pay

The approximate base salary range for this position is $107,123 - $140,251. The total compensation package includes base, bonus, and equity. Compensation will vary based on individual factors such as education, qualifications, and experience of the final candidate(s), specific office location, and calibration against relevant market data and internal team equity