Post Doctoral Research Fellow- Biostatistics and Spatial Transcriptomics

We need to output HTML fragment with sections: About Us? 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. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Us: description of MSK mission etc. That's substantive. Should we include as a section? The allowed headings include "About the role" but not "About Us". However we can still use

for any heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples but we can use other headings? Probably we should stick to those categories. The "About Us" could be considered "About the role"? Not exactly. But we could treat it as a brief intro paragraph without heading? The instruction: "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." It doesn't forbid other headings, but says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect we use those headings where applicable. The posting includes "About Us" which is not exactly about the role but about the organization. Could we include as a

without heading? Probably yes. We can include a paragraph describing MSK. Then "Exciting Opportunity at MSK: Computational Scientist" is the job title; we should not repeat as heading. Then sections: Key Requirements (Education, Technical Expertise, Experience, Soft Skills). Could map to Requirements or Qualifications. We'll use

Requirements

and list items. Then "Core Skills" with sub-bullets: Methodological & Pipeline Development, Spatial Architecture & Niche Profiling, Immunophenotyping & Clinical Association, Study Design. Could be under Skills or Responsibilities. Probably Skills. Then "We offer a competitive salary and benefits package, as well as the opportunity to work in a highly collaborative and innovative environment." That's Benefits (generic). But we need actual content: they mention competitive salary and benefits package, but not specifics. The instruction says never create Benefits section unless posting actually states them. It does state "competitive salary and benefits package" which is a statement but not specific. Is that enough? It's vague but it's a statement. Might be considered filler? It says "competitive salary and benefits package" - that's a statement but not specific details. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive salary and benefits package" is somewhat generic but not exactly placeholder. Might be okay to include Benefits section with that sentence. Pay: They have "Pay Range: $72,000 – $87,564 Based on PGY*". Also later "Pay Range: $0.00 - $10,000,000.00" seems duplicated or erroneous. We should preserve ALL substantive information; do not invent or summarize away detail. There's contradictory pay ranges. The first is specific: $72,000 – $87,564 Based on PGY*. The second is a huge range $0.00 - $10,000,000.00 which seems like a placeholder or error. Should we include both? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The second seems likely a boilerplate placeholder; but it's still in the posting. However it's likely not substantive; it's a generic range. The instruction says never emit a heading followed by filler/placeholder text. The second pay range is filler/placeholder. So we should not include that. We'll keep the specific pay range. Also there is "FSLA Status: Exempt" and "Closing At MSK, we believe in fair, competitive pay..." etc. That's boilerplate EEO etc. Should remove. Application instructions: "Please submit your CV, bibliography, brief statement of research interests, and names and details of 2 references to John Pintado at pintadoj@mskcc.org." That's application instruction; we should remove per instruction: remove application instructions. So we drop that. Also "Helpful links: MSK Compensation Philosophy Review Our Great Benefits Offerings" - that's boilerplate; remove. Thus we need sections: maybe About (as paragraph), Requirements (as list), Skills (as list), Benefits (maybe short paragraph), Pay (maybe as paragraph or list? Pay is a single statement; we can use

). Schedule not present, so omit. We need to use

• for any list of duties/requirements/benefits. For Requirements we have subcategories: Education, Technical Expertise, Experience, Soft Skills. Could we make a nested list? Probably just list each requirement as
• with sub-bullets? The instruction: Use
  • for any list of duties/requirements/benefits. So we can make a top-level
    with each requirement as
    • . Inside each
    • we can have further detail as

      or

      ? Might be okay to just put text. Similarly for Skills: list of four items. We need to preserve all substantive information: include details like PhD in Biostatistics etc., specific platforms, packages, etc. Let's extract: About Us paragraph: "The people of Memorial Sloan Kettering Cancer Center (MSK) are united by a singular mission: ending cancer for life. Our specialized care teams provide personalized, compassionate, expert care to patients of all ages. Informed by basic research done at our Sloan Kettering Institute, scientists across MSK collaborate to conduct innovative translational and clinical research that is driving a revolution in our understanding of cancer as a disease and improving the ability to prevent, diagnose, and treat it. MSK is dedicated to training the next generation of scientists and clinicians, who go on to pursue our mission at MSK and around the globe." That's substantive. Key Requirements: Education: PhD in Biostatistics, Statistics, Computational Biology, Bioinformatics, or a closely related quantitative field with strong core statistical training. Technical Expertise: - Proven track record in analyzing and modeling single-cell and high-plex spatial profiling data. - Direct experience processing data from multiplexed imaging or sequencing-based spatial platforms (e.g., Imaging Mass Cytometry (IMC), 10x Genomics Xenium, NanoString CosMx, and/or 10x Genomics Visium). - Advanced proficiency in Python and/or R programming and expert-level familiarity with single-cell and spatial ecosystems, specifically Seurat, Giotto, and relevant Bioconductor packages. - Strong foundation in spatial statistics, including spatial autocorrelation, cell deconvolution algorithms, and distance-based neighborhood modeling. Experience: - Demonstrated experience working with paired single-cell RNA-seq and V(D)J/TCR sequencing datasets. - Experience analyzing translational data involving tumor-infiltrating lymphocytes (TILs), immunophenotyping markers, and clinical-pathological correlation. - Ability to bridge the gap between complex mathematical/algorithmic theory and practical clinical interpretation. Soft Skills: - Outstanding communication skills, with a proven ability to collaborate effectively across multidisciplinary teams of clinicians, statisticians, and computational biologists. Core Skills (maybe Skills): Methodological & Pipeline Development: Develop, scale, and implement novel statistical methods and machine learning frameworks tailored for high-dimensional spatial omics and single-cell landscapes. This includes building pipelines for multiplexed spatial imaging data and paired single-cell multi-omics. Spatial Architecture & Niche Profiling: Implement advanced spatial point pattern analysis, cell-cell interaction modeling, and neighborhood/niche identification to map cell-to-cell spatial proximity and architectural differences within the tumor microenvironment across distinct clinical cohorts. Immunophenotyping & Clinical Association: Design analytical strategies to model the landscape of the immune microenvironment (e.g., PD-L1 expression patterns, tumor-infiltrating lymphocyte densities) and statistically associate these spatial phenotypes with clinical outcomes. Study Design: Provide expert statistical guidance on study design, sample size estimation, and power calculations for translational protocols and grant proposals (NIH/NCI). Benefits: "We offer a competitive salary and benefits package, as well as the opportunity to work in a highly collaborative and innovative environment." Pay: "Pay Range: $72,000 – $87,564 Based on PGY*" We should not include the duplicated huge range. We also need to avoid duplication: The posting also had "Pay Range: $0.00 - $10,000,000.00" which we drop. Now format. We'll output:

      About

      maybe? But they said use

      for section headings (e.g. About the role...). Could use

      About the role

      but that's not exactly about the role. However we could use

      About MSK

      . Not in examples but likely acceptable. Safer to use

      About the role

      and put the About Us paragraph there? Might be misleading. Better to use

      About the organization

      but not in list. The instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical headings; we can use others but they gave examples. I'd stick to those where applicable. For the mission description, maybe we can just put as a

      without heading. That's allowed: they didn't say all content must be under headings. So we can have a leading

      for About Us. Then

      Requirements

      with
      list. Then

      Skills

      with
      list. Then

      Benefits

      with

      . Then

      Pay

      with

      . We should not include Schedule. Check for any other substantive content: "Exciting Opportunity at MSK: Computational Scientist" is job title; we ignore. "Adusumilli Lab, in close collaboration with the Department of Epidemiology and Biostatistics, is seeking a highly motivated and talented PhD-level Computational Scientist to drive cutting-edge translational cancer research.This unique joint role sits at the intersection of rigorous statistical methodology, advanced single-cell/spatial omics, and clinical translation in surgical oncology.You will develop and apply innovative statistical frameworks to map the tumor immune microenvironment (TIME), decode multi-cellular architectural niches, and collaborate closely with a multidisciplinary team of computational biologists, statisticians, and surgeons." This is a description of the role; could be considered Responsibilities. We should include that as Responsibilities section. Indeed we have a Responsibilities heading in examples. So we should add a Responsibilities section with that paragraph. Thus sections: Responsibilities, Requirements, Skills, Benefits, Pay. We need to preserve all substantive info: that description includes details about role. Let's extract that paragraph exactly: "Adusumilli Lab, in close