Jobs · Information Technology · Massachusetts

Senior Research Lead

Siemens Healthineers · Newton, MA · 3 wk ago
Information Technology$165k–$228k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description. We need headings for sections that have real content: About the role (maybe intro), Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include boilerplate like EEO, legal, etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". Pay and Benefits are present: Base Pay Range $165,490 - $227,546, and benefits list. Schedule not mentioned, so omit. Skills? There's a list of qualifications/experience; we could treat that as Qualifications section. Preferred Qualifications could be part of Qualifications or separate Skills? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have About the role (intro paragraph). Responsibilities (list). Qualifications (your qualifications and experience). Preferred Qualifications maybe could be under Skills or Qualifications. Could create a Skills section for preferred qualifications? But better to keep Qualifications covering both required and preferred. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills into one Qualifications section. Benefits and Pay are present. So sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not include Job ID etc. Must not include application instructions. Must strip boilerplate: EEO, Reasonable Accommodations, California Privacy Notice, Export Control, Data Privacy, Beware of Job Scams, etc. Also remove "To find out more about Siemens Healthineers businesses, please visit our company page here." That's maybe not substantive? It's a link; could be considered boilerplate. Probably remove. We need to preserve all substantive information: the inspiring paragraph, the description of the role, responsibilities list, qualifications list, preferred qualifications, benefits list, pay range. We must use

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

    for prose. We must output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine the introductory paragraphs: "Join us in pioneering breakthroughs in healthcare. For everyone. Everywhere. Sustainably. Our inspiring and caring environment forms a global community that celebrates diversity and individuality. We encourage you to step beyond your comfort zone, offering resources and flexibility to foster your professional and personal growth, all while valuing your unique contributions. We are currently looking for an ambitious Senior Research Lead to join our Endovascular Robotics business within Advanced Therapies. We are a global technology leader in robotic-assisted vascular interventions. We believe the combination of endovascular robotics, image guidance and dedicated devices will change the way neurovascular procedures will be done in the future, enabling better outcomes, and enabling our customers to provide better access to care. The Senior Research Lead at EVR will support an exciting new project that is focused on developing an autonomous and remote robotics system focused on stroke therapy. This project covers areas of interventional imaging, neurovascular device interfaces, robotics, and AI development." That's prose; put in

    . Responsibilities: list bullet points after "As a Senior Research Lead, you will be responsible for:" then list. We'll put each as

  • . Qualifications: combine "Your Qualifications And Experience" paragraph and bullet list? Actually it's a paragraph with bullet-like sentences separated by periods. Could treat as
    • each qualification. But the instruction: use
      • for any list of duties/requirements/benefits. So we can convert each sentence into list items. However we must preserve all substantive information; we can keep as

        if not a list? The text: "More than 7-10 years of experience in research collaborations, technology development, or related activities within the medical technology or healthcare sector. At least five years of experience leading complex scientific or technical projects, including the coordination of multidisciplinary and multi-institutional teams. A Master's degree or equivalent professional qualification in engineering, medicine, physics, computer science, or a related scientific or technical discipline is required. A Ph.D. will be considered an asset. Strong experience in scientific evaluation, experimental planning, and study design. Demonstrated ability to define, negotiate, and maintain accountability for project deliverables, milestones, and sponsor commitments. Strong analytical and problem-solving capabilities, with the ability to develop pragmatic and creative solutions to complex technical challenges. Excellent stakeholder-management, negotiation, facilitation, and decision-making skills. Excellent written and verbal communication skills in English, including the ability to communicate complex scientific and technical information to executive, technical, clinical, and external audiences. A collaborative leadership style and the ability to influence decisions effectively across organizational and functional boundaries." That's a list of qualifications; we can make

        • each. Preferred Qualifications: "Knowledge of neurovascular imaging, neurovascular devices and interventions, endovascular robotics, closed-loop safety architectures, or AI and machine learning for image-guided interventions. A demonstrated record of translating scientific research into product-development activities, technology solutions, or clinical applications." We could either add to Qualifications list or make a Skills section. Since we have a Skills heading possible, we could put preferred qualifications under Skills. But we said prefer few sections; maybe we add another
            under Qualifications with a subheading? Not allowed; only headings are h3. Could incorporate preferred qualifications into Qualifications list as additional items. That would keep sections fewer. Thus Qualifications section will contain both required and preferred items. Benefits: list: medical insurance, dental insurance, vision insurance, 401(k) retirement plan, life insurance, long-term and short-term disability insurance, paid parking/public transportation, paid time off, paid sick and safe time. Pay: Base Pay Range $165,490 - $227,546 plus note about factors affecting starting pay and commission eligibility. That's substantive; we should include that as prose maybe

            . The instruction: include Pay section only if posting actually states them. Yes. So we will have a Pay section with

            containing that info. Schedule: not mentioned, omit. Now ensure we removed boilerplate: EEO statement, Reasonable Accommodations, California Privacy Notice, Export Control, Data Privacy, Beware of Job Scams, To find out more..., etc. Also remove "Who we are:" paragraph? That is somewhat generic but could be considered substantive? It describes the company; but maybe it's boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who we are:" paragraph is more about the company; could be considered part of About the role? It's not directly about the role but could be considered filler. However it's not explicitly listed as boilerplate to remove. But we might keep it as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." The Who we are paragraph is generic company description; could be considered boilerplate but not explicitly listed. Safer to keep? It might be considered fluff. However the instruction says preserve ALL substantive information; does not say to remove generic company description. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Who we are is not those. So we could keep it in About the role section as extra prose. But we already have a long About the role paragraph; we could append the Who we are paragraph after it. Let's include: "Who we are: We are a team of more than 72,000 highly dedicated Healthineers in more than 70 countries. As a leader in medical technology, we constantly push the boundaries to create better outcomes and experiences for patients, no matter where they live or what health issues they are facing. Our portfolio is crucial for clinical decision-making and treatment pathways. How we work: When you join Siemens Healthineers, you become one in a global team of scientists, clinicians, developers, researchers, professionals, and skilled specialists, who believe in each individual’s potential to contribute with diverse ideas. We are from different backgrounds, cultures, religions, political and/or sexual orientations, and work together, to fight the world’s most threatening diseases and enable access to care, united by one purpose: to pioneer breakthroughs in healthcare. For everyone. Everywhere. Sustainably." That's substantive; keep. Now construct HTML. Structure:

            About the role

            ... (intro + who we are)

            Responsibilities

            • ...
            • ...

            Qualifications

            • ...
            • ...

            Benefits

            • ...
            • ...

            Pay

            ...

            Make sure no extra whitespace issues. Now extract responsibilities list exactly as given: - Providing scientific and technical program leadership within a cross-functional, global project team. - Serving as the central technical point of contact for the project, with responsibility for coordinating technology-related activities, deliverables, and milestones. - Aligning internal and external stakeholders on project objectives, technical priorities, interdependencies, timelines, and expected outcomes. - Collaborating with researchers, engineers, and medical experts to plan and execute project-related research activities. - Translating program objectives into clearly defined technical work packages, deliverables, acceptance criteria, and measurable milestones. - Evaluating and supporting the PI and Project Manager in monitoring scientific and technical progress, identifying risks and dependencies, and coordinating appropriate mitigation and escalation actions. - Maintaining alignment between research activities, product-development objectives, regulatory considerations, and the commitments made to the project sponsor. - Preparing and presenting milestone reports, technical updates, project results, risks, and recommendations to internal management and the project sponsor. Now qualifications list (required + preferred). Let's list each sentence as item. Required: - More than 7-10 years of experience in research collaborations, technology development, or related activities within the medical technology or healthcare sector. - At least five years of experience leading complex scientific or technical projects, including the coordination of multidisciplinary and multi-institutional teams. - A Master's degree or equivalent professional qualification in engineering, medicine, physics, computer science, or a related scientific or technical discipline is required. - A Ph.D. will be considered an asset. - Strong experience in scientific evaluation, experimental planning, and study design. - Demonstrated ability to define, negotiate, and maintain accountability for project deliverables, milestones, and sponsor commitments. - Strong analytical and problem-solving capabilities, with the ability to develop pragmatic and creative solutions to complex technical challenges. - Excellent stakeholder-management, negotiation, facilitation, and decision-making skills. - Excellent written and verbal communication skills in English, including the ability to communicate complex scientific and technical information to executive, technical, clinical, and external audiences. - A collaborative leadership style and the ability to influence decisions effectively across organizational and functional boundaries. Preferred: - Knowledge of neurovascular imaging, neurovascular devices and interventions, endovascular robotics, closed-loop safety architectures, or AI and machine learning for image-guided interventions. - A demonstrated record of translating scientific research into product-development activities, technology solutions, or clinical applications. Now benefits list: - medical insurance - dental insurance - vision insurance - 401(k) retirement plan - life insurance - long-term and short-term disability insurance - paid parking/public transportation - paid time off - paid sick and safe time Now pay paragraph: "The Base Pay Range For This Position Is $165,490 - $227,546. Factors which may affect starting pay within this range may include geography/market, skills, education, experience, and other qualifications of the successful candidate. If this is a commission eligible position the commission eligibility will be in accordance with the terms of the Company's plan

Similar jobs

RESEARCHER SENIOR LEAD

University of Alabama at BirminghamGreater Birmingham, Alabama Area· 4 mo ago
Analyst$64k–$90k/yrapply on uab.taleo.net

Senior Research Executive

Research PartnershipUnited States· 6 days ago
RemoteBusiness Development$85k–$95k/yrapply on job-boards.greenhouse.io

Senior Research Executive

Research PartnershipSan Francisco, CA· 2 mo ago
Business Development$85k–$95k/yrapply on job-boards.greenhouse.io

Lead/Senior Scientist

QnityHayward, CA· 1 mo ago
Analyst$95k–$149k/yrapply on careers.qnityelectronics.com