Biological Science Instructional Support Technician II
California State University, Fullerton · Fullerton, CA · 1 mo ago
Information Technology$5k–$7k/moFull-time
We need to output HTML fragment with sections: headings for sections present with real content. Must not repeat job title. Must not include Job ID etc. Must include sections like About the role (maybe "Why CSUF" or description), Responsibilities (Duties and Responsibilities), Requirements (Essential Qualifications, Preferred Qualifications maybe combined), Benefits, Pay, Schedule. Must only include sections if posting has real specific content. Let's extract.
Job Title: Biological Science Instructional Support Technician II (not to be used as heading).
Classification: Instructional Support Technician II (maybe not needed).
Salary Range: Classification Range $4,595 - $6,694 per month (Hiring range depending on qualifications, not anticipated to exceed $4,595 - $5,646 per month). So we have pay info. Provide Pay section.
Work Schedule: Monday - Friday, 8:00 AM - 5:00 PM. So Schedule section.
Why CSUF: description about university. Could be "About the role" or "About CSUF". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use About the role for the university description and department description. Or maybe "About the role" is appropriate.
Responsibilities: Duties and Responsibilities paragraph.
Requirements: Essential Qualifications (maybe also Preferred Qualifications). Could combine into Requirements section.
Benefits: Benefits at a Glance list.
Skills: Not explicitly listed but could be derived from abilities etc. But we should only include if posting has real specific content. There's a list of abilities etc. Could put under Skills or Requirements. Since we have Requirements already, maybe we put Skills separate? But we can combine. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including essential and preferred qualifications and abilities), Benefits, Pay, Schedule.
We must not create sections with filler like "commensurate with experience". Not present.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the long legal paragraphs at the end (like Notice of Non-Discrimination, Reasonable accommodations, equal opportunity employer, CSU Out-of-State Employment Policy, mandated reporter, disclosure of sexual harassment, release form, multiple positions, staff vs academic student, regular attendance, performance test, online application deadline, H-1B, salary step structure, hiring preference). Those are boilerplate/legal. Must remove them.
Also remove "Special Working Conditions Notice of Non-Discrimination on the Basis of Gender or Sex and Contact Information for Title IX Coordinator" line? That's also legal. Remove.
Also remove "Must have a reliable source of transportation." That's a requirement maybe? It's under Special Working Conditions? Actually it's a line: "Must have a reliable source of transportation." That's a substantive requirement (maybe). Should we keep? It's not boilerplate; it's a job requirement. Could be included in Requirements.
Also "Care for living organisms of a potentially pathogenic nature..." etc. Those are part of Special Working Conditions but are substantive. Keep.
We need to preserve all substantive information: duties, responsibilities, qualifications, abilities, etc.
Thus we need to extract the substantive parts:
- Why CSUF (description of university)
- Department description (College of Natural Science and Mathematics)
- Duties and Responsibilities (long list)
- Essential Qualifications (list)
- Preferred Qualifications (list)
- Abilities (list) maybe part of Essential Qualifications but we can include.
- Benefits at a Glance (list)
- Pay (salary range)
- Schedule (work schedule)
- Maybe "Must have a reliable source of transportation." (include in Requirements)
- "Care for living organisms of a potentially pathogenic nature..." etc (include in Requirements or Special Working Conditions but we can put under Requirements or maybe a separate "Working Conditions" but we don't have that heading; we could incorporate into Requirements or maybe a separate "Working Conditions" not in allowed headings. Since only allowed headings are listed, we should not create new headings like Working Conditions. So we need to fit that info into existing headings: maybe under Requirements or Responsibilities? It's more about working conditions. Could put under Requirements as a bullet.
Also "Ability to stand odors generated..." etc.
Thus we will create sections:
for sections present with real content. Must not repeat job title. Must not include Job ID etc. Must include sections like About the role (maybe "Why CSUF" or description), Responsibilities (Duties and Responsibilities), Requirements (Essential Qualifications, Preferred Qualifications maybe combined), Benefits, Pay, Schedule. Must only include sections if posting has real specific content. Let's extract.
Job Title: Biological Science Instructional Support Technician II (not to be used as heading).
Classification: Instructional Support Technician II (maybe not needed).
Salary Range: Classification Range $4,595 - $6,694 per month (Hiring range depending on qualifications, not anticipated to exceed $4,595 - $5,646 per month). So we have pay info. Provide Pay section.
Work Schedule: Monday - Friday, 8:00 AM - 5:00 PM. So Schedule section.
Why CSUF: description about university. Could be "About the role" or "About CSUF". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use About the role for the university description and department description. Or maybe "About the role" is appropriate.
Responsibilities: Duties and Responsibilities paragraph.
Requirements: Essential Qualifications (maybe also Preferred Qualifications). Could combine into Requirements section.
Benefits: Benefits at a Glance list.
Skills: Not explicitly listed but could be derived from abilities etc. But we should only include if posting has real specific content. There's a list of abilities etc. Could put under Skills or Requirements. Since we have Requirements already, maybe we put Skills separate? But we can combine. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including essential and preferred qualifications and abilities), Benefits, Pay, Schedule.
We must not create sections with filler like "commensurate with experience". Not present.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the long legal paragraphs at the end (like Notice of Non-Discrimination, Reasonable accommodations, equal opportunity employer, CSU Out-of-State Employment Policy, mandated reporter, disclosure of sexual harassment, release form, multiple positions, staff vs academic student, regular attendance, performance test, online application deadline, H-1B, salary step structure, hiring preference). Those are boilerplate/legal. Must remove them.
Also remove "Special Working Conditions Notice of Non-Discrimination on the Basis of Gender or Sex and Contact Information for Title IX Coordinator" line? That's also legal. Remove.
Also remove "Must have a reliable source of transportation." That's a requirement maybe? It's under Special Working Conditions? Actually it's a line: "Must have a reliable source of transportation." That's a substantive requirement (maybe). Should we keep? It's not boilerplate; it's a job requirement. Could be included in Requirements.
Also "Care for living organisms of a potentially pathogenic nature..." etc. Those are part of Special Working Conditions but are substantive. Keep.
We need to preserve all substantive information: duties, responsibilities, qualifications, abilities, etc.
Thus we need to extract the substantive parts:
- Why CSUF (description of university)
- Department description (College of Natural Science and Mathematics)
- Duties and Responsibilities (long list)
- Essential Qualifications (list)
- Preferred Qualifications (list)
- Abilities (list) maybe part of Essential Qualifications but we can include.
- Benefits at a Glance (list)
- Pay (salary range)
- Schedule (work schedule)
- Maybe "Must have a reliable source of transportation." (include in Requirements)
- "Care for living organisms of a potentially pathogenic nature..." etc (include in Requirements or Special Working Conditions but we can put under Requirements or maybe a separate "Working Conditions" but we don't have that heading; we could incorporate into Requirements or maybe a separate "Working Conditions" not in allowed headings. Since only allowed headings are listed, we should not create new headings like Working Conditions. So we need to fit that info into existing headings: maybe under Requirements or Responsibilities? It's more about working conditions. Could put under Requirements as a bullet.
Also "Ability to stand odors generated..." etc.
Thus we will create sections:
About the role
Why CSUF ... Department ...
Responsibilities
- ... each duty ...
Requirements
- Essential Qualifications bullets
- Preferred Qualifications bullets
- Abilities bullets
- Must have reliable transportation
- Care for living organisms ...
- Ability to stand odors ...