Research Scientist II PhD (Immunology - Bapat Lab)
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop
- Preserve ALL substantive information; do NOT invent or summarize
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning), duplicated lines, application instructions
- Include section ONLY when posting has real, specific content — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content:
1. Job Summary: This is "About the role". It has prose describing the lab, research focus, position overview. I'll use
About the role
and for the prose.
2. Responsibilities: Listed as "ESSENTIAL FUNCTIONS" with bullet points. I'll use
Responsibilities
and - for each.
3. Work Environment and Physical Requirements: This is specific content about frequency of exposure, physical requirements. Could be a separate section "Work environment" or "Physical requirements". Since it's detailed, I'll include as a section.
4. Minimum Qualifications: Includes equivalency statement and job levels. This is "Requirements" or "Qualifications". I'll use
Qualifications
and include the equivalency statement and the PhD + experience requirement.
5. Preferences: List of preferred qualifications. This could be "Skills" or "Preferred qualifications". I'll use Preferred qualifications
and list.
6. Special Instructions: Anticipated start date, application materials (CV, cover letter), encouragement to highlight experience. This is application instructions, but the rule says remove application instructions. However, the start date and what to include in application might be considered substantive? The rule says "Remove ... application instructions". But the start date is not exactly application instruction; it's a detail about the position. The user says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the application instructions (how to apply, link). But the anticipated start date and what materials to provide might be kept? The rule says "Preserve ALL substantive information". The start date is substantive. The required application materials (CV, cover letter) are part of application instructions, but they are specific. However, the rule says remove application instructions. I'll keep the start date as a note, but not the application link or how to apply. I'll include a short paragraph about anticipated start date and required materials.
7. Metadata: Requisition Number, Full Time/Part Time, Work Schedule Summary, Department, Location, Pay Rate Range, Close Date, Open Until Filled. These are minor metadata. The rule says "fold minor metadata into a short or drop it." Also, "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Pay Rate Range and Work Schedule Summary. So I could create a "Pay" section and "Schedule" section? But the rule says only if the posting actually states them. It does state pay range and schedule. However, the rule also says "Prefer a few substantive sections over many thin ones." And "never emit a heading followed by filler/placeholder text". The pay range is specific: 43,796 - 84,883. Schedule: On site, variable schedule based on needs of lab. 40 hours per week @ 1.00 FTE; 30 hours per week @ 0.75 FTE. That's substantive. So I could include a "Pay" section and "Schedule" section. But the user might consider them as metadata. The rule says "fold minor metadata into a short
or drop it." Pay and schedule are not minor; they are important. However, the example headings include Pay, Schedule, Benefits. The posting does not mention benefits explicitly, but says "fully benefited position" and links to benefits. That's not specific. So I won't create Benefits section.
I'll create a "Pay and schedule" section or separate. Let's see: The posting has "Pay Rate Range" and "Work Schedule Summary". I'll create two sections:
Pay
and Schedule
with the details.
But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So I'll include.
Also, "Close Date" and "Open Until Filled" are metadata; I'll fold into a short paragraph.
Requisition Number, Department, Location: minor metadata, fold into a short paragraph.
Now, let's structure:
- About the role (from Job Summary)
- Responsibilities (from ESSENTIAL FUNCTIONS)
- Work environment and physical requirements (from Work Environment and Level of Frequency...)
- Qualifications (from Minimum Qualifications)
- Preferred qualifications (from Preferences)
- Additional information (start date, application materials) — but remove application instructions. I'll include anticipated start date and required materials as a note.
- Pay
- Schedule
- Maybe a closing paragraph with other metadata.
But the rule says "Output ONLY the HTML fragment". So I'll produce HTML with these sections.
Let's write the HTML.
First, About the role: The job summary has two paragraphs? Actually it's one block. I'll put as maybe two paragraphs.
Responsibilities: list of 10 bullet points.
Work environment and physical requirements: two subsections? Could be one section with two lists. I'll use
Work environment and physical requirements
then maybe two with headings? But rule says use for section headings. I could use but not allowed? The rule only mentions for section headings. It doesn't forbid . But to keep simple, I'll make it one section with prose describing the frequencies.
Qualifications: includes equivalency statement and the requirement for Research Scientist II. I'll put as
for equivalency and then a list? Actually it's a statement. I'll use
for equivalency and then a
for the requirement? The requirement is "PhD in a scientific discipline and 4+ years of directly related work experience." That's one item. Could be a list with one item. I'll do a list.
Preferences: list of 10 items.
Special Instructions: anticipated start date, application materials. I'll make a section "Additional information" with for start date and required materials.
Pay:
Pay
Pay rate range: $43,796 - $84,883 per year.
Schedule: Schedule
On site, variable schedule based on needs of lab. 40 hours per week at 1.00 FTE; 30 hours per week at 0.75 FTE.
Then a final paragraph with other metadata: Requisition Number, Department, Location, Close Date, Open Until Filled.
But the rule says "fold minor metadata into a short or drop it." I'll include a short paragraph at the end.
Now, ensure no boilerplate: The posting includes "Copyright ©2025 Jobelephant.com Inc. All rights reserved. Posted by the FREE value-added recruitment advertising agency..." That's boilerplate, remove.
Also "To apply, visit https://utah.peopleadmin.com/postings/211308" - application instruction, remove.
"Learn about the great benefits of working for University of Utah at benefits.utah.edu." - that's a link, but not specific benefits. The posting says "fully benefited position". Could mention benefits in a sentence? But no specific benefits listed. So I won't create Benefits section.
Now, write HTML.
I'll start with
About the role
then ...
Then Responsibilities
...
Then Work environment and physical requirements
...
maybe with lists.
Then Qualifications
...
...
Then Preferred qualifications
...
Then Additional information
...
Then Pay
...
Then Schedule
...
Then ... metadata ...
Let's craft the content.
Job Summary text: "The Bapat Lab in the Department of Pathology seeks a Research Scientist II to advance studies investigating the fundamental roles of the immune system in tissue physiology, metabolic regulation, inflammatory disease, and cancer. Our research integrates mouse models, cellular and molecular immunology, genetic perturbation approaches, and high-dimensional genomic technologies to identify mechanisms through which immune cells respond to and regulate physiological states. The successful candidate will independently design, execute, and interpret mechanistic experiments investigating immune cell function in vivo and in vitro, with particular emphasis on T cell biology, tissue immunology, immunometabolism, and cancer immunology. Responsibilities include developing experimental approaches, performing advanced cellular and molecular assays, analyzing complex datasets, contributing to manuscripts and research proposals, and collaborating with other laboratory members. The position offers opportunities for substantial scientific contributions to ongoing and emerging research programs. NOTE: This is a full-time, fully benefited position that can accommodate a 1.00 FTE/40 hour per week employee, or a 0.75 FTE/30 hour per week employee."
I'll keep as one paragraph or split. I'll keep as one paragraph.
Responsibilities: 10 bullet points.
Work Environment and Physical Requirements:
"Work Environment and Level of Frequency that may be required: Nearly Continuously: Laboratory environment. Often: Exposure to animals. Physical Requirements and Level of Frequency that may be required: Nearly Continuously: Hearing, listening, talking. Often: Repetitive hand motion (such as typing and pipetting), walking, standing, sitting. Seldom: Bending, reaching overhead."
I'll format as two lists or prose. I'll do prose with semicolons.
Qualifications: "EQUIVALENCY STATEMENT: 1 year of higher education can be substituted for 1 year of directly related work experience (Example: bachelor's degree = 4 years of directly related work experience). Department may hire employee at one of the following job levels: Research Scientist, II: Requires a PhD in a scientific discipline and 4+ years of directly related work experience."
I'll put equivalency as paragraph, then requirement as list.
Preferences: 10 bullet points.
Special Instructions: "Anticipated start date: January 2027. Applicants should provide a current CV, including relevant publications,
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop - Preserve ALL substantive information; do NOT invent or summarize - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning), duplicated lines, application instructions - Include section ONLY when posting has real, specific content — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content: 1. Job Summary: This is "About the role". It has prose describing the lab, research focus, position overview. I'll use
About the role
andfor the prose. 2. Responsibilities: Listed as "ESSENTIAL FUNCTIONS" with bullet points. I'll use
Responsibilities
and- for each.
3. Work Environment and Physical Requirements: This is specific content about frequency of exposure, physical requirements. Could be a separate section "Work environment" or "Physical requirements". Since it's detailed, I'll include as a section.
4. Minimum Qualifications: Includes equivalency statement and job levels. This is "Requirements" or "Qualifications". I'll use
Qualifications
and include the equivalency statement and the PhD + experience requirement. 5. Preferences: List of preferred qualifications. This could be "Skills" or "Preferred qualifications". I'll usePreferred qualifications
and list. 6. Special Instructions: Anticipated start date, application materials (CV, cover letter), encouragement to highlight experience. This is application instructions, but the rule says remove application instructions. However, the start date and what to include in application might be considered substantive? The rule says "Remove ... application instructions". But the start date is not exactly application instruction; it's a detail about the position. The user says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the application instructions (how to apply, link). But the anticipated start date and what materials to provide might be kept? The rule says "Preserve ALL substantive information". The start date is substantive. The required application materials (CV, cover letter) are part of application instructions, but they are specific. However, the rule says remove application instructions. I'll keep the start date as a note, but not the application link or how to apply. I'll include a short paragraph about anticipated start date and required materials. 7. Metadata: Requisition Number, Full Time/Part Time, Work Schedule Summary, Department, Location, Pay Rate Range, Close Date, Open Until Filled. These are minor metadata. The rule says "fold minor metadata into a shortor drop it." Also, "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Pay Rate Range and Work Schedule Summary. So I could create a "Pay" section and "Schedule" section? But the rule says only if the posting actually states them. It does state pay range and schedule. However, the rule also says "Prefer a few substantive sections over many thin ones." And "never emit a heading followed by filler/placeholder text". The pay range is specific: 43,796 - 84,883. Schedule: On site, variable schedule based on needs of lab. 40 hours per week @ 1.00 FTE; 30 hours per week @ 0.75 FTE. That's substantive. So I could include a "Pay" section and "Schedule" section. But the user might consider them as metadata. The rule says "fold minor metadata into a short
or drop it." Pay and schedule are not minor; they are important. However, the example headings include Pay, Schedule, Benefits. The posting does not mention benefits explicitly, but says "fully benefited position" and links to benefits. That's not specific. So I won't create Benefits section. I'll create a "Pay and schedule" section or separate. Let's see: The posting has "Pay Rate Range" and "Work Schedule Summary". I'll create two sections:
Pay
andSchedule
with the details. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So I'll include. Also, "Close Date" and "Open Until Filled" are metadata; I'll fold into a short paragraph. Requisition Number, Department, Location: minor metadata, fold into a short paragraph. Now, let's structure: - About the role (from Job Summary) - Responsibilities (from ESSENTIAL FUNCTIONS) - Work environment and physical requirements (from Work Environment and Level of Frequency...) - Qualifications (from Minimum Qualifications) - Preferred qualifications (from Preferences) - Additional information (start date, application materials) — but remove application instructions. I'll include anticipated start date and required materials as a note. - Pay - Schedule - Maybe a closing paragraph with other metadata. But the rule says "Output ONLY the HTML fragment". So I'll produce HTML with these sections. Let's write the HTML. First, About the role: The job summary has two paragraphs? Actually it's one block. I'll put asmaybe two paragraphs. Responsibilities: list of 10 bullet points. Work environment and physical requirements: two subsections? Could be one section with two lists. I'll use
Work environment and physical requirements
then maybe two- with headings? But rule says use
for section headings. I could use
but not allowed? The rule only mentions
for section headings. It doesn't forbid
. But to keep simple, I'll make it one section with prose describing the frequencies. Qualifications: includes equivalency statement and the requirement for Research Scientist II. I'll put as
for equivalency and then a list? Actually it's a statement. I'll use
for equivalency and then a
- for the requirement? The requirement is "PhD in a scientific discipline and 4+ years of directly related work experience." That's one item. Could be a list with one item. I'll do a list.
Preferences: list of 10 items.
Special Instructions: anticipated start date, application materials. I'll make a section "Additional information" with
for start date and required materials. Pay:
Pay
Pay rate range: $43,796 - $84,883 per year.
Schedule:Schedule
On site, variable schedule based on needs of lab. 40 hours per week at 1.00 FTE; 30 hours per week at 0.75 FTE.
Then a final paragraph with other metadata: Requisition Number, Department, Location, Close Date, Open Until Filled. But the rule says "fold minor metadata into a shortor drop it." I'll include a short paragraph at the end. Now, ensure no boilerplate: The posting includes "Copyright ©2025 Jobelephant.com Inc. All rights reserved. Posted by the FREE value-added recruitment advertising agency..." That's boilerplate, remove. Also "To apply, visit https://utah.peopleadmin.com/postings/211308" - application instruction, remove. "Learn about the great benefits of working for University of Utah at benefits.utah.edu." - that's a link, but not specific benefits. The posting says "fully benefited position". Could mention benefits in a sentence? But no specific benefits listed. So I won't create Benefits section. Now, write HTML. I'll start with
About the role
then...
ThenResponsibilities
- ...
Work environment and physical requirements
...
maybe with lists. ThenQualifications
...
- ...
Preferred qualifications
- ...
Additional information
...
ThenPay
...
ThenSchedule
...
Then... metadata ...
Let's craft the content. Job Summary text: "The Bapat Lab in the Department of Pathology seeks a Research Scientist II to advance studies investigating the fundamental roles of the immune system in tissue physiology, metabolic regulation, inflammatory disease, and cancer. Our research integrates mouse models, cellular and molecular immunology, genetic perturbation approaches, and high-dimensional genomic technologies to identify mechanisms through which immune cells respond to and regulate physiological states. The successful candidate will independently design, execute, and interpret mechanistic experiments investigating immune cell function in vivo and in vitro, with particular emphasis on T cell biology, tissue immunology, immunometabolism, and cancer immunology. Responsibilities include developing experimental approaches, performing advanced cellular and molecular assays, analyzing complex datasets, contributing to manuscripts and research proposals, and collaborating with other laboratory members. The position offers opportunities for substantial scientific contributions to ongoing and emerging research programs. NOTE: This is a full-time, fully benefited position that can accommodate a 1.00 FTE/40 hour per week employee, or a 0.75 FTE/30 hour per week employee." I'll keep as one paragraph or split. I'll keep as one paragraph. Responsibilities: 10 bullet points. Work Environment and Physical Requirements: "Work Environment and Level of Frequency that may be required: Nearly Continuously: Laboratory environment. Often: Exposure to animals. Physical Requirements and Level of Frequency that may be required: Nearly Continuously: Hearing, listening, talking. Often: Repetitive hand motion (such as typing and pipetting), walking, standing, sitting. Seldom: Bending, reaching overhead." I'll format as two lists or prose. I'll do prose with semicolons. Qualifications: "EQUIVALENCY STATEMENT: 1 year of higher education can be substituted for 1 year of directly related work experience (Example: bachelor's degree = 4 years of directly related work experience). Department may hire employee at one of the following job levels: Research Scientist, II: Requires a PhD in a scientific discipline and 4+ years of directly related work experience." I'll put equivalency as paragraph, then requirement as list. Preferences: 10 bullet points. Special Instructions: "Anticipated start date: January 2027. Applicants should provide a current CV, including relevant publications,