Research Engineering/ Scientist Associate II

We need to output HTML fragment with sections: h3 headings for sections present with content. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse posting. Key sections: - General Notes (maybe "About the role"? Actually "General Notes" is description of department. Could be "About the role" or "About the department". The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. "General Notes" could be "About the role". We'll use

About the role

and put the paragraph. - Responsibilities: list of duties. Use

• . - Required Qualifications: list? It's a paragraph with bullet-like sentences. Could be
  • . The instruction: Use
    • for any list of duties/requirements/benefits. So we can list each qualification as li. - Preferred Qualifications: also list. - Salary Range: mention Pay. So we need a Pay section with the salary range. It says "$48,000 (prorated: 24,000) + depending on qualifications". That's substantive. So include

      Pay

      with

      . - Working Conditions: maybe could be under "Requirements" or "Skills"? Not exactly. Could be "Requirements" includes physical requirements. But we have a separate "Working Conditions" block. Could map to "Requirements" or maybe "Skills"? The instruction says we can include sections only when posting has real specific content. We have content for working conditions. Could create a section "Requirements" and include those? But we already have Required Qualifications. Might be better to have a section "Working Conditions" but not in the list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Working Conditions is not listed. Could we put under "Requirements"? Probably yes: physical requirements are part of requirements. But we already have Required Qualifications (education/experience). Could combine? The instruction: Prefer a few substantive sections over many thin ones. So maybe combine working conditions into Requirements or Skills? However, they are not skills. Could put under "Requirements". We'll create a

      Requirements

      and include both the qualifications and working conditions? But we also have Preferred Qualifications. Could have Qualifications section with required and preferred. But we need to preserve all info. Let's think. We have: - Required Qualifications (education, experience, skills) - Preferred Qualifications (more experience, additional experience, project management, knowledge of UT inventory systems) - Working Conditions (chemicals, biohazards, keyboard, lifting, climbing stairs/ladders, etc.) - Salary Range (Pay) - Responsibilities (list) - General Notes (About the role) - Required Materials (Resume/CV, references, letter of interest) - this is application instructions, which we must remove per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove Required Materials section. - Employment Eligibility, Retirement Plan, Background Checks, etc. Those are boilerplate/legal; remove. Thus we keep: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Working Conditions (maybe as Requirements), Pay. We need to decide headings. Option: Use "Requirements" for both required qualifications and working conditions? But we also have Preferred Qualifications. Could have "Qualifications" section with required and preferred subpoints. But the instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications as possible headings. Could use Requirements for mandatory qualifications and working conditions, and Qualifications for preferred qualifications? Or vice versa. Better: Use "Requirements" for required qualifications (education/experience) and "Qualifications" for preferred qualifications. Working conditions could be under "Requirements" as well (physical requirements). But we might exceed. Let's structure:

      About the role

      General Notes paragraph.

      Responsibilities

      • ... each responsibility.

      Requirements

      • Bachelor's degree in biology, biochemistry, life science or related field and two years of laboratory experience.
      • Previous employment in a research lab with familiarity in using and maintaining lab equipment.
      • Excellent organizational and time-management skills.
      • Relevant education and experience may be substituted as appropriate.
      • May work around chemicals and chemical fumes.
      • May work around standard office conditions.
      • May work around biohazards.
      • Repetitive use of a keyboard at a workstation.
      • Use of manual dexterity.
      • Climbing of stairs.
      • Climbing of ladders.
      • Must be able to lift a minimum of 30 pounds.

      Qualifications

      • More than the required experience in a research lab.
      • Additional experience maintaining laboratory equipment.
      • Experience in project management.
      • Knowledge of University of Texas inventory systems and processes.

      Pay

      $48,000 (prorated: 24,000) + depending on qualifications

      We should not include Schedule, Benefits sections as not present. Check for any other substantive content: "Weekly Scheduled Hours: 20" is schedule info. Actually we have Weekly Scheduled Hours: 20. That is schedule info. The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. So we have schedule: Weekly Scheduled Hours: 20. So we should add a Schedule section. Also FLSA Status: Exempt from FLSA. That's metadata but could be included in Schedule? Not needed. But schedule is definitely substantive. Thus add

      Schedule

      Weekly Scheduled Hours: 20

      Also "Position Open To: All Applicants" maybe minor metadata; could be dropped. "Earliest Start Date: Immediately" maybe minor; could be dropped. "Position Duration: Expected to Continue" maybe minor; could be dropped. "Location: AUSTIN, TX" maybe minor; could be dropped but it's substantive location. However location is not among allowed headings; we could incorporate into About the role paragraph? But we must preserve all substantive information. Location is substantive. Where to put? Could add a short paragraph after About the role? But we cannot create new headings not in list. Could we add a

      within About the role that includes location? The About the role currently is the General Notes paragraph. We could append location info to that paragraph. That would preserve it without new heading. Similarly "FLSA Status: Exempt from FLSA" maybe not needed. We need to preserve all substantive information: location, weekly scheduled hours, maybe FLSA status? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. FLSA status is not boilerplate; it's substantive. But we don't have a heading for it. Could we include it under Schedule or Requirements? Probably under Schedule as additional info. Or we could add a

      under Schedule that includes both weekly hours and FLSA status. Similarly "Position Open To: All Applicants" maybe not needed. "Earliest Start Date: Immediately" maybe not needed. "Position Duration: Expected to Continue" maybe not needed. We'll incorporate location into About the role paragraph. Let's craft About the role paragraph: Combine General Notes plus location. General Notes: "The Department of Molecular Biosciences leads in research and education spanning molecular, microbial, cellular, developmental, chemical, plant, structural and systems biology. Exploring the molecular foundations of biology and disease, our faculty include world experts in cell and developmental biology, systems and synthetic biology and structural biology. Our faculty and their teams not only make discoveries that change the world, but they also leverage these discoveries into state-of-the art courses and training experiences for undergraduate and graduate students as part of our core educational mission." Add location: "Location: AUSTIN, TX." We'll make one paragraph. Now schedule: weekly scheduled hours 20, FLSA status Exempt from FLSA. We'll put:

      Weekly Scheduled Hours: 20. FLSA Status: Exempt from FLSA.

      Now check for any other substantive content: "Retirement Plan Eligibility: The retirement plan for this position is Teacher Retirement System of Texas (TRS), subject to the position being at least 20 hours per week and at least 135 days in length." That's substantive but maybe considered benefits? It's about retirement plan. Could be considered Benefits. The instruction says include Benefits section only if posting actually states them. This is a benefit description. So we should add a Benefits section with that info. Also "Employment Eligibility: Regular staff who have been employed in their current position for the last six continuous months are eligible for openings being recruited for through University-Wide or Open Recruiting, to include both promotional opportunities and lateral transfers. Staff who are promotion/transfer eligible may apply for positions without supervisor approval." That's more eligibility info; maybe not needed but it's substantive. However it's somewhat procedural; could be considered boilerplate? Not exactly EEO. Might be considered metadata. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those but could be considered eligibility rules. Might be okay to keep? But we already have many sections; we could add a Benefits section for retirement plan, and maybe keep eligibility under Requirements? Not sure. Better to keep only retirement plan as Benefits. Also "Background Checks: A criminal history background check will be required for finalist(s) under consideration for this position." That's also substantive but could be considered part of Requirements? Might be considered a condition of employment. Could add to Requirements as a bullet. But the instruction says Prefer a few substantive sections over many thin ones. Adding many bullets may be okay. We need to decide what to keep. Let's list all substantive info from posting: - Department description (General Notes) - Purpose: support department research infrastructure by assisting with shared equipment, spaces, resources. - Responsibilities (list) - Required Qualifications (list) - Preferred Qualifications (list) - Salary Range - Working Conditions (list) - Weekly Scheduled Hours: 20 - FLSA Status: Exempt - Location: AUSTIN, TX - Retirement Plan Eligibility: TRS, subject to >=20 hrs/week and >=135 days. - Background Checks: criminal history required. - Employment Eligibility: regular staff employed 6 months eligible etc. - Retirement Plan Eligibility (already) - Required Materials (remove) - Application instructions (remove) - EEO etc (remove) - Pay Transparency etc (remove) - Employment Eligibility Verification etc (remove) - E-Verify etc (remove) - Compliance etc (remove) We need to preserve all substantive information; not invent or summarize away detail. So we must keep all of the above unless they are considered boilerplate/legal/EEO etc. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must remove EEO, legal, etc. But items like Retirement