Program Quality Manager
Jobot · Stockton, CA · 1 mo ago
On-siteQuality Assurance$120k–$140k/yrFull-time
We need to output HTML fragment with sections: About the role (maybe "About the role" or "About us"? The posting includes "A bit about us:" which is about the company. Could be "About the role" or "About us". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings are appropriate based on content.
We have:
- Salary: $115,000 - $140,000 per year (also earlier "$120k to $140k").
- Location: Stockton, CA / Onsite.
- Company description: "Founded more than 60 years ago...". That's about us.
- Why join us? bullet list: Base salary $120k–$140k+ (duplicate), Medical, dental, vision, matching 401(k), Generous PTO, sick leave, and paid holidays, Fully onsite in Stockton — the role is embedded with program teams and hands-on by nature, Program-level ownership of quality: you lead across multiple programs, not one narrow slice, Long-standing customer platforms and a stable, multi-decade program base.
- Job Details: responsibilities list.
- Looking for: qualifications/experience.
We need to avoid boilerplate: EEO, legal, etc. Remove navigation, cookie, etc. Remove duplicated lines.
We need to include sections only when posting has real specific content. So we can have:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not exclusive. So we can add About the company.
But to be safe, we could incorporate that into About the role section.
Let's craft:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings are appropriate based on content.
We have:
- Salary: $115,000 - $140,000 per year (also earlier "$120k to $140k").
- Location: Stockton, CA / Onsite.
- Company description: "Founded more than 60 years ago...". That's about us.
- Why join us? bullet list: Base salary $120k–$140k+ (duplicate), Medical, dental, vision, matching 401(k), Generous PTO, sick leave, and paid holidays, Fully onsite in Stockton — the role is embedded with program teams and hands-on by nature, Program-level ownership of quality: you lead across multiple programs, not one narrow slice, Long-standing customer platforms and a stable, multi-decade program base.
- Job Details: responsibilities list.
- Looking for: qualifications/experience.
We need to avoid boilerplate: EEO, legal, etc. Remove navigation, cookie, etc. Remove duplicated lines.
We need to include sections only when posting has real specific content. So we can have:
About the Company
maybe but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says e.g., not limited to. So we can use About the role (maybe about the role description). But we have "A bit about us:" which is about company. Could treat as About the role? Might be okay. But we could also use "About the role" for role description and "About the company" not in list but maybe okay. Safer to stick to given examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for:
- About the role: maybe the "Job Details" paragraph describing role.
- Responsibilities: bullet list of duties.
- Requirements/Qualifications: "Looking for:" list.
- Skills: maybe Microsoft Office, database management, etc.
- Benefits: bullet list from "Why join us?" includes Medical, dental, vision, matching 401(k), Generous PTO, sick leave, paid holidays.
- Pay: salary range.
- Schedule: Fully onsite in Stockton.
We must not include placeholder text like "commensurate with experience". We have actual specifics.
We must not repeat job title as heading.
We must not include Job ID etc.
We must output only HTML fragment.
Let's extract details:
About the role: Could be the paragraph: "You'll provide quality oversight for engineers and inspectors embedded within Program Management teams, keeping quality objectives aligned across multiple aerospace and defense programs. Manage and coordinate quality activities across multiple dedicated program teams to ensure alignment of objectives Provide staff-level Quality Engineering oversight for Quality Engineers carrying technical and programmatic responsibilities Mentor and train Quality Engineers and Inspectors, guiding their professional and career development Champion a Continual Improvement Culture (CIC) and drive processes that reduce cycle time and cost Advise and support the Director of Quality Assurance on performance activities, recruiting, budgeting, and third-party audits"
That's a run-on; we can split into sentences.
Responsibilities: Could be same as above? Actually the "Job Details" is responsibilities. Could treat that as Responsibilities. Then About the role could be brief summary: "Program Quality Manager role at a Tier 1 Aerospace Supplier, overseeing quality across multiple programs." But we need to preserve all substantive info; we can't invent. So we need to use actual text. Maybe we can have About the role: "Program Quality Manager — Aerospace & Defense Program Quality — $120k to $140k — Stockton, CA / Onsite — Tier 1 Aerospace Supplier". But that includes salary etc. Might be duplication.
Better: Use About the role: short description from first line: "Program Quality Manager — Aerospace & Defense Program Quality". But that's basically job title. Might be okay.
But we need to avoid repeating job title as heading, not as content. It's fine to have job title in content.
Let's structure:
About the role
Program Quality Manager — Aerospace & Defense Program Quality — $120k to $140k — Stockton, CA / Onsite — Tier 1 Aerospace Supplier.
But that includes salary and location which we also have separate sections; might duplicate. Could keep it generic: "Program Quality Manager role overseeing quality across multiple aerospace and defense programs." That's not directly from text but summarizing. Might be considered inventing. Safer to use the exact sentence from "A bit about us:"? That's about company. Maybe we can skip About the role and go straight to Responsibilities, Requirements, Benefits, Pay, Schedule. The instruction says prefer a few substantive sections over many thin ones. So we can combine. We have: - Responsibilities: the Job Details paragraph. - Requirements: the "Looking for:" list. - Benefits: the "Why join us?" list (excluding base salary duplicate maybe). - Pay: salary range. - Schedule: Fully onsite in Stockton. We also have company description: "Founded more than 60 years ago...". Could be included in About the role or a separate About the company but not in list. Could add as a paragraph under About the role? Might be okay. Let's extract company description: "Founded more than 60 years ago and based in Stockton, California, we are a mid-tier aerospace and defense manufacturer building flight-critical structures, assemblies, and precision hardware for launch vehicles, satellites, and defense platforms. Much of the hardware we produce has flown on our customers' platforms for decades, making us one of the more capable independent suppliers in the region. Our Quality organization sits at the center of every program we deliver." We can put that underAbout the company
but not in allowed list. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not exclusive. So we can add About the company.
But to be safe, we could incorporate that into About the role section.
Let's craft:
About the role
Founded more than 60 years ago and based in Stockton, California, we are a mid-tier aerospace and defense manufacturer building flight-critical structures, assemblies, and precision hardware for launch vehicles, satellites, and defense platforms. Much of the hardware we produce has flown on our customers' platforms for decades, making us one of the more capable independent suppliers in the region. Our Quality organization sits at the center of every program we deliver. As a Program Quality Manager, you will provide quality oversight for engineers and inspectors embedded within Program Management teams, keeping quality objectives aligned across multiple aerospace and defense programs.
That combines company description and role overview. Then Responsibilities: list bullet points from Job Details. Let's extract bullet points: - Manage and coordinate quality activities across multiple dedicated program teams to ensure alignment of objectives - Provide staff-level Quality Engineering oversight for Quality Engineers carrying technical and programmatic responsibilities - Mentor and train Quality Engineers and Inspectors, guiding their professional and career development - Champion a Continual Improvement Culture (CIC) and drive processes that reduce cycle time and cost - Advise and support the Director of Quality Assurance on performance activities, recruiting, budgeting, and third-party audits We need to ensure we keep all details. Now Requirements/Qualifications: from "Looking for:" list: - Experience in Quality or Manufacturing environment, with prior supervisory or management experience strongly preferred - Bachelor's degree in a technical field preferred - Aerospace industry experience preferred; other regulated industries considered - Strong Microsoft Office skills; database management a plus - Manager level; strong senior or lead quality candidates ready to step up considered - Experience in any of the following areas welcomed: * Aerospace or defense manufacturing quality * AS9100 or equivalent quality management systems * Continuous improvement (Lean, Six Sigma, root cause / corrective action) * Supplier and third-party audits * Mentoring or leading Quality Engineers and Inspectors We need to preserve all. We could make a- list.
Skills: maybe Microsoft Office, database management, etc. Could be part of Requirements.
But we could have a Skills section: "Strong Microsoft Office skills; database management a plus". However that's already in Requirements. Might be redundant.
Better to have Requirements/Qualifications combined.
Benefits: from "Why join us?" list:
- Base salary $120k–$140k+ (but we have Pay separate)
- Medical, dental, vision, matching 401(k)
- Generous PTO, sick leave, and paid holidays
- Fully onsite in Stockton — the role is embedded with program teams and hands-on by nature
- Program-level ownership of quality: you lead across multiple programs, not one narrow slice
- Long-standing customer platforms and a stable, multi-decade program base
We need to avoid duplicating salary in Benefits if we have Pay section. So we can omit base salary from Benefits.
Pay: Salary range: $115,000 - $140,000 per year (also earlier $120k to $140k). We'll use the exact: "$115,000 - $140,000 per year".
Schedule: Fully onsite in Stockton.
Now we need to ensure we don't include boilerplate: EEO, legal, etc. Remove.
Now produce HTML:
About the role
Founded more than 60 years ago and based in Stockton, California, we are a mid-tier aerospace and defense manufacturer building flight-critical structures, assemblies, and precision hardware for launch vehicles, satellites, and defense platforms. Much of the hardware we produce has flown on our customers' platforms for decades, making us one of the more capable independent suppliers in the region. Our Quality organization sits at the center of every program we deliver. As a Program Quality Manager, you will provide quality oversight for engineers and inspectors embedded within Program Management teams, keeping quality objectives aligned across multiple aerospace and defense programs.
Responsibilities
- Manage and coordinate quality activities across multiple dedicated program teams to ensure alignment of objectives
- Provide staff-level Quality Engineering oversight for Quality Engineers carrying technical and programmatic responsibilities
- Mentor and train Quality Engineers and Inspectors, guiding their professional and career development
- Champion a Continual Improvement Culture (CIC) and drive processes that reduce cycle time and cost
- Advise and support the Director of Quality Assurance on performance activities, recruiting, budgeting, and third-party audits
Requirements
- Experience in Quality or Manufacturing environment, with prior supervisory or management experience strongly preferred
- Bachelor's degree in a technical field preferred
- Aerospace industry experience preferred; other regulated industries considered
- Strong Microsoft Office skills; database management a plus
- Manager level; strong senior or lead quality candidates ready to step up considered
- Experience in any of the following areas welcomed:
- Aerospace or defense manufacturing quality
- AS9100 or equivalent quality management systems
- Continuous improvement (Lean, Six Sigma, root cause / corrective action)
- Supplier and third-party audits
- M