Jobs · Research

Clinical Scientist

Worldwide Clinical Trials · Portland, OR · 1 mo ago
RemoteRemoteResearch$157k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). The posting includes sections: "Who we are", "Why Worldwide", "What The Clinical Scientist Does At Worldwide", "What You Will Do", "What You Bring To The Role", "Your Experience", then compensation and benefits info. We need to map to headings: About the role (maybe "Who we are" and "Why Worldwide"? Actually "About the role" likely describes role overview. Could combine "What The Clinical Scientist Does At Worldwide" as about the role. Also "Who we are" and "Why Worldwide" are company description, maybe not needed as about the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have: - About the role: description of what the Clinical Scientist does. That's in "What The Clinical Scientist Does At Worldwide" and maybe "What You Will Do" is responsibilities. - Responsibilities: list of duties from "What You Will Do". That's a bullet list. - Requirements: maybe "What You Bring To The Role" includes knowledge, skills, abilities. Could be split into Requirements, Qualifications, Skills. But we need to follow instruction: prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But headings are predefined; we can omit sections if no specific content. We need to decide which headings have real content. We have content for: - About the role: yes (role description). - Responsibilities: yes (list of duties). - Requirements: maybe the "What You Bring To The Role" includes knowledge, experience, etc. Could be considered Requirements. - Qualifications: maybe "Your Experience" includes education, years experience, etc. Could be Qualifications. - Skills: maybe overlapping with Requirements; but we could combine. - Benefits: posting mentions "competitive benefits package depending on location". No specifics. So we should NOT create Benefits section because no specific content (just generic). So omit Benefits. - Pay: salary range provided: $79,000 - $15? Actually $79,000.00 - $157,000.00. That's specific. So include Pay section. - Schedule: no mention of schedule (full-time/part-time, hours). Not present. So omit Schedule. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Pay. But we need to avoid thin sections. Could combine Requirements, Qualifications, Skills into one "Requirements" maybe? But headings list includes Requirements, Qualifications, Skills separately. We could include all three if they have distinct content. Let's see if we can split: - Requirements: maybe the mandatory requirements: "Strong knowledge of oncology clinical development processes and study design principles. Deep understanding of oncology product profiles and safety concepts... Experience with solid tumors, liquid tumors, imaging clinical data review..." etc. That's a list of knowledge/abilities. - Qualifications: maybe education/experience: "Advanced clinical or scientific degree preferred (e.g., PharmD, PhD, MSN, ARNP) with 8+ years of industry‑related experience in Oncology Proficiency in Microsoft Office Suite. Experience with EDC systems and data visualization platforms." - Skills: maybe "Proficient with electronic data capture systems and data visualization tools. Solid understanding of GCP, ICH guidelines, and regulatory requirements. Excellent written, oral communication, and presentation skills. Strong organizational, analytical, and problem‑solving abilities. Ability to manage multiple priorities and adapt to changing demands. Strong interpersonal skills and the ability to collaborate across teams and levels. Demonstrated ability to work independently and within teams. Good judgment and decision‑making skills. Willingness to travel as needed." But there is overlap. However we can still separate as per content. We must not invent or summarize away detail. Must preserve all substantive info. So we need to include all bullet points from "What You Will Do" as
  • . Also include all bullet points from "What You Bring To The Role" and "Your Experience" etc. We must not include boilerplate like "The duties and responsibilities listed above are representative..." that's a generic line; we should keep? It's substantive? It's a disclaimer; maybe we can keep but it's not boilerplate? It's a standard line but it's part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not exactly boilerplate but it's a generic disclaimer. Might be considered boilerplate? It's not about EEO. It's about duties not all-inclusive. Could keep? Safer to keep as it's substantive? It's not navigation. I'd keep it as a

    . Also the line "Promotion to the next level is not automatic based on years of experience. Personnel are evaluated on proven competency, level of responsibility, and ability to work independently." That's substantive. Also compensation paragraph includes details about salary range and benefits. We'll include Pay section with salary range. Benefits we omit because no specifics. We must not include navigation like "To view our other roles, check out our careers page at Discover a world of difference at Worldwide! For more information on Worldwide, visit www.Worldwide.com or connect with us on LinkedIn." That's boilerplate/application instructions; remove. Also "We love knowing that someone is going to have a better life because of the work we do." That's fluff but maybe keep? It's not boilerplate but could be considered fluff. Might keep as part of About the role? It's not essential. I'd remove as it's not substantive info about role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. That line is not substantive about role; it's a motivational statement. Could be considered boilerplate? Not exactly. Safer to remove? It's not navigation/legal/EEO. It's just fluff. I'd remove to keep concise. Also "At Worldwide Clinical Trials, we are committed to fostering an inclusive and equitable workplace by providing transparent compensation." That's related to compensation; we can keep in Pay section maybe as a

    . Now structure:

    About the role

    ... description from "What The Clinical Scientist Does At Worldwide". Combine maybe also "Who we are" and "Why Worldwide"? But those are company description, not role. The heading About the role likely expects role overview. We'll use the paragraph from "What The Clinical Scientist Does At Worldwide". That paragraph: "The Clinical Scientist is responsible for the review, interpretation, and assessment of oncology clinical data specifically solid tumor data with key findings communicated to Clients and study team. The Clinical Scientist works closely with the Medical Monitor as appropriate. This role communicates and presents clinical trends and findings to the Study Team and Clients while working collaboratively to ensure high quality data, maintain the highest integrity of the clinical database and clinical study reports (e.g., CSR). The Clinical Scientist partners with Clients, subcontractors, and internal study team members to meet project timelines and expectations related to clinical data review." We'll put that in

    . Then Responsibilities:

    Responsibilities

    • ... each bullet from "What You Will Do". Need to preserve each bullet exactly as given, but we can trim trailing punctuation? Keep as is. List: - Develop oncology clinical data review plans for assigned studies. - Conduct ongoing oncology clinical data review and analysis of clinical data, (e.g., efficacy, safety related data components) utilizing listings, visual analytics, tables, figures, graphs, and EDC continually - Present key oncology data trends and findings to the Medical Monitor, Study Team, and Client. - Collaborate with cross‑functional study team members to ensure protocol‑defined variables are collected and reported accurately. - Track and analyze potential safety events in collaboration with Pharmacovigilance and Medical Monitoring. - Contribute to discussions on potential study or strategy modifications based on clinical data review. - Create data summary slides for Safety Review Committee Meetings, Data Review Meetings with support from Director. - Query data as appropriate on EDC data as needed during Clinical review with timely follow up, and identification of potential protocol deviations. - Partner with vendors and study team members to ensure accurate endpoint reporting. - Serve as a point of contact for site staff and monitors for protocol and clinical inquiries. - Collaborate with Data Management on CRF design, CRF instructions, and data quality plans. - Review data‑driven sections of regulatory and clinical reporting documents (e.g., CSRs, INDs, NDAs/BLAs, annual reports, IBs, etc.). - Provide scientific writing support, including patient narratives, abstracts, posters, and presentations. - Mentor and train junior staff. - Utilize visual analytics tools to interpret and communicate data insights. Note there is a sentence: "The duties and responsibilities listed above are representative of the nature and level of work assigned and are not necessarily all-inclusive." We'll add as a

      after the list maybe. Then Requirements:

      Requirements

      • ... from "What You Bring To The Role". Let's extract each bullet (they are sentences separated by periods). The text: "Strong knowledge of oncology clinical development processes and study design principles. Deep understanding of oncology product profiles and safety concepts (e.g. DCs, bi-specific antibodies, CAR-T) Experience with solid tumors, liquid tumors, imaging clinical data review Clinical understanding of the physiological and pathological effects of oncology disease states and anticancer therapies on human organ systems. Skilled in oncology clinical data analysis, interpretation, and assessing clinical relevance in human clinical trials, within the relevant therapeutic area. Proficient with electronic data capture systems and data visualization tools. Solid understanding of GCP, ICH guidelines, and regulatory requirements. Excellent written, oral communication, and presentation skills. Strong organizational, analytical, and problem‑solving abilities. Ability to manage multiple priorities and adapt to changing demands. Strong interpersonal skills and the ability to collaborate across teams and levels. Demonstrated ability to work independently and within teams. Good judgment and decision‑making skills. Willingness to travel as needed." We'll put each as
      • . Then Qualifications:

        Qualifications

        • ... from "Your Experience". The text: "Advanced clinical or scientific degree preferred (e.g., PharmD, PhD, MSN, ARNP) with 8+ years of industry‑related experience in Oncology Proficiency in Microsoft Office Suite. Experience with EDC systems and data visualization platforms. Promotion to the next level is not automatic based on years of experience. Personnel are evaluated on proven competency, level of responsibility, and ability to work independently." We'll put each as
        • . Note the last two sentences are separate; we can make two
        • items. Then Skills: maybe we could omit because overlapping; but we already used many items in Requirements and Qualifications. Could we combine Requirements and Qualifications into one? But we have distinct content; we could keep Requirements as the knowledge/abilities, Qualifications as education/experience, and Skills maybe we could omit because it's thin. However we already listed many skills in Requirements. To avoid thin sections, we could omit Skills heading entirely. The instruction: Prefer a few substantive sections over many thin ones. So we can drop Skills if it's not adding much beyond what's already covered. But we have not yet included a Skills section; we have Requirements and Qualifications. That's fine. Now Pay:

          Pay

          ... include salary range and compensation transparency statement.

          We need to include the salary range: "United States of America - $79,000.00 - $157,000.00

Similar jobs

Clinical Scientist

Krystal Biotech, Inc.Pittsburgh, PA· 3 mo ago
Researchapply on krystalbiotech.applytojob.com

Clinical Scientist

kps lifeUnited States· 1 wk ago
RemoteAnalystapply on portal.dynamicsats.com

Clinical Scientist

Hyperfine | AI-Powered Portable MRIPalo Alto, CA· 3 mo ago
Analystapply on job-boards.greenhouse.io

Clinical Scientist

ActalentAlameda, CA· 2 mo ago
RemoteAnalyst$90–$95/hrapply on ars2.equest.com

Clinical Scientist

JobsInMass.comNeedham, MA· 3 mo ago
Analyst$181k–$194k/yrapply on jobsinmass.com