Office Assistant

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. First, there is a long intro about Meshy (company description). That is not part of the role description; but we might include as "About the role"? Actually "About The Role" heading appears later. The intro about Meshy is company overview; could be considered part of "About the role"? Usually "About the role" includes description of role and maybe company. But we have a separate "About The Role" section later. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections accordingly. We need to extract content for each. Let's identify: - About the role: The paragraph after "About The Role" heading: "We're looking for a part-time Office Assistant who thrives in a people-facing, hands-on role and wants to be a genuine contributor to a vibrant workplace culture. From coordinating weekly bubble tea orders and Wednesday afternoon tea setups to onboarding new hires and managing company assets, no two days look exactly the same. You'll be the kind of person the whole office counts on — the one who keeps the space stocked, the operations smooth, and the team feeling taken care of. If you're reliable, resourceful, and take pride in the details others overlook, this role was made for you." Also maybe include Basic Information? That could be separate? But we have sections for Pay, Schedule, etc. Basic Information includes Job Type, Location, Compensation. We'll put Compensation in Pay section, Location maybe in Schedule? Actually location is not schedule. Could be part of About the role? Might be better to include location in About the role or maybe not needed. The instruction: include a section ONLY when posting has real, specific content for it. So we need to decide. We have Pay: Compensation: $25-30/hr. Schedule: Basic Information: Part-time (10 hours/week) Location: Sunnyvale, CA (onsite). Work onsite at our Sunnyvale office on Monday, Wednesday, and Friday, approximately 10 hours per week. Wednesday afternoon is required; hours on the other days are flexible. Thus Schedule section can contain that. Benefits: Not explicitly listed. There's "Why Join Meshy?" which lists opportunities, flexible work environment, etc. That could be considered Benefits. The posting includes: "Opportunity to work with a talented and passionate team at the forefront of AI and 3D technology. Flexible work environment Opportunities for fast professional growth and development. An inclusive culture that values creativity, innovation, and collaboration." Also earlier: "Enjoy a vibrant work environment, daily interactions with leadership, and all the perks of working in the heart of Silicon Valley." That's benefits. So we can create Benefits section with those bullet points. Qualifications: Could be "What We're Looking For" includes experience, education, etc. That's qualifications. Also "Nice To Have" maybe skills. Skills: Could be "Fluent English", "Mandarin Chinese is a plus", "Strong attention to detail", etc. But we need to separate. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. Responsibilities: The "What You'll Do" list. Requirements: maybe the "What We're Looking For" (mandatory). Qualifications: maybe education? But we can combine. Better: Use Requirements for mandatory qualifications (experience, education, etc). Qualifications for preferred? But we have both. Let's decide: - About the role: company overview + role summary (the paragraph after About The Role heading). Could also include location? But location is schedule. - Responsibilities: the bullet list under "What You'll Do". - Requirements: mandatory items from "What We're Looking For": 1+ year of experience in office administration, operations, or similar role is preferred; candidates without prior experience are welcome to apply (so not strict). High school diploma or above. Strong attention to detail and thoroughness. High work initiative and reliability. Social, collaborative personality. Physical ability to handle supply restocking and office setup. Fluent English (reading, writing, speaking, listening). That's requirements. - Qualifications: maybe "Nice To Have": Mandarin Chinese is a plus but not required. Could also include "Basic Information" like part-time etc but that's schedule. - Skills: maybe we can list specific skills like "Office supplies & snacks procurement", "Daily refrigerator restocking", etc but those are responsibilities. Skills could be "Organizational skills", "Communication", etc. But we might not have explicit skills list. Could combine with Requirements. Given instruction: Prefer a few substantive sections over many thin ones. So we might not need all eight sections; only those with real content. We have substantive content for: - About the role (company overview + role summary) - Responsibilities (What You'll Do) - Requirements (What We're Looking For mandatory) - Benefits (Why Join Meshy? + perks) - Pay (Compensation) - Schedule (Work schedule, location) Qualifications and Skills may be thin; we could omit them if not enough distinct content. However we have "Nice To Have" Mandarin Chinese which could be Skills. But we could put that under Requirements as a nice-to-have note. Or we could create a Skills section with "Fluent English" and "Mandarin Chinese is a plus". But Fluent English is already a requirement. Better to keep Requirements and maybe Skills separate: Requirements: mandatory; Skills: language skills etc. But we need to avoid filler. Let's see if we have enough for Skills: Fluent English (requirement), Mandarin Chinese (nice-to-have). That's two items. Could be a Skills section. Qualifications: maybe education (high school diploma or above) is already in Requirements. Could be Qualifications: "High school diploma or above". But that's also requirement. Given we already have Requirements covering education, experience, etc. So Qualifications may be redundant. Thus we can output sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Check each for substantive content. About the role: we need to include company overview and role summary. The company overview is lengthy; we should preserve all substantive information. So we need to include the whole paragraph about Meshy (the first big block) plus the role summary paragraph. However the instruction: "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." So we can include the company overview as part of About the role. Thus About the role

About the role

then

containing the Meshy description and the role summary. But we need to ensure we don't include boilerplate like cookie/navigation/legal/EEO etc. There's none. Now Responsibilities: list of duties from "What You'll Do". We'll make

• each item. Requirements: list from "What We're Looking For" mandatory items. We'll make
  • . Skills: language skills: Fluent English (reading, writing, speaking, listening) and Mandarin Chinese is a plus but not required. Could be
    • . Benefits: from "Why Join Meshy?" and location perks. We'll make
      • . Pay:

        $25-30/hr

        . Schedule:

        Part-time (10 hours/week). Onsite in Sunnyvale, CA. Work Monday, Wednesday, Friday approx 10 hours/week; Wednesday afternoon required; other days flexible.

        Check for any duplicate content: Ensure we didn't miss any responsibilities like "Office supplies & snacks procurement (1–2 times/week)" etc. We'll include all. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML fragment only. Let's craft. First, About the role content: Meshy description: "Headquartered in Silicon Valley, Meshy is the leading 3D generative AI company on a mission to Unleash 3D Creativity by transforming the content creation pipeline. Meshy makes it effortless for both professional artists and hobbyists to create unique 3D assets—turning text and images into stunning 3D models in just minutes. What once took weeks and cost $1,000 now takes just 2 minutes and $1. Our world-class team of top experts in computer graphics, AI, and art includes alumni from MIT, Stanford, and Berkeley, as well as veterans from Nvidia and Microsoft. Our talent spans the globe, with team members distributed across North America, Asia, and Oceania, fostering a diverse and innovative multi-regional culture focused on solving global 3D challenges. Meshy is trusted by top developers, backed by premier venture capital firms like Sequoia and Granite Asia, and has successfully raised nearly $400 Million in funding. Meshy is the market leader, recognized as the No.1 in popularity among 3D AI tools (according to 2024 A16Z Games) and No.1 in website traffic (according to SimilarWeb, with 10 Million monthly visits). The platform boasts over 12 Million users and has generated 100 Million models. Founder and CEO Yuanming (Ethan) Hu earned his Ph.D. in graphics and AI from MIT, where he developed the acclaimed Taichi GPU programming language (27K stars on GitHub, used by 300+ institutes). His work is highly influential, including an honorable mention for the SIGGRAPH 2022 Outstanding Doctoral Dissertation Award and over 2,700 research citations." Then role summary: "We're looking for a part-time Office Assistant who thrives in a people-facing, hands-on role and wants to be a genuine contributor to a vibrant workplace culture. From coordinating weekly bubble tea orders and Wednesday afternoon tea setups to onboarding new hires and managing company assets, no two days look exactly the same. You'll be the kind of person the whole office counts on — the one who keeps the space stocked, the operations smooth, and the team feeling taken care of. If you're reliable, resourceful, and take pride in the details others overlook, this role was made for you." We can combine into one

        or multiple

        . Use

        for prose; we can have multiple

        elements. Now Responsibilities list items: - Work onsite at our Sunnyvale office on Monday, Wednesday, and Friday, approximately 10 hours per week. Wednesday afternoon is required; hours on the other days are flexible - Office supplies & snacks procurement (1–2 times/week) - Daily refrigerator restocking and maintenance - Weekly bubble tea orders (2x) and Wednesday afternoon tea setup & coordination - Preparing and mailing new hire packages for remote employees - Tracking returned company assets from departing employees (especially computers) and ensuring proper data reset before archival—this may involve coordinating with departing staff for login credentials or working with IT - Office supply maintenance and organization; proper storage of sensitive items like old computers - Support for company team-building events and special projects as needed - Other duties and projects assigned by management as needed Note: The first bullet about schedule is also in Schedule section; but it's also a duty. Might duplicate. But we can keep it in Responsibilities as it's part of what you'll do. However schedule section also includes that. To avoid duplication, maybe we move schedule details to Schedule section and not repeat in Responsibilities. The "What You'll Do" list starts with "Work onsite at our Sunnyvale office on Monday, Wednesday, and Friday, approximately 10 hours per week. Wednesday afternoon is required; hours on the other days are