Staff Scientist - Computational Data Sciences Shared Resource

We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about Beckman Research Institute. That could be "About the role" or maybe "About the position". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content: description of role (responsibilities). Also qualifications. Also maybe "Core Services" could be part of responsibilities. There's no explicit Benefits, Pay, Schedule. There's a line about pay: "City of Hope employees pay is based on the following criteria: work experience, qualifications, and work location." That's not a specific salary figure, but it's some info about pay criteria. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay criteria, albeit not a number. Is that enough? It says "City of Hope employees pay is based on the following criteria: work experience, qualifications, and work location." That's a statement about pay. Could be considered pay info. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". This is similar: pay based on criteria, not a specific range. Might be considered vague. Safer to omit Pay section because it's not a specific salary or range. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay, but it's vague. I'd lean to omit Pay section to avoid thin section. Benefits: there is a link "To learn more about our Comprehensive Benefits, please CLICK HERE." That's not describing benefits, just a link. So no Benefits section. Schedule: none. Thus we will have sections: About the role (intro), Responsibilities (list of duties), Qualifications (maybe split into Requirements and Qualifications? The posting has "Your qualifications should include:" and then list. Could treat as Qualifications. Also maybe "Skills" could be extracted from qualifications (programming proficiency etc). But we can combine into Qualifications. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate. Let's extract substantive content: Intro paragraph: "Join the forefront of groundbreaking research at the Beckman Research Institute of City of Hope, where we're changing lives and making a real difference in the fight against cancer, diabetes, and other life-threatening illnesses. Our dedicated and compassionate faculty and staff are driven by a common mission: Contribute to innovative approaches in predicting, preventing, and curing diseases, shaping the future of medicine through cutting-edge research. We are looking for a Staff Scientist for the Computational Data Sciences Shared Resource. You will provide advanced analytical, computational, and scientific support for research programs across City of Hope, including cancer, diabetes, and broader translational sciences. Working under the leadership of the Shared Resource Director, this position delivers expert services in bioinformatics, multi‑omics data analysis, computational biology, predictive modeling, and computational oncology. You will function as a senior technical and scientific contributor, collaborating directly with research teams to design studies, analyze data, interpret results, and support grant development. You will also contribute to implementing and maintaining analytical pipelines, training users, and ensuring that core services meet CCSG expectations for rigor, reproducibility, and impact." Then "Core Services:" list: - Bioinformatics, multi‑omics data analysis & QC - Computational biology, predictive modeling, and AI/ML methods - Data visualization, results interpretation, and collaborative consulting - Training, documentation, and data science literacy support Then "As a successful candidate, you will be:" list: - Provide high‑level analytical support across genomics, transcriptomics, proteomics, imaging, and clinical/translational datasets. - Implement, maintain, and document computational workflows and pipelines that ensure robust, reproducible analyses. - Consult with investigators on study design, computational strategies, data quality, and interpretation of results. - Develop and apply innovative computational methods, including machine learning and mathematical modeling approaches. - Prepare analysis reports, figures, methods documentation, and contributions to manuscripts and grant applications. - Collaborate closely with the Director to improve service intake processes, ensure timely delivery, and maintain user satisfaction. - Support compilation of metrics, service logs, and impact summaries for CCSG reporting and institutional reviews. - Contribute to workshops, training sessions, documentation, and efforts to build computational capacity among research teams. - Work with IT and informatics partners to support the computational infrastructure required for core operations. - Maintain a high standard of scientific integrity, confidentiality, and compliance with institutional data governance policies. - Develop staffing plans, and equipment acquisitions to ensure sustainability and innovation in core operations. Then "Your qualifications should include:" list: - PhD or equivalent degree in bioinformatics, computational biology, mathematics, physics, engineering, computer science, or a related quantitative discipline; Or equivocal demonstrated track record through publications and prior work experience. - Demonstrated expertise in computational methods used in biomedical and translational research. - Experience working with multi‑omics datasets (e.g., genomics, transcriptomics, proteomics, single‑cell, imaging). - Strong programming proficiency in relevant languages (e.g., R, Python, MATLAB, Bash) and experience using HPC or cloud environments. - Proven ability to collaborate effectively with interdisciplinary teams, including bench scientists and clinical researchers. - Strong analytical, problem‑solving, and communication skills, including experience presenting scientific results. - Track record of contributing to peer‑reviewed publications. - Experience preparing analysis documentation, reports, or grant‑related materials preferred. - Familiarity with peer review funding mechanisms is desirable but not required. Then pay line: "City of Hope employees pay is based on the following criteria: work experience, qualifications, and work location." Then EEO line: "City of Hope is an equal opportunity employer." Then benefits link: "To learn more about our Comprehensive Benefits, please CLICK HERE." We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO line and benefits link? The benefits link is not boilerplate? It's a link to benefits; but it's not describing benefits. It's basically a call to action. Might be considered application instruction? It's not exactly application instruction but it's a link. The instruction says remove boilerplate, duplicated lines, and application instructions. The benefits link is not an application instruction but it's a call to learn more. Might be considered boilerplate? It's not legal/EEO. It's a benefits link. Could be considered not substantive because it doesn't describe benefits. So we can drop it. We also need to drop duplicated lines (none apparent). Keep all substantive info. Now structure:

  About the role

  Join the forefront of groundbreaking research at the Beckman Research Institute of City of Hope, where we're changing lives and making a real difference in the fight against cancer, diabetes, and other life-threatening illnesses. Our dedicated and compassionate faculty and staff are driven by a common mission: Contribute to innovative approaches in predicting, preventing, and curing diseases, shaping the future of medicine through cutting-edge research. We are looking for a Staff Scientist for the Computational Data Sciences Shared Resource. You will provide advanced analytical, computational, and scientific support for research programs across City of Hope, including cancer, diabetes, and broader translational sciences. Working under the leadership of the Shared Resource Director, this position delivers expert services in bioinformatics, multi‑omics data analysis, computational biology, predictive modeling, and computational oncology. You will function as a senior technical and scientific contributor, collaborating directly with research teams to design studies, analyze data, interpret results, and support grant development. You will also contribute to implementing and maintaining analytical pipelines, training users, and ensuring that core services meet CCSG expectations for rigor, reproducibility, and impact.

  Then maybe a subsection for Core Services? Could be part of Responsibilities. But we could make a separate section "Core Services" as a heading? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Core Services is not in the list but we could treat as Responsibilities. Better to put under Responsibilities. Thus

  Responsibilities

  Core Services:

  • Bioinformatics, multi‑omics data analysis & QC
  • Computational biology, predictive modeling, and AI/ML methods
  • Data visualization, results interpretation, and collaborative consulting
  • Training, documentation, and data science literacy support

  As a successful candidate, you will be:

  • Provide high‑level analytical support across genomics, transcriptomics, proteomics, imaging, and clinical/translational datasets.
  • Implement, maintain, and document computational workflows and pipelines that ensure robust, reproducible analyses.
  • Consult with investigators on study design, computational strategies, data quality, and interpretation of results.
  • Develop and apply innovative computational methods, including machine learning and mathematical modeling approaches.
  • Prepare analysis reports, figures, methods documentation, and contributions to manuscripts and grant applications.
  • Collaborate closely with the Director to improve service intake processes, ensure timely delivery, and maintain user satisfaction.
  • Support compilation of metrics, service logs, and impact summaries for CCSG reporting and institutional reviews.
  • Contribute to workshops, training sessions, documentation, and efforts to build computational capacity among research teams.
  • Work with IT and informatics partners to support the computational infrastructure required for core operations.
  • Maintain a high standard of scientific integrity, confidentiality, and compliance with institutional data governance policies.
  • Develop staffing plans, and equipment acquisitions to ensure sustainability and innovation in core operations.
  Then Qualifications:

  Qualifications

  • PhD or equivalent degree in bioinformatics, computational biology, mathematics, physics, engineering, computer science, or a related quantitative discipline; Or equivocal demonstrated track record through publications and prior work experience.
  • Demonstrated expertise in computational methods used in biomedical and translational research.
  • Experience working with multi‑omics datasets (e.g., genomics, transcriptomics, proteomics, single‑cell, imaging).
  • Strong programming proficiency in relevant languages (e.g., R, Python, MATLAB, Bash) and experience using HPC or cloud environments.
  • Proven ability to collaborate effectively with interdisciplinary teams, including bench scientists and clinical researchers.
  • Strong analytical, problem‑solving, and communication skills, including experience presenting scientific results.
  • Track record of contributing to peer‑reviewed publications.
  • Experience preparing analysis documentation, reports, or grant‑related materials preferred.
  • Familiarity with peer review funding mechanisms is desirable but not required.
  Optionally we could add a short paragraph for pay criteria? The instruction says avoid Pay section unless posting actually states them. It does state pay criteria. But it's vague. Might be better to include a short

  under About the role or a separate Pay section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, albeit vague. I'd include a Pay section with that line. But they also said prefer a few substantive sections over many thin ones. Adding a Pay section with just one line might be thin. However it's still substantive info. Could we incorporate it into About the role as a sentence? That would avoid a thin section. The instruction: "Prefer a few substantive sections over many thin ones." So better to incorporate pay info into About the role or another section. Let's add a sentence at end of About the role paragraph: "City of Hope employees