Senior TMF Specialist

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse. The description includes: "Description This position is responsible for collecting, reviewing, maintaining, and archiving essential Regulatory documents for the Trial Master File (TMF) in accordance with Good Clinical Practice (GCP), E6 ICH Guidelines and other regulatory guidance documents, relevant regulations (e.g., 21 CFR Parts 312 and 314, EMA Clinical Trials Directives), and Arcus Standard Operating Procedures (SOPs) as appropriate. The Senior Clinical Document Specialist will provide support to the TMF content owners on one or more clinical programs. This position will work closely with the Study Management Teams (SMT) to ensure that the TMF is kept both current and inspection ready according to Arcus SOPs and applicable regulations." That's about the role. So we can have

About the role

with a paragraph. Responsibilities: list of duties. The posting has a "Responsibilities" heading then many bullet-like sentences. We need to put them in

• . Should we keep each sentence as separate li? Yes. Qualifications: there is a "Qualifications" heading with bullet-like sentences. We'll put

  Qualifications

  with
  • . Skills: there is a list of skills after qualifications: "Strong computer skills (MS Office) including exposure to data/document management systemsMust be able to work quickly, prioritize effectively, and show attention to detailGood communication and interpersonal skillsGood time management skills, excellent attention to detail, and ability to multi-task in a high- volume environment Team oriented and flexible; maintaining integrity and high ethical standardsAbility to build strong relationships with co-workers of various backgrounds and expertiseAbility to function at a high level in a team setting whether as group contribution or acting as an individual contributor". This is more like skills. We'll put

    Skills

    with
    • . Benefits: The posting mentions "In addition to a competitive market-based salary, Arcus offers the opportunity to participate in stock programs, a performance-based bonus, and a comprehensive benefits package. Additional information about our total rewards program can be found here: https://arcusbio.com/careers ." That's benefits content. So we can have

      Benefits

      with
      • for each benefit: stock programs, performance-based bonus, comprehensive benefits package. Also maybe mention link? Probably not needed. Pay: The posting includes salary range: "The anticipated salary range for fully qualified candidates applying for this position is $115,000- $125,000 USD annually." Also note about actual salary may vary. So we have pay content. So

        Pay

        with paragraph. Schedule: Not mentioned. No schedule info. So we should not create Schedule section. Location: "This role can be based at our Hayward or Brisbane, CA location (preferred) or can be remote based." That's location info. Could be part of About the role or maybe a separate section? There's no heading for Location in the prescribed list. Could fold into About the role paragraph. We'll include location in About the role paragraph. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EOE etc. That's boilerplate; we should remove. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, qualifications, skills, benefits, pay. We need to output only HTML fragment. Let's craft. Structure:

        About the role

        ...

        Responsibilities

        • ...
        ...

        Qualifications

        • ...
        ...

        Skills

        • ...
        ...

        Benefits

        • ...
        ...

        Pay

        ...

        We must ensure no empty sections. Now extract details. About the role paragraph: combine the description sentences. Original: "Description This position is responsible for collecting, reviewing, maintaining, and archiving essential Regulatory documents for the Trial Master File (TMF) in accordance with Good Clinical Practice (GCP), E6 ICH Guidelines and other regulatory guidance documents, relevant regulations (e.g., 21 CFR Parts 312 and 314, EMA Clinical Trials Directives), and Arcus Standard Operating Procedures (SOPs) as appropriate. The Senior Clinical Document Specialist will provide support to the TMF content owners on one or more clinical programs. This position will work closely with the Study Management Teams (SMT) to ensure that the TMF is kept both current and inspection ready according to Arcus SOPs and applicable regulations. This role can be based at our Hayward or Brisbane, CA location (preferred) or can be remote based." We'll make a paragraph. Responsibilities list: Let's extract each bullet from the responsibilities section. Original responsibilities text (starting after "Responsibilities"): "Work directly with TMF Content Owners to identify issues, perform completeness checks, and upload documents to the eTMF Acting as TMF subject matter expert (SME)/point of contact for study teams and TMF stakeholders, including attending study team meetings and managing EDLs Review and classify documents collected from internal and external sources Reconcile essential documents to avoid duplication Support study teams with the TMF quality review process Perform QC and maintenance of eTMF for assigned studies Perform data entry and reconciliation in various clinical systems and tracking tools Provide input on revision of TMF related Work Instructions and SOPs Support the management and oversight of the CRO study-specific trial master files Support the coordination of the transfer of study-specific trial master files from the CRO Follow up on quality findings Manage paper document filing process for wet-signed documents including QC review and paper/electronic filing. Participation in audit, inspection readiness preparation and inspection activities as needed Work cross-functionally with internal departments and external resources (e.g., CROs, Partners, etc.) to resolve gaps in the eTMF May provide training and mentoring activities for new and current staff Develop metrics, reports, and TMF tools/trainings Act as stand-in leading team meetings, managing team tasks as needed Position may require occasional travel" We need to turn each line into
      • . Ensure we keep the content exactly. Qualifications list: after "Qualifications" heading. Original: "Bachelors or Associates degree and 4+ years of professional clinical trial experience OR a high school diploma and 6+ years of clinical support experience with essential regulatory documents Demonstrated experience or knowledge with sponsor or CRO clinical research process, including collection of documents at study start-up, during study conduct and close-out Demonstrated knowledge of the Clinical Study Process and an understanding of the range of working procedures relating to it, together with an understanding of the ICH/GCP guidelines Familiarity with international clinical trials, clinical trial documents and document QC process highly desirable Experience with Veeva Vault electronic trial master file system(s) including uploading, reviewing, quality checks (QC), approval of study required documents. Working knowledge of DIA reference model Works under general supervision and guidance. Works with manager to establish priorities and timelines Strong computer skills (MS Office) including exposure to data/document management systems Must be able to work quickly, prioritize effectively, and show attention to detail Good communication and interpersonal skills Good time management skills, excellent attention to detail, and ability to multi-task in a high- volume environment Team oriented and flexible; maintaining integrity and high ethical standards Ability to build strong relationships with co-workers of various backgrounds and expertise Ability to function at a high level in a team setting whether as group contribution or acting as an individual contributor" Note: Some of these later items might be considered skills, but they are under Qualifications heading in the posting. However we have a separate Skills section; we could keep them under Qualifications as they are listed there. But the instruction says to use sections only when posting has real specific content for it. The posting has a Qualifications heading with those items. So we should keep them under Qualifications. However we also see later a block that seems like skills but is still under Qualifications. To avoid duplication, we should not create a separate Skills section if the content is already under Qualifications. But the instruction says we can have Skills section if posting has real specific content for it. The posting does not have a separate Skills heading; the skills are mixed in Qualifications. So we should not create a Skills section; we should keep those items under Qualifications. However the instruction also says "Prefer a few substantive sections over many thin ones." So better to keep Qualifications only, not separate Skills. But we also have a separate block after Qualifications that reads: "Strong computer skills (MS Office) including exposure to data/document management systemsMust be able to work quickly, prioritize effectively, and show attention to detailGood communication and interpersonal skillsGood time management skills, excellent attention to detail, and ability to multi-task in a high- volume environment Team oriented and flexible; maintaining integrity and high ethical standardsAbility to build strong relationships with co-workers of various backgrounds and expertiseAbility to function at a high level in a team setting whether as group contribution or acting as an individual contributor". Actually that is part of Qualifications (the lines after "Working knowledge of DIA reference model"). Thus we will not create a Skills section. Benefits: we have that. Pay: we have that. Schedule: none. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Check if any other sections like "Location" could be part of About the role. Now we need to ensure we don't include boilerplate like EEO etc. At the end there is "Physical Requirements Office Setting ..." and then EOE etc. Those are boilerplate; we should remove. Also there is "Physical Requirements Office Setting Must possess mobility..." That's also boilerplate; remove. Now let's craft the HTML. We need to be careful with HTML escaping: no special characters that need escaping? We have ampersand in "eTMF"? That's fine. We have parentheses. We'll just output as is. Make sure each
      • ends properly. Let's write. About the role paragraph:

        This position is responsible for collecting, reviewing, maintaining, and archiving essential Regulatory documents for the Trial Master File (TMF) in accordance with Good Clinical Practice (GCP), E6 ICH Guidelines and other regulatory guidance documents, relevant regulations (e.g., 21 CFR Parts 312 and 314, EMA Clinical Trials Directives), and Arcus Standard Operating Procedures (SOPs) as appropriate. The Senior Clinical Document Specialist will provide support to the TMF content owners on one or more clinical programs. This position will work closely with the Study Management Teams (SMT) to ensure that the TMF is kept both current and inspection ready according to Arcus SOPs and applicable regulations. This role can be based at our Hayward or Brisbane, CA location (preferred) or can be remote based.

        Now Responsibilities ul: We'll list each line. I'll copy each line exactly as in responsibilities, ensuring punctuation. 1. Work directly with TMF Content Owners to identify issues, perform completeness checks, and upload documents to the eTMF 2. Acting as TMF subject matter expert (SME)/point of contact for study teams and TMF stakeholders, including attending study team meetings and managing EDLs 3. Review and classify documents collected from internal and external sources 4. Reconcile essential documents