Research Assistant IV - Pediatric Surgery - Bondoc Lab
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Us" is not listed but it's substantive. I'll include as "About the organization" or "About us". I'll use "About the organization" as heading. - There's also "Comprehensive Job Description Provided Upon Request." That's boilerplate, drop. - EEO statement: boilerplate, drop. Now, metadata: Primary Location, Department, Shift, Schedule, Weekly Hours, FTE, Employee Status. These are minor metadata. The rules: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I should fold these into a short paragraph, maybe at top or in a section. Could create a "Position details" section? But rules say prefer few substantive sections. Could include in a
before sections. But the output should be HTML fragment with sections. I'll include a
with metadata at the beginning, then sections. Pay: Expected Starting Pay Range is given with details. That's a Pay section. Schedule: Full time, Weekly Hours 40, Shift Day. That's schedule info. Could be a Schedule section. The rules say include Schedule section only if posting actually states them. It does state schedule: Full time, Weekly Hours 40, Shift Day. So include Schedule section. Benefits: The posting mentions "Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply." But no specific benefits listed. The About Us section lists awards and culture but not explicit benefits like health insurance, etc. The rules: never create Benefits section unless posting actually states them. The posting says "benefits may apply" but no details. So I should not create a Benefits section. However, the About Us section includes recognition as best employers, etc. That's more about company culture. Could be "About the organization". I'll include that. Now, structure: - Opening paragraph with metadata: Primary Location, Department, Shift, Schedule, Weekly Hours, FTE, Employee Status. Maybe combine into one paragraph. - Pay section: with pay range and note. - Schedule section: Full time, Weekly Hours 40, Shift Day. - About the role: paragraph. - Responsibilities: with sub-lists. The responsibilities are grouped. I'll create a Responsibilities section with subheadings? The rules: use
for section headings. For subcategories, maybe use ? But the rules only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid subheadings, but to keep simple, I'll make Responsibilities a single section with a list of duties, but the duties are grouped. Could make a list with nested lists? Or just a flat list of all bullet points. The posting has categories: Research, Laboratory Techniques, Animal Studies, Laboratory Operations, Training and Collaboration. Each has bullet points. I'll create a Responsibilities section with an introductory paragraph? The posting says "Representative Responsibilities" then lists categories. I'll include each category as a subheading using ? But the rules only specify for main sections. However, using for subsections is okay as semantic HTML. But the instruction: "use for section headings". It doesn't say not to use other headings. I'll use for main sections, and for subcategories within Responsibilities, I'll use to keep structure. That's acceptable.
Alternatively, I could make each category a separate section? But they are all responsibilities. I'll keep as one Responsibilities section with subheadings.
- Preferred Experience: that's a Skills or Qualifications section. The rules mention Skills as a heading. I'll use "Preferred qualifications" or "Skills". The heading "Preferred Experience" is given. I'll use "Preferred qualifications" as .
- Job Qualifications: that's Requirements/Qualifications. Use "Qualifications" as .
- About the organization: About the organization.
Now, ensure no filler. Remove EEO, "Comprehensive Job Description Provided Upon Request."
Now, write HTML.
Let's draft.
First, metadata paragraph:
for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid subheadings, but to keep simple, I'll make Responsibilities a single section with a list of duties, but the duties are grouped. Could make a list with nested lists? Or just a flat list of all bullet points. The posting has categories: Research, Laboratory Techniques, Animal Studies, Laboratory Operations, Training and Collaboration. Each has bullet points. I'll create a Responsibilities section with an introductory paragraph? The posting says "Representative Responsibilities" then lists categories. I'll include each category as a subheading using ? But the rules only specify for main sections. However, using for subsections is okay as semantic HTML. But the instruction: "use for section headings". It doesn't say not to use other headings. I'll use for main sections, and for subcategories within Responsibilities, I'll use to keep structure. That's acceptable.
Alternatively, I could make each category a separate section? But they are all responsibilities. I'll keep as one Responsibilities section with subheadings.
- Preferred Experience: that's a Skills or Qualifications section. The rules mention Skills as a heading. I'll use "Preferred qualifications" or "Skills". The heading "Preferred Experience" is given. I'll use "Preferred qualifications" as .
- Job Qualifications: that's Requirements/Qualifications. Use "Qualifications" as .
- About the organization: About the organization.
Now, ensure no filler. Remove EEO, "Comprehensive Job Description Provided Upon Request."
Now, write HTML.
Let's draft.
First, metadata paragraph:
? But the rules only specify for main sections. However, using for subsections is okay as semantic HTML. But the instruction: "use for section headings". It doesn't say not to use other headings. I'll use for main sections, and for subcategories within Responsibilities, I'll use to keep structure. That's acceptable.
Alternatively, I could make each category a separate section? But they are all responsibilities. I'll keep as one Responsibilities section with subheadings.
- Preferred Experience: that's a Skills or Qualifications section. The rules mention Skills as a heading. I'll use "Preferred qualifications" or "Skills". The heading "Preferred Experience" is given. I'll use "Preferred qualifications" as .
- Job Qualifications: that's Requirements/Qualifications. Use "Qualifications" as .
- About the organization: About the organization.
Now, ensure no filler. Remove EEO, "Comprehensive Job Description Provided Upon Request."
Now, write HTML.
Let's draft.
First, metadata paragraph:
for subsections is okay as semantic HTML. But the instruction: "use for section headings". It doesn't say not to use other headings. I'll use for main sections, and for subcategories within Responsibilities, I'll use to keep structure. That's acceptable.
Alternatively, I could make each category a separate section? But they are all responsibilities. I'll keep as one Responsibilities section with subheadings.
- Preferred Experience: that's a Skills or Qualifications section. The rules mention Skills as a heading. I'll use "Preferred qualifications" or "Skills". The heading "Preferred Experience" is given. I'll use "Preferred qualifications" as .
- Job Qualifications: that's Requirements/Qualifications. Use "Qualifications" as .
- About the organization: About the organization.
Now, ensure no filler. Remove EEO, "Comprehensive Job Description Provided Upon Request."
Now, write HTML.
Let's draft.
First, metadata paragraph:
for main sections, and for subcategories within Responsibilities, I'll use to keep structure. That's acceptable.
Alternatively, I could make each category a separate section? But they are all responsibilities. I'll keep as one Responsibilities section with subheadings.
- Preferred Experience: that's a Skills or Qualifications section. The rules mention Skills as a heading. I'll use "Preferred qualifications" or "Skills". The heading "Preferred Experience" is given. I'll use "Preferred qualifications" as .
- Job Qualifications: that's Requirements/Qualifications. Use "Qualifications" as .
- About the organization: About the organization.
Now, ensure no filler. Remove EEO, "Comprehensive Job Description Provided Upon Request."
Now, write HTML.
Let's draft.
First, metadata paragraph:
.
- Job Qualifications: that's Requirements/Qualifications. Use "Qualifications" as .
- About the organization: About the organization.
Now, ensure no filler. Remove EEO, "Comprehensive Job Description Provided Upon Request."
Now, write HTML.
Let's draft.
First, metadata paragraph:
About the organization. Now, ensure no filler. Remove EEO, "Comprehensive Job Description Provided Upon Request." Now, write HTML. Let's draft. First, metadata paragraph:
Primary Location: Burnet Campus | Department: Pediatric Surgery | Shift: Day | Schedule: Full time | Weekly Hours: 40 | FTE: 1 | Employee Status: Regular
Pay section:Pay
Expected Starting Pay Range: $58,406.40 - $74,588.80
Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply. Annual pay may vary based on FTE status.
Schedule section:Schedule
- Full time
- Weekly Hours: 40
- Shift: Day
About the role
The Bondoc Laboratory is seeking a highly motivated and experienced Research Assistant to support research focused on pediatric liver cancer, liver development, stem cell biology, and organoid models. The successful candidate will independently perform complex laboratory experiments, support animal studies, analyze data, and contribute to collaborative research projects.
Responsibilities:Responsibilities
Research
- Design, perform, troubleshoot, and optimize laboratory experiments.
- Execute and adapt research protocols to meet project objectives.
- Analyze and interpret experimental data.
- Maintain accurate laboratory records and documentation.
- Contribute to publications, presentations, and other research activities.
Laboratory Techniques
- Perform mammalian cell culture, primary cell culture, and human iPSC culture.
- Conduct molecular biology assays including PCR, qPCR, and Western blotting.
- Perform histology, immunohistochemistry, immunofluorescence, and microscopy-based analyses.
- Prepare and process samples for flow cytometry and related applications.
- Assist with development, optimization, and implementation of new laboratory methods.
Animal Studies
- Maintain research mouse colonies.
- Perform animal handling, monitoring, tissue collection, and surgical procedures.
- Support in vivo studies and associated data collection.
Laboratory Operations
- Maintain laboratory equipment, supplies, and inventory.
- Troubleshoot technical and equipment issues.
- Ensure compliance with institutional, safety, biosafety, and animal care requirements.
- Support laboratory organization and day-to-day operations.
Training and Collaboration
- Train and mentor students, trainees, and junior staff.
- Serve as a technical resource within the laboratory.
- Contribute to a collaborative and productive research environment.
Preferred qualifications
- Human iPSC culture and differentiation
- Organoid culture systems
- Flow cytometry and cell sorting
- Histology and immunostaining
- Confocal microscopy
- qPCR and Western blotting
- Mouse handling, colony management, and survival surgery
Qualifications
- Bachelor’s degree in a related field and 3 years of experience in related job discipline
- OR Master’s degree in a related field and 2 years of experience
About the organization
At Cincinnati Children’s, we come to work with one goal: to make children’s health better. We believe in a holistic team approach, both in caring for patients and their families, and in advancing science and discovery. We strive to do better and find energy and inspiration in our shared purpose. If you want to be the best you can be, you can do it at Cincinnati Children’s.
- Recognized by U.S. News & World Report as a top 10 best Children's Hospitals in the nation for more than 15 years
- Consistently among the top 3 Children's Hospitals for National Institutes of Health (NIH) Funding
- Recognized as one of America’s Best Large Employers (2025), America’s Best Employers for New Grads (2025)
- One of the nation's America’s Most Innovative Companies as noted by Fortune
- Consistently certified as great place to work
- A Leading Disability Employer as noted by the National Organization on Disability
- Magnet® designated for the fourth consecutive time by the American Nurses Credentialing Center (ANCC)
We Embrace Innovation—Together. We believe in empowering our teams with the tools that help us work smarter and care better. That’s why we support the responsible use of artificial intelligence. By encouraging innovation, we’re creating space for new ideas, better outcomes, and a stronger future—for all of us.
That's all. No EEO, no boilerplate. Check rules: "Do NOT repeat the job title as a heading (the page already shows it)" - job title not given, but we didn't include. "Do NOT put Job ID / requisition numbers as headings" - none. "Preserve ALL substantive information" - yes. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - done. "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text" - all sections have content. "Prefer a few substantive sections over many thin ones." - we have 7 sections: metadata paragraph, Pay, Schedule, About the role, Responsibilities, Preferred qualifications, Qualifications, About the organization. That's okay. Now output only HTML fragment, no markdown fences. Ensure proper escaping of & in "U.S. News & World Report" -> &. Also "Cincinnati Children’s" uses