Brand Operations Lead, Fulfillment

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key sections: - About Faire (company description) maybe not needed? The instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. We have "About This Role" which is about the role. That could go under

About the role

. Then responsibilities: "What You’ll Do" list. That's responsibilities. Then qualifications: "Minimum qualifications" and "Preferred Qualifications". That's qualifications. Skills: maybe we can extract from qualifications? There's no explicit skills section but we could include skills derived? The instruction: include a section ONLY when posting has real, specific content for it. There's no explicit "Skills" heading in posting, but we could infer from qualifications? However better to not create Skills section if not explicit. The posting mentions "Strong communication", "root cause analysis", etc. Those could be skills. But we need to decide: If we create Skills section, we need specific content. The posting does have skill-like items under qualifications. Could we treat them as skills? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; only include when posting has real specific content. There's no explicit Skills section, but we could still create one if we have skill-specific content. However the qualifications already cover skills; maybe better to not duplicate. I'd omit Skills. Benefits: posting mentions "eligible for equity and benefits", "competitive pay, equity, and comprehensive benefits". Also "Real rewards. Competitive pay, equity, and comprehensive benefits designed to support your life inside and outside of work." Also "Move fast... Equipped to scale... Best in class... Real rewards... Belonging". Those are benefits/culture. There's also mention of hybrid work schedule. So we can include Benefits section with bullet points: equity, comprehensive benefits, etc. Also maybe mention "Hybrid role based in San Francisco and New York with up to 20% travel". That's location/travel, not benefits. But we could include under Benefits? Might be better to have a separate section for Schedule? There's schedule info: "Hybrid Faire employees currently go into the office 3 days per week on Tuesdays, Thursdays, and a third flex day of their choosing (Monday, Wednesday, or Friday). Additionally, hybrid in-office roles will have the flexibility to work remotely up to 4 weeks per year." Also travel expectation: 20-25% travel earlier, then later says up to 20% travel. So schedule/hybrid info. Pay: Salary range given: $116,000 to $159,500 per year. Also equity eligibility. Thus we can have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We must not include Requirements if not present; there is no separate Requirements besides qualifications. So omit Requirements. We must not include Skills if not explicit; we can omit. Now we need to format: Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Must not omit any substantive info. We need to include details from About This Role paragraph, responsibilities bullet list, qualifications (minimum and preferred), benefits (equity, comprehensive benefits, etc), pay range, schedule/hybrid and travel. We must not include boilerplate like EEO, privacy, etc. We must not include navigation, cookie, legal, duplicated lines. We must not include application instructions. We must not repeat job title. We must not put Job ID/requisition numbers as headings. Now let's extract substantive content. From posting: About Faire (company description) maybe not needed for role sections but could be considered "About the role"? Actually "About This Role" is separate. The initial "About Faire" is company overview; maybe we could include under About the role? But the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the role" likely corresponds to the "About This Role" section. The company overview may be considered extra but not required; we could omit as not under those headings. However we must preserve ALL substantive information; if we omit company overview, we lose substantive info. But maybe we can incorporate it into About the role? The heading "About the role" could include both role description and company context? The instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). It doesn't forbid adding extra content under that heading beyond the role description. So we could put the company overview under About the role as prose before diving into role specifics. That would preserve it. Thus About the role section: include company overview paragraph(s) and then the "About This Role" paragraph. Let's capture company overview: "About Faire Faire is a technology wholesale platform built on the belief that the future is local. Independent retailers around the globe collectively represent a multi-hundred-billion-dollar wholesale market that has historically been fragmented and offline. At Faire, we're using the power of tech, data, and machine learning to connect this thriving community of entrepreneurs across the globe. Picture your favorite boutique in town — we help them discover the best products from around the world to sell in their stores. With the right tools and insights, we believe that we can level the playing field so businesses can grow and local communities can thrive. We’re looking for smart, resourceful and passionate people to join us as we power the shop local movement. If you believe in community, come join ours." That's substantive. Then "About This Role" paragraph: "We're looking for a senior operator to own how brand onboarding works for Fulfilled by Faire (FbF), not just how individual brands get live. Our specialist team runs brands from commitment to activation today. This role sits above that. You'll own the program itself: the KPIs, the dashboard that tells us whether onboarding is healthy, and the roadmap that fixes what keeps breaking. FbF is scaling from roughly 1% to 20% of GMV. Onboarding cannot be the thing that breaks on the way there. Your job is to make sure it doesn't, by building leverage rather than absorbing volume. You'll also set the bar for the specialist team. You'll write the playbooks, coach people on root-cause rigor and brand communication, and raise the standard around you. This is a senior IC role with no direct reports. Your influence comes from judgment, evidence and follow-through. Expect 20-25% travel to our fulfillment nodes, and warehouse partners." Note travel expectation appears here; also later says up to 20% travel. We'll capture travel in Schedule section maybe. Now Responsibilities: "What You’ll Do" list: - Own the onboarding system Own the end-to-end onboarding experience for brands joining FbF, from commitment through activation and post-launch stabilization - Be accountable for the KPIs - Carry a focused portfolio of strategic and at-risk brands yourself while the team handles day-to-day volume - Diagnose ambiguous, high-impact problems independently - Build the measurement layer Monitor and recommend improvements the FbF onboarding KPI set - Document the definitions with Analytics so the numbers mean the same thing to everyone - Build and maintain the dashboard leadership reads - Run the weekly onboarding operating review - Use the data to see capacity constraints and bottlenecks coming early enough to plan - Drive strategic improvement Define and sequence a rolling 3-6 month improvement roadmap, prioritized by business impact - Lead complex cross-functional pilots from hypothesis to measured result - Find leverage through automation, self-serve and playbooks so throughput grows faster than headcount - Insist on structural fixes and track corrective actions to verified closure - Own three cross-functional lanes - Product roadmap partnership. Be the named ops counterpart to FbF Product. Write the problem briefs, quantify the impact, and represent onboarding in prioritization. - Onboarding enablement and playbooks. Own the SOP library and how new specialists ramp, onboarding enablement, talk track, etc. - 3PL and network readiness. Own receiving-standard readiness and the inbound exception playbook as we add nodes, so a new facility can take FbF volume without a bespoke launch. - Raise the bar around you - Personally guide through onboarding our largest (Platinum +) brands - Coach the specialist team on root-cause rigor, brand communication and operational judgment, without direct authority - Run the escalation review and make your standard for closure the team's standard - Communicate at every altitude: floor detail with warehouse partners, executive narrative with leadership, honest updates with brands when things slip We need to convert to

  • items. Some items have sub-bullets; we can keep them as part of the li text. Now Qualifications: Minimum qualifications and Preferred Qualifications. Minimum qualifications list: - 3+ years in client facing fulfillment operations, seller onboarding, marketplace operations, or a related field - Hands-on experience with physical goods fulfillment and warehousing, ideally in a 3PL setting - Ownership of an operational KPI you personally moved - Experience defining metrics and building your own reporting - Track record of resolving ambiguous problems independently and driving cross-functional work to closure through influence rather than authority - Structured root cause analysis, and the judgment to tell a symptomatic fix from a structural one - Experience working directly with brands, merchants or partners across seniority levels - Strong communication, including taking operational complexity to a leadership audience without losing fidelity Preferred Qualifications list: - Scaled a marketplace or seller onboarding program through a step change in volume - Stood up operations at a new 3PL node or fulfillment center - Working knowledge of WMS/OMS and how configuration shows up on the floor - Designed or launched a self-serve or automated flow that removed manual steps - Owned an SOP library or enablement program - Comfort using AI tooling to compress analysis, documentation etc. - Prior online marketplace experience We'll put these under Qualifications section, maybe separate Minimum and Preferred as subheadings? But we only have allowed headings: Qualifications. Could we include subheadings? Not specified; we could just list all qualifications in a single list, but we need to preserve distinction? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we merge them, we lose the distinction between minimum and preferred. However we could keep them as separate
    with a preceding

    indicating Minimum qualifications and Preferred qualifications. That's allowed: we can have prose paragraphs before lists. Thus Qualifications section:

    Qualifications

    then

    Minimum qualifications:

    ... then

    Preferred qualifications:

    ... Now Benefits: The posting mentions: - "This role will also be eligible for equity and benefits." - "Real rewards. Competitive pay, equity, and comprehensive benefits designed to support your life inside and outside of work." - Also "Move fast... Equipped to scale... Best in class... Real rewards... Belonging" these are cultural benefits. We could list benefits: equity, comprehensive benefits (health, etc), maybe mention "competitive pay" but that's Pay section. Also "Belonging" etc. We need to avoid filler like "commensurate with experience". Not present. Thus Benefits section:

    Benefits

    <