Transportation Logistics Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if content exists. They say: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections to include based on content. The posting includes: About The Company, What To Expect, Job Overview, Duties And Responsibilities, Minimum Qualifications, Knowledge, Skills, And Abilities, Work Environment And Physical Demands, plus EEO boilerplate (to remove). Also maybe "About The Company" could be considered "About the role"? But they said 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. They gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can also use other headings if appropriate? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when applicable. But we can also use other headings if they better match? Probably they want us to map content to those standard headings. Let's map:
- About The Company -> maybe "About the role"? Not exactly. Could be "About the company" but not in list. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. But they also say "Prefer a few substantive sections over many thin ones." So we could combine some.
We have substantive content: About The Company, What To Expect (core values), Job Overview, Duties And Responsibilities, Minimum Qualifications, Knowledge, Skills, And Abilities, Work Environment And Physical Demands.
We could create sections: About the company (maybe as "About the role"? but that seems off). Perhaps we can use "About the role" for Job Overview + What To Expect? But they said do NOT repeat the job title as a heading. Not about repeating company.
Better to follow the examples: Use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have content for Responsibilities (Duties And Responsibilities). Requirements could be Minimum Qualifications. Qualifications could be Knowledge, Skills, And Abilities (or combine). Skills could be part of Knowledge, Skills, And Abilities. Benefits, Pay, Schedule not present (no mention). So we should not include those sections.
We also have About The Company and What To Expect and Job Overview. Could be combined into "About the role" (description of role and company). Or we could have separate sections: "About the company" and "Job overview". But the instruction says use those example headings; but not strictly required? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I'd interpret that we should use those headings for sections we include. If we have content that doesn't fit those, maybe we still use a heading but not from list? Safer to stick to those headings and map content accordingly.
Thus we can have:
- About the role
: combine About The Company, What To Expect, Job Overview.
- Responsibilities
: Duties And Responsibilities.
- Requirements
: Minimum Qualifications.
- Qualifications
: Knowledge, Skills, And Abilities (maybe also include Work Environment? but that's not qualifications). Could also include Work Environment under a separate heading? Not in list; maybe we could omit or include as part of Qualifications? But better to include as its own section if we have content; but instruction says prefer few substantive sections over many thin ones. Work Environment is substantive; we could include as a separate heading like "Work Environment". But not in examples. However we could still use Work Environment
as it's a heading. The instruction didn't forbid other headings, just gave examples. So we can include.
Thus final HTML:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I'd interpret that we should use those headings for sections we include. If we have content that doesn't fit those, maybe we still use a heading but not from list? Safer to stick to those headings and map content accordingly.
Thus we can have:
- About the role
: combine About The Company, What To Expect, Job Overview.
- Responsibilities
: Duties And Responsibilities.
- Requirements
: Minimum Qualifications.
- Qualifications
: Knowledge, Skills, And Abilities (maybe also include Work Environment? but that's not qualifications). Could also include Work Environment under a separate heading? Not in list; maybe we could omit or include as part of Qualifications? But better to include as its own section if we have content; but instruction says prefer few substantive sections over many thin ones. Work Environment is substantive; we could include as a separate heading like "Work Environment". But not in examples. However we could still use Work Environment
as it's a heading. The instruction didn't forbid other headings, just gave examples. So we can include.
Thus final HTML:
About the role
...combined text...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Work Environment
...text...
We must preserve all substantive information, not invent or summarize away detail. So we need to copy the text verbatim (or close) but format intoor
. We must not include EEO boilerplate. Now output HTML fragment only. Let's craft. Be careful to escape any HTML special characters? The text includes ampersand (&) in "OCC cardboard"? Actually "OCC" is fine. There's an ampersand in "Purpose, Integrity, Progress, and Collaboration" - that's fine as plain text. No need to escape. We'll output:
About the role
Fiber Global is a climate technology company focused on advancing building materials. Our mission is to reclaim abundant global waste streams to create sustainable, high performing building materials. Fiber Global creates products that are both sustainable by design and higher performing than existing products on the market. Our flagship product, Forged Fiber Board (FFB) reclaims corrugated cardboard to manufacture panels that are used in the furniture and construction industries. To learn more, please visit fiberglobal.com.
You can expect to make a positive difference in the world with Fiber Global. However, doing that is not easy. It requires a lot of hard work, taking action with solutions to problems and challenges, and demonstrating unwavering resilience. Our core values - Purpose, Integrity, Progress, and Collaboration - are the baseline of how we do everything. You can expect to work with individuals and teams who are driven by a sense of purpose, and hold themselves and others accountable for positively contributing to the company’s mission.
Fiber Global is seeking an experienced Logistics Lead to lead all inbound and outbound logistics operations for our La Mirada facility. This role is responsible for developing and executing logistics strategies that ensure the timely movement of raw materials and finished goods while optimizing transportation costs, inventory flow, and operational efficiency. The Logistics Leader will oversee carrier relationships, warehouse logistics, inbound material planning, shipping operations, and logistics performance metrics. Working cross-functionally with Operations,