Jobs · Quality Assurance · Kansas

Quality Engineer

Mid-Continent Instruments and Avionics · Wichita, KS · 3 wk ago
On-siteQuality AssuranceFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: Intro: "COME JOIN MID-CONTINENT! “Where your work is valued—above-market pay, real work-life balance, and a team that feels like home.” THE POSITION… As a Quality Engineer, you will provide quality engineering support across products and manufacturing processes for suppliers, customers, and the quality management system. This position combines audit leadership, root cause and corrective action, data analysis, quality reporting, and cross-functional problem-solving. You will lead internal and external audits, interface with customers and suppliers, and use data to drive product and process improvements." That's about the role. Then "THIS POSITION MAY BE FOR YOU IF…" list of requirements/qualifications. Then "WE WOULD REALLY LIKE IT IF… (but it’s not a deal breaker)" list of nice-to-have. Then "WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT…" list of duties/responsibilities. Then "WE ARE ONE OF THE BEST PLACES TO WORK…" benefits, above-market pay, comprehensive benefits package, work-life balance, facility, events, food drive, etc. Then "WHO WE ARE…" company description. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: we have description of role (first paragraph). Good. - Responsibilities: we have "WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT…" which lists duties. Also earlier "As a Quality Engineer, you will..." but that's more about role. We'll put responsibilities from that list. - Requirements: "THIS POSITION MAY BE FOR YOU IF…" list includes bachelor's degree, 5 years experience, experience leading audits, root cause, etc., ability to analyze data, read drawings, proficiency with MS Office, attention to detail, organized, focused, results oriented, problem-solver, critical thinking, prioritizing, excellent verbal/written/interpersonal communications. - Qualifications: maybe overlapping with requirements; but we could treat "WE WOULD REALLY LIKE IT IF…" as qualifications (nice-to-have). Or we could treat them as Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to decide which content maps. We have "Skills" maybe list of proficiencies: Microsoft Office, attention to detail, organized, focused, results oriented, problem-solver, critical thinking, prioritizing, communication skills. Could be separate Skills section. But we can combine some. We need to avoid filler like "commensurate with experience". Not present. Pay: posting says "above-market pay". Also "We provide above-market pay and a comprehensive benefits package." So we have Pay info: above-market pay. Not specific number but it's stated. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state above-market pay, so we can include Pay section with that statement. Benefits: they mention comprehensive benefits package, plus events, food drive, etc. So Benefits section. Schedule: Not mentioned. No schedule info. So we should NOT include Schedule heading. Now we need to output HTML fragment only, no /. Use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all points from the lists. Let's extract lists. About the role prose: first paragraph(s) up to "THE POSITION…". Actually the intro includes tagline. We'll combine into a paragraph. Responsibilities list: from "WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT…" bullet points (though not bullet but sentences separated by line breaks). We'll convert each sentence to

  • . List items: - Plan, lead, document, and follow up on internal and external audits, including corrective actions and effectiveness verification - Serve as a primary quality interface with customers and suppliers regarding quality requirements, product issues, investigations, corrective actions, performance, and improvement plans - Lead root cause and corrective action activities for customer returns, internal and supplier nonconformities, audit findings, quality escapes, and recurring product or process issues - Collect, analyze, and interpret data; create reports, dashboards, metrics, and presentations that drive action - Participate in Material Review Board activities by evaluating nonconformities, supporting technically sound dispositions, identifying systemic issues, and tracking actions - Participate in Engineering Change Order activities by evaluating proposed changes for quality, inspection, documentation, configuration, manufacturing, supplier, and customer impacts - Support quality throughout the product lifecycle, including new product introduction, first article builds, FAI documentation, production, service, supplier quality, customer returns, and product or process changes Also earlier "As a Quality Engineer, you will provide quality engineering support across products and manufacturing processes for suppliers, customers, and the quality management system. This position combines audit leadership, root cause and corrective action, data analysis, quality reporting, and cross-functional problem-solving. You will lead internal and external audits, interface with customers and suppliers, and use data to drive product and process improvements." This could be part of About the role, but we could also include in Responsibilities. However we already have responsibilities list; we could keep that as part of About the role prose. To avoid duplication, we can incorporate that into About the role. Requirements list: from "THIS POSITION MAY BE FOR YOU IF…" bullet points (though not bullet). Let's list each: - You have a bachelor’s degree in engineering, quality, manufacturing, or a related field. - You have a minimum of five years of experience in quality engineering, manufacturing engineering, aviation quality assurance, or a related technical role. - You have experience leading audits, root cause investigations, corrective actions, and cross-functional improvement activities. - You can analyze quality and manufacturing data, identify meaningful trends, and communicate the results through clear reports and presentations. - You can read and interpret engineering drawings, specifications, customer requirements, and manufacturing documentation. - You are proficient with Microsoft Office. - You have strong attention to detail. - You are organized, focused, and results oriented. - You are a problem-solver with critical thinking and prioritizing skills. - You have excellent good verbal, written, and interpersonal communications skills. (Note: "excellent good" seems typo but we keep as is.) Qualifications (nice-to-have) list: from "WE WOULD REALLY LIKE IT IF… (but it’s not a deal breaker)": - You have experience in aviation or another highly regulated manufacturing environment. - You have working knowledge of AS9100, FAA requirements, AS9102 First Article Inspection, and customer-specific quality requirements. - You have experience applying statistical analysis, Six Sigma, APQP, risk management, or other structured quality, or other structured quality and continuous-improvement methods. Skills: Could be derived from requirements like proficiency with MS Office, attention to detail, organized, focused, results oriented, problem-solver, critical thinking, prioritizing, communication skills. But we already have those in Requirements. Perhaps we can treat Skills as a separate section for those soft skills and technical proficiencies not covered elsewhere. However to avoid duplication, we might combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we don't need a separate Skills section; we can incorporate those into Requirements or Qualifications. But we need to follow the allowed headings; we can omit Skills if no specific content beyond what's already covered. However we have explicit skill mentions: "You are proficient with Microsoft Office." "You have strong attention to detail." "You are organized, focused, and results oriented." "You are a problem-solver with critical thinking and prioritizing skills." "You have excellent good verbal, written, and interpersonal communications skills." Those could be considered Skills. But they are also requirements. To avoid duplication, we could put them under Requirements and not have Skills section. The instruction says we can use those headings; we don't have to use all. So we can omit Skills. Benefits: from "WE ARE ONE OF THE BEST PLACES TO WORK…" includes: - We provide above-market pay and a comprehensive benefits package. - We promote an environment where you can excel in your career while still maintaining a healthy work-life balance. - Our facility is climate-controlled, clean, organized, and safe. - We operate in a professional, light manufacturing environment. - We believe anything worth doing is worth doing right – every time. - We have frequent events to keep work interesting. - Our food drive is super impressive; we enjoy an annual food truck fest appreciation day, monthly fruit/donut day, employee luncheons throughout the year, wellness challenges with incentives, and frequent ticket raffles for local sporting and cultural events. - We have a small company feel – even though we’re doing big things! Also earlier tagline: "above-market pay, real work-life balance, and a team that feels like home." That's also benefits. Pay: "above-market pay". Also "We provide above-market pay and a comprehensive benefits package." So Pay section: maybe just a sentence: "Above-market pay." But we need to preserve all substantive information; we should not drop the benefits details. So Benefits section will contain the list of benefits. Pay section: maybe just a short paragraph: "Above-market pay." Could also include that it's part of benefits but we separate. Schedule: none, omit. Now About the role: we need to include the description: "As a Quality Engineer, you will provide quality engineering support across products and manufacturing processes for suppliers, customers, and the quality management system. This position combines audit leadership, root cause and corrective action, data analysis, quality reporting, and cross-functional problem-solving. You will lead internal and external audits, interface with customers and suppliers, and use data to drive product and process improvements." Also maybe the tagline? The tagline is more about company culture; could be part of Benefits or About the role? Probably About the role is about the position; tagline is about company. We'll keep tagline maybe in Benefits or About the role? The tagline: “Where your work is valued—above-market pay, real work-life balance, and a team that feels like home.” That's more about benefits/culture. Could go under Benefits as part of work-life balance and team feel. But we already have work-life balance in Benefits. We'll incorporate tagline into Benefits as a sentence. Thus About the role paragraph: the description above. Now we need to ensure we don't repeat content. Let's craft. HTML:

    About the role

    As a Quality Engineer, you will provide quality engineering support across products and manufacturing processes for suppliers, customers, and the quality management system. This position combines audit leadership, root cause and corrective action, data analysis, quality reporting, and cross-functional problem-solving. You will lead internal and external audits, interface with customers and suppliers, and use data to drive product and process improvements.

    Responsibilities

    • Plan, lead, document, and follow up on internal and external audits, including corrective actions and effectiveness verification
    • Serve as a primary quality interface with customers and suppliers regarding quality requirements, product issues, investigations, corrective actions, performance, and improvement plans
    • Lead root cause and corrective action activities for customer returns, internal and supplier nonconformities, audit findings, quality escapes, and recurring product or process issues
    • Collect, analyze, and interpret data; create reports, dashboards, metrics, and presentations that drive action

Similar jobs

Quality Engineer

Grammer AGBelden, MS· 1 mo ago
Quality Assuranceapply on de.jobsyn.org

Quality Engineer

Applied MedicalRancho Santa Margarita, CA· 1 mo ago
Quality Assurance$71k–$75k/yrapply on careers.appliedmedical.com

Quality Engineer

Corning IncorporatedRochester, NY· 1 mo ago
Engineeringapply on bit.ly

Quality Engineer

MANITOU GroupMadison, SD· 1 mo ago
$60k–$85k/yrapply on careers.manitou-group.com

Quality Engineer

Bastion Technologies, Inc.New Orleans, LA· 2 mo ago
Engineeringapply on bastiontechnologies.applicantpro.com

Quality Engineer

Amsted AutomotiveTaylor, MI· 2 mo ago
Quality Assuranceapply on ars2.equest.com