Jobs · Engineering · Indiana

Program Manager / Project Manager

Genezen · Fishers, IN · 3 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role? The posting includes a job summary, essential functions, special job requirements, knowledge, skills and experience (education, on-the-job experience, skills/abilities), physical demands, Genezen's cures value-based competencies (maybe not needed), benefits, additional details (but we should drop boilerplate like EEO, legal, etc). We need to include sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have job summary: could be About the role. Responsibilities: essential job functions list. Requirements: special job requirements? Or maybe "Requirements" includes special job requirements and knowledge/skills/experience? But we have separate headings for Qualifications, Skills. We need to decide. We have Education/Certifications/Licenses, On-the-job experience, Skills/Abilities. Could map Education/Certifications to Qualifications, Skills/Abilities to Skills, On-the-job experience maybe to Requirements? Or combine. We also have Physical Demands - maybe not a standard heading; we could include under Requirements or Qualifications? But we must only use allowed headings. Could we add a section for Physical Demands? Not allowed. So we need to either drop it or incorporate into another section (maybe Requirements). The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. Likely we should only use those headings. So we need to map content to those sections. We have no explicit Pay or Schedule info. There's mention: "Adaptability required as work schedule may change based on business needs, including flexibility for different time zones" under Special Job Requirements. That's schedule info. So we can include Schedule section with that detail. Pay: not mentioned, so we should not include Pay section. Benefits: we have a list of benefits. So Benefits section. About the role: job summary paragraph. Responsibilities: essential job functions list. Requirements: maybe special job requirements + physical demands? Could also include education? But we have Qualifications for education/certifications. Skills for skills/abilities. So Requirements could be special job requirements (adaptability, background check, other duties) and maybe physical demands. Qualifications: education/certifications/licenses (BS degree essential, life sciences desired, PMP desired). Skills: skills/abilities (MS Office Suite, MS Project, etc). Also maybe include on-the-job experience? Could be part of Qualifications? But we have separate On-the-job experience; maybe we put that under Qualifications as well (experience). However Qualifications heading is for education/certifications/licenses; but we can include experience there as part of qualifications. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid adding other headings? It says use those for section headings; likely we should stick to those. So we need to fit all content into those sections. Thus: - About the role: job summary paragraph. - Responsibilities: essential job functions (list). - Requirements: special job requirements + physical demands (maybe also on-the-job experience? but we can put experience under Qualifications). Let's put special job requirements and physical demands under Requirements. - Qualifications: education/certifications/licenses + on-the-job experience (3+ years project management, 1-2 years lab experience). Also maybe desired PMP. - Skills: skills/abilities (MS Office Suite, MS Project, etc). Also maybe include knowledge of project management methodologies? Not listed. - Benefits: list. - Schedule: adaptability/flexibility for different time zones (from special job requirements). Could also mention work schedule may change. We should not repeat job title. No metadata like Job ID. We must remove boilerplate: EEO, EVerify, visa sponsorship, locations description? The location description is additional details but not boilerplate; it's about locations. Should we keep? It's not a standard heading; we could maybe drop it as it's not required. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Location description is not boilerplate; but it's not under any allowed heading. Could we incorporate into About the role? Maybe not needed. Safer to drop it because we have no heading for location. However we could include under About the role as extra detail? But that might be considered adding content not under headings? The instruction says output ONLY the HTML fragment; we can include paragraphs under headings. So we could add a paragraph about locations under About the role or maybe under Responsibilities? But it's not about role. Probably better to omit location description as it's not essential to job description? But it's substantive info about where job is located. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep location info. But we have no heading for location; we could put it under About the role as a paragraph after job summary. That seems acceptable: About the role can include summary and location. Similarly, the "GENEZEN'S CURES VALUE-BASED COMPETENCIES" is maybe not needed; could be omitted as not under headings. It's substantive but maybe considered fluff? It's core values; could be included under About the role? But we have no heading for values. Might be considered boilerplate? Not exactly. But we could drop it as it's not required headings. However instruction says preserve ALL substantive information; we should keep it. Could we put under About the role? Might be okay. But we need to avoid creating sections with filler text. We'll only create sections when we have real content. Thus final HTML:

About the role

The Program Manager supports client programs through Process Development and into GMP Manufacturing of gene therapy viral vectors. The PM is well-versed in contract clinical manufacturing and effectively delivering client projects in a fast-paced environment. The Program Manager will act as the primary contact between clients, Genezen project team members, and functional groups to track progress and ensure the delivery of quality products and services. They will be responsible for developing, tracking, and reporting on the projects. They will effectively monitor and present project updates to relevant stakeholders, clients, and project team members. Genezen operates two locations: one in Fishers, Indiana and the second in Lexington, Massachusetts. Fishers is a suburb of Indianapolis and was named the #1 place to live in the US by Money Magazine in 2017 for its livability, safety and entrepreneurship. Lexington, Massachusetts, located just northwest of Boston, is renowned as a historic suburb with a rich cultural heritage, picturesque New England charm, tree-lined streets, and a vibrant community.

Responsibilities

  • Deliver client satisfaction through timely, effective communication and facilitation of expectations with stakeholders
  • Prepare detailed project schedules, including identification of major milestones for overseeing, controlling, communicating, and managing all activities required to complete client projects
  • Monitor projects and help resolve issues or escalate appropriately to ensure on time delivery of all milestones and help identify risk mitigation plans
  • Organize, set agenda for, and lead meetings with clients and internal teams to facilitate project completion
  • Ensure that project deliverables are client focused, results oriented, performance driven, and in compliance with all applicable internal and external requirements
  • Deliver project status updates to team members and clients during all stages of the project, manage expectations, and escalate risk immediately
  • Build strong relationships with clients and collaborate with business development to obtain new business opportunities from existing clients
  • Monitor project costs and prepare regular project updates with management and clients
  • Support company financial goals and objectives by supporting forecasting processes, assuring timely invoicing of project milestones, and supporting finance department in resolving disputes related to accounts receivable from clients
  • Identify appropriate applications and methods in managing projects
  • Proactively suggest improvements to existing processes and think creatively to promote new ideas that will benefit the team and our overall efforts

Requirements

  • Adaptability required as work schedule may change based on business needs, including flexibility for different time zones
  • Criminal background check required
  • Other duties as assigned
  • Physical demands: regularly sit for long periods; repeated hand movements, typing, use of keyboard and mouse; frequently required to stand; sit; use hands to finger, handle, or feel; reach with hands and arms; occasionally required to walk; climb or balance; and stoop, kneel, crouch, or crawl; frequently lift and/or move up to 10 pounds; occasionally lift and/or move up to 25 pounds; frequently utilize close vision and ability to adjust focus; frequently required to communicate by talking, hearing, using telephone and e-mail

Qualifications

  • BS degree in scientific field (Essential)
  • BS degree in life sciences (Desired)
  • PMP training or certification (Desired)
  • 3+ years of experience effectively managing projects in pharmaceutical or biotech company, CDMO, CRO, or related experience (Essential)
  • 1-2 years of life science laboratory experience, especially cell culture, molecular biology, virology (Desired)

Skills

  • Proficient in MS Office Suite, including MS Project or similar project management software (Essential)

Benefits

  • Paid vacation days, amount based on tenure
  • Paid sick time
  • 10 observed holidays + 2 floating holiday + 1 volunteer day
  • 401(k) plan with company match up to 6% of salary
  • Share Appreciation Rights
  • Choice of several healthcare plans
  • FSA and HSA programs
  • Dental & vision care
  • Employer-paid basic term life/personal accident insurance
  • Voluntary disability, universal life/personal accident insurance
  • Accidental Death & Dismemberment (AD&D) Insurance

Schedule

Work schedule may change based on business needs, requiring flexibility for different time zones.

We need to ensure we didn't include Pay section (none). Also we didn't include any empty sections. Check for any duplicated lines: we have adaptability mentioned both in Requirements and Schedule; but that's okay as it's not duplicated exactly; we have it in Requirements as a bullet and Schedule as a paragraph. Might be considered duplication but it's okay because it's in different sections. Could we remove from Requirements? The special job requirements include adaptability and background check and other duties. We could keep adaptability only under Schedule and keep background check and other duties under Requirements. But the instruction: "Preserve ALL substantive information". If we remove adaptability from Requirements, we still have it under Schedule, so it's preserved. So we can remove adaptability from Requirements to avoid duplication. Let's do that. Thus Requirements bullet list: criminal background check required; other duties as assigned; physical demands details. Now check that we didn't miss any substantive info: The "GENEZEN'S CURES VALUE-BASED COMPETENCIES" we omitted. That's substantive but maybe considered fluff; but we could incorporate into About the role as a sentence. Let's add a paragraph after location: "Genezen's core values include

Similar jobs