IT Support Tech (WKND)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. Do not repeat job title. Remove boilerplate. Must preserve all substantive info. No invented details. No filler sections. We need to parse the posting. First part: "About ThredUp" description about company. That's not about the role; but we could put 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 have an "About the role" section summarizing the role description. The posting includes: "As an IT Support Technician, you will serve as the primary on-site technical resource for our warehouse operations. You will provide critical hands-on support for a diverse ecosystem of hardware, software, and networking infrastructure. This role requires a "fixer" mentality—someone who can pivot from debugging a Linux script to performing mechanical repairs on high-end equipment, all while providing exceptional service to our operational teams. How You Will Make An Impact Ensure Operational Continuity: Maintain maximum uptime for warehouse systems by providing rapid response to hardware and software failures.Empower Operators: Act as a technical bridge, translating complex issues into simple solutions for non-technical staff and DC leadership.Continuous Improvement: Identify recurring technical bottlenecks and work independently to implement lasting fixes or process improvements." We can put that under About the role (maybe also include the company description? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. The company description is not required but could be considered part of About the role? Usually "About the role" includes role description, not company overview. However we can include company overview as part of About the role? Might be okay but not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the company description somewhere. Could put it in a

before sections? The instruction says output ONLY the HTML fragment — no /. It didn't forbid a leading paragraph. We could include a

with company overview before sections. That would preserve info. Then sections for role specifics. We must not include boilerplate like cookie/navigation/legal/EEO etc. At the end there is legal stuff: "Before you go, our legal team wants you to know...You must be at least 18 years old and have basic English literacy skills. Employment with thredUP is contingent on each candidate passing a 7-year background check." Also disability accommodation request etc. Those are legal/EEO boilerplate; we should remove them. Also "We live by our DOTS Values..." maybe not boilerplate but could be considered culture; but it's not a standard heading; we could include under Benefits? Not exactly. It's more about culture. Could be omitted? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The DOTS Values is not exactly legal; it's cultural. Might keep as part of Benefits? But Benefits section is for benefits like pay, schedule, etc. The DOTS Values is not a benefit. Could be omitted? It's substantive info about company values; maybe we keep as a paragraph under About the role? Not sure. Safer to keep it as a paragraph under About the role? But it's not about the role. Could create a separate section like "Company Culture" but not in allowed headings. Since we must only use those headings, we could embed it in a

before sections or after sections as a general paragraph. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs outside sections. So we can have a leading

with company overview and values, then sections. Now we need to extract Responsibilities: list under "Key Responsibilities" with bullet points. We'll make

• for each. Responsibilities list: - Hardware & Mechanical Support: Install, configure, and perform physical repairs on desktops, touchscreen monitors, printers, and handheld devices. Maintain and troubleshoot specialized photography equipment, including mechanical components and sensor cleaning. - Linux & Software Administration: Support and troubleshoot Linux-based workstations and specialized warehouse management software. Execute basic scripting to automate routine tasks. - Network Maintenance: Diagnose and resolve connectivity issues related to Wi-Fi access points, Ethernet cabling, and network peripherals. Assist engineering teams with on-site rack cable management and port patching. - Documentation & Training: Manage the IT ticketing lifecycle; document all resolutions to build a local knowledge base. Train warehouse operators on basic troubleshooting to reduce repetitive service requests. - Data & Quality Assurance: Analyze operational data to identify quality trends. Perform testing on new internal application releases before they go live on the warehouse floor. - Inventory & Procurement: Independently manage the lifecycle of IT assets, from placing orders for supplies to processing RMAs for defective hardware. We need to keep each as a list item; maybe keep the heading inside the li? Could keep as is. Now Requirements/Qualifications/Skills: The posting has "What We’re Looking For" with bullet points: Experience: 1–3 years of technical support experience in a warehouse, production, or high-volume environment. Linux Proficiency: Comfort working within a Linux terminal; ability to navigate file systems and run diagnostic commands. Technical Versatility: Strong mechanical aptitude for disassembling/reassembling hardware and a solid understanding of TCP/IP networking fundamentals. Customer Service Excellence: Proven ability to remain calm under pressure and communicate effectively with users of varying technical skill levels. Independence: A self-starter who can prioritize a high-volume ticket queue without constant supervision. Physical Requirement: Ability to lift up to 50 lbs and work on a ladder or in tight spaces as required by hardware placement. This role is not eligible for visa sponsorship. We need to map to sections: Requirements, Qualifications, Skills. The instruction says use headings for those categories if content exists. We have experience, Linux proficiency, technical versatility, customer service, independence, physical requirement, visa sponsorship. Could split: Requirements (experience, Linux proficiency, technical versatility), Qualifications (customer service, independence), Skills (maybe physical requirement?). But we need to preserve all info; we can just put all under Requirements (or Qualifications) as a list. However we must not create empty sections. We can create a single section e.g.,

  Requirements

  with a
  containing all items. That would satisfy. Or we could split into Requirements and Qualifications and Skills but we need to ensure each has content. Let's decide: Use Requirements for experience, Linux proficiency, technical versatility. Use Qualifications for customer service excellence, independence. Use Skills for physical requirement and maybe visa sponsorship? Visa sponsorship is not a skill; maybe we can put under Requirements as a note. Better to put all under Requirements to avoid empty sections. The instruction: "Prefer a few substantive sections over many thin ones." So we can have just Requirements section with all items. That's fine. Now Benefits, Pay, Schedule: The posting includes "What We Offer": "Consistent, set schedule! Competitive pay (we leverage market data). Employee stock purchase plan. PTO + paid holidays. Medical, dental, vision, 401k, life and disability insurance offered." So we have schedule, pay, benefits. We need to create sections for Benefits, Pay, Schedule only if posting actually states them. It does state schedule ("Consistent, set schedule!"), pay ("Competitive pay (we leverage market data)."), benefits (list). So we should create three sections: Benefits, Pay, Schedule. Each with content. Benefits: Employee stock purchase plan, PTO + paid holidays, Medical, dental, vision, 401k, life and disability insurance offered. Pay: Competitive pay (we leverage market data). Schedule: Consistent, set schedule! We should not include filler like "commensurate with experience". Not present. Now we need to ensure we don't repeat job title. Not needed. We need to remove boilerplate: The legal bits at end, disability accommodation request, etc. Also the "We live by our DOTS Values..." maybe we can keep as a paragraph under Benefits? Not exactly. Could include as a paragraph before sections as part of company overview. Let's include a paragraph after company overview maybe. Let's craft HTML:

  About ThredUp: ThredUp is transforming resale with technology and a mission to inspire the world to think secondhand first. By making it easy to buy and sell secondhand, ThredUp has become one of the world's largest online resale platforms for apparel, shoes and accessories. Sellers love ThredUp because we make it easy to clean out their closets and unlock value for themselves or for the charity of their choice while doing good for the planet. Buyers love shopping value, premium and luxury brands all in one place, at up to 90% off estimated retail price. Our proprietary operating platform is the foundation for our managed marketplace and consists of distributed processing infrastructure, proprietary software and systems and data science expertise. With ThredUp’s Resale-as-a-Service, some of the world's leading brands and retailers are leveraging our platform to deliver customizable, scalable resale experiences to their customers. ThredUp has processed over 172 million unique secondhand items from 55,000 brands across 100 categories. By extending the life cycle of clothing, ThredUp is changing the way consumers shop and ushering in a more sustainable future for the fashion industry. Recognized on TIME Most Influential Companies of 2023, Digiday's WorkLife 50 2023, TIME's Best Inventions of 2022, and Lattice's People Success Awards 2022. We live by our DOTS Values of Delivering an exceptional customer experience, Openly giving and receiving feedback, Teaming up to make thredUP a success, and Striving for excellence. We believe diversity, inclusion and belonging is key for our team At ThredUp, our mission has been built on extending the lives of millions of unique clothing items. Much like our inventory, we are proud to have fostered a workplace that is one-of-a-kind. As a company focused on diversity, inclusion and belonging, we are committed to ensuring our employees are comfortable bringing their authentic selves to work every day. A unique perspective is critical to solving complex problems and inspiring a new generation to think secondhand first. Be you.

  Then sections:

  About the role

  As an IT Support Technician, you will serve as the primary on-site technical resource for our warehouse operations. You will provide critical hands-on support for a diverse ecosystem of hardware, software, and networking infrastructure. This role requires a "fixer" mentality—someone who can pivot from debugging a Linux script to performing mechanical repairs on high-end equipment, all while providing exceptional service to our operational teams. How You Will Make An Impact Ensure Operational Continuity: Maintain maximum uptime for warehouse systems by providing rapid response to hardware and software failures.Empower Operators: Act as a technical bridge, translating complex issues into simple solutions for non-technical staff and DC leadership.Continuous Improvement: Identify recurring technical bottlenecks and work independently to implement lasting fixes or process improvements.

  Note: The run-on sentences missing spaces after colons; we should preserve as is? The original had no spaces after colons. We should keep exactly? Probably keep as is but we can add spaces for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding spaces is not changing substantive info, just formatting. Might be okay. Safer to keep original text exactly. However original had missing spaces; we can keep as is. Now Responsibilities: