Discovery Research Domain Analyst, IT Business Analyst

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes: - Intro paragraph about BMS, purpose, etc. Could be "About the role" or maybe "About the role" is appropriate. The intro is about the company and role. We'll put that in

under

About the role

. - Responsibilities: list of bullet points under "Key Responsibilities". We'll output

• each. - Qualifications: bullet list under "Qualifications". We'll output
  • . - Desired Skills: bullet list under "Desired Skills". Could be "Skills" section. - Compensation Overview: includes pay ranges for locations. That's Pay section. We'll include

    Pay

    with

    containing the ranges. - Benefits: paragraph about benefits. We'll include

    Benefits

    with

    . - Possibly Schedule? Not mentioned. No schedule specifics. So omit. - Also maybe "How We Work" etc but not required headings. We'll ignore. We must not repeat job title as heading. No Job ID/requisition as heading. We can include minor metadata in a short

    or drop it. The posting ends with "R1605714 : Discovery Research Domain Analyst, IT Business Analyst". That's job ID and title. We can drop it or put in a short

    . Probably drop it. We must not include boilerplate like EEO, legal, etc. Remove those sections: "Supporting People With Disabilities", "Candidate Rights", "Data Protection", etc. Also remove "How We Work" maybe not needed but it's not boilerplate; but it's not a required heading. Could be omitted as not matching headings list. We'll omit. We must preserve all substantive information. So we need to include the content from "How We Work"? It's not under a heading we are using; but we could incorporate into About the role? Might be considered substantive but not under headings list. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying we can use those headings; but we should only include sections when posting has real specific content for it. It doesn't forbid other headings, but we should stick to those. The "How We Work" could be considered "About the role" maybe. But we can incorporate that content into About the role paragraph. Similarly, "We hire for skills and capabilities..." is a statement; could be part of Qualifications or Skills. We'll incorporate into Skills maybe. We need to output only HTML fragment, no markdown fences. Let's craft:

    About the role

    At Bristol Myers Squibb, our employees often ask, “Who are you working for?”—a question that fuels collaboration, accountability, and urgency in our work. Our purpose-driven culture inspires us to discover, develop, and deliver innovative medicines to prevail over serious diseases. We offer uniquely interesting and meaningful work, opportunities for growth, and a supportive environment that values inclusion, wellbeing, flexibility, and comprehensive benefits. This is work that transforms the lives of patients, and the careers of those who do it. Bristol Myers Squibb is seeking a curious, collaborative, and detail-oriented individual to support innovation in early drug discovery through data. As part of the Molecular Invention Data Product Team, this role will contribute to the analysis, documentation, testing, and improvement of data solutions that enable predictive and AI-informed research across Drug Discovery domains, including Molecular Invention (MI), Early Biology, and Preclinical Research.

    Responsibilities

    • Work with Research stakeholders to understand scientific data workflows, capture needs, and document business requirements with guidance from senior team members.
    • Translate scientific needs into clear user stories, acceptance criteria, process notes, and requirements for IT and engineering teams.
    • Support demand intake and analysis by mapping workflows, identifying friction points, and escalating risks or open questions to product and business analysis leads.
    • Represent researcher context in product discussions by sharing observations, clarifying use cases, and helping validate whether delivered capabilities meet defined needs.
    • Collaborate with Data Engineers to support data collection, testing, validation, issue tracking, and continuous improvement of data products.
    • Maintain field-level metadata, business glossaries, and documentation that support FAIR-aligned practices.
    • Support alignment of identifiers, terminology, and definitions across MI data sources to improve downstream integration and analytics.
    • Participate in stakeholder conversations, summarize feedback, clarify expectations, and help build trust in data product capabilities.
    • Stay aware of relevant industry practices and emerging approaches to scientific data challenges, sharing observations with the team as appropriate.
    • Communicate clearly with scientific and technical audiences, escalating ambiguity and summarizing decisions, risks, and follow-ups.
    • Demonstrate a growth mindset and ownership for developing business analysis, data literacy, AI/ML awareness, and Pharmaceutical R&D knowledge.

    Qualifications

    • B.S. or M.S. in a relevant life sciences, informatics, data, or technical discipline; advanced degree a plus.
    • Practical experience or strong academic grounding in early life sciences domains, with interest in Molecular Invention research areas such as Biologics, Sequencing, Protein Engineering, Antibody Discovery, Chemistry, or related fields.
    • Familiarity with Research workflows in pharmaceutical or biotech settings.
    • 2+ years of experience in IT, informatics, data analysis, business analysis, or a scientific data-focused role; relevant graduate research or internship experience may be considered.
    • Ability to collaborate effectively with scientific and technical teams while following established processes and seeking guidance when needed.
    • Analytical problem-solving skills with the ability to organize information, identify patterns, document issues, and recommend practical next steps.
    • Ability to learn new tools and adapt in a dynamic environment.
    • IIBA Certification or similar Business Analysis Certification is a plus.

    Skills

    • Strong commitment to a career in technology with a passion for healthcare.
    • Analytical thinker with strong communication and collaboration skills, able to effectively communicate complex ideas and concepts.
    • Good stakeholder engagement skills, with the ability to listen, ask clarifying questions, document needs, and build alignment in straightforward to moderately complex situations.
    • Curious problem-solver who contributes ideas for improving workflows, documentation, data quality, and user experience.
    • Familiarity with data product development, data modeling, data governance, analytics, or modern research data platforms.
    • We hire for skills and capabilities, not just credentials – if this role excites you, but doesn’t perfectly match your resume, we encourage you to apply anyway.

    Pay

    Compensation Overview: Cambridge Crossing: $83,680 - $101,404; Princeton - NJ - US: $76,080 - $92,185. The starting pay range(s) listed above is for full-time employees (FTE). You may also be eligible for additional discretionary incentive cash and stock opportunities. We determine starting pay thoughtfully – carefully considering the nature of the role, required skills, work location, schedule and the knowledge and experience you bring. Final compensation is guided by pay equity principles and applicable employment laws. Compensation programs are reviewed on an ongoing basis and may be adjusted over time to reflect evolving market factors, and individual, team or Company performance.

    Benefits

    Subject to the terms and conditions of the applicable plans then in effect, you may be eligible to participate in our comprehensive benefit plans – including wellbeing support, retirement and financial protection benefits, and insurance offerings (medical, dental, vision, life and disability). U.S.-based exempt employees are eligible for Flexible Time Off (FTO), which provides paid time off without a set accrual limit, subject to manager approval, along with 11 paid company holidays each year. Non-exempt employees, RayzeBio employees, and employees located in Puerto Rico receive 160 hours of paid vacation annually for new hires (subject to manager approval), 11 paid company holidays, and 3 optional holidays. Depending on eligibility, employees may also have access to additional time-off benefits, including paid sick leave, up to two paid volunteer days per year, summer hours flexibility, and leaves of absence for medical, personal, parental, caregiver, bereavement, or military needs. Eligible employees also enjoy an annual Global Shutdown between Christmas Day and New Year's Day. U.S.-based job seekers can explore full benefit offerings at https://careers.bms.com/benefits

    We should not include any extra sections like Schedule. No extra headings. Make sure no markdown fences. Output just HTML. Check that we didn't repeat job title as heading. Good. We included "About the role" with intro. Good. We preserved all substantive info: responsibilities, qualifications, skills, pay, benefits. We omitted "How We Work" but we could incorporate a sentence about work models into About the role? Might be considered substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not drop the "How We Work" paragraph. It's substantive. We need to include it somewhere. Since we don't have a heading for it, we could incorporate it into About the role paragraph as additional sentences. That would preserve the info without creating a new heading. Let's add a sentence after the intro: "Our roles are structured across four work models: site-essential, site-by-design, field-based and remote-by-design. The model assigned to this role is based on its core responsibilities. Learn more at https://careers.bms.com/ways-of-working." That preserves. Also we have a statement "We hire for skills and capabilities..." we already included in Skills list as a bullet. Good. We also have "Supporting People With Disabilities", "Candidate Rights", "Data Protection" etc which are boilerplate/legal; we should remove. Good. We also have "Visit careers.bms.com/eeo-accessibility" etc; remove. We also have "Any data processed..." etc; remove. We also have "If this posting is missing required information..." etc; remove. We also have "Do not send application-related inquiries to this email." etc; remove. We also have "To check your application status..." etc; remove. We also have "R1605714 : Discovery Research Domain Analyst, IT Business Analyst" at end; we can drop or put in a short p. Probably drop as minor metadata. Now ensure we didn't inadvertently include any boilerplate. Let's review the final HTML. We'll output:

    About the role

    At Bristol Myers Squibb, our employees often ask, “Who are you working for?”—a question that fuels collaboration, accountability, and urgency in our work. Our purpose-driven culture inspires us to discover, develop, and deliver innovative medicines to prevail over serious diseases. We offer uniquely interesting and meaningful work, opportunities for growth, and a supportive environment that values inclusion, wellbeing, flexibility, and comprehensive benefits. This is work that transforms the lives of patients, and the careers of those who do it. Bristol Myers Squibb is seeking a curious, collaborative, and detail-oriented individual to support innovation in early drug discovery through data. As part of the Molecular Invention Data Product Team, this role will contribute to the analysis, documentation, testing, and improvement of data solutions that enable predictive and AI-informed research across Drug Discovery domains, including Molecular Invention (MI), Early Biology