Open-Source Technology Lead
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate etc. Include a section only when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Intro paragraph: At Bristol Myers Squibb... This is work that transforms... (purpose-driven culture). That's about the role? Could be "About the role" or "About the company". We'll treat as "About the role" maybe.
- Key Responsibilities: bullet list of responsibilities (starting with "Own container management..." etc). We'll put under
Responsibilities
with - each.
- Qualifications & Experience: list of qualifications (Bachelor's..., 5+ years..., deep expertise..., etc). We'll put under
Qualifications
maybe also "Requirements". The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. The posting includes qualifications and experience; also skills (like communication, collaboration). Could combine qualifications and skills? But we should not create thin sections. Perhaps we can have "Qualifications" covering both qualifications and skills. Or separate "Requirements" for mandatory qualifications and "Skills" for preferred? However we need to avoid filler. The posting includes both required and preferred items. Could put all under "Qualifications". Or we could have "Requirements" for mandatory (Bachelor's, 5+ years, deep expertise, container management, package management, compliance knowledge) and "Skills" for preferred (multilingual/NLP, Pharmaverse, cloud platforms, data quality concepts, communication, etc). But we need to ensure we don't create sections with little content. Let's see content:
Mandatory (seems required):
- Bachelor's or Master's degree in CS, SE, Computational Linguistics, or related.
- 5+ years hands-on software engineering experience, including direct work with open source technologies and communities.
- Requires deep, hands-on technical expertise in both R and Python, including package/library development and dependency management in each.
- Strong, demonstrated experience with container management — Docker, Kubernetes, image build/scan/sign pipelines, and container registries — in production environments.
- Proven experience with open source package management tooling and workflows (e.g., CRAN/Posit Package Manager, PyPI/conda/pip, Artifactory, Nexus, JFrog).
- Solid working knowledge of open source compliance practices — license management (e.g., GPL, MIT, Apache), vulnerability/SBOM scanning, and governance frameworks.
Preferred/plus:
- Demonstrated experience with multilingual/NLP technologies, localization tooling, or text-processing frameworks (e.g., spaCy, Hugging Face, ICU, Apache OpenNLP) is a plus.
- Knowledge of Pharmaverse and an active presence in PHUSE or other open source life sciences communities is a plus.
- Experience with cloud platforms (AWS, Azure, or GCP) supporting containerized and open source workloads.
- Solid understanding of data quality, data governance, and data management concepts.
- Strong communication, collaboration, and stakeholder engagement skills.
- Ability to work independently and collaboratively in fast-paced, Agile environments.
- Prior exposure to Life Sciences Research & Development is a plus.
- Active contributor or maintainer on recognized open source projects is a plus.
Also note: "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." That's a note.
Compensation Overview: includes pay range: Princeton - NJ - US: $94,180 - $114,124. Also mentions additional discretionary incentive cash and stock opportunities. So we have Pay info.
Benefits: paragraph describing benefits: comprehensive benefit plans – wellbeing support, retirement, financial protection, insurance offerings (medical, dental, vision, life and disability). U.S.-based exempt employees eligible for Flexible Time Off (FTO) etc. Non-exempt employees etc. Also mention Global Shutdown, etc. So we have Benefits.
Schedule: Not explicitly mentioned. No schedule info. So we should NOT create a Schedule section.
We also have "How We Work" describing work models (site-essential, site-by-design, field-based, remote-by-design). That could be considered Schedule? But it's about work model, not schedule. The instruction says only create Schedule section if posting actually states them. It does not state schedule (like full-time, part-time, shift). So we skip Schedule.
We also have "Supporting People With Disabilities", "Candidate Rights", "Data Protection", etc. Those are boilerplate to remove.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all the responsibilities, qualifications, compensation, benefits details. Also the intro paragraph about purpose-driven culture.
We need to format as HTML fragment: use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to include: About the role (intro), Responsibilities, Qualifications (maybe combine qualifications and skills), Benefits, Pay. Possibly also "How We Work" as a section? Not in the allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "How We Work" to maybe "About the role" or "Qualifications"? Not ideal. Better to omit if not matching allowed headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings, but likely they want us to stick to those. However we could include a section like "Work Model" if needed, but not in list. Safer to stick to allowed headings.
Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements? But we have qualifications covering requirements. Could split: Requirements for mandatory, Qualifications for preferred? But that may create thin sections. Let's see if we can combine.
We have a lot of content for qualifications (both mandatory and preferred). Could put all under Qualifications. That would be a substantive section.
We could also have a Skills section for the soft skills (communication, collaboration, stakeholder engagement, ability to work independently, Agile). But those are also part of qualifications. Might be thin if separated.
Thus I'll produce sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive info: include the intro paragraph, responsibilities bullet list, qualifications bullet list (maybe separate mandatory and preferred but still within same ), benefits paragraph, compensation paragraph.
We must not repeat job title as heading. The job title is "Open-Source Technology Lead" (shown at end). We'll not use that as heading.
We must not put Job ID/requisition numbers as headings; we can drop them or fold into short . The posting ends with "R1605060 : Open-Source Technology Lead". We can drop that or include as a short
maybe as metadata. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can either drop it or include a short
. I'd drop it to keep minimal.
Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove sections like "How We Work", "Supporting People With Disabilities", "Candidate Rights", "Data Protection", etc. Also remove the note about "We hire for skills and capabilities..."? That is substantive? It's a note encouraging applicants; could be considered part of About the role? Might keep as prose in About the role.
We also need to remove duplicated lines: there may be none.
Now craft HTML.
Structure:
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. 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.
Responsibilities
- Own container management for open source multilingual and data-quality tooling — building, hardening, and maintaining Docker/Kubernetes images and deployment pipelines used by BI&T and Data and Quantitative Sciences (DQS) teams.
- Design and operate container orchestration and registry strategy (build, scan, sign, version, and promote images) to ensure secure, reproducible environments for open source components.
- Lead open source package management across the BI&T and DQS technology stack — evaluating, onboarding, versioning, and retiring R and Python packages/libraries in a controlled, auditable manner.
- Establish and maintain internal package repositories/mirrors (e.g., CRAN/Posit Package Manager, PyPI mirrors, Artifactory/Nexus) to manage dependencies, licensing, and version drift at scale.
- Drive open source compliance — license scanning, vulnerability management, SBOM generation, and policy enforcement — partnering with Legal, IT Security, and Open Source Governance stakeholders.
- Define and enforce open source intake, approval, and risk-assessment processes so new packages and containers meet BMS security, licensing, and quality standards before adoption.
- Apply deep technical expertise in R and Python to design, build, and optimize production-quality code, libraries, and tooling supporting multilingual data processing, validation, and quality-control workflows.
- Contribute code, documentation, and improvements upstream to relevant open source projects, building BMS's presence within the open source ecosystem.
- Partner directly with DQS engineering and data teams to embed containerized, compliant open source tooling into multilingual data quality pipelines and automation.
- Track the open source landscape for emerging multilingual, NLP, container, and package-management technologies, and recommend adoption where it advances DQS priorities.
- Represent BMS within Pharmaverse, PHUSE, and other relevant open source life sciences communities — engaging with working groups, contributing to community initiatives, and bringing external best practices back into DQS.
- Mentor engineers and analysts on container best practices, open source package management, and compliance-by-design principles.
Qualifications
- Bachelor's
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate etc. Include a section only when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Intro paragraph: At Bristol Myers Squibb... This is work that transforms... (purpose-driven culture). That's about the role? Could be "About the role" or "About the company". We'll treat as "About the role" maybe. - Key Responsibilities: bullet list of responsibilities (starting with "Own container management..." etc). We'll put under
Responsibilities
with- each.
- Qualifications & Experience: list of qualifications (Bachelor's..., 5+ years..., deep expertise..., etc). We'll put under
Qualifications
maybe also "Requirements". The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. The posting includes qualifications and experience; also skills (like communication, collaboration). Could combine qualifications and skills? But we should not create thin sections. Perhaps we can have "Qualifications" covering both qualifications and skills. Or separate "Requirements" for mandatory qualifications and "Skills" for preferred? However we need to avoid filler. The posting includes both required and preferred items. Could put all under "Qualifications". Or we could have "Requirements" for mandatory (Bachelor's, 5+ years, deep expertise, container management, package management, compliance knowledge) and "Skills" for preferred (multilingual/NLP, Pharmaverse, cloud platforms, data quality concepts, communication, etc). But we need to ensure we don't create sections with little content. Let's see content: Mandatory (seems required): - Bachelor's or Master's degree in CS, SE, Computational Linguistics, or related. - 5+ years hands-on software engineering experience, including direct work with open source technologies and communities. - Requires deep, hands-on technical expertise in both R and Python, including package/library development and dependency management in each. - Strong, demonstrated experience with container management — Docker, Kubernetes, image build/scan/sign pipelines, and container registries — in production environments. - Proven experience with open source package management tooling and workflows (e.g., CRAN/Posit Package Manager, PyPI/conda/pip, Artifactory, Nexus, JFrog). - Solid working knowledge of open source compliance practices — license management (e.g., GPL, MIT, Apache), vulnerability/SBOM scanning, and governance frameworks. Preferred/plus: - Demonstrated experience with multilingual/NLP technologies, localization tooling, or text-processing frameworks (e.g., spaCy, Hugging Face, ICU, Apache OpenNLP) is a plus. - Knowledge of Pharmaverse and an active presence in PHUSE or other open source life sciences communities is a plus. - Experience with cloud platforms (AWS, Azure, or GCP) supporting containerized and open source workloads. - Solid understanding of data quality, data governance, and data management concepts. - Strong communication, collaboration, and stakeholder engagement skills. - Ability to work independently and collaboratively in fast-paced, Agile environments. - Prior exposure to Life Sciences Research & Development is a plus. - Active contributor or maintainer on recognized open source projects is a plus. Also note: "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." That's a note. Compensation Overview: includes pay range: Princeton - NJ - US: $94,180 - $114,124. Also mentions additional discretionary incentive cash and stock opportunities. So we have Pay info. Benefits: paragraph describing benefits: comprehensive benefit plans – wellbeing support, retirement, financial protection, insurance offerings (medical, dental, vision, life and disability). U.S.-based exempt employees eligible for Flexible Time Off (FTO) etc. Non-exempt employees etc. Also mention Global Shutdown, etc. So we have Benefits. Schedule: Not explicitly mentioned. No schedule info. So we should NOT create a Schedule section. We also have "How We Work" describing work models (site-essential, site-by-design, field-based, remote-by-design). That could be considered Schedule? But it's about work model, not schedule. The instruction says only create Schedule section if posting actually states them. It does not state schedule (like full-time, part-time, shift). So we skip Schedule. We also have "Supporting People With Disabilities", "Candidate Rights", "Data Protection", etc. Those are boilerplate to remove. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all the responsibilities, qualifications, compensation, benefits details. Also the intro paragraph about purpose-driven culture. We need to format as HTML fragment: usefor section headings. Use
- for any list of duties/requirements/benefits. Use
for prose. We need to decide which sections to include: About the role (intro), Responsibilities, Qualifications (maybe combine qualifications and skills), Benefits, Pay. Possibly also "How We Work" as a section? Not in the allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "How We Work" to maybe "About the role" or "Qualifications"? Not ideal. Better to omit if not matching allowed headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings, but likely they want us to stick to those. However we could include a section like "Work Model" if needed, but not in list. Safer to stick to allowed headings. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements? But we have qualifications covering requirements. Could split: Requirements for mandatory, Qualifications for preferred? But that may create thin sections. Let's see if we can combine. We have a lot of content for qualifications (both mandatory and preferred). Could put all under Qualifications. That would be a substantive section. We could also have a Skills section for the soft skills (communication, collaboration, stakeholder engagement, ability to work independently, Agile). But those are also part of qualifications. Might be thin if separated. Thus I'll produce sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive info: include the intro paragraph, responsibilities bullet list, qualifications bullet list (maybe separate mandatory and preferred but still within same
- ), benefits paragraph, compensation paragraph.
We must not repeat job title as heading. The job title is "Open-Source Technology Lead" (shown at end). We'll not use that as heading.
We must not put Job ID/requisition numbers as headings; we can drop them or fold into short
- Own container management for open source multilingual and data-quality tooling — building, hardening, and maintaining Docker/Kubernetes images and deployment pipelines used by BI&T and Data and Quantitative Sciences (DQS) teams.
- Design and operate container orchestration and registry strategy (build, scan, sign, version, and promote images) to ensure secure, reproducible environments for open source components.
- Lead open source package management across the BI&T and DQS technology stack — evaluating, onboarding, versioning, and retiring R and Python packages/libraries in a controlled, auditable manner.
- Establish and maintain internal package repositories/mirrors (e.g., CRAN/Posit Package Manager, PyPI mirrors, Artifactory/Nexus) to manage dependencies, licensing, and version drift at scale.
- Drive open source compliance — license scanning, vulnerability management, SBOM generation, and policy enforcement — partnering with Legal, IT Security, and Open Source Governance stakeholders.
- Define and enforce open source intake, approval, and risk-assessment processes so new packages and containers meet BMS security, licensing, and quality standards before adoption.
- Apply deep technical expertise in R and Python to design, build, and optimize production-quality code, libraries, and tooling supporting multilingual data processing, validation, and quality-control workflows.
- Contribute code, documentation, and improvements upstream to relevant open source projects, building BMS's presence within the open source ecosystem.
- Partner directly with DQS engineering and data teams to embed containerized, compliant open source tooling into multilingual data quality pipelines and automation.
- Track the open source landscape for emerging multilingual, NLP, container, and package-management technologies, and recommend adoption where it advances DQS priorities.
- Represent BMS within Pharmaverse, PHUSE, and other relevant open source life sciences communities — engaging with working groups, contributing to community initiatives, and bringing external best practices back into DQS.
- Mentor engineers and analysts on container best practices, open source package management, and compliance-by-design principles.
- Bachelor's
. The posting ends with "R1605060 : Open-Source Technology Lead". We can drop that or include as a short
maybe as metadata. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can either drop it or include a short
. I'd drop it to keep minimal. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove sections like "How We Work", "Supporting People With Disabilities", "Candidate Rights", "Data Protection", etc. Also remove the note about "We hire for skills and capabilities..."? That is substantive? It's a note encouraging applicants; could be considered part of About the role? Might keep as prose in About the role. We also need to remove duplicated lines: there may be none. Now craft HTML. Structure:
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. 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.
Responsibilities
Qualifications
- for any list of duties/requirements/benefits. Use