R&D Research Expert

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where posting has real specific content. We need to parse the posting. The posting includes: - Intro: "Life at IBA ..." (company description). Not a section heading; we can put as

maybe under "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "Mission As an R&D (Research and Development) Research Expert, you will be part of the CRA ...". That's description of role. So we can put that under

About the role

with paragraphs. - Responsibilities: The "Challenges we trust you with" bullet list (actually paragraphs). That's responsibilities. So

Responsibilities

with

• items. - Requirements/Qualifications: The "What We Value" section includes required education/experience: Master's degree, PhD preferred, 2 years beam physics system ownership, etc. Also "Preferred education and experience:" and "Additional eligibility requirements:" plus "Physical Demands". Those could be under Requirements or Qualifications. We need to decide: maybe combine into

  Requirements

  and include both required and preferred? Or separate Qualifications and Skills? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate if content fits. Let's extract: Requirements (mandatory): - Master’s degree in Physics or Engineering, preferably a PhD. - At least 2 years of beam physics system ownership for a ProteusPLUS site (or equivalent technology). Ideally for a ProteusONE site as well. - Score at least an Experienced (Level 3) Engineer for Beam on the TCM. - Knowledgeable of cyclotron operations, beam health monitoring equipment and dosimetry tools. - Proven ability to lead troubleshooting efforts regarding beam, i.e. pausing, aborts, electrical noise on beam monitoring equipment, etc. with successful results. - Excellent communication skills and can manage customer relationship in continuous alignment with the local operations team and R&D. - Able to read, write and speak English. - Willing to travel up to 20% of your time and work weekend or night shifts. - Physical Demands: Regularly required to stoop, kneel, bend, crouch and lift up to 25 pounds. Required to drive and travel by plane to visit prospects and customer sites and facilities. Preferred: - Knowledgeable of FLASH and Radiation Therapy more generally. - A team player, always thoughtful to ensure synchronization of your efforts with those of colleagues. - A customer-oriented person with excellent interpersonal communication skills including presentation of ideas. - Able to report technical progress with different levels of abstraction to our different internal and external stakeholders. Skills: maybe communication, teamwork, etc. But we already have communication in requirements. Could separate Skills: e.g., communication, interpersonal, presentation, reporting technical progress, team player, customer-oriented. But we might not need separate Skills if content overlaps. However instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section, maybe "Requirements". But we have both required and preferred; we could put all under Requirements. Or we could have "Qualifications" for education/experience and "Skills" for soft skills. Let's see: The posting has "What We Value You have:" then list of required. Then "Preferred education and experience:" then list. Then "Additional eligibility requirements:" then language, travel, shifts. Then "Physical Demands". So we could have: - Requirements (education/experience) - Qualifications (maybe same as Requirements? hmm) - Skills (communication, teamwork, customer-oriented, reporting) - Benefits (explicit) - Pay (salary range) - Schedule? Not mentioned besides travel up to 20% and weekend/night shifts; no explicit schedule like full-time, shift work. Could infer but not explicit. So we should not create Schedule section unless posting actually states them. It does mention willing to work weekend or night shifts, but not a schedule like "Full-time" or "Shift work". Might be considered schedule info. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state willingness to work weekend or night shifts, which is schedule-related. Could include Schedule section with that detail. But also travel up to 20% is not schedule. Might be okay to include Schedule with "Willing to work weekend or night shifts; travel up to 20% of time." However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state weekend/night shifts, so we can include Schedule. Pay: The posting includes "Approximate Salary Range: Approx. $148,000 - $196,000." and variable pay details. So we can include Pay section. Benefits: The posting includes "Compensation And Benefits" with details. So Benefits section. Now we need to avoid boilerplate like EEO etc. Not present. We need to preserve all substantive information. So we need to include all details from the posting, but we can rephrase? Must not invent or summarize away detail. We should keep the details as is, maybe using same wording but can be in

  or

• . Must not omit any substantive info. So we need to include everything: company intro, mission description, responsibilities list, requirements (including preferred, eligibility, physical demands), benefits, pay, schedule (weekend/night shifts, travel). Also maybe include "Life at IBA" intro as part of About the role? Could be separate section "About IBA"? Not in headings list. But we could put under About the role as a paragraph describing the company and mission. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role containing company description and role mission. We must not repeat the job title as a heading. The job title is "R&D (Research and Development) Research Expert". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must output only HTML fragment, no /, no markdown. Let's structure:

  About the role

  Life at IBA ... (the paragraph about company).

  Mission As an R&D (Research and Development) Research Expert, you will be part of the CRA (Clinical Research & Application) group within the R&D department of our PT (Proton Therapy) BU and be based in Philadelphia (either locally contracted, or on a mission of minimum 2 years). You will be key to the continuation of the FLASH Fast Forward program at the University of Pennsylvania Proton Therapy Center and success of the first human clinical trial into ConformalFLASH. You will work in close collaboration with both the IBA R&D teams at our Belgian headquarters in Louvain-la-Neuve and the customer’s leading research team in Philadelphia, to advance equipment, radiobiological and clinical research into FLASH proton therapy. Beyond this main collaboration, you will maintain, coordinate and monitor IBA’s exploration plan on FLASH throughout IBA’s different research collaborations in order to answer open questions for IBA’s product strategy on FLASH.

  Then Responsibilities:

  Responsibilities

  • Contribute to the completion of the design, delivery, installation and handover to the local IBA team and the customer’s clinical research team of the HW and SW solutions developed for FLASH research on the ProteusPLUS and ProteusONE proton therapy systems.
  • Support and monitor their performance and use by the customer and report to IBA R&D teams.
  • Coordinate on-site follow-up and corrective actions on behalf of IBA’s R&D teams.
  • Consolidate the FLASH activities linked to the demonstration of the clinical relevance of FLASH based on the workstreams identified.
  • Coordinate with both the FLASH Program Manager and the Flash Product Manager to build the FLASH master plan and report on its progress to the FLASH Steering Committee.
  Then Requirements (maybe combine required and preferred and eligibility and physical demands). Could split into Requirements and Qualifications but we need to avoid thin sections. Let's make one Requirements section with subpoints maybe using
  and separate paragraphs for preferred etc. But we must preserve all details. We'll include:

  Requirements

  Required education and experience:

  • Master’s degree in Physics or Engineering, preferably a PhD.
  • At least 2 years of beam physics system ownership for a ProteusPLUS site (or equivalent technology). Ideally for a ProteusONE site as well.
  • Score at least an Experienced (Level 3) Engineer for Beam on the TCM.
  • Knowledgeable of cyclotron operations, beam health monitoring equipment and dosimetry tools.
  • Proven ability to lead troubleshooting efforts regarding beam, i.e. pausing, aborts, electrical noise on beam monitoring equipment, etc. with successful results.
  • Excellent communication skills and can manage customer relationship in continuous alignment with the local operations team and R&D.

  Preferred education and experience:

  • Knowledgeable of FLASH and Radiation Therapy more generally.
  • A team player, always thoughtful to ensure synchronization of your efforts with those of colleagues.
  • A customer-oriented person with excellent interpersonal communication skills including presentation of ideas.
  • Able to report technical progress with different levels of abstraction to our different internal and external stakeholders.

  Additional eligibility requirements:

  • Able to read, write and speak English.
  • Willing to travel up to 20% of your time and work weekend or night shifts.

  Physical Demands:

  • Regularly required to stoop, kneel, bend, crouch and lift up to 25 pounds.
  • Required to drive and travel by plane to visit prospects and customer sites and facilities.
  But we might be duplicating travel and weekend/night shifts which also belong to Schedule. We could move those to Schedule section and keep Requirements focused on education/experience/skills. However the instruction says prefer few substantive sections over many thin ones. Having many sections may be okay if each has content. But we already have About, Responsibilities, Requirements, Benefits, Pay, Schedule. That's 6 sections. Could be okay. Let's separate: - Requirements: education/experience (required + preferred) - Skills: maybe communication, teamwork, customer-oriented, reporting technical progress (these are soft skills). But we already included them in required/preferred. Could move them to Skills. But we need to avoid thin sections. If we split too much, we get many thin sections. Let's think: The posting includes a lot of details under "What We Value You have:" (required), "Preferred education and experience:", "Additional eligibility requirements:", "Physical Demands". That's a lot; we could keep them all under a single "Requirements" section with subheadings (using

  ...) and lists. That's substantive. Then we can have Benefits, Pay, Schedule. Schedule: includes willingness to travel up to 20% and work weekend or night shifts. We'll put that. Now Benefits: need to include all details from "Compensation And Benefits". Let's extract: - IBA offers a comprehensive benefits package that reflects our commitment to employee wellbeing and our values as a B Corp. Our