DirectJobHub
Jobs · Analyst · Ohio

Director, Bioprocess Development (Biologics Research)

BioSpace · New Hampshire, OH · 3 wk ago
On-siteAnalystFull-time
We need to output HTML fragment with sections: About the role (maybe "About The Role" heading), Responsibilities (maybe "What You'll Do" content), Requirements (maybe "Who You Are"), Benefits (maybe "Highlights Of Our U.S. Offerings Include"), Pay (maybe "Pay Range" but not given actual range; they said "Pay Range" heading but no actual range; we should not create Pay section unless posting actually states them. The posting says "Pay Range" but no actual numbers. It says "Pay Range" heading but no content. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Since no actual range given, we should not include Pay section. Schedule: they mention "full-time, in-person presence" and "Travel Requirements Minimal travel expected". That's schedule info? Could be considered schedule. The rule: include a section only when posting has real, specific content for it. They have "full-time, in-person presence" and "Travel Requirements Minimal travel expected". That's specific enough for Schedule? Might be considered schedule. But they didn't give hours. Could still include Schedule section with that info. Benefits: they have "Highlights Of Our U.S. Offerings Include ..." which is benefits. So include Benefits section. We need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use appropriate headings. We should not repeat job title as heading. No Job ID. We need to preserve all substantive information; remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions, cookie/navigation/legal etc. We need to output only HTML fragment. Let's extract content: Intro paragraph: "At Insmed, every moment and every patient counts — and so does every person who joins in. As a global biopharmaceutical company dedicated to transforming the lives of patients with serious and rare diseases, you’ll be part of a community that prioritizes the human experience, celebrates curiosity, and values every person’s contributions to meaningful progress. That commitment has earned us recognition as Science magazine’s No. 1 Top Employer for five consecutive years, certification as a Great Place to Work® in the U.S., and a place on The Sunday Times Best Places to Work list in the UK. For patients, for each other, and for the future of science, we’re in. Are you?" This is introductory fluff; we can keep as

maybe under a generic intro? Not a heading. Probably we can keep as opening paragraph before sections. Then "About The Role" heading? The posting says "About The Role". We'll use

About The Role

. Then content: "What You'll Do: Role In this role, you’ll have the opportunity to
  • . The content includes sentences; we can keep them as list items. We need to preserve all substantive info; we should not lose any details. Let's extract each bullet: Team Leadership & Organizational Build: - Build, lead, and mentor a high-performing research bioprocess development team - Establish a collaborative, accountable, and scientifically rigorous team culture - Set priorities and allocate resources across multiple concurrent programs Laboratory & Capability Development: - Design and oversee the buildout of new state-of-the-art research bioprocess development laboratories - Define equipment strategy and select platforms for upstream processing (USP): microbial and mammalian expression systems, as well as downstream processing (DSP): purification workflows including chromatography and filtration - Implement scalable, fit-for-purpose technologies aligned with early-stage and preclinical needs Technical Leadership (Upstream & Downstream): - Provide subject matter expertise in recombinant protein expression in bacterial and mammalian systems, cell culture process development, media optimization, scale-up strategies, and protein purification processes including flocculation, tangential flow and depth filtration, buffer exchange, and affinity, ion exchange, and mixed mode chromatography - Drive development of robust, reproducible processes suitable for preclinical material generation - Establish platform approaches and best practices for rapid program advancement Hands-On Execution: - Contribute directly to experimental design, experimentation, troubleshooting, and data interpretation - Lead or support critical experiments, especially during early lab setup and high-priority programs - Develop and review protocols, reports, and technical documentation Program Support & Cross-Functional Collaboration: - Partner closely with Discovery, Analytical, Technical Operations, and Preclinical Development teams - Support multiple biologics programs across modalities (e.g., enzymes, antibodies, fusion proteins) - Ensure alignment of bioprocess strategies with program timelines and CMC expectations - Provide input into candidate selection based on developability and manufacturability CMC & Preclinical Development Interface: - Establish processes and documentation to support transition into formal CMC development - Collaborate with external partners or internal CMC teams for tech transfer and scale-up - Ensure early processes are designed with downstream manufacturability in mind Now "Who You Are" section: heading maybe

    Who You Are

    or

    Requirements

    . According to allowed headings list includes Requirements, Qualifications, Skills. We'll use Requirements. Content: "You have a PhD in chemical engineering, biochemical engineering, biology, or related field with 5+ years of industry experience, or M.S. with 8+ years of industry experience. You are or you also have:" then list. List items: - Demonstrated experience in biologics process development within biotech or pharmaceutical settings. - Deep experience in both upstream and downstream bioprocess development. - Expertise in early- to late-stage preclinical CMC for biotherapeutic development candidates. - Hands-on experience with microbial expression systems (specific expertise with E. coli), mammalian expression systems, optimization of bioreactor operations (bench-scale; scale-up knowledge preferred), optimization of protein purification and characterization workflows (with knowledge of scalable processes), and construction and optimization of commercial expression strains (both microbial and mammalian) - Successful track record of tech transfer to technical operations groups and/or CDMOs. - A builder’s mindset with the ability to create structure while maintaining agility and willingness to be hands-on while operating at a strategic level. - Passion for developing people and advancing innovative biologics programs. - Proven track record of building and leading teams and/or functional groups. - Strong leadership and mentoring skills - Experience managing multiple programs in a fast-paced, research-driven environment - Excellent communication and cross-functional collaboration abilities Then "Nice To Have (but Not Required)" maybe as Skills? Could be a subsection but we can include as list under Requirements or separate Skills heading. Since we have Skills heading allowed, we could put Nice To Have under Skills. But we need to avoid filler. It's substantive. We'll create

    Skills

    and list nice-to-have items. Nice To Have: - Experience building laboratories and selecting capital equipment - Exposure to early GMP considerations - Familiarity with a range of biologic modalities (e.g., enzymes, mAbs, bispecifics, engineered proteins, half-life extension technologies) Now "Where You’ll Work": heading maybe Schedule? Actually it's location and work arrangement. Could be Schedule? But we have Schedule heading for full-time, in-person presence and travel. We'll put that under Schedule. Content: "This role is based out of our Lebanon, NH office and requires full-time, in-person presence to support hands-on collaboration, access specialized equipment, and/or operational needs. Travel Requirements Minimal travel expected" We can put as

    under Schedule heading. Now Benefits: "Highlights Of Our U.S. Offerings Include Comprehensive medical, dental, and vision coverage and mental health support, annual wellbeing reimbursement, and access to our Employee Assistance Program (EAP) Generous paid time off policies, fertility and family-forming benefits, caregiver support, and flexible work schedules with purposeful in-person collaboration 401(k) plan with a competitive company match, annual equity awards, and participation in our Employee Stock Purchase Plan (ESPP), and company-paid life and disability insurance Company Learning Institute providing access to LinkedIn Learning, skill building workshops, leadership programs, mentorship connections, and networking opportunities Employee resource groups, service and recognition programs, and meaningful opportunities to connect, volunteer, and give back Eligibility for specific programs may vary and is subject to the terms and conditions of each plan." We need to format as list maybe. We'll create

    • for each benefit item. But the paragraph is a run-on; we can split by sentences. Let's split: - Comprehensive medical, dental, and vision coverage and mental health support, annual wellbeing reimbursement, and access to our Employee Assistance Program (EAP) - Generous paid time off policies, fertility and family-forming benefits, caregiver support, and flexible work schedules with purposeful in-person collaboration - 401(k) plan with a competitive company match, annual equity awards, and participation in our Employee Stock Purchase Plan (ESPP), and company-paid life and disability insurance - Company Learning Institute providing access to LinkedIn Learning, skill building workshops, leadership programs, mentorship connections, and networking opportunities - Employee resource groups, service and recognition programs, and meaningful opportunities to connect, volunteer, and give back - Eligibility for specific programs may vary and is subject to the terms and conditions of each plan. Now we need to exclude boilerplate: EEO, legal, etc. Remove all that after "Eligibility for specific programs may vary..." Actually that line is part of benefits; we keep it. After that there is "Current Insmed Employees: Please apply via the Jobs Hub in Workday." That's application instruction; remove. Then "Insmed Incorporated is an Equal Opportunity employer..." etc. Remove all EEO/legal. Also remove "Unsolicited resumes from agencies..." etc. Remove all that. Now we need to ensure we didn't miss any substantive content like "Life at Insmed" heading. That's just fluff; we can keep as part of benefits intro maybe. The paragraph "Life at Insmed At Insmed, you’ll find a culture as human as our mission—intentionally designed for the people behind it. You deserve a workplace that reflects the same care you bring to your work each day, with support for how you work, how you grow, and how you show up for patients, your team, and yourself." This is descriptive; we could include as a

      before Benefits heading or as part of Benefits intro. Since we have Benefits heading, we can put that as a

      before the list. Now we need to output only HTML fragment. Structure:

      Intro paragraph (the first big paragraph).

      About The Role

      What You'll Do: Role In this role, you’ll have the opportunity to play a critical role in establishing a high-performing team and state-of-the-art laboratories to support a diverse pipeline of biotherapeutic programs from early discovery through preclinical CMC. You’ll also:

      Then maybe we can combine the bullet groups under one
        with headings? But spec says use
        • for any list of duties/requirements/benefits. It doesn't forbid headings inside list? Probably better to have separate
            for each functional area with a preceding

            heading? But they said use

            for section headings. So we could have subheadings like

            but not allowed? Only h3 for section headings. Could use

            bold? Not allowed. We could just make one big list with all duties; but that loses grouping. However spec didn't forbid grouping via headings inside list? Might be okay to have

            for each subsection? But they said use

            for section headings (e.g. About the

    • Similar jobs