Jobs · Engineering · Texas

Sustaining Engineer II

CardioQuip · College Station, TX · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role? The posting includes description of responsibilities, what you'll do, what we're looking for (must-haves, nice-to-haves), what we offer (benefits, compensation). Also "Why Join?" maybe as a section? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have responsibilities content, we have requirements (must-haves, nice-to-haves). We have benefits/compensation. We have "Why Join?" maybe could be "About the role"? Actually "About the role" could be the introductory paragraph: "Sustaining Engineers collaborate with cross-functional teams..." That's a description. Could be "About the role". Then "Responsibilities" for the bullet list of duties (the "What you’ll do" list). Then "Requirements" for must-haves and nice-to-haves? Could split into "Qualifications" and "Skills". But we can combine. The instruction: prefer a few substantive sections over many thin ones. So maybe sections: About the role, Responsibilities, Qualifications, Benefits. Pay: they mention "Competitive Compensation A fair salary commensurate with experience and qualifications." That's vague but it's actual content: they say competitive compensation, fair salary commensurate with experience. That's not a specific number, but it's still content. The instruction says: 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. They do state "Competitive Compensation A fair salary commensurate with experience and qualifications." That's still somewhat vague but it's actual statement. Is "commensurate with experience" considered filler? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So "commensurate with experience" is explicitly listed as filler. So we should not create a Pay section because the content is just that phrase. However they also say "Competitive Compensation" which is a heading but the detail is just that phrase. Since the detail is filler, we should avoid Pay section. Similarly Benefits: they list specific benefits: health, dental, vision insurance, retirement savings plan with company contribution, paid time off, etc. That's substantive. So we can have Benefits section. Schedule: not mentioned, so omit. Thus sections: About the role (intro paragraph), Responsibilities (list of duties from "What you’ll do"), Qualifications (must-haves and nice-to-haves maybe combined), Benefits (list). Could also have "Skills" but we can incorporate into Qualifications. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. We need to output only HTML fragment. Let's extract content. Intro: "Sustaining Engineers collaborate with cross-functional teams to support released CardioQuip products throughout the post-market lifecycle." That's a prose sentence. Could be part of About the role. Then after that: "Responsibilities include product and process changes, design transfer, complaint investigations, manufacturing support, post-market data review, product improvement, and maintenance of compliant engineering and quality documentation." That's also responsibilities but maybe part of About the role? But we have a separate Responsibilities section later with detailed list. We'll keep the intro as About the role paragraph. Then "What you’ll do" list: many items each starting with a verb. We'll turn each into

  • . Let's list them: - Independently execute routine lifecycle-management and post-market maintenance activities for released CardioQuip products, including controlled product and process changes from problem definition through technical justification, risk assessment, verification and validation, documentation, and implementation. - Lead or coordinate routine design transfer activities for new products and product changes, including manufacturing readiness, drawings and bills of material, work instructions, inspection and test methods, training support, and production documentation. - Analyze post-market, service, manufacturing, complaint, and customer feedback data to identify trends, product issues, and improvement opportunities and recommend appropriate actions. - Lead routine engineering investigations and root cause analyses for product, manufacturing, service, and complaint issues and implement or coordinate corrective actions. - Perform complaint handling activities assigned to Engineering, including customer communication, device investigations, complaint determinations and documentation, risk assessments, corrective-action or CAPA evaluations, and domestic and international reportability determinations, regulatory reporting documentation, and approvals, as assigned, authorized, and qualified. - Plan, draft, execute, and document verification, validation, and process validation activities supporting sustaining changes. - Conduct routine engineering manufacturing-line audits and observations to verify personnel adherence to approved procedures, work instructions, and manufacturing practices; document findings and coordinate appropriate follow-up. - Maintain design, manufacturing, risk-management, and change-control records for assigned products in accordance with applicable standards, regulations, and CardioQuip quality requirements. - Work directly with contract manufacturers, suppliers, Service, distributors, and customers to resolve technical issues, evaluate changes, and support product and supply continuity. - Coordinate cross-functional sustaining activities and update management and stakeholders regarding project progress, risks, budgets, and timelines. - Participate in continuous improvement of engineering and sustaining processes and in outreach for prospective engineering talent. - Other duties as assigned. Now "What we’re looking for" includes Must-haves and Nice-to-haves. Must-haves: - Completed a bachelor's degree in a relevant engineering field. - At least 1 year of relevant industry experience, preferably in the medical device industry. - Project management experience or CAPM certification preferred. Nice-to-haves: - Experience with design controls, design history and technical documentation, change control, risk management, RCA, FMEAs, CAPA, design verification and validation, process validation, statistical methods, and risk-based design. - Experience supporting released products through design changes, manufacturing investigations, supplier changes, design transfer, or other sustaining-engineering activities. - Knowledge of manufacturing processes, engineering drawings and bills of material, DFM/DFA/DFS, and production problem solving. - Knowledge of and experience with medical-device regulations and standards, such as FDA QMSR, 21 CFR Part 803, ISO 13485, ISO 14971, EU MDR, IEC 60601, IEC 62304, and IEC 62366, as applicable. - Ability to analyze technical and post-market data, exercise sound engineering judgment, and translate findings into appropriate recommendations. - Ability to lead routine project planning, scheduling, budgeting, and tracking efforts; excellent organizational, technical writing, oral, and interpersonal skills. Now "What We Offer": - Competitive Compensation: A fair salary commensurate with experience and qualifications. (We decided to omit Pay section because it's filler; but we could include it as part of Benefits? The instruction says only create Pay section if posting actually states them. It does state "Competitive Compensation A fair salary commensurate with experience and qualifications." That's still vague but it's a statement. However the filler phrase "commensurate with experience" is considered filler; but the heading "Competitive Compensation" is not filler. The detail is filler. The instruction says 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. So if we create a Pay section, the content would be that filler sentence. That's disallowed. So we should not create a Pay section. We could incorporate the compensation statement into Benefits section? But Benefits section is for benefits like health insurance etc. The instruction says we can have Benefits section only if posting actually states them. It does state benefits. So we can have Benefits section that includes both the compensation statement and the benefits list? Might be okay but the compensation statement is filler; but if we include it inside Benefits, it's still filler content. The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include filler inside a section as long as the section heading is not followed by filler only. If we have Benefits heading and then a list that includes both substantive items and a filler sentence, that's okay? The heading is not followed solely by filler. So we could include the compensation statement as a
  • inside Benefits. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (Competitive Compensation). So we could create a Benefits section and include the compensation statement as a list item. That seems acceptable. But we need to decide: maybe better to have a Benefits section that includes the compensation statement and the benefits list. However the compensation statement is vague; but it's still stated. We'll include it. Now Benefits list: - Competitive Compensation: A fair salary commensurate with experience and qualifications. - Comprehensive Benefits: Health, dental, and vision insurance. - Retirement savings plan with company contribution. - Dynamic Work Environment: A supportive team culture that values innovation, improvement, and empowerment. - Work-Life Balance: Paid time off, including vacation days and holidays. - Fun and Engaging Culture: We believe in working hard and celebrating our successes together, fostering a sense of camaraderie and enjoyment in our work. But note: The text includes headings like "Competitive Compensation", "Comprehensive Benefits", "Dynamic Work Environment", "Work-Life Balance", "Fun and Engaging Culture". Those are like subheadings within the "What We Offer" section. We could treat each as a list item with bold? But we only have
    • . We can keep the phrasing as sentences. We need to preserve all substantive information. So we should keep those descriptions. Thus Benefits section will have a
        with each benefit as
      • . Now "Why Join?" section: It's a paragraph about mission. Could be considered "About the role" or maybe "About the company". The instructions list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Join?" is not in the list, but we could treat it as "About the role"? However we already have About the role intro. Could we add another section like "About the company"? Not in list but we could still use

        for any heading? The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. It says use

        for section headings (e.g. ...). So we can use other headings as long as they are

        . But we should avoid creating sections with filler. The "Why Join?" paragraph is substantive. Could we include it as part of About the role? Might be better to have a section "About the company" or "Why Join?" but not in the examples. Safer to incorporate it into About the role paragraph? But About the role currently only has the first sentence. We could expand About the role to include the introductory paragraph and the "Why Join?" paragraph. That would keep sections few. Thus About the role will contain two paragraphs: first about role collaboration, second about why join (mission). That preserves all. Now we need to ensure we don't repeat job title as heading. Not using. Now produce HTML:

        About the role

        Sustaining Engineers collaborate with cross-functional teams to support released CardioQuip products throughout the post-market lifecycle.

        At CardioQuip, we are dedicated to empowering people towards better healthcare. As a leading company in the medical device industry, we design

Similar jobs

Sustaining Engineer II

MedtronicPlymouth, MN· 1 wk ago
Quality Assurance$82k–$122k/yrapply on medtronic.wd1.myworkdayjobs.com

Sustaining Engineer II

Seagate TechnologyFremont, CA· 1 mo ago
Quality Assurance$88k–$125k/yrapply on seagatecareers.com

Sustaining Engineer II

MedtronicFridley, MN· 1 mo ago
Quality Assurance$82k–$122k/yrapply on medtronic.wd1.myworkdayjobs.com

Sustaining Engineer II

IDEMIA Public SecurityMadison, WI· 1 mo ago
Engineeringapply on uscareers-idemia.icims.com

Sustaining Engineer II

Jupiter EndovascularSan Francisco, CA· 4 mo ago
Quality Assurance$90k–$105k/yrapply on grnh.se