Jobs · Management · Tennessee

Postdoctoral Research Associate - Coastal Landscape Geospatial Modeling

UT-Battelle · Oak Ridge, TN · 1 mo ago
ManagementFull-time
We need to produce HTML fragment with sections: About the role (maybe Overview), Responsibilities (Major Duties/Responsibilities), Requirements (Basic Qualifications), maybe Preferred Qualifications as part of Requirements or separate Skills? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real, specific content. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Remove boilerplate, duplicated lines, application instructions. Preserve all substantive information; do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections: About the role (Overview), Responsibilities (Major Duties/Responsibilities), Requirements (Basic Qualifications), maybe Skills (Preferred Qualifications?), Benefits (ORNL offers competitive pay and benefits programs... list of benefits). Pay: not specified, so we should NOT include Pay section. Schedule: not specified, so omit. Benefits: we have a list of benefits; we can include Benefits section with

  • . Also maybe Qualifications section could combine Basic and Preferred? But instruction: Use headings like Requirements, Qualifications, Skills. We could have Requirements for Basic Qualifications, Skills for Preferred Qualifications, or Qualifications for both. Let's decide: Use Requirements for Basic Qualifications, Skills for Preferred Qualifications. Benefits separate. We need to include a short

    for metadata like Requisition Id maybe? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include a

    at top: Requisition Id 17130. Or we could drop it entirely. Probably include a short

    . Now we need to preserve all substantive information: Overview paragraph, duties list, basic qualifications list, preferred qualifications list, benefits list, ORNL description maybe? The "About ORNL" section is substantive; could be part of About the role? Might be separate but we can include as part of About the role or maybe a separate "About ORNL" but not in list of headings. The instruction only gave examples of headings; we can add other headings if needed? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. The About ORNL description could be part of About the role or maybe we can include a brief paragraph under About the role. The overview already describes the role; we could add ORNL description as part of About the role. We must not include boilerplate like equal opportunity, E-Verify, etc. Also remove application instructions (like how to upload documents, contact email, etc). Also remove "Contact for Position: Ben Sulman (sulmanbn@ornl.gov)"? That's maybe minor metadata; could be folded into a short

    or dropped. Probably drop it as it's contact info; not required. The instruction says preserve ALL substantive information; contact info might be considered substantive? But it's not about the role; it's application instruction. Might be considered boilerplate? It's not exactly boilerplate but it's contact. The instruction says remove application instructions. Contact for Position is part of application instructions. So we can drop it. Also remove "Special Requirements" about PhD time limit, appointment length, etc. That is substantive? It's about appointment details; maybe we should keep? It's not in the list of headings but could be included in About the role or Requirements? It's about eligibility. Might be considered substantive. However, the instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep that info. Where to place? Could be under Requirements or a separate section like "Appointment Details". But not in the given heading list. Could fold into Requirements as a paragraph. Or we could add a section "Details" but better to stick to given headings. We could add a paragraph under Requirements about appointment length and special requirements. Also "Please submit three letters of reference when applying to this position." That's application instruction; drop. Also "Instructions to upload documents to your candidate profile:" drop. Also "For employment at Oak Ridge National Laboratory (ORNL), a Real ID compliant form of identification will be required..." etc. That's about eligibility; maybe keep as part of Requirements? It's about eligibility for employment. Could be included under Requirements. But we need to be careful not to include too much boilerplate. The special requirements about PhD time limit, appointment length, etc are specific to the position; we should keep. Also "This position will remain open for a minimum of 5 days after which it will close when a qualified candidate is identified and/or hired." That's application instruction; drop. Also "We accept Word (.doc, .docx), Adobe (unsecured .pdf), Rich Text Format (.rtf), and HTML (.htm, .html) up to 5MB in size." drop. Also "Resumes from third party vendors will not be accepted;" drop. Also "If you have trouble applying for a position, please email ORNLRecruiting@ornl.gov." drop. Also "ORNL is an equal opportunity employer..." drop. Also "UT-Battelle is an E-Verify employer." drop. Now we need to keep ORNL description about legacy, benefits, etc. That's substantive. Now produce HTML. Structure:

    Requisition Id 17130

    About the role

    Overview paragraph: The Plant-Soil Interactions Group within the Environmental Sciences Division (ESD) at Oak Ridge National Laboratory (ORNL) seeks a postdoctoral researcher in Coastal Landscape analysis and modeling, with a focus on training and application of predictive machine learning tools. This researcher will synthesize regional-scale remote sensing imagery and ecological monitoring data and develop data-driven methods for predicting land loss and ecosystem transitions in wetland-rich landscapes of the Gulf Coast with a focus on coastal Louisiana. This candidate will directly support the Exploring Gulf Region Ecosystem Transitions (EGRET) project, an interdisciplinary and multi-institutional collaboration focused on disturbance-driven ecosystem transitions and their impacts across the U.S. Gulf Coast. EGRET employs an integrated model–experiment (ModEx) approach accelerated by artificial intelligence (AI) to advance predictive understanding of how plant–microbial–soil interactions vary across inundation and salinity gradients to shape ecological, hydrological, and geomorphological responses to abrupt disturbance. A cohort of postdoctoral researchers will be hired across multiple institutions to collaboratively support scientific advances guided by AI/ML, remote sensing, process-based modeling, field observations and experiments, and advanced analytical techniques.

    Maybe also include ORNL description after overview? Could be part of About the role: ORNL offers competitive pay and benefits programs... but we have Benefits section separate. So we can keep ORNL legacy description in About the role? Might be better to keep it under About the role as a paragraph about the lab. But we already have Benefits section for benefits. The ORNL description includes legacy, team size, mission, etc. That's substantive; we can include as a paragraph under About the role after the overview. Thus About the role will have two paragraphs: overview and ORNL description. Now Responsibilities:

    Responsibilities

    • Synthesize, harmonize, and analyze large environmental monitoring and remote sensing datasets from coastal Louisiana
    • Train and apply multimodal and generative AI methods to predict land loss and vegetation change at high spatial resolution
    • Work closely with remote-sensing scientists, modelers, and empiricists across DOE laboratories and universities to address project objectives
    • Present results within the research group and at national and international conferences and publish manuscripts in peer-reviewed journals
    • Deliver ORNL’s mission by aligning behaviors, priorities, and interactions with our core values of Impact, Integrity, Teamwork, Safety, and Service
    Now Requirements (Basic Qualifications):

    Requirements

    • PhD in Earth science, Ecology, Geography, Environmental Sciences, Geosciences, or a related field completed within the last 5 years or expected to be completed soon
    • Expertise in AI/ML methods in an environmental or Earth science context
    • Experience programming in Python or related languages
    • A strong record of independent and productive research, as indicated by conference presentations and/or publications in peer-reviewed journals
    • Ability to work independently and collaboratively as part of a large multidisciplinary team
    • Excellent interpersonal, oral, and written communication skills
    We may also add a paragraph about special requirements: appointment length up to 24 months, potential extension, PhD time limit, etc. Could be added as a

    after the list. Now Skills (Preferred Qualifications):

    Skills

    • Experience with AI/ML approaches for spatiotemporal or Earth system data, including generative AI methods
    • Expertise in coastal landscape ecology, hydrology, and/or geomorphology
    • Experience analyzing large, heterogeneous environmental, geospatial, remote-sensing, or time-series datasets
    Now Benefits:

    Benefits

    • 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
    • Employee Discounts
    We might also include mention of medical and retirement plans, flexible work hours, on-site fitness, banking, cafeteria facilities. Those are also benefits. Could add them as list items. Thus Benefits list: medical and retirement plans, flexible work hours, on-site fitness, banking, cafeteria facilities, plus the enumerated list. We need to preserve all substantive information: The text says "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." Thus we should include medical and retirement plans, flexible work hours, on-site fitness, banking, cafeteria facilities as benefits items. Now we need to ensure we didn't include Pay or Schedule sections (not present). Good. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft final HTML. Check for any leftover boilerplate: We removed contact, special requirements about PhD time limit? We kept appointment length etc in Requirements paragraph? We haven't added that yet. Let's add a

    after Requirements list: "Appointment length will be up to 24 months with potential for extension, subject to performance and

Similar jobs