Jobs · Analyst

Medical Science Liaison - LA, TX, OK, MS, AL

Pharmacosmos Therapeutics Inc. · San Francisco, CA · 1 mo ago
RemoteRemoteAnalystFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to extract content: The posting includes About Us (company description) but not necessarily a section heading. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We need to preserve all substantive information, remove boilerplate etc. We need to decide which sections to include. We have: - About Us (company description) could be considered "About the role"? Actually "About the role" is a typical heading describing the job purpose. The posting includes "Job Purpose" section describing MSL role. So we can map that to "About the role". Use

About the role

and then

with the job purpose text. - Duties And Responsibilities: we can map to

Responsibilities

with
  • items. - Education & Professional Background: could be "Requirements" or "Qualifications". The posting includes Education & Professional Background (doctoral degree, experience, etc.) plus Competencies, Attitude And Behavior. Could combine into Requirements and Qualifications? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include based on content. We have: - Education & Professional Background (doctoral degree, 1-2 years experience, proven experience building KOL relationships, previous experience in Hematology/Oncology preferred, knowledge of PhRMA/OIG/ICH-GCP, understanding of clinical development process). That's qualifications/requirements. - Competencies (Leadership, Customer-oriented, Excellent communication skills, Responsible, Transparency, Accountability, Ability to act locally...). That's skills/competencies. - Attitude And Behavior (list of traits). Could be also skills or qualifications. - Flexibility (reasonable flexibility). Could be part of responsibilities? Not needed. - Additional Information: budgetary responsibilities, traveling 65%, eligible for Cash Bonus, LTIP, hybrid work schedule (Morristown NJ offices + remote). That's benefits/pay/schedule. We have mention of Cash Bonus and LTIP (Long Term Incentive Plan) – that's compensation/benefits. Also hybrid work schedule – schedule. We need to include Benefits section if there is real specific content: we have "This position is eligible for Cash Bonus" and "This position is eligible for LTIP (Long Term Incentive Plan)". Also maybe "hybrid work schedule" could be schedule. Pay: Not explicitly stated salary range, so we should NOT create Pay section because no specific pay info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: we have eligibility for cash bonus and LTIP – that is a benefit. So we can include Benefits section. Schedule: hybrid work schedule described: "Pharmacosmos Therapeutics Inc. has adopted a hybrid work schedule – a combination of being on-site at our Morristown, NJ offices along with remote working." That's schedule info. So we can include Schedule section. Pay: no specific salary, so omit. Now we need to decide on Requirements vs Qualifications vs Skills. The posting includes Education & Professional Background (requirements), Competencies (skills), Attitude And Behavior (maybe also skills). We could combine into Requirements (education/experience) and Qualifications (maybe same). But we need to avoid thin sections. Perhaps we can have: - Requirements (education, experience, knowledge) - Skills (competencies, attitude/behavior) But we also have "Qualifications" heading possible. Could we use both Requirements and Qualifications? Might be redundant. Better to have Requirements (education/experience) and Skills (competencies/attitude). The instruction says we can use those headings; we just need to include sections only when posting has real specific content. Thus:

    About the role

    Job Purpose text...

    Responsibilities

    • ... each duty

    Requirements

    Education & Professional Background bullet points? Could be list.

    maybe
    • Doctoral degree in health sciences (PharmD, DNP, MD, PhD)
    • etc.

      Skills

      • Leadership – ethical, ambitious, focused, organized
      • ... etc plus Attitude And Behavior items.

        Benefits

        • Eligible for Cash Bonus
        • Eligible for LTIP (Long Term Incentive Plan)

        Schedule

        Hybrid work schedule: combination of on-site at Morristown, NJ offices and remote working.

        We must not include About Us company description? The instruction says we should not repeat job title as heading; but we can include About the role (job purpose). The About Us company description could be considered boilerplate? It's not a standard heading but could be considered "About the company". Not in list of allowed headings. Should we include it? The instruction: Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings if needed, but better to stick to those. The About Us description is substantive but not a standard heading; we could incorporate it into About the role? But About the role is about the job purpose, not company. However we could treat About Us as part of About the role? Might be okay to include a brief paragraph about company under About the role? But the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Perhaps we can include a

        after About the role heading that includes both job purpose and company overview? Or we could add a separate heading like "About the company" but not in list; risk of violating instruction? The instruction says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can use other headings if needed, but better to follow examples. However we could embed the About Us description in a

        under About the role heading, as it's still about the role context. That would preserve info. Thus:

        About the role

        The Medical Science Liaison (MSL) is a field-based scientific professional who serves as an extension of the Medical Affairs organization. ... (job purpose).

        About Us: We are a global, family-owned company driven by a passion for innovation. Building on our foundational expertise in carbohydrate chemistry and cell cycle biology, we develop innovative treatments for unmet patient needs, with a focus on iron metabolism and blood-related disorders. With 700+ employees across the UK, Ireland, the Nordics, Germany, and the USA, we are committed to scientific excellence, patient care, and collaborative partnerships with the medical community. Our Core Values Define Who We Are ... (maybe we can trim some but preserve all). However we need to preserve ALL substantive information; we cannot summarize away detail. So we need to include the entire About Us paragraph and Core Values etc. That's a lot of text. But we can include it as a paragraph; it's okay. But we must remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Us includes core values etc. That's substantive. We need to ensure we don't include EEO statements at the end (the long equal opportunity statement). That is boilerplate; we should remove it. Also remove "All job requirements listed indicate the minimum level..." etc. That's boilerplate? Might be considered generic; but it's part of job description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO statement is definitely boilerplate; remove. Also lines like "This job description is not to be construed as an exhaustive statement..." maybe generic but not EEO; could be considered boilerplate? It's a disclaimer; maybe remove. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. That line is a legal disclaimer; likely remove. Also "Pharmacosmos Therapeutics Inc. is committed to equal opportunity in employment..." is EEO; remove. Also "We select and employ qualified candidates..." is also EEO; remove. Also "To learn more visit www.pharmacosmos.us" maybe minor metadata; could be folded into short p or drop. Probably drop. Also "All job requirements listed indicate the minimum level of knowledge, skills and/or experience necessary to perform the job proficiently." This is generic; maybe drop as boilerplate? Not sure. It's not EEO but it's a generic statement; could be considered boilerplate. Safer to drop. Also "Employees will be required to perform any other job-related duties as requested by their supervisor, subject to reasonable accommodation." That's generic; maybe drop. Thus we need to keep substantive content: About Us, Core Values, Job Purpose, Duties And Responsibilities, Education & Professional Background, Competencies, Attitude And Behavior, Flexibility, Additional Information (budgetary responsibilities, traveling, Cash Bonus, LTIP, hybrid work schedule). Also maybe "Significant variations in duties and responsibilities should be discussed between the employee and manager." That's generic; maybe drop. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the exact wording? Not required to keep exact wording but cannot summarize away detail; we can rephrase but must keep all info. Safer to keep original sentences. Thus we will produce HTML with sections and lists. Let's extract each piece. About Us paragraph: "We are a global, family-owned company driven by a passion for innovation. Building on our foundational expertise in carbohydrate chemistry and cell cycle biology, we develop innovative treatments for unmet patient needs, with a focus on iron metabolism and blood-related disorders. With 700+ employees across the UK, Ireland, the Nordics, Germany, and the USA, we are committed to scientific excellence, patient care, and collaborative partnerships with the medical community." Core Values: "Our Core Values Define Who We Are People-Driven – We are a family-held company built on passionate, knowledgeable people. We value integrity, open-mindedness and respect and are guided by these values in all our endeavors. We respect each individual who becomes a part of our journey, from our employees and partners to our end-users. And we recognize that the strength in all our collaborations is trust.Committed to Quality – Quality is our source of inspiration. Quality drives our results. It represents our aspiration for excellence and our focus on driving continual improvements. For our partners and end-users, quality must always be tangible in our products, processes and people. This way, quality is the promise we keep every day.Innovating for Better Lives – Innovation is essential in our quest to improve the lives of humans. We seek to address unmet needs through our expertise in iron and carbohydrate-based pharmaceuticals. We believe in a holistic and collaborative approach to research and innovation, so we work together with the scientific and medical communities to set new standards. We have continued our growth trajectory since we launched our first product in the US, Monoferric® (ferric derisomaltose), through acquisitions, partnerships, and pipeline. Our R&D investments continue to leverage

Similar jobs