Asset Lifecycle Coordinator

We need to output HTML fragment with sections: About the role? Actually we have "About IonQ" description, but we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. 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: description of company, location, etc. Could be "About the role"? Actually "About the role" is a heading for description of role. The posting includes "The Role:" paragraph describing the role. So we could use heading "About the role" for that paragraph. - Responsibilities: we have a detailed list under "Responsibilities:" with sub-bullets. So we need a

Responsibilities

and then

• items. - Requirements: we have "Requirements:" with bullet-like lines. So

  Requirements

  and list. - Preferred Qualifications: we have "Preferred Qualifications:" with bullet lines. Could be under "Qualifications" heading. The instruction includes Qualifications as possible heading. So we could combine Requirements and Preferred Qualifications under Qualifications? But they said prefer a few substantive sections over many thin ones. Could have separate sections: Requirements and Qualifications (Preferred). However we have both; we could make "Requirements" and "Qualifications" sections. Or we could merge them into one "Requirements" section with subheadings? But we must follow instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications sections. - Skills: Not explicitly listed as separate; but we have technical foundations, customer service skills, physical stamina etc. Those are part of Requirements. Could we create a Skills section? Might be redundant. Better to keep Requirements and Qualifications. - Benefits: we have "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." So we have Benefits content. So include Benefits section. - Pay: we have "The approximate base salary range for this position is $86,767 - $113,601." plus description about total compensation includes base, bonus, equity, etc. So we have Pay content. So include Pay section. - Schedule: Not mentioned besides travel 10% domestic/international. No explicit schedule like full-time, hours. So we should not create Schedule section because no specific schedule content. Travel could be mentioned elsewhere maybe in a short paragraph under About the role? But we should not create Schedule heading if no content. - Also we have location: "Location: This role is based at our Bothell, WA office." Travel: 10% domestic or international. This could be included in About the role paragraph or a separate short paragraph. We'll include location and travel in About the role section perhaps. We must remove boilerplate: EEO, legal, export control, etc. Also remove duplicated lines, application instructions. Also remove "Posted base salary figures are subject to change..." maybe keep as part of Pay? It's substantive about pay variability. It's okay. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details about responsibilities, requirements, qualifications, benefits, pay, location, travel, etc. We must not include Job ID. So drop "Job ID: 1717". Also drop "Location:" line maybe incorporate into About the role. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  We are seeking a detail-oriented, organized, and proactive Asset Lifecycle Coordinator to manage the physical and logical lifecycle of our corporate IT assets. In this role, you will be the custodian of our hardware inventory—overseeing everything from initial receiving and staging to deployment, tracking, and final, secure disposal. Beyond core logistical duties, you will serve as a vital extension of our IT support team, utilizing your foundational technical skills to handle basic helpdesk requests, provision devices, and assist local users. This dual-impact role ensures our technology assets are tracked flawlessly while maintaining an excellent support experience for our team. Location: This role is based at our Bothell, WA office. Travel: 10% domestic or international.

  Responsibilities

  • Asset Lifecycle & Logistics Management
    • Receiving & Intake: Securely receive, unbox, inspect, and tag all incoming IT hardware (laptops, monitors, peripherals, and network gear).
    • Inventory Tracking: Maintain 100% accuracy in our Asset Management system. Record serial numbers, user assignments, warranty statuses, and physical locations.
    • Deployment & Provisioning: Coordinate the logistics of shipping hardware to remote employees or setting up workspaces for local staff, ensuring all accessories and standard peripherals are included.
    • Harvesting & Offboarding: Manage the secure return of IT equipment from departing employees. Clean, inspect, test, and assess returned hardware for redeployment or retirement.
    • E-Waste & Secure Disposal: Coordinate the safe and compliant disposal or recycling of legacy hardware. Ensure data sanitization certificates are obtained and filed in compliance with corporate security policies.
  • Legal Holds & Security Compliance
    • Legal Hold Management: Securely isolate, track, and log all hardware placed on active legal holds. Ensure these assets are strictly preserved and exempted from standard data wiping, refurbishment, or disposal cycles.
    • Chain of Custody: Maintain an airtight, documented chain of custody for all sensitive or legally restricted hardware in strict accordance with instructions from the Legal and Security teams.
    • Policy Enforcement: Strictly adhere to corporate security protocols and legal procedures regarding device handling, data privacy, and evidence preservation.
  • Basic IT Helpdesk Support
    • First-Line Triage: Monitor incoming helpdesk tickets, Slack channels, or walk-up requests, providing basic technical assistance or routing complex issues to tier-2 engineers.
    • Hardware Preparation: Perform basic provisioning tasks (e.g., enrolling devices via MDM, imaging laptops, running OS updates, and conducting initial hardware functionality checks).
    • Peripherals & Conference Rooms: Troubleshoot basic workplace tech issues, including monitors, docking stations, keyboards, printers, and meeting room AV setups.
  But note: The instruction says use
  • for any list of duties/requirements/benefits. It didn't forbid nested lists? Probably okay but we could flatten. However we can keep nested lists; still each item is
  • . Might be okay. But we need to preserve all substantive information; we have a lot of sub-bullets. We'll keep them. Next Requirements:

    Requirements

    • Experience: 1–3 years of experience in IT asset management, warehouse inventory tracking, logistics, or an IT desktop support role.
    • Detail-Oriented Mindset: Extreme accuracy in data entry and a passion for keeping spreadsheets, asset databases, and physical storage spaces immaculate.
    • Technical Foundations: Basic familiarity with Mac and Windows operating systems, modern hardware components, and standard computer peripherals.
    • Customer Service Skills: Excellent interpersonal skills with a helpful, friendly attitude when interacting with employees during hardware handoffs and troubleshooting.
    • Physical Stamina: Ability to physically move, organize, and lift boxes of computer equipment (up to 40 lbs) safely and regularly.
    Next Qualifications (Preferred):

    Qualifications

    • Experience using IT Asset Management (ITAM) or ITSM software (e.g., Snipe-IT, Jira Service Desk, ServiceNow, Freshservice).
    • Basic understanding of Mobile Device Management (MDM) concepts (e.g., Jamf, Kandji, Intune) or Cloud Directories.
    • Prior experience handling sensitive data destruction protocols or e-waste logistics.
    Next Benefits:

    Benefits

    • Comprehensive medical, dental, and vision plans
    • Matching 401(k)
    • Unlimited PTO and paid holidays
    • Parental/adoption leave
    • Legal insurance
    • Home technology stipend
    Next Pay:

    Pay

    The approximate base salary range for this position is $86,767 - $113,601. The total compensation package includes base, bonus, equity, and a range of benefit options found on our career site. 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. Posted base salary figures are subject to change as new market data becomes available.

    We should not include Schedule section. We also need to include maybe a short paragraph about IonQ description? The "About IonQ" at start is company overview. Should we include that? The instruction: use headings for sections like About the role, Responsibilities, etc. The company overview could be placed under About the role? But we already used About the role for role description. Could we add a separate "About IonQ" section? Not in the list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a heading for About IonQ. However we could incorporate the IonQ description into the About the role paragraph as a brief intro? But the instruction says preserve ALL substantive information; do not invent or summarize away detail. The IonQ description is substantive; we need to keep it somewhere. Since we cannot create a heading not in the list, we could put it as a

    before the first heading (i.e., a general paragraph). That's allowed: we can have prose outside headings. The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having other paragraphs outside headings. So we can include a paragraph about IonQ at the top. Thus output:

    IonQ, Inc. [NYSE: IONQ] is the world's leading quantum platform and merchant supplier - delivering integrated quantum solutions across computing, networking, sensing, and security. IonQ's newest generation of quantum computers, the IonQ Tempo, is the latest in a line of cutting-edge systems that have been helping customers and partners including Amazon Web Services, and AstraZeneca achieve 20x performance results and accelerate innovation in drug discovery, materials science