Postdoctoral Researcher - Explainable AI for 3D Data

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. The posting includes: About Us (maybe not needed), Why Join ExxonMobil (maybe not needed), About The Role (that's about the role). Key Responsibilities (list). Required Qualifications (list). Preferred Qualifications (list). Desired Attributes (list). Duration (maybe schedule? Not exactly). Work Location (maybe not needed). Your Total Rewards (benefits). Relocation Options (maybe benefits). Pay: not specific; only says individual pay determined based on factors, no numbers. So we should NOT include Pay section because no specific pay. Schedule: not given. Benefits: we have "Your Total Rewards" description about benefits categories, but no specific list. It says "More information on our Company’s benefits can be found at ..." Not specific. So we should not include Benefits unless there is real specific content. The posting does not list specific benefits like health insurance, retirement, etc. So we should omit Benefits section. However we could include a short paragraph about benefits? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The benefits description is vague but still some content: "Our commitment to you runs deep: our employees grow personally and professionally, with benefits built on our core categories of health, security, finance, and life." That's somewhat specific but still generic. Might be considered filler? It's not a list. Could be considered prose. The rule says we should not create Benefits section unless posting actually states them. It does state benefits categories (health, security, finance, life). That's specific enough? Might be okay to include a Benefits section with that prose. However we also have Relocation Options which could be part of benefits. But we can combine. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment. Let's extract sections: - About The Role: prose paragraph(s). We'll put under

  About the Role

  with

  content. - Key Responsibilities: list. We'll put under

  Responsibilities

  with
  • each. - Required Qualifications: list. Under

    Requirements

    maybe? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Requirements and Qualifications separate. Required Qualifications likely go under Requirements. Preferred Qualifications maybe under Qualifications. Desired Attributes maybe under Skills. Thus:

    Requirements

    with
    of Required Qualifications.

    Qualifications

    with
    of Preferred Qualifications.

    Skills

    with
    of Desired Attributes (maybe also include programming skills etc but those are in qualifications). We'll put Desired Attributes. - Benefits: we have "Your Total Rewards" paragraph. We'll put under

    Benefits

    with

    that paragraph. - Duration: maybe not a standard heading but could be considered Schedule? Not exactly. The posting includes Duration: one to three years subject to annual review. That's like schedule/term. Could be placed under Schedule? But schedule usually refers to work schedule (full-time, part-time). Not present. Duration is more like term. Could we create a Schedule section? The rule says only create Schedule if posting actually states them. It does state duration, but not schedule. Might be better to omit Schedule. - Work Location: not a standard heading; could be omitted. - Relocation Options: could be part of Benefits? Might be separate but we can include in Benefits paragraph. We need to preserve all substantive information. So we need to include the duration and work location somewhere. If we don't have a heading for them, we could include them in a

    under About the Role or maybe a separate

    after sections. The instruction says we should not invent headings; we can just include prose paragraphs without headings? The instruction says use

    for section headings (list). It doesn't forbid other headings, but we should follow the pattern. Probably we can include a

    for location and duration after the sections. But we need to preserve all substantive information: About Us, Why Join ExxonMobil maybe not needed as they are generic. The instruction says remove boilerplate like About Us? It's not explicitly boilerplate but could be considered generic. However it's substantive about company vision. Might be okay to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not those. But we already have About The Role; maybe we can keep About Us as a separate section? Not in allowed headings. Could we treat it as

    without heading? Probably okay. But to be safe, we can include About Us as a

    before the sections. Let's extract the About Us paragraph: "At ExxonMobil, our vision is to lead in energy innovations that advance modern living while reducing emissions. As one of the world’s largest publicly traded energy and chemical companies, we are powered by a unique and diverse workforce fueled by the pride in what we do and what we stand for. The success of our Upstream, Product Solutions and Low Carbon Solutions businesses is the result of the talent, curiosity and drive of our people. They bring solutions every day to optimize our strategy in energy, chemicals, lubricants and lower-emissions technologies. We invite you to bring your ideas to ExxonMobil to help create sustainable solutions that improve quality of life and meet society’s evolving needs. Learn more about our What and our Why and how we can work together." We'll keep that as a

    . Why Join ExxonMobil? paragraph: "At ExxonMobil, we apply advanced optimization and machine learning techniques to solve some of the most challenging problems in energy, manufacturing, and low-carbon technologies. In this role, you will work on cutting-edge methods at the intersection of OR and AI, directly impacting critical business decisions and shaping next-generation computational decision-support capabilities." That's also relevant to role; we could incorporate into About The Role or keep separate. But we already have About The Role; maybe we can merge. However we must preserve all substantive information; we can include it as part of About The Role paragraph. Thus About The Role section will combine the About The Role paragraph and the Why Join ExxonMobil paragraph. Now let's list the content. About The Role paragraph(s): From posting: "About The Role ExxonMobil is seeking a highly motivated Postdoctoral Researcher specializing in Explainable Artificial Intelligence (XAI) for large-scale 3D data analysis. The successful candidate will develop interpretable machine learning methods for segmentation, classification, and anomaly detection in high-dimensional volumetric datasets to support critical business and engineering decisions. This role is ideal for a recent Ph.D. graduate with expertise in XAI and deep learning applied to complex spatial data. The candidate will work closely with domain experts to create transparent, trustworthy AI systems that provide actionable insights for high-stakes applications." Why Join ExxonMobil paragraph: "At ExxonMobil, we apply advanced optimization and machine learning techniques to solve some of the most challenging problems in energy, manufacturing, and low-carbon technologies. In this role, you will work on cutting-edge methods at the intersection of OR and AI, directly impacting critical business decisions and shaping next-generation computational decision-support capabilities." Combine them. Now Responsibilities list: The posting has "Key Responsibilities" repeated twice; we need to list each bullet. List: - Develop explainable AI methods for deep learning models applied to 3D volumetric data. - Design and implement models for segmentation, classification, and anomaly detection in large-scale datasets. - Create techniques to improve model interpretability, transparency, and trustworthiness, including post hoc explanation and inherently interpretable approaches. - Develop uncertainty-aware predictions to support decision-making in critical applications. - Optimize models for scalability and performance on large 3D datasets. - Evaluate models using both predictive accuracy and explainability metrics relevant to domain needs. - Collaborate with domain experts to translate model outputs into decision-support tools. - Implement workflows using modern ML frameworks and reproducible software practices. - Communicate findings through technical reports, journal publications, and conference presentations. Also there is "Example Research & Application Areas" list; that seems like additional info but not responsibilities. Should we include? It's substantive; maybe we could include under Responsibilities or a separate section like "Research Areas". But not in allowed headings. Could we add a

    describing those? The instruction says preserve ALL substantive information. So we need to include that list somewhere. Could be under Responsibilities as additional bullet points? But they are example areas, not responsibilities. Could create a section like "Research Areas" but not allowed heading. However we could include them as a

    paragraph describing them. But we need to preserve the list items. Could we put them under Responsibilities as extra bullets? Might be misleading but still preserves info. Better to create a separate section with heading maybe "Research Areas" but not in allowed list; but the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. However we could still include other headings but risk violating. Safer to stick to allowed headings. Where to put Example Research & Application Areas? Could be part of About The Role or Responsibilities as a note. We'll add a

    after Responsibilities describing those areas. Now Required Qualifications list: - Ph.D. in Computer Science, Artificial Intelligence, Machine Learning, Computational Science, or a closely related field, with a focus on explainable AI or interpretable machine learning. - Demonstrated research experience in explainable AI and deep learning, including one or more of: - Model interpretability (e.g., saliency methods, attribution, feature importance) - Explainability techniques for neural networks - Interpretable model design - Experience with 3D data (e.g., volumetric imaging, point clouds, or spatiotemporal data) and deep learning methods such as CNNs, transformers, or graph neural networks. - Proven experience in segmentation, classification, or anomaly detection tasks. - Strong programming skills in Python. - Hands-on experience with machine learning frameworks such as PyTorch or TensorFlow. - Strong analytical, problem-solving, and communication skills. - Ability to work effectively in multidisciplinary teams. Note: The bullet with sub-bullets; we need to preserve. We'll flatten? Could keep sub-bullets as nested

    . That's okay. Preferred Qualifications list: - Experience with XAI methods for computer vision or 3D data. - Familiarity with uncertainty quantification, probabilistic ML, or Bayesian deep learning. - Experience with large-scale data processing and GPU-accelerated training. - Knowledge of evaluation metrics for explainability and model trustworthiness. - Experience applying AI to engineering, geospatial, industrial, or scientific datasets. - Strong publication record in XAI, machine learning, or computer vision. - Demonstrated ability to translate research into decision-support applications. Desired Attributes list: - Passion for developing trustworthy and interpretable AI systems. - Interest in solving high-impact, real-world problems involving complex data. - Ability to bridge machine learning methods with practical decision-making needs. - Collaborative mindset and strong communication