Jobs · Engineering · New York

QA Systems Engineer

Baxter International Inc. · Medina, NY · 1 mo ago
Engineering$76k–$105k/yrFull-time
We need to output HTML fragment with sections only if content present. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job posting. First, there is introductory fluff: "This is where your work makes a difference..." etc. That's likely "About the role" content. Should we include that? The instruction: "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." So we can have an About the role section with the introductory paragraph(s) describing Baxter mission etc. That seems appropriate. Then "Your role at Baxter This document outlines the employment prerequisites and job responsibilities for the Quality Assurance Systems Engineer position." That's also part of about. Then "What You'll Be Doing Reporting to the QA Systems Manager, the primary responsibilities are:" then list of responsibilities. That's Responsibilities section. Then "What You'll Bring" includes qualifications, requirements, skills. We need to separate into Requirements, Qualifications, Skills maybe. But we should only create sections if there is real specific content. The posting includes Bachelor's degree, experience, etc. Could be Requirements. Also "Experience in the manufacturing and/or medical device industry preferred..." etc. Also "Basic understanding of validation guidelines, cGMPs Regulations, and Good Manufacturing Practices, preferred." Also "Experienced multitasker..." etc. Also "Support plant initiatives..." etc. Also "Highly motivated..." etc. Also "Ability to meet tight deadlines." Then Physical Demands and Work Environment. Those could be under Requirements or maybe separate sections? The instruction only allows certain headings; we can put Physical Demands and Work Environment under Requirements or maybe as part of Requirements. But we should not create extra headings not listed. So we can include them in Requirements section as paragraphs/lists. Then "We understand compensation is an important factor..." includes Pay info: estimated base salary $76,000-$104,500 annually. Also mention discretionary bonuses. So we need a Pay section. Then "US Benefits at Baxter (except for Puerto Rico)" includes benefits description. So Benefits section. Schedule: not mentioned. So we should not create Schedule section. Also we need to remove boilerplate: EEO, Reasonable Accommodations, Recruitment Fraud Notice, etc. Also navigation/legal etc. So we drop those. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details like physical demands, work environment, etc. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to decide what constitutes a list. The responsibilities are a list of items each starting with a verb. We can put them in

    • . Similarly, the qualifications/requirements could be a list. Benefits also list. We need to avoid filler like "commensurate with experience" etc. Not present. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine the introductory paragraphs up to "Your role at Baxter This document outlines the employment prerequisites and job responsibilities for the Quality Assurance Systems Engineer position." Might be two paragraphs. We'll put them in

      . Then Responsibilities: heading

      Responsibilities

      then
      • each item. List items from posting: - Support and execute complex validations, including IQ, OQ, PQ, and MSA protocols and reports for processes, equipment, test methods, and computerized systems within the facility throughout the validation stages with little or no guidance. - Own and drive change control based on procedural requirements - Assist, present, defend, and communicate with external auditors and other validations or projects in which you lead or participated. - Assist or lead process improvement projects (scrap reduction, defect reduction, etc.) with little or no guidance. - Work collaboratively with a cross-functional team (production, quality, laboratory, etc.) - Apply solid technical understanding of engineering principles and procedures (e.g., CAD and its application or scheduling a series of technical tasks utilizing software-based tools and/or specialties such as electrical, mechanical, chemical, industrial, or biological). - Assists in the preparation and participation of technical reviews and is responsible for organizing data and preparing appropriate documentation for assigned projects. - Assist management or other engineers during process design, equipment installation, qualification, and/or process monitoring. - Provide technical reports and/or data-driven analysis after training. - Other duties as assigned We need to keep exactly as given. Then Requirements/Qualifications/Skills: The posting has "What You'll Bring" with bullet-like sentences. We could split into Requirements (education, experience) and Skills (technical abilities). But we have limited headings; we could combine into Requirements section and maybe Skills section if we have distinct content. Let's see. What You'll Bring list: - Bachelor's degree in Engineering. - 1-3 years of engineering experience preferred. - Prefer experience and/ or training with process improvement methods (e.g. six sigma, lean) - Interest in obtaining certifications (ASQ) - Experience in the manufacturing and/or medical device industry preferred, including experience in the development and deployment of Quality Systems. - Experience with technical communication, cross-functional collaboration, problem-solving, root cause analysis, and applying engineering principles. - Basic understanding of validation guidelines, cGMPs Regulations, and Good Manufacturing Practices, preferred. - Experienced multitasker with solid prioritization skills is essential - Support plant initiatives with the development and implementation of new processes/technologies - Highly motivated to learn and accomplish goals. - Ability to meet tight deadlines. - PHYSICAL DEMANDS ... (list) - WORK ENVIRONMENT ... (list) We could treat the first set as Requirements/Qualifications, and then Physical Demands and Work Environment as part of Requirements (maybe as sub-sections but we cannot add headings). We could just include them as paragraphs under Requirements. But we also have Skills: maybe we could create a Skills section for items like "Experience with technical communication, cross-functional collaboration, problem-solving, root cause analysis, and applying engineering principles." and "Basic understanding of validation guidelines, cGMPs Regulations, and Good Manufacturing Practices, preferred." and "Experienced multitasker with solid prioritization skills is essential". However, the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section called Requirements (or Qualifications). But we have both Requirements and Qualifications headings allowed. We could use Qualifications for education/experience/certifications, and Skills for technical abilities. That would be two sections, both substantive. Let's decide: Qualifications section: Bachelor's degree in Engineering; 1-3 years of engineering experience preferred; Prefer experience and/or training with process improvement methods (e.g. six sigma, lean); Interest in obtaining certifications (ASQ); Experience in the manufacturing and/or medical device industry preferred, including experience in the development and deployment of Quality Systems. Skills section: Experience with technical communication, cross-functional collaboration, problem-solving, root cause analysis, and applying engineering principles; Basic understanding of validation guidelines, cGMPs Regulations, and Good Manufacturing Practices, preferred; Experienced multitasker with solid prioritization skills is essential; Support plant initiatives with the development and implementation of new processes/technologies; Highly motivated to learn and accomplish goals; Ability to meet tight deadlines. Then Physical Demands and Work Environment could be part of Requirements or maybe a separate section? Not allowed headings. Could be included under Requirements as paragraphs. But we already used Requirements heading? Not yet. We could use Requirements for physical demands and work environment. However we already used Qualifications and Skills. We could also have Requirements section for physical demands and work environment. That would be three sections: Qualifications, Skills, Requirements (physical demands & work environment). That seems okay. But we need to ensure we don't create thin sections. Each has substantive content. Alternatively, we could combine physical demands and work environment into Requirements section. Then we would have Qualifications and Skills only. That's two sections. Which is better? The instruction: "Prefer a few substantive sections over many thin ones." So two sections is better than three. However we need to capture all info. Physical demands and work environment are important; we can include them in Requirements section as paragraphs. Thus we will have: - About the role (intro) - Responsibilities - Qualifications (education, experience, certifications, industry experience) - Skills (technical abilities, soft skills, etc.) - Benefits - Pay We need to ensure we don't miss any content like "Other duties as assigned" already in responsibilities. Now Benefits: we need to list benefits as
        • . The posting includes: - medical and dental coverage that start on day one - insurance coverage for basic life, accident, short-term and long-term disability, and business travel accident insurance - Employee Stock Purchase Plan (ESPP), with the ability to purchase company stock at a discount - 401(k) Retirement Savings Plan (RSP), with options for employee contributions and company matching - Flexible Spending Accounts - educational assistance programs - time-off benefits such as paid holidays, paid time off ranging from 20 to 35 days based on length of service, family and medical leaves of absence, and paid parental leave - commuting benefits - Employee Discount Program - Employee Assistance Program (EAP) - childcare benefits We need to keep all. Pay: we have estimated base salary $76,000-$104,500 annually. Also mention discretionary bonuses. We'll put that in

          . Now we need to ensure we don't include boilerplate like "We understand compensation is an important factor..." but we need to keep the salary range and discretionary bonuses. The surrounding sentences about pay philosophy etc may be considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The pay philosophy paragraph may be considered boilerplate but it's part of the pay description. However we need to preserve ALL substantive information; the salary range is substantive. The rest about "estimated range is meant to reflect..." etc may be considered boilerplate but still part of pay description. The instruction says to remove boilerplate, but not sure if we should remove the explanatory sentences. It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The pay philosophy is not explicitly listed, but could be considered boilerplate. However it's not navigation/legal/EEO/scam-warning. It's about pay practices. Might be considered part of the job posting but not essential. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The explanatory sentences about the range being estimated etc are not substantive detail about the job; they are more generic. Could be considered boilerplate. Safer to keep only the concrete salary range and discretionary bonuses. We'll keep a short sentence: "The estimated base salary for this position is $76,000-$104,500 annually. This position may also be eligible for discretionary bonuses." Now Benefits: we should keep the introductory sentence "We understand compensation is an important factor..." is about pay, not benefits. For benefits, there is an introductory paragraph: "US Benefits at Baxter (except for Puerto Rico) This is where your well-being matters. Baxter offers comprehensive compensation and benefits packages for eligible roles." That's somewhat boilerplate but we can keep a short summary: "Baxter offers comprehensive compensation and benefits packages for eligible roles." But we need to preserve substantive info; the list is substantive. The intro sentences may be considered filler but not disallowed. We'll keep a brief

          before the list: "Baxter offers comprehensive compensation and benefits packages for eligible roles." Now we need to ensure we don't

Similar jobs

System QA Engineer

CapmontPalo Alto, CA· 3 mo ago
Quality Assuranceapply on careers.cmont.com

QA Engineer

Lennar TitleMiami, FL· 2 mo ago
Engineering$30k/yrapply on careers.lennar.com

QA Engineer

O2 Technologies,IncChapel Hill, NC· 2 mo ago
Engineeringapply on oneai.o2inc.net

QA Engineer

Burford CapitalNew York, NY· 2 mo ago
Engineering$100k–$120k/yrapply on careers.burfordcapital.com

QA Engineer

Katalyst CROPittsburgh, PA· 2 mo ago
Quality Assuranceapply on www1.jobdiva.com