Quality Assurance Manager, Customization
Quince · Santa Fe Springs, CA · 1 mo ago
On-siteQuality Assurance$112k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we have sections: About Quince (company description), OUR CULTURE, THE ROLE (description), Responsibilities, Qualifications, Physical Requirements, Pay Range, Why Quince? (maybe Benefits?), but we must only include sections when posting has real specific content. We should not repeat job title as heading. Use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can adapt headings to match content: "About Quince" maybe not in list but we can use "About the role"? The instruction: use
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can adapt headings to match content: "About Quince" maybe not in list but we can use "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those headings if appropriate. But we must not repeat the job title as a heading. We can have sections: About Quince (maybe not in list but could be "About the role"? Actually "About the role" is a heading for role description. We have a description of the role under "THE ROLE". So we can use About the role
and put the role description there.
Responsibilities: we have a list.
Qualifications: we have Required and Nice to have.
Physical Requirements: maybe could be under "Requirements"? But we have separate "Physical Requirements". Could be part of "Requirements" but we can create a section "Requirements" and include both qualifications and physical? However instruction: Use headings as examples; we can create "Requirements" heading and put qualifications and physical requirements inside. But we also have "Qualifications" as a possible heading. Might be better to follow the examples: Use "Qualifications" for qualifications, "Responsibilities" for responsibilities, "Pay" for pay range, "Schedule" maybe not present (schedule is mentioned: Monday through Friday regular business hours). That's schedule info. So we can include Schedule section.
Benefits: not explicitly listed besides bonus and equity may be provided. That's a benefit. So we can include Benefits section with bonus and equity.
Skills: maybe not separate; we could omit.
About the role: we have description.
We also have "Why Quince?" which could be like "About Quince" or "Why Quince?" but not in examples; we could omit or treat as "About Quince"? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include a section for "Why Quince?" maybe as Why Quince?
with paragraph.
We must not include boilerplate like EEO, security advisory, accommodation, background check, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, except boilerplate.
Let's extract substantive content:
- About Quince: description of company mission, M2C model, etc.
- OUR CULTURE: description of culture.
- THE ROLE: description: Quality Assurance Manager, Customization; on-site in Santa Fe Springs, CA; Monday-Friday regular business hours; may involve transportation to LA Warehouse and other decorators; role description: eyes and ears, inspect inbound inventory, audit production quality, raise issues, build processes for 99% OTD and 99% QA, link between floor and remote PM team, inputs shape Production Management Software.
- Responsibilities: bullet list (we need to convert to - ).
List of responsibilities from text:
"Own quality outcomes, holding performance to 99% on-time delivery and 99% quality acceptance rate targets across all production runs."
"Monitor the inspection of inbound inventory received at the facility, verifying quantities, condition, and specifications against purchase orders and production requirements, drive timely inventory replacements to minimize production delays."
"Identify root cause issues stemming from the warehouse, and work cross-functionally to implement SOPs at the warehouse level to resolve issues."
"Conduct production quality checks throughout the decoration process (e.g., embroidery, screen-printing, heat transfer, embossing), identifying defects, inconsistencies, or deviations from brand standards."
"Raise issues quickly and clearly, documenting defects, inventory discrepancies, and production delays with supporting evidence (photos, data, root cause notes) and driving swift resolution with the decorator."
"Push the third party to implement changes rapidly."
"Provide structured and ad hoc updates to the remote project manager team, communicating production status, quality metrics, open issues, and risk flags in a clear, actionable format."
"Work with the Program Manager to incorporate project updates into the Production Management System."
"Build and implement QA processes and SOPs from the ground up — from incoming goods inspection to final outbound audits — to create a repeatable, scalable quality system."
"Track and analyze quality and delivery KPIs, identifying trends, recurring issues, and opportunities for improvement, and presenting findings to internal stakeholders."
"Influence and partner with the 3P decorator to drive adoption of Quince quality standards, SOPs, and process improvements — building trust and buy-in at the facility level to implement changes that stick."
"Identify root causes of quality failures, inventory discrepancies, and delivery misses, and work cross-functionally with internal project managers, sourcing, and the decorator to resolve them and prevent recurrence."
"Support onboarding of new product lines or decoration techniques by developing quality checkpoints and training criteria specific to each program."
"Maintain accurate records of quality references, inspections, defect rates, corrective actions, and inventory discrepancies in Quince's tracking systems."
"Conduct weekly operations check-ins with decorators to review performance, open issues, corrective actions, and upcoming production requirements."
That's all responsibilities.
- Qualifications: Required: 5+ years experience in warehouse operations, QA, QC, or production ops, preferably within apparel, accessories, textiles or decorated goods. Proven ability to identify, escalate, and resolve production and inventory quality issues in a fast-moving environment. Strong process-building mindset — experience creating SOPs, inspection criteria, and quality frameworks from scratch. Excellent communicator, able to translate on-the-ground observations into clear, concise written updates for a remote team. Detail-oriented and data-driven, with experience tracking KPIs and using metrics to drive decisions and accountability. Comfortable working independently on-site with minimal direct supervision while staying tightly aligned with a distributed team. Proficiency with production tracking tools, WMS/OMS systems, or similar platforms; strong skills in Excel/Google Sheets for reporting. Flexible and solutions-oriented, with the ability to adapt quickly to shifting priorities, rush orders, and unexpected issues.
Nice to have: Hands-on knowledge of decoration techniques (embroidery, screen-printing, heat transfer, embossing) and the quality standards associated with each.
- Physical Requirements: This is a fully on-site role, located in Santa Fe Springs, CA. You will be present at the facility during regular business hours. This is not a remote or hybrid position. Lifting up to 50 pounds. Standing and walking throughout the entirety of your shift. Ability to go up and down stairs, use of ladders throughout the day as needed. Bending, twisting, or kneeling may be required throughout the day for lifting or maneuvering objects. May be asked to work outside or travel to shoots off-site as needed.
- Pay Range: $112,000 USD - $120,000 USD. Also note: "All posted ranges are reflective of base salary and may vary depending upon experience level and location. Bonus and equity may also be provided for eligible roles."
- Schedule: Monday through Friday during regular business hours (already mentioned). Could be separate.
- Why Quince?: paragraph: "Joining Quince means being part of a mission-driven team reshaping retail. You will work alongside talented colleagues, tackle meaningful challenges, and contribute to building a more sustainable, accessible future for customers and partners alike."
We should not include EEO, hiring integrity, security advisory, accommodation form, background check, etc.
Now produce HTML fragment with
headings and appropriate content.
We need to decide which headings to use. Use:
About the role
(contains role description maybe plus company overview? Actually "About the role" could include role description; we could also include About Quince and Our Culture under a different heading like "About Quince" but not in examples. However we could put company description under "About the role"? That seems odd. Better to have separate sections: "About Quince" and "Our Culture" maybe not in list but we can still use for them; the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they expect us to use those exact headings when applicable. But we can also use other headings if needed? Safer to stick to those examples. So we need to map content to those headings.
We have:
- About the role: could include role description and maybe also company overview? But "About the role" likely refers to description of the role. We'll put the role description there.
- Responsibilities: list.
- Requirements: could include qualifications and physical requirements? But we also have Qualifications heading example. Could use Qualifications for qualifications, and Requirements for physical requirements? Or combine.
- Qualifications: for qualifications.
- Skills: maybe not needed.
- Benefits: for bonus and equity.
- Pay: for pay range.
- Schedule: for work schedule.
We also have "Why Quince?" maybe could be under "About the role"? Or we could add a section "About Quince" but not in list; maybe we can incorporate into "About the role" as a brief intro? But that would mix company description with role description; still okay as long as we preserve all info.
Better to have separate sections: "About Quince" and "Our Culture" but not in examples; risk of being considered filler? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning examples, not exclusive. So we can use other headings as long as they are . So we can add headings like "About Quince", "Our Culture", "Why Quince?".
Thus we will produce sections:
About Quince
...
Our Culture
...
About the role
...
Responsibilities
...
Qualifications
...
(maybe separate required and nice-to-have as sublists? Could keep as with items; nice-to-have could be separate Nice to have
but not required. We'll just include all qualifications in list, maybe mark nice-to-have.
Physical Requirements
...
Benefits
Bonus and equity may be provided for eligible roles.
Pay
$112,000 USD - $120,000 USD base salary (may vary depending on experience level and location).
Schedule
Monday through Friday during regular business hours.
Why Quince?
...
We must not include boilerplate like EEO, security advisory, accommodation, background check.
Now ensure we preserve all substantive information from the sections we extracted.
Let's craft the HTML.
We need to be careful to not lose any details.
About Quince paragraph: combine the description: "Quince is a destination for builders, creators
About the role
and put the role description there. Responsibilities: we have a list. Qualifications: we have Required and Nice to have. Physical Requirements: maybe could be under "Requirements"? But we have separate "Physical Requirements". Could be part of "Requirements" but we can create a section "Requirements" and include both qualifications and physical? However instruction: Use headings as examples; we can create "Requirements" heading and put qualifications and physical requirements inside. But we also have "Qualifications" as a possible heading. Might be better to follow the examples: Use "Qualifications" for qualifications, "Responsibilities" for responsibilities, "Pay" for pay range, "Schedule" maybe not present (schedule is mentioned: Monday through Friday regular business hours). That's schedule info. So we can include Schedule section. Benefits: not explicitly listed besides bonus and equity may be provided. That's a benefit. So we can include Benefits section with bonus and equity. Skills: maybe not separate; we could omit. About the role: we have description. We also have "Why Quince?" which could be like "About Quince" or "Why Quince?" but not in examples; we could omit or treat as "About Quince"? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include a section for "Why Quince?" maybe asWhy Quince?
with paragraph. We must not include boilerplate like EEO, security advisory, accommodation, background check, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, except boilerplate. Let's extract substantive content: - About Quince: description of company mission, M2C model, etc. - OUR CULTURE: description of culture. - THE ROLE: description: Quality Assurance Manager, Customization; on-site in Santa Fe Springs, CA; Monday-Friday regular business hours; may involve transportation to LA Warehouse and other decorators; role description: eyes and ears, inspect inbound inventory, audit production quality, raise issues, build processes for 99% OTD and 99% QA, link between floor and remote PM team, inputs shape Production Management Software. - Responsibilities: bullet list (we need to convert to- ).
List of responsibilities from text:
"Own quality outcomes, holding performance to 99% on-time delivery and 99% quality acceptance rate targets across all production runs."
"Monitor the inspection of inbound inventory received at the facility, verifying quantities, condition, and specifications against purchase orders and production requirements, drive timely inventory replacements to minimize production delays."
"Identify root cause issues stemming from the warehouse, and work cross-functionally to implement SOPs at the warehouse level to resolve issues."
"Conduct production quality checks throughout the decoration process (e.g., embroidery, screen-printing, heat transfer, embossing), identifying defects, inconsistencies, or deviations from brand standards."
"Raise issues quickly and clearly, documenting defects, inventory discrepancies, and production delays with supporting evidence (photos, data, root cause notes) and driving swift resolution with the decorator."
"Push the third party to implement changes rapidly."
"Provide structured and ad hoc updates to the remote project manager team, communicating production status, quality metrics, open issues, and risk flags in a clear, actionable format."
"Work with the Program Manager to incorporate project updates into the Production Management System."
"Build and implement QA processes and SOPs from the ground up — from incoming goods inspection to final outbound audits — to create a repeatable, scalable quality system."
"Track and analyze quality and delivery KPIs, identifying trends, recurring issues, and opportunities for improvement, and presenting findings to internal stakeholders."
"Influence and partner with the 3P decorator to drive adoption of Quince quality standards, SOPs, and process improvements — building trust and buy-in at the facility level to implement changes that stick."
"Identify root causes of quality failures, inventory discrepancies, and delivery misses, and work cross-functionally with internal project managers, sourcing, and the decorator to resolve them and prevent recurrence."
"Support onboarding of new product lines or decoration techniques by developing quality checkpoints and training criteria specific to each program."
"Maintain accurate records of quality references, inspections, defect rates, corrective actions, and inventory discrepancies in Quince's tracking systems."
"Conduct weekly operations check-ins with decorators to review performance, open issues, corrective actions, and upcoming production requirements."
That's all responsibilities.
- Qualifications: Required: 5+ years experience in warehouse operations, QA, QC, or production ops, preferably within apparel, accessories, textiles or decorated goods. Proven ability to identify, escalate, and resolve production and inventory quality issues in a fast-moving environment. Strong process-building mindset — experience creating SOPs, inspection criteria, and quality frameworks from scratch. Excellent communicator, able to translate on-the-ground observations into clear, concise written updates for a remote team. Detail-oriented and data-driven, with experience tracking KPIs and using metrics to drive decisions and accountability. Comfortable working independently on-site with minimal direct supervision while staying tightly aligned with a distributed team. Proficiency with production tracking tools, WMS/OMS systems, or similar platforms; strong skills in Excel/Google Sheets for reporting. Flexible and solutions-oriented, with the ability to adapt quickly to shifting priorities, rush orders, and unexpected issues.
Nice to have: Hands-on knowledge of decoration techniques (embroidery, screen-printing, heat transfer, embossing) and the quality standards associated with each.
- Physical Requirements: This is a fully on-site role, located in Santa Fe Springs, CA. You will be present at the facility during regular business hours. This is not a remote or hybrid position. Lifting up to 50 pounds. Standing and walking throughout the entirety of your shift. Ability to go up and down stairs, use of ladders throughout the day as needed. Bending, twisting, or kneeling may be required throughout the day for lifting or maneuvering objects. May be asked to work outside or travel to shoots off-site as needed.
- Pay Range: $112,000 USD - $120,000 USD. Also note: "All posted ranges are reflective of base salary and may vary depending upon experience level and location. Bonus and equity may also be provided for eligible roles."
- Schedule: Monday through Friday during regular business hours (already mentioned). Could be separate.
- Why Quince?: paragraph: "Joining Quince means being part of a mission-driven team reshaping retail. You will work alongside talented colleagues, tackle meaningful challenges, and contribute to building a more sustainable, accessible future for customers and partners alike."
We should not include EEO, hiring integrity, security advisory, accommodation form, background check, etc.
Now produce HTML fragment with
headings and appropriate content. We need to decide which headings to use. Use:
About the role
(contains role description maybe plus company overview? Actually "About the role" could include role description; we could also include About Quince and Our Culture under a different heading like "About Quince" but not in examples. However we could put company description under "About the role"? That seems odd. Better to have separate sections: "About Quince" and "Our Culture" maybe not in list but we can still usefor them; the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for section headings (e.g. those). Likely they expect us to use those exact headings when applicable. But we can also use other headings if needed? Safer to stick to those examples. So we need to map content to those headings. We have: - About the role: could include role description and maybe also company overview? But "About the role" likely refers to description of the role. We'll put the role description there. - Responsibilities: list. - Requirements: could include qualifications and physical requirements? But we also have Qualifications heading example. Could use Qualifications for qualifications, and Requirements for physical requirements? Or combine. - Qualifications: for qualifications. - Skills: maybe not needed. - Benefits: for bonus and equity. - Pay: for pay range. - Schedule: for work schedule. We also have "Why Quince?" maybe could be under "About the role"? Or we could add a section "About Quince" but not in list; maybe we can incorporate into "About the role" as a brief intro? But that would mix company description with role description; still okay as long as we preserve all info. Better to have separate sections: "About Quince" and "Our Culture" but not in examples; risk of being considered filler? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning examples, not exclusive. So we can use other headings as long as they are
. So we can add headings like "About Quince", "Our Culture", "Why Quince?". Thus we will produce sections:
About Quince
...
Our Culture
...
About the role
...
Responsibilities
- ...
Qualifications
- ...
- with items; nice-to-have could be separate
Nice to have
but not required. We'll just include all qualifications in list, maybe mark nice-to-have.Physical Requirements
- ...
Benefits
Bonus and equity may be provided for eligible roles.
Pay
$112,000 USD - $120,000 USD base salary (may vary depending on experience level and location).
Schedule
Monday through Friday during regular business hours.
Why Quince?
...
We must not include boilerplate like EEO, security advisory, accommodation, background check. Now ensure we preserve all substantive information from the sections we extracted. Let's craft the HTML. We need to be careful to not lose any details. About Quince paragraph: combine the description: "Quince is a destination for builders, creators