Director, Bioconjugation
Bristol Myers Squibb · Cambridge, MA · 3 wk ago
On-siteOTHR$247k–$299k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. Must not repeat job title as heading. Must not include Job ID/requisition numbers as headings. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes compensation overview with pay range, and benefits description. So we can include Pay and Benefits sections. Schedule? Not mentioned. So we should not include Schedule. Also maybe "About the role" corresponds to Position Summary. "Responsibilities" corresponds to Key Responsibilities. "Qualifications" maybe combine Qualifications & Experience and Preferred Qualification? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to include based on content. There's "Qualifications & Experience" and "Preferred Qualification". Could map to Qualifications. There's no explicit Skills section but we could embed skills within Qualifications or maybe create Skills heading if there is skill content. The posting includes many skill-like items: hands-on expertise, ability to interpret data, communication, etc. Could create a Skills section. However we must not create sections unless posting has real specific content for it. There is skill content, so we could include Skills. But we also have Qualifications. Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. But they gave examples of possible headings; we can choose which to use. Let's think: The posting includes "Qualifications & Experience" and "Preferred Qualification". That's qualifications. It also includes skill-like items (hands-on expertise, ability to interpret data, communication). Those could be part of qualifications. So we can have a single Qualifications section covering both required and preferred. Then we have About the role (Position Summary). Responsibilities (Key Responsibilities). Benefits (Benefits). Pay (Compensation Overview). No Schedule. No Requirements separate (maybe covered in Qualifications). So we will output:
items.
Qualifications: combine required and preferred.
Required qualifications (from Qualifications & Experience):
- Bachelor's Degree 15+ years of academic / industry experience OR Master's Degree 12+ years of academic / industry experience OR PhD 8+ years of academic / industry experience
- 6+ years of leadership experience
- Degree in organic chemistry, medicinal chemistry, chemical biology, biochemistry, bioengineering, or a related scientific discipline.
- Deep, hands-on expertise in bioconjugation chemistry cysteine and lysine conjugation, site-specific and enzymatic conjugation (e.g., transglutaminase, sortase, engineered tags), click and bioorthogonal chemistry, and linker design (cleavable and non-cleavable).
- Demonstrated hands-on experience with cytotoxic small molecule ADCs, plus direct experience with antibody–RNA/oligonucleotide conjugates, and working familiarity with degrader-antibody and dual-payload architectures.
- Direct experience with highly potent small molecule payload classes (e.g., topoisomerase I inhibitors, auristatins/maytansinoids, or comparable), including safe handling and containment requirements.
- Demonstrated program leadership track record of leading discovery programs and setting program strategy, with candidates advanced to nomination or into clinical development.
- Ability to interpret and evaluate conjugate analytical data (RP-HPLC, SEC, HIC, IEX, LC-MS/HRMS, CE-SDS).
- Excellent written and verbal communication; proven ability to influence senior stakeholders and drive alignment across functions.
Preferred Qualification (list):
- 8+ years of progressive leadership experience, including direct experience as the bioconjugation lead on discovery project teams, with a proven track record of advancing bioconjugate therapeutics from concept through development candidate nomination.
- Depth in oligonucleotide therapeutics (siRNA, ASO) applied to conjugates oligo design and chemical modification, conjugate purification, analytical characterization, and the delivery/PK considerations specific to antibody–RNA conjugates.
- Hands on experience with glycan-mediated bioconjugation platforms.
- Targeted protein degradation experience and the specific challenges of conjugating and delivering degrader payloads.
- Experience with dual-payload or multi-payload conjugate design and the orthogonal conjugation strategies it requires.
- CMC and tech-transfer exposure; experience supporting IND-enabling packages for conjugate modalities.
- Experience with high-throughput/automated conjugation
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. Must not repeat job title as heading. Must not include Job ID/requisition numbers as headings. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes compensation overview with pay range, and benefits description. So we can include Pay and Benefits sections. Schedule? Not mentioned. So we should not include Schedule. Also maybe "About the role" corresponds to Position Summary. "Responsibilities" corresponds to Key Responsibilities. "Qualifications" maybe combine Qualifications & Experience and Preferred Qualification? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to include based on content. There's "Qualifications & Experience" and "Preferred Qualification". Could map to Qualifications. There's no explicit Skills section but we could embed skills within Qualifications or maybe create Skills heading if there is skill content. The posting includes many skill-like items: hands-on expertise, ability to interpret data, communication, etc. Could create a Skills section. However we must not create sections unless posting has real specific content for it. There is skill content, so we could include Skills. But we also have Qualifications. Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. But they gave examples of possible headings; we can choose which to use. Let's think: The posting includes "Qualifications & Experience" and "Preferred Qualification". That's qualifications. It also includes skill-like items (hands-on expertise, ability to interpret data, communication). Those could be part of qualifications. So we can have a single Qualifications section covering both required and preferred. Then we have About the role (Position Summary). Responsibilities (Key Responsibilities). Benefits (Benefits). Pay (Compensation Overview). No Schedule. No Requirements separate (maybe covered in Qualifications). So we will output:
About the role
...position summary...
Responsibilities
- ... each responsibility...
Qualifications
... required qualifications ...
- ... preferred qualifications ...