Operations Training Manager

We need to output HTML fragment with sections only if real content. Must not repeat job title. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have sections: About the company (maybe "About the role"? Actually "About Nuage Designs" is company description; could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists. We need to decide which sections to include based on content. We have: - About Nuage Designs (company description) -> could go under "About the role"? Actually "About the role" is about the role, not company. But we have "The Role" section describing opportunity. Could map to "About the role". We'll put that. - Duties & Responsibilities: we have "What This Role Owns", "Key Responsibilities". So we can put under "Responsibilities". - Qualifications & Experience: includes Required and Preferred. Could be "Qualifications". Also "How You Work" maybe skills? Could be "Skills". We'll separate. - Physical Requirements and Work Environment maybe part of "Requirements"? Could be under "Requirements". But we have separate "Requirements" heading allowed. We'll put physical demands etc under "Requirements". - Benefits: The offer includes salary range: commensurate with experience (we must not include if it's just "commensurate with experience" as placeholder? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting says "Salary range: commensurate with experience." That's placeholder; we should not create Pay section. Benefits: they list medical, dental, vision, life insurance, 401K with company match, PTO, Holiday Pay, travel support. Those are real benefits. So we can include Benefits section. - Pay: we should not include because salary range is placeholder. - Schedule: they mention "Schedule flexibility is required, including early mornings, evenings, and peak-season weekends, aligned to the training and audit calendar." Also earlier: "Willingness to work the hours the operation works, including early mornings and peak-season weekends, and to travel to Chicago regularly (estimated 20–30%, front-loaded around launch)." So we have schedule info. So we can include Schedule section. We must not include boilerplate like EEO etc. Already removed. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. We'll need to include lists for duties, qualifications, etc. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. We must not include Job ID etc. We'll produce something like:

  About the role

  ... (the opportunity description)

  Responsibilities

  • ... each duty
  We need to capture all duties from the text. Let's extract. From "What This Role Owns": bullet-like sentences: - The standard. Every core operational process documented, current, and written for the people who actually do the work. - The capability. Every operator trained and certified against that standard, with a clear path from new hire to certified operator to trainer. - The evidence. A regular cadence of floor observation and audit that shows — with data, not impression — where performance meets the standard and where it does not. Then "Boundary of authority: ..." maybe part of responsibilities. Then "Scope of Processes" list many processes. Then "Key Responsibilities" with subheadings: SOP Review and Standardization, Training and Development, Performance Standards and Measurement, Chicago and New Market Readiness. We need to capture each bullet as list items. We'll need to be careful not to lose detail. Let's parse sections: **SOP Review and Standardization** - Inventory every existing SOP, work instruction, and informal practice across Miami and Chicago; identify what exists, what is out of date, and what has never been written down. - Rewrite and consolidate into a single SOP library with one owner, one version, and one review cycle. - Write for the audience: short, visual, bilingual (English/Spanish), step-and-photo format usable on the floor — not binder documents nobody opens. - Eliminate market-by-market variation where there is no good reason for it, and document the reasons where variation is legitimate. - Establish change control so SOPs are updated when process, product, or system changes — not six months later. **Training and Development** - Build a structured onboarding and certification path for each operational function, with defined skill blocks, hands-on practice, and sign-off criteria. - Deliver training directly on the floor and in the classroom; do not outsource credibility. - Develop internal trainers and certified leads in each market so training capacity scales without this role in the room. - Build cross-training so peak season is covered by capable people rather than warm bodies. - Own the training calendar against the seasonal cycle: heavy build before peak, refresh and correction after. **Performance Standards and Measurement** - Define operational performance standards for each process — accuracy, throughput, on-time, quality, safety — in terms an operator can understand and a supervisor can measure. - Run a recurring floor audit and observation program; report results by market, by shift, and by function. - Analyze failure patterns (mispicks, short-ships, load errors, damage, rework and rewash, count variances) back to root cause — SOP gap, training gap, tooling gap, or accountability gap — and name which it is. - Bring findings and corrective plans to the weekly operations meeting with a clear read on whether performance is improving. - Close the loop: retrain, re-certify, revise the SOP, or escalate. **Chicago and New Market Readiness** - Build the operating standard into the Chicago facility from day one rather than retrofitting it later. - Train and certify the Chicago team against the same standard as Miami, on the launch timeline. - Capture what Chicago proves out and bring it back to Miami; treat the two sites as one operating system, not two. - Create the repeatable playbook for standing up operations in the next market. Also earlier "What This Role Owns" could be included as responsibilities. We'll combine. Now Requirements/Qualifications: **Qualifications & Experience Required** - 8+ years in warehouse, distribution, logistics, or production operations, including hands-on time on the floor — this role loses the room without operational credibility. - Demonstrated experience writing SOPs and building training programs that hourly teams actually used, not documents that were filed. - Experience in a multi-site operation, with a track record of making two locations run the same way. - Comfort with data: able to build and read an accuracy or quality report, and to trace a defect back to its cause. - Ability to teach an hourly workforce with varied educational backgrounds — plain language, demonstration, repetition, patience. - Bilingual English/Spanish. - Willingness to work the hours the operation works, including early mornings and peak-season weekends, and to travel to Chicago regularly (estimated 20–30%, front-loaded around launch). **Preferred** - Rental, hospitality, events, linen/laundry, or other closed-loop and reverse-logistics operations. - Formal continuous improvement training (Lean, Six Sigma, TWI, or equivalent) applied in a practical, non-bureaucratic way. - Experience implementing or operating alongside WMS, ERP, or RFID/barcode scanning systems. - Experience standing up a new facility or entering a new market. **How You Work** (maybe Skills) - You would rather fix the process than blame the person — and you will still hold the line when the process is fine and the execution is not. - You are direct. You tell operations leaders and executives what you actually found. - You build standards with the people who do the work, not at them. - You care about the detail because you understand the client: at a Nuage event, an incorrect linen, missing furniture, or a late truck is not a small miss. We could put these under "Skills" heading. Physical Requirements and Work Environment could be under "Requirements" heading. Physical Requirements: - Regularly required to stand, walk, bend, stoop, kneel, and reach throughout the workday while observing, auditing, and coaching on the warehouse floor. - Frequently required to lift, carry, push, and pull items weighing up to 50 lbs unassisted; team lift required for items exceeding 50 lbs, including when demonstrating correct technique during training. - Must be able to operate and demonstrate the operation of powered industrial equipment including forklifts and pallet jacks. - Must be able to remain on feet for extended periods and move throughout large warehouse facilities in both Miami and Chicago. Work Environment: - This position operates in a warehouse environment across both the Miami and Chicago facilities, with exposure to varying temperatures, noise levels, dust, and moving equipment. - Requires recurring travel between Miami and Chicago (estimated 20–30%, front-loaded around the Chicago launch), including air travel. - The employee may occasionally be required to work in outdoor loading dock areas subject to varying weather conditions. - Personal Protective Equipment (PPE) including safety footwear, high visibility vests, and gloves is required in designated areas. - Schedule flexibility is required, including early mornings, evenings, and peak-season weekends, aligned to the training and audit calendar. But schedule flexibility also appears in Schedule section. We'll create Schedule section with that info. Now Benefits section: list benefits. - Medical, dental, vision, and life insurance. - 401K with company match. - PTO. - Holiday Pay. - Travel between Miami and Chicago supported under Nuage’s travel and expense policy. We should not include salary range. Now we need to ensure we don't create empty sections. We'll produce HTML:

  About the role

  Nuage delivers linen, furniture, and tabletop to the most demanding events in the country. That promise is kept or broken on the warehouse floor — in how an order is pulled, how a truck is loaded, how a returned item is inspected, and how a repair is judged good enough to go back on the shelf. Today that standard lives in the heads of a handful of long-tenured people. It is not written down consistently, not taught consistently, and not measured consistently. As Nuage doubles in size and opens a new Chicago facility, an undocumented standard will not scale and will not travel. This role exists to make the Nuage operational standard explicit, teachable, and verifiable — one standard, deployed identically in every market, executed the same way on every shift.

  Then Responsibilities with ul. We need to include all duty items as li. Let's compile list: From "What This Role Owns": - The standard: Every core operational process documented, current, and written for the people who actually do the work. - The capability: Every operator trained and certified against that standard, with a clear path from new hire to certified operator to trainer. - The evidence: A regular cadence of floor observation and audit that shows — with data, not impression — where performance meets the standard and where it does not. Boundary of authority: This role owns the standard and the capability to execute it. Market Operations Leaders own daily execution and results. This role does not direct daily work, assign shifts, or supervise the floor; it defines what “right” looks like, teaches it, measures it, and escalates gaps. We could include that as a li. Scope of Processes list many processes; we could include as a li summarizing? But we need to preserve ALL substantive information; we cannot summarize away detail. However we can keep the list as a single li containing the enumeration? That might be okay