Manager, Global Logistics & Compliance

We need to output HTML fragment with sections: About the role? The posting includes description at top: "As the Manager of Global Logistics and Compliance, you will oversee..." That's about the role. Then "What You Will Do:" list. Then "Supervisor Responsibilities: Yes" maybe part of responsibilities? Could be a bullet? It's a line: "Supervisor Responsibilities: Yes". Probably include under Responsibilities? Could be a separate bullet. Then "What We Are Looking For:" list of requirements. Then "Nice To Have:" list. Then "What We Offer" includes benefits, schedule, pay info. Need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Let's map: - About the role: first paragraph(s) describing role. Yes. - Responsibilities: "What You Will Do:" list of duties. Also "Supervisor Responsibilities: Yes" maybe part of responsibilities. So include. - Requirements: "What We Are Looking For:" list includes experience, license, track record, knowledge, proficiency, skills. Those are requirements. - Qualifications: maybe education? The Nice To Have includes Bachelor's degree etc. Could be qualifications. But we could treat Nice To Have as Qualifications? Actually "Nice To Have" is optional qualifications. Could be under Qualifications. But we need to avoid thin sections. Could combine Requirements and Qualifications? But spec says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. We have Skills: maybe "Exceptional project management, communication, and interpersonal skills" etc. That's under Requirements. Could separate Skills section. We have Benefits: described in "What We Offer": benefits package includes medical, life, 401K, disability, tuition reimbursement, flexible work schedule, volunteer hours. Pay: "The base salary may vary based on experience..." Not specific numbers, but it's mention of salary variable. The rule: do NOT create Pay section unless posting actually states them. It states base salary may vary... that's still stating something about pay, albeit not specific. It says "The base salary may vary based on experience, role tenure, performance, industry, and location." That's a statement about pay. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (base salary may vary). So we can include Pay section with that sentence. Schedule: "Our work environment provides a flexible work schedule that includes a Monday through Thursday on-site, with an optional WFH on Fridays, up to 20 workdays fully remote each year, and Time Off for vacation and sick leave." That's schedule info. So include Schedule section. Benefits: we have benefits list. Include Benefits section. Now we need to avoid boilerplate: remove EEO, legal, recruitment safety, etc. Also remove duplicated lines. We need to preserve all substantive information. So include all duties, requirements, nice-to-have, benefits, pay, schedule. We must not repeat job title as heading. So no heading for Manager of Global Logistics and Compliance. We need to use

for section headings. Use

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

  for prose. We need to decide which content goes into which section. Let's outline:

  About the role

  As the Manager of Global Logistics and Compliance, you will oversee our global supply chain operations and ensure strict compliance with international trade regulations! Leading a team of logistics professionals, you will coordinate cross-functionally and manage external partnerships to guarantee the timely, cost-effective delivery of our products worldwide. You will drive continuous process improvements, monitor tariff developments, and foster a culture of integrity across our supply chain. Come join one of the world's biggest toy-making companies and help us shape the future of play!

  That's the intro.

  Responsibilities

  • Oversee Harmonized Tariff Schedule (HTS) classifications for products in development and accurately manage the internal HTS database
  • Develop, monitor, and update the Import Compliance Manual, standard operating procedures (SOPs), and company policies to ensure adherence to international trade regulations
  • Monitor industry news for tariffs and trade agreements while reviewing import/export requirements for new business segment initiatives
  • Collaborate cross-functionally with Product Development, Sourcing, Supply Chain, and Warehousing to enforce compliance matters and provide internal training on customs regulations
  • Manage relationships and contractual obligations with ocean carriers, air forwarders, freight forwarders, and customs brokers to resolve compliance-related issues
  • Support team investigations by proactively identifying compliance gaps, implementing corrective actions, and driving continuous process improvements for cost savings
  • Utilize ACE/CARM reporting systems to monitor trade documentation compliance and ensure ethical behaviors across all logistics entities
  • Supervisor Responsibilities: Yes
  Note: "Supervisor Responsibilities: Yes" is not a duty but a flag. Could be a list item.

  Requirements

  • 5+ years of experience in global logistics, supply chain management, and international trade compliance
  • Customs Brokers License required
  • Proven track record of managing complex global logistics operations, motivating personnel, and developing a high-performing team
  • Strong knowledge of international trade regulations, customs requirements, and hands-on experience with the ACE platform
  • Proficiency in logistics software and tools, including TMS, WMS, and ERP systems
  • Exceptional project management, communication, and interpersonal skills to effectively collaborate with cross-functional teams and external partners
  We could also have Skills section separate, but we already included skills in Requirements. Could split: Requirements (experience, license, track record, knowledge, proficiency) and Skills (project management, communication, interpersonal). But we already included those in Requirements. To follow spec, we could create a Skills section for those skills. Let's see: The spec says use headings for Skills. It's okay to have both Requirements and Skills if content exists. Let's extract skills: "Exceptional project management, communication, and interpersonal skills". That's a skill. Could also include "Proficiency in logistics software and tools" maybe skill. But we can keep simple: Requirements includes experience, license, track record, knowledge, proficiency. Skills includes project management, communication, interpersonal. However the spec says "Prefer a few substantive sections over many thin ones." So maybe better to keep Requirements only and not create Skills separate to avoid thin section. But we need to follow instruction: Use headings for sections like Skills if we have content. If we don't create Skills, it's okay. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to include all. So we can omit Skills if we think it's thin. However we have skill content; we could put it under Requirements as we did. That's fine. Qualifications: we have Nice To Have: Bachelor's degree, Importing compliance certification. That's qualifications. So we can have Qualifications section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now Benefits: list benefits.

  Benefits

  • Basic medical insurance that is 100% company-paid for employees and their children
  • Employee basic life and AD&D insurance
  • 401(K) retirement program with Jazwares matching up to 4% of pretax or post-tax deferrals
  • Short and long-term disability
  • Tuition reimbursement
  • Flexible work schedule: Monday through Thursday on-site, optional WFH on Fridays, up to 20 workdays fully remote each year
  • Time off for vacation and sick leave
  • Volunteer opportunity: up to 16 hours a year on community service projects through Jazwares Cares
  Pay: we have statement about base salary may vary, eligibility for annual performance incentive may apply, Jazwares is multi-state employer so salary range may not apply to other states. We'll include that as prose.

  Pay

  The base salary may vary based on experience, role tenure, performance, industry, and location. Eligibility for the annual performance incentive may apply. Jazwares is a multi-state employer, so the salary range may not apply to other states.

  Schedule: we already included flexible schedule in Benefits but also schedule specifics. Could separate schedule section: but we already have schedule info in Benefits. To avoid duplication, maybe move schedule details to Schedule section and keep Benefits focusing on insurance, retirement, etc. Let's parse: Benefits package includes medical, life, 401K, disability, tuition reimbursement. Work environment provides flexible work schedule... That's more schedule. So we can separate. Thus Benefits: medical, life, 401K, disability, tuition reimbursement, volunteer. Schedule: flexible work schedule details. Let's do that. Benefits list: - Basic medical insurance that is 100% company-paid for employees and their children - Employee basic life and AD&D insurance - 401(K) retirement program with Jazwares matching up to 4% of pretax or post-tax deferrals - Short and long-term disability - Tuition reimbursement - Volunteer opportunity: up to 16 hours a year on community service projects through Jazwares Cares Schedule: - Flexible work schedule: Monday through Thursday on-site, optional WFH on Fridays, up to 20 workdays fully remote each year - Time off for vacation and sick leave Now we need to ensure we didn't miss any substantive info: The "What We Offer" also mentions "Our work environment provides a flexible work schedule that includes a Monday through Thursday on-site, with an optional WFH on Fridays, up to 20 workdays fully remote each year, and Time Off for vacation and sick leave." That's covered. Also "Through Jazwares Cares, you will have the opportunity to volunteer for up to 16 hours a year on community service projects." covered. Now "Reasonable Accommodations" and "Working at Jazwares" sections are boilerplate? They contain some culture description but maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Working at Jazwares" includes pillars Passion, Collaboration, Humility. That's not exactly boilerplate but could be considered company culture description. It's substantive? Might be considered fluff but still part of posting. However we already have About the role covering some of that. The "Working at Jazwares" section includes description of pillars and "Don't miss out on this extraordinary opportunity..." That's promotional. Might be considered boilerplate? The instruction says remove duplicated lines, not necessarily remove all promotional text. But we should preserve ALL substantive information. The pillars could be considered substantive? However they are generic values. Might be considered boilerplate? Not sure. Safer to keep? But we already have About the role that includes "Come join one of the world's biggest toy-making companies and help us shape the future of play!" That's similar. The pillars might be extra. However we risk missing info if we omit. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it if it's substantive. But we need to decide if it's substantive or boilerplate. It's describing company values, could be considered substantive. However the instruction also says "Prefer a few substantive sections over many thin ones." If we add a section for "Culture" or "Working at J