Postdoctoral Research Associate - Urban Energy Modeling, Grid-interactive Controls

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID/requisition numbers as headings; can fold minor metadata into short p or drop. We need to preserve all substantive information, but remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove instructions about uploading documents, etc. However we need to keep substantive info: duties/responsibilities, qualifications, skills, benefits, maybe schedule? The posting mentions appointment length up to 24 months with potential extension. That's schedule? Could be considered schedule (duration). Pay not mentioned. So we should not create Pay section because no pay info. Benefits: there is a paragraph about ORNL offers competitive pay and benefits programs, listing many benefits. That is substantive. So include Benefits section. About the role: The overview paragraph: "We are seeking a Postdoctoral Research Associate who will focus on urban-scale energy modeling. This position resides in the Grid Interactive Control Group in the Energy Systems Integration section, Electrification and Energy Infrastructure Division, Energy Science and Technology Directorate, at Oak Ridge National Laboratory (ORNL)." That's about the role. Also maybe "About ORNL" is separate but could be part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also Schedule (appointment length). The posting mentions appointment length up to 24 months with potential extension. That's schedule info. So include Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we should list duties as
  • . For Requirements (basic qualifications) list as
    • . For Preferred Qualifications maybe under Qualifications? The instruction: Use headings Requirements, Qualifications, Skills. We need to decide mapping. Usually Requirements = basic qualifications. Qualifications = preferred qualifications? Skills = skills list. We'll follow that. Thus:

      About the role

      We are seeking a Postdoctoral Research Associate who will focus on urban-scale energy modeling. This position resides in the Grid Interactive Control Group in the Energy Systems Integration section, Electrification and Energy Infrastructure Division, Energy Science and Technology Directorate, at Oak Ridge National Laboratory (ORNL).

      Maybe also include a brief about ORNL mission? That's more about ORNL, but could be part of About the role? Might be considered boilerplate? It's descriptive of ORNL but still substantive. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About ORNL" paragraph is not boilerplate; it's describing the lab. Could include but maybe better to keep in About the role? Might be okay. However we risk adding filler. The instruction: Prefer a few substantive sections over many thin ones. Could combine About ORNL into About the role section as extra paragraph. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About ORNL paragraph. It's substantive. So include it in About the role. Now Responsibilities: list from Major Duties/Responsibilities bullet points (though they are sentences separated by periods). We'll extract each duty as list item. Duties: - Conduct research and create innovative ideas and solutions for urban planning, transportation, and grid integration issues, focusing on sustainability and resilience. - Develop innovative equity-based planning principles and frameworks that can be applied to various urban environments. - Monitor and evaluate multi-energy-system integration solutions to ensure they comply with regulations and standards. - Develop and implement public engagement and outreach plans for community energy system integration. - Establish and maintain relationships with stakeholders and community members to ensure alignment with community needs and goals. - Deliver ORNL’s mission by aligning behaviors, priorities, and interactions with our core values of Impact, Integrity, Teamwork, Safety, and Service. - Promote equal opportunity by fostering a respectful workplace – in how we treat one another, work together, and measure success. We'll put each as
    • . Now Requirements (basic qualifications): list: - A PhD in mechanical engineering, computer science, or a related field completed within the last 5 years. Also Special Requirements: Applicants cannot have received their Ph.D. more than five years prior to the date of application and must complete all degree requirements before starting their appointment. The appointment length will be up to 24 months with the potential for extension. Initial appointments and extensions are subject to performance and availability of funding. Please submit three letters of reference when applying to this position. ... That's more about application instructions; we should remove application instructions (like submit three letters). But the special requirement about PhD within 5 years is already covered. The appointment length up to 24 months is schedule. So we can put that in Schedule section. The requirement about submitting letters is application instruction -> remove. Also the bit about Real ID etc is legal/boilerplate; remove. So Requirements section will just have the basic qualification. Now Qualifications (preferred qualifications): list: - Proven RDD&D experience in urban-scale building energy modeling. - Experience planning and designing solutions for a variety of community projects, including community electrification and decarbonization. - Understanding for creating, modifying, and analyzing OpenStudio and EnergyPlus building energy models. - Strong software development skills for automation of many knowledge-based tasks in a version-controlled environment. - Strong strategic planning, community engagement, communication, and public presentation skills. - Prepare technical solutions, reports, and visuals to support a variety of planning project types, including transportation/grid, environmental, community, equity, and sustainability planning. - Excellent communication skills for conveying technical material to both scientists and non-scientists in both written and oral presentations. - Self-disciplined work ethic and eagerness to tackle challenging research problems - Strong desire to work in a team environment. - Excellent analytical skills with high attention to detail. - Experience with geospatial data visualization tools such as ArcGIS, Cesium, or similar. - Familiarity with urban-scale building energy modeling/analysis. - Experience working in Agile/SCRUM teams. - Excellent written and oral communication skills. (duplicate of earlier) - Motivated and conscientious self-starter with the ability to work independently, follow-up on all action items, and participate creatively in collaborative teams across the laboratory. - Ability to function well in a fast-paced research environment, set priorities to accomplish multiple tasks within deadlines, and adapt to ever changing needs. We need to avoid duplication; we can combine similar items. But we must preserve ALL substantive information; we can deduplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay but we might want to avoid redundant lines. However duplication is not invented; it's present. Could keep both but maybe better to keep unique. The instruction didn't forbid removing duplicates explicitly, but said remove duplicated lines. So we should remove duplicated lines. So we need to identify duplicate lines: "Excellent communication skills for conveying technical material to both scientists and non-scientists in both written and oral presentations." and "Excellent written and oral communication skills." are similar but not identical. Might be considered duplicate? Safer to keep both? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to detect exact duplicate lines. The two lines are not exact duplicates; one is longer. So we keep both. Now Skills section: maybe we can list skills like software development, strategic planning, etc. But many of those are already in preferred qualifications. Could treat Skills as separate but we might not have distinct skills beyond those. However we could still create Skills section listing things like: Strong software development skills, Strong strategic planning, community engagement, communication, public presentation skills, Excellent analytical skills, Experience with geospatial data visualization tools, Experience working in Agile/SCRUM teams, etc. But that would duplicate content from Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one? But we need to follow headings list; we can omit sections if no real specific content. If we put Skills, we need to have content. We could extract skills from the list that are skill-oriented: Strong software development skills, Strong strategic planning, community engagement, communication, public presentation skills, Excellent communication skills, Self-disciplined work ethic, Strong desire to work in a team environment, Excellent analytical skills, Experience with geospatial data visualization tools, Familiarity with urban-scale building energy modeling/analysis, Experience working in Agile/SCRUM teams, Motivated and conscientious self-starter, Ability to function well in fast-paced environment. That's many. But they overlap with Qualifications. To avoid duplication, we could treat Qualifications as preferred qualifications and Skills as a subset (like technical skills). However the instruction says preserve ALL substantive information; we could split the preferred qualifications into two categories: Qualifications (experience/education) and Skills (abilities). But we risk losing some info if we omit. Better to keep Qualifications as preferred qualifications and omit Skills section if no distinct skill content beyond what's already covered. But we need to check if there is any explicit "Skills" heading in original? Not really. So we can omit Skills section. Thus sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Benefits, Schedule. Now Benefits: list from paragraph: "ORNL offers competitive pay and benefits programs to attract and retain individuals who demonstrate exceptional work behaviors. The laboratory provides a range of employee benefits, including medical and retirement plans and flexible work hours, to support the well-being of you and your family. Employee amenities such as on-site fitness, banking, and cafeteria facilities are also available for added convenience. Other benefits include the following: Prescription Drug Plan, Dental Plan, Vision Plan, 401(k) Retirement Plan, Contributory Pension Plan, Life Insurance, Disability Benefits, Generous Vacation and Holidays, Parental Leave, Legal Insurance with Identity Theft Protection, Employee Assistance Plan, Flexible Spending Accounts, Health Savings Accounts, Wellness Programs, Educational Assistance, Relocation Assistance, and Employee Discounts." We need to put Benefits as
      • each item. Also include the introductory sentences maybe as

        before list. Schedule: appointment length up to 24 months with potential extension. Also mention initial appointments and extensions subject to performance and availability of funding. That's schedule info. We'll put as

        . Now we must not include Pay section because no pay info. Now ensure we don't include any boilerplate like "Please submit three letters of reference", "Real ID", etc. Remove those. Also remove duplicated lines: we need to check if any duplicate lines appear in responsibilities or qualifications. Responsibilities list seems unique. Qualifications list: we have "Excellent communication skills for conveying technical material to both scientists and non-scientists in both written and oral presentations." and "Excellent written and oral communication skills." Not exact duplicates, keep both. Also "Strong desire to work in a team environment." appears maybe only once. "Self-disciplined work ethic and eagerness to tackle challenging research problems" unique. "Motivated and conscientious self-starter with the ability to work independently, follow-up on all action items, and participate creatively in collaborative teams across the laboratory." unique. "Ability to function well in a fast-paced research environment, set priorities to accomplish multiple tasks within deadlines, and adapt to ever changing needs." unique. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

        About the