Jobs · Information Technology · Maryland

Field Service Engineer, Ventilation (East)

Nihon Kohden America · Baltimore, MD · 4 wk ago
Information Technology$80k–$105k/yrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO etc. We need to parse the posting. Let's extract sections: - About the role: The first paragraph(s) describing role: "The Field Service Engineer is primarily responsible for supporting NKA ventilator systems by providing troubleshooting, preventive maintenance, repair, software updates, and other service activities as required. The position is responsible for supporting the success of NKA customer relationships by identifying, evaluating, resolving, or appropriately escalating customer technical needs. The individual serves as a customer advocate and liaison between customers and the NKA organization. In addition to ventilator support, the position will also provide support for patient monitoring and other NKA medical device systems, including connectivity-related support when applicable. The role partners closely with hospital clinical, biomedical, and technical teams to ensure safe, reliable, and effective operation of NKA solutions." That's about the role. - Responsibilities: The "Essential Functions And Main Duties" list. Many bullet-like sentences. We need to put them in
  • . Should we separate into multiple
  • items. The text includes many sentences separated by periods. We'll break each duty into a list item. List items: - Assume responsibility for servicing, maintaining, and troubleshooting ventilator, patient monitoring, and related medical device systems. - Provide on-site and remote technical support, including troubleshooting, repair, installation support, customer training, and technical guidance. - Provide on-site diagnostic troubleshooting for hardware, software, pneumatic, electrical, mechanical, and connectivity issues. - Perform preventive maintenance inspections and scheduled service activities in accordance with manufacturer specifications and company procedures. - Provide installation, post-installation, preventive maintenance, and corrective maintenance support. - Perform setup, calibration verification, operational testing, and validation activities to ensure equipment performance and regulatory compliance. - Track and resolve service tickets promptly and effectively while ensuring optimal customer service. - Provide timely and effective communication to customers regarding service expectations, estimated arrival times, service status updates, and follow-up activities. - Work closely with Biomed, Respiratory Therapy, Nursing, IT, and clinical teams at customer locations. - Support integration, connectivity, and interoperability of NKA medical device systems within customer environments when applicable. - Demonstrate a basic understanding of hospital network infrastructure and troubleshoot device connectivity issues, including wired and wireless network communications, escalating advanced networking issues when appropriate. - Utilize troubleshooting techniques and analytical thinking skills to diagnose hardware, software, networking, pneumatic, mechanical, and system performance issues; determine corrective actions and resolve service tickets. - Escalate complex technical issues appropriately while collaborating with Technical Support, Product Specialists, Engineering, Quality, and other internal teams to achieve timely resolution. - Assist with compiling device information, service history, and inventory management documentation. - Obtain and convey information as needed; document all problems, including root cause, corrective action, and resolution information. - Accurately document service activities, equipment status, corrective actions, and maintenance records in accordance with company, regulatory, and quality system requirements. - Work with NKA internal teams to ensure successful coordination and delivery of product support. - Maintain and enhance technical skills related to ventilator technology, respiratory care applications, patient monitoring systems, hospital networking fundamentals, and emerging medical device technologies. - Promote goodwill and a positive image of the Company. - Demonstrate good judgment in the utilization of company credit cards while adhering to established business guidelines. - Complete administrative requirements within expected timeframes. - Maintain a professional appearance and conduct at all times. - Adheres to all company policies, procedures, and business ethics codes. - Duties may be modified or assigned at any time based on business need. We need to ensure we don't include boilerplate like "Duties may be modified or assigned at any time based on business need." That's part of responsibilities, okay. - Requirements: The posting has "Qualifications Education / Certification / Experience required ..." plus "Competencies Required". Might treat "Qualifications" as a section for education/experience/certifications. "Skills" maybe for competencies. But we need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role (we have) - Responsibilities (we have) - Qualifications (education/certification/experience) (we have) - Skills (competencies) (we have) - Pay (compensation range) (we have) - Schedule (working conditions schedule) (we have) - Benefits (there is a line: "Perks And Benefits Visit our Career page to learn more about Perks & Benefits and working at Nihon Kohden America." That's not specific; it's a generic reference. According to rule: never create Benefits section unless posting actually states them. This line is vague, not specific benefits. So we should not include Benefits section. - Requirements: Might be similar to Qualifications? The posting uses "Qualifications Education / Certification / Experience required". There's also "Competencies Required". Could treat "Requirements" as the qualifications (education/experience). But we already have Qualifications section. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have both Requirements and Qualifications if content distinct. However the posting lumps education/experience under "Qualifications". There's no separate "Requirements" heading. We could treat "Requirements" as the same as Qualifications, but we shouldn't duplicate. Better to have only Qualifications (education/experience/certifications) and Skills (competencies). The "Requirements" heading could be omitted if no distinct content. 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 if we don't have distinct content for Requirements, we omit it. Thus sections: About the role, Responsibilities, Qualifications, Skills, Pay, Schedule. Check if any other content like "Working Conditions" includes schedule and physical, travel, location. The schedule part we have. The location and travel could be considered part of Schedule? But schedule heading is for schedule only. The location and travel details maybe could be omitted unless we put under Schedule? But schedule heading is specifically for schedule. The location and travel are not schedule. There's no separate heading for Location or Travel. Could we put them under Schedule? Not appropriate. Could we create a separate section like "Working Conditions"? Not in allowed headings. So we may omit location/travel details? But we must preserve ALL substantive information. However we cannot invent headings not allowed. The allowed headings list is given as examples; we could possibly add other headings if needed? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, but likely they expect only those headings. Safer to stick to those. If we have location/travel info, we could incorporate into Schedule? Not ideal but maybe we can include location under Schedule as a note? But schedule heading is for schedule; location is not schedule. However we could treat location as part of Schedule? Might be considered "Working Conditions" but not allowed. Could we put location/travel under "About the role"? Might be okay as extra detail. But we must preserve all substantive info. Let's see if we can incorporate location/travel into About the role or Responsibilities as a sentence. The location: "Location: Must reside within assign region of Baltimore or Philadelphia." Travel: "Approximately 75%". Also "Access to Customer Sites: It is an essential function...". That's substantive. We could add a paragraph under About the role or Responsibilities. Perhaps under About the role we can add a sentence about location and travel. But About the role currently is about role description; location/travel is more about working conditions. Could add a separate paragraph after About the role before Responsibilities? But we need headings. Could we add a heading "Working Conditions"? Not allowed. Could we add a paragraph under Responsibilities? Not ideal but maybe acceptable as part of responsibilities? The responsibilities list includes duties; location/travel is not a duty but a condition. However we could add a separate

    after Responsibilities before Qualifications, without a heading? The instruction says output ONLY the HTML fragment, no restrictions on having stray paragraphs without heading? It says use

    for section headings,
    • for any list,

      for prose. It doesn't forbid having

      without heading. So we could have a

      for location/travel info. That would preserve info without needing a heading. That seems acceptable. Thus we will have:

      About the role

      ... (the role description)

      Responsibilities

        ...

      Location: Must reside within assigned region of Baltimore or Philadelphia. Travel: Approximately 75% of time. Access to customer sites requires vendor credentialing, including proof of vaccinations (e.g., COVID-19) and compliance with other criteria; typical vendor credentialing expenses will be paid/reimbursed by the Company.

      Qualifications

      Education / Certification / Experience required: Associate's degree in Biomedical Engineering, Electrical Engineering, Mechanical Engineering, Respiratory Therapy, Information Technology, or a related technical discipline; Bachelor's degree preferred, relevant education and experience accepted in lieu of a degree. 4+ years of experience servicing, maintaining, troubleshooting, repairing, or supporting ventilators or respiratory therapy equipment. CompTIA Network+, CBET, BMET, military technical training, respiratory therapy certifications, or equivalent technical certifications preferred. Experience diagnosing and resolving hardware, software, electrical, mechanical, pneumatic, and system-performance issues. Experience providing customer-facing technical support in healthcare, biomedical, respiratory therapy, or medical device environments. Basic knowledge of hospital networking and wired and wireless device connectivity preferred. Knowledge of hospital clinical environments and customer-support practices preferred.

      Skills

      • Technical Troubleshooting and Problem Solving
      • Customer Focus
      • Technical Communication
      • Clinical Environment Acumen
      • Healthcare Technology Connectivity
      • Must be able to communicate verbally and in writing, and to receive and understand verbal and written instructions in English
      • Able to work effectively both independently and in a collaborative team environment

      Pay

      The anticipated range for this position is $80,000 to $105,000. Actual placement within the range is dependent on multiple factors, including but not limited to skills, education, experience and location.

      Schedule

      Working Conditions Schedule: The regular hours for this full-time position are 8:00 a.m. to 5:00 p.m., Monday–Friday, unless otherwise stated by the department manager. Holiday, weekend, and evening work hours may be required. Regular hours may vary due to the needs of the organization or department and are subject to change at any time at the Company’s discretion.

      We might also include physical, travel details? Already included travel in location paragraph. Physical details: "Physical: Generally, may require some reaching, bending, stooping, squatting, crawling, kneeling, pushing, pulling, lifting, carrying up to 45 pounds, finger dexterity, repetitive motions, standing, walking, sitting, hearing, visual acuity, and color vision. More specific details may be provided as needed or requested." That's substantive. Could add another

      after Schedule

Similar jobs

Field Service Engineer

Bruker DaltonicsWill County, IL· 3 mo ago
RemoteCustomer Service$87k–$140k/yrapply on uscareers-bruker.icims.com

Field Service Engineer

MMTPennsauken Township, NJ· 4 mo ago
Information Technologyapply on recruiting.paylocity.com

Field Service Engineer

Park Place TechnologiesNew Jersey, United States· 2 mo ago
RemoteInformation Technologyapply on recruiting.ultipro.com

Field Service Engineer

Fives IntralogisticsNorth Canton, OH· 3 mo ago
Engineeringapply on career.fivesgroup.com

Field Service Engineer

Broetje Automation-USAWichita, KS· 3 mo ago
Information Technology$34–$43/hrapply on broetjeautomation.applytojob.com