Associate Director, Computational Biology

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us" and "The Opportunity". The instructions: 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. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include: About the role (maybe from "The Opportunity" description), Responsibilities (Key Responsibilities), Requirements (Qualifications), Skills (maybe Nice to Have?), Benefits (Compensation & Total Rewards includes benefits), Pay (Compensation & Total Rewards includes salary range), Schedule (maybe not present). The posting includes "Additional Functions" with travel, but not schedule. So we might not include Schedule. We must not include sections with placeholder text. So we need to ensure each section has content. We need to strip boilerplate: "About Us" maybe we can treat as "About the role"? Actually "About Us" is about the organization, not role. The instruction says use headings like About the role, Responsibilities, etc. So we can create an "About the role" section summarizing the opportunity description. Must preserve all substantive info, not invent or summarize away detail. But we can paraphrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep the details, not omit them. However we can rephrase? It says do NOT summarize away detail. So we need to keep the content, maybe as paragraphs or lists. We can embed the content from "The Opportunity" as prose under About the role. Then responsibilities as list under Responsibilities. Qualifications as list under Requirements (or Qualifications). Nice to Have could be under Skills or maybe a separate "Preferred Qualifications". But instruction only lists Skills as possible heading. We could put Nice to Have under Skills. Benefits: we have details under Compensation & Total Rewards: health, retirement, etc. Also salary range. So we can have Benefits section for benefits, and Pay section for salary range. We must not include sections like Schedule if not present. We must remove EEO boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Us: "Sage Bionetworks uses open science and collaboration to improve human health. We bring together scientific, technical, and operational expertise to advance biomedical research through responsible data sharing, strong governance, and innovative approaches to research and technology. Our work is complex, interdisciplinary, and mission-driven. We value curiosity, diverse perspectives, experimentation, accountability, and radical collaboration." The Opportunity: long paragraph describing role. We'll keep that as prose. Key Responsibilities: list bullet points under headings: Lead Biomedical Data Science & Stewardship with subpoints, Build Community & Team Capability with subpoints. We need to flatten into a single

• list? The instruction: Use
  • for any list of duties/requirements/benefits. So we can have a list for responsibilities, each duty as
  • . Could include sub-bullets? Probably just flat list items. Qualifications: Education, Experience, etc. We'll list each as
  • . Nice to Have: list as
  • under Skills. Benefits: list health & wellness, future security, work-life harmony. Pay: salary range. We must not include "Note: Please do not upload your resume as your cover letter (required)" etc. That's application instruction; remove. Also remove "Job Functions And Physical Requirements" etc? That's substantive? It includes physical demands, cognitive demands, additional functions (travel). That is substantive info about job. Should we include? The instruction says preserve ALL substantive information. So we should include that info. Could be under a section like "Job Functions" or "Requirements"? But we already have Requirements. Could add a section "Job Functions" but not in the list of allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map that info into one of those. Physical demands etc could be part of Requirements or Qualifications? Probably Requirements. We'll include under Requirements as list items. Also "Additional Functions" includes travel twice per year, communication skills, teamwork, policies. That's also requirements. Thus we can put all those under Requirements. Now we need to ensure we don't duplicate content. Let's extract. From "Job Functions And Physical Requirements": Physical Demands: - Extended periods of sitting at a desk and using a computer. - Repeated wrist, hand, and finger movements. - Requires clear vision for tasks like data analysis, transcribing, computer use, and reading. - Occasionally lifting or moving objects weighing up to 10 pounds. Cognitive Demands: - Able to work effectively under deadlines. - Strong problem-solving and analytical skills. - Attention to detail and accuracy. - Flexibility to adapt to changing environments, priorities and multitask. Additional Functions: - Travel two times per year for on-site events in Seattle, WA. - Effective verbal and written communication skills. - Works well in a team and maintains professionalism. - Follows company policies, procedures, and relevant laws and regulations. - Note: This list is not exhaustive and may be subject to modification as job duties evolve. We should keep that note? It's meta; maybe we can drop as it's not substantive? It's a note about list not exhaustive. Could be considered boilerplate? Might be okay to keep but it's not a duty. Safer to drop. Now "Compensation & Total Rewards": - Sage Bionetworks implements equitable workplace strategies to ensure fair pay. Actual compensation is determined by market data, specific experience, and internal parity. - Job Level: Associate Director - Annual Salary Range: $140,000 - $180,000 - Note: New hires typically receive an offer between the minimum and the midpoint of the range to allow for future growth within the role. Higher offers may be considered for exceptional experience or specific market conditions. - Comprehensive Benefits: We offer a package competitive with both commercial biotech and nonprofit sectors: - Health & Wellness: Comprehensive medical, dental, vision, life, AD&D, and long-term disability. - Future Security: Robust retirement plan and flexible spending accounts (FSA). - Work-Life Harmony: Paid time off and flexible work arrangements. - Learn more at: Benefits – Sage Bionetworks We should keep the link? Probably can keep as plain text. Now "Equal Opportunity & Inclusion" boilerplate: remove. Now "About Us" we can include as part of About the role? Or we could have an "About the role" that includes both About Us and The Opportunity. But About Us is about organization, not role. However we could still include it under About the role as context. The instruction says use heading About the role for section headings (e.g. About the role...). So we can put About Us + The Opportunity under About the role. Now we need to ensure we don't repeat job title as heading. The job title is "Associate Director, Computational Biology". We must not put that as heading. Now produce HTML:

    About the role

    About Us: Sage Bionetworks uses open science and collaboration to improve human health. We bring together scientific, technical, and operational expertise to advance biomedical research through responsible data sharing, strong governance, and innovative approaches to research and technology. Our work is complex, interdisciplinary, and mission-driven. We value curiosity, diverse perspectives, experimentation, accountability, and radical collaboration.

    The Opportunity: Sage Bionetworks is seeking an Associate Director, Computational Biology to lead and grow a multidisciplinary team focused on applied scientific research, biomedical data stewardship, and community engagement around Sage’s data assets, including widely used resources such as Synapse, the AD Knowledge Portal, and the Cancer Complexity Knowledge Portal. This is a scientific and people leadership role with an opportunity to shape how Sage curates, governs, shares, and activates its biomedical data. You will establish scientific direction, data management standards, and community-engagement practices in partnership with Sage’s governance and platform teams. Your work will help ensure Sage’s data are Findable, Accessible, Interoperable, and Reusable (FAIR), aligned with GA4GH data-sharing standards, and trusted and actively used by the research community. You will lead a multidisciplinary team of biomedical data managers, biomedical data engineers, community engagement staff, and program managers. You’ll also serve as a strategic partner to organizational leadership, connect data stewardship and community initiatives to Sage’s broader mission, identify opportunities to expand adoption of Sage’s data assets, and contribute to platform development priorities. Externally, you will represent Sage with data generators, researchers, funders, consortium partners, and other stakeholders. You will communicate the scientific value of Sage’s managed data, data derivatives, and software platforms while identifying community needs and opportunities for growth. This role combines scientific leadership, people leadership, and hands-on technical work. You will develop your team, strengthen Sage’s data stewardship and community capabilities, and continue contributing directly through computational biology, statistical, and bioinformatic work. The role is intentionally focused on applied, data- and community-oriented science rather than maintaining an independent, hypothesis-driven research program. The current scope includes substantial work with spatial and imaging data. You should have the practical technical understanding needed to design effective approaches for complex datasets, including large-scale, multi-omic data, and to evaluate emerging assays, data modalities, and computational methods. You'll Know You're Succeeding When Sage’s biomedical data are well curated, governed, documented, and shared in ways that meet FAIR and GA4GH standards. Researchers actively use, contribute to, and help improve Sage’s data resources. Data sharing is responsible, ethical, and compliant, with appropriate access and minimal unnecessary friction. External scientists have well-coordinated and well-supported research experiences with Sage. Your team has clear expectations, effective practices, and the support needed to deliver high-quality data stewardship and community programs. Data quality, metadata, and harmonization practices support cross-study and cross-consortium reuse. You identify opportunities for new projects, collaborations, and funding, including contributing to or leading competitive grant proposals. You are a trusted scientific and data stewardship partner to internal leadership and the external research community. Sage is well represented in large-scale Data Coordination Center (DCC) and consortium initiatives, including engagement with program officers, leading scientists, and other stakeholders. You balance strategic leadership, team development, and hands-on scientific contribution based on program needs.

    Now Responsibilities: We need to list each duty from Key Responsibilities. Key Responsibilities headings: Lead Biomedical Data Science & Stewardship (with subpoints), Build Community & Team Capability (with subpoints). We'll flatten. List items: - Apply statistical, bioinformatic, and computational biology methods—including exploratory analysis, benchmarking, and tooling—to Sage’s large-scale, multi-omic data to improve usability, discoverability, and scientific value. - Oversee the curation, organization, annotation, and lifecycle management of biomedical datasets in alignment with FAIR principles. - Partner with Sage’s Privacy and Compliance Office to inform data governance frameworks and access-control models and ensure responsible, ethical, and compliant data sharing. - Champion FAIR principles and relevant GA4GH standards, including data-use ontologies, federated data access, and genomic data-sharing frameworks. - Lead harmonization of complex, multi-source biomedical datasets to