Research Associate II - Goldberg Laboratory

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes "A Brief Overview", "About The Laboratory", "Technical Skills", "What You Will Do", "Education Qualifications", "Experience Qualifications", "Skills And Abilities". Also salary range present: "SALARY RANGE: $76,100.00 - $97,000.00 Annually". So we need a Pay section. No schedule or benefits mentioned. So we should not include Benefits or Schedule sections. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove "Learn more." etc. Also remove "Click here for more information regarding CHOP's Compensation and Benefits." Also remove "To carry out its mission..." maybe keep? It's a statement about influenza vaccine requirement; that's a condition of employment, maybe considered boilerplate? It's not exactly EEO but it's a requirement. Might be considered relevant? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The influenza vaccine requirement is a condition of employment, maybe not boilerplate but could be considered legal. Safer to drop it. Also drop "Learn more." and the sentence about CHOP's commitment. We need to preserve all substantive information. So we need to include the overview text, lab description, technical skills, what you will do, education qualifications, experience qualifications, skills and abilities, and salary range. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which content is list vs prose. Many bullet-like sentences are separated by line breaks. We can convert them to

  • . For example, "A Brief Overview" paragraph: multiple sentences describing role. Could be prose

    . But we could also break into list if they are duties. The instruction: Use

    • for any list of duties/requirements/benefits. So if we have a list of duties, we should use list. The "What You Will Do" section is a list of duties. So we should make that a
      • . Similarly "Technical Skills" is a list of skills; could be list. "Education Qualifications" and "Experience Qualifications" could be list. "Skills And Abilities" also list. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the exact phrasing? Probably we can keep the sentences as is, but we can split into list items. We must not create sections with filler like "commensurate with experience". We have salary range, so we can make a Pay section with

        Pay

        and then

        Salary range: $76,100.00 - $97,000.00 annually.

        We must not include Benefits or Schedule sections. Now produce HTML fragment. Let's extract content: - A Brief Overview: "This role is an advanced independent researcher that plans, coordinates and executes complex research projects. Works with the Principal Investigator. Participates in and assists in the planning and coordination of research projects, is independent and responsible for a specific aspect of the one or more research projects. Assists in determining the direction of the project. Prepares and writes manuscripts and research proposals, performs data management and quantitative analyses, collaborates in development of innovative research and educational programs, and serves as an educational resource for the laboratory and the Institution." We could keep as a paragraph

        . - About The Laboratory: includes description of lab, techniques, applicant will work..., ideal candidate..., etc. This is prose; could be paragraph(s). Might be long; we can keep as

        with multiple sentences. - Technical Skills: list of skills. We'll make

        • each bullet. - What You Will Do: list of duties. - Education Qualifications: list. - Experience Qualifications: list. - Skills And Abilities: list. - Pay: paragraph. We need to ensure we don't include boilerplate like "CHOP does not discriminate..." etc. Remove that. Also remove "Shift: Day (United States of America)" maybe not needed; it's metadata but could be considered minor metadata; we can drop or include in a short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it. So we could include a short p for shift and location. But shift is not a heading; we could include a

          Shift: Day (United States of America)

          at top. However the instruction says "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." So we can include shift as a short p. But is that considered minor metadata? Probably yes. We'll include a

          Shift: Day (United States of America)

          at the beginning. Now produce HTML. Let's craft:

          Shift: Day (United States of America)

          About the role

          maybe? The heading "About the role" is not explicitly in text but we have "A Brief Overview". Could use that as heading. The instruction: use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if applicable. We have content that matches About the role (overview). So we can use

          About the role

          and put the overview paragraph there. Next, we have "About The Laboratory" which could be considered part of About the role or maybe "About the laboratory". Not in the list; but we could still use

          About the laboratory

          but not in the examples. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely we should stick to those headings where applicable. For lab description, maybe we can incorporate into About the role or Responsibilities? But better to keep a heading like "About the laboratory" as h3; it's still a section heading. The instruction didn't say we cannot use other headings, just that we should use h3 for section headings (e.g. those). So using h3 for About the laboratory is fine. But we also have "Technical Skills" which maps to Skills heading. So we can use

          Skills

          . "What You Will Do" maps to Responsibilities. "Education Qualifications" maps to Qualifications. "Experience Qualifications" maybe also Qualifications? Could be part of Qualifications. But we could keep separate headings? The instruction: Prefer a few substantive sections over many thin ones. So we could combine Education and Experience under Qualifications. But we need to preserve all info; we can have a Qualifications section with subpoints? However we need to use
          • for list. Could have two sublists? Might be okay to have separate headings but that creates many thin sections. Better to combine Education and Experience into Qualifications heading, with two sublists? But we need to follow instruction: Use

            for section headings. If we combine, we need to still present both education and experience info. Could do a

            Qualifications

            then have two

            headings? Not allowed? We could use

            Education:

            then
            etc. That's acceptable. Similarly Skills And Abilities could go under Skills heading. Thus we can have sections: About the role, Responsibilities, Qualifications, Skills, Pay. We also might need a section for "About the laboratory" maybe incorporate into About the role? Could add a paragraph after overview. Let's decide: We'll have: - About the role (includes brief overview and lab description) - Responsibilities (What You Will Do) - Qualifications (Education and Experience) - Skills (Technical Skills and Skills And Abilities) - Pay (Salary range) That's few substantive sections. Now we need to extract content and format. Let's gather text: About the role overview paragraph: as above. Lab description paragraph: "A Research Associate position is available in the laboratory of Ethan M. Goldberg, M.D., Ph.D., in the Division of Neurology at The Children’s Hospital of Philadelphia and the new Center for Brain Research in Development, Genetics, and Engineering (BRIDGE). The lab studies mechanisms of neurodevelopmental disorders toward development of novel therapies using a range of techniques, including: human and mouse genetics; neurons and brain organoids generated from induced pluripotent stem cells from human patients with neurodevelopmental disorders; electrophysiology including voltage clamp of ionic currents in heterologous systems and acute brain slice in mouse; advanced microscopy including two-photon calcium imaging in vivo; and animal behavior in mouse models of neurodevelopmental disorders using machine learning based analysis of video. The applicant will work with the Principal Investigator and research laboratory to lead a project(s), conduct experiments, analyze data for lab- and Center-wide collaborative projects, generate data for manuscripts and grant applications, train and mentor undergraduate and graduate students, develop data acquisition and analysis pipelines, develop and maintain data storage systems. The ideal candidate will be experienced, enthusiastic, self-driven, and committed to learning and working as part of a team. Specific prior experience with signal processing, data analysis, statistics, computational modeling, coding, and/or machine learning, is required. She or he will have excellent organizational and communication skills and the ability to multi-task. This is an opportunity to work in a fast-paced high-level research environment translating neuroscience discovery into treatment and cure for brain disorders of childhood." We'll keep that as a paragraph after overview. Now Responsibilities: list items from "What You Will Do". Let's extract each sentence: - Assists faculty in the conduct of research of significant value in the basic and/or translational science area - Functions with a high level of independence in the development and execution of research projects - Plans, conducts, and manages research projects within the federal, institutional regulations and policies - Collaborates with researchers, external agencies and institutions to develop cooperative research initiatives - Trains technical staff, students, fellows, and physicians in lab procedures - Reviews manuscripts for peer-reviewed journals - Assist in composing/developing applications for grants, contracts, and research funding proposals. - Responsible for appropriate use of research funds - May supervise students or other research staff as assigned. Note: "Assist" should be "Assists" but keep as is. Now Qualifications: Education and Experience. Education Qualifications: - Bachelor's Degree Required - Masters Degree in Bioengineering, Neuroscience, or an interdisciplinary field (computer science, biology) Preferred - Doctorate in Bioengineering, Neuroscience, or an interdisciplinary field (computer science, biology) Preferred Experience Qualifications: - At least eight (8) years of directly relevant post grad scientific lab experience Required - At least ten (10) years of directly relevant post grad scientific lab experience Preferred - Successful completion of a Post Doc Fellowship Preferred We'll combine. Now Skills: Technical Skills list and Skills And Abilities list. Technical Skills bullets (split by sentences? The paragraph is long with many semicolons. Better to split into logical items: - Strong programming skills in Python, MATLAB, and/or R, including development of data analysis pipelines, reproducible code, and integration of diverse data sources. - Familiarity with computational libraries and frameworks such as NumPy, SciPy, Pandas, Scikit-learn, PyTorch, and TensorFlow. - Demonstrated ability to design, implement, and optimize data analysis pipelines for processing, organizing, integrating, and analyzing large-scale datasets, and to translate analytical results into scientific publications and other research outputs. - Experience with data quality control, validation and visualization tools, including automated quality