Young Investigator, Climate Modeling

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. We have content: "Persons in these roles are expected to work from our offices in Seattle. On-site requirements vary based on position and team. If you have questions about on-site work arrangements for this role, please ask your recruiter." That's about location/on-site. Could be "Schedule"? Not exactly schedule. Could be "Work Arrangements". But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content to these. We have compensation: "$159,650.00". That's Pay. So we can create Pay section with that amount. We have "Who You Are:" description: "We seek a Young Investigator for a new three-year project to develop an AI-powered physics-informed hybrid climate model trained on historical data that is capable of multidecadal forecasts that are more accurate than the current state of the art. We're looking for someone with experience in AI and earth science who is excited to push the frontier in climate model development. Note: This position has a three year term." That's about role description. Could be "About the role". We have "Who We Are:" description about Ai2's Climate Modeling team. Could be part of About the role or maybe "About the team". But we only have allowed headings; we could incorporate into About the role. We have "Your Next Challenge:" description of tasks. That's responsibilities. We have "You'll get to work on:" bullet list: "Select, design and evaluate NeuralGCM+ training and testing cases, using both historical data and customized physics-based climate model outputs. Conceiving and implementing NeuralGCM+ model improvements that increase its generalizability to unseen climates and improve the simulated coupling between earth system components such as the atmosphere, ocean, land, and sea ice, in collaboration with other team members. Presenting results at major relevant AI and climate modeling conferences and in peer-reviewed publications. Open-source code development as part of a tightly connected team, including daily meetings, code review, design documents and interaction with external collaborators. Mentoring interns as appropriate." That's responsibilities. We have "What You'll Need:" bullet list: "You must have substantial experience building and deploying a relevant ML application in a practical or academic research setting and be fluent in Python and collaborative coding practices. You must have a Ph. D. in computer or computational science, applied mathematics/statistics, or atmospheric science or a related geophysical science, with at least one accepted conference paper or peer-reviewed first-authored publication making extensive use of ML. Demonstrated excellent communications skills." That's qualifications/requirements. We have "It's A Bonus If You:" bullet list: "Have formal training and/or practical experience with physically-based atmospheric, oceanic, or related model development. Have experience writing machine learning code in JAX. Have formal graduate-level ML coursework." That's skills (bonus skills). We have "Physical Demands and Work Environment:" description: "The physical demands described here are representative of those that must be met by a team member to successfully perform the essential functions of this position. Reasonable accommodations may be made to enable individuals with disabilities to perform the functions. Must be able to remain in a stationary position for long periods of time. The ability to communicate information and ideas so others will understand. Must be able to exchange accurate information in these situations. The ability to observe details at close range. Can work under deadlines." That's maybe not a standard heading; could be omitted or placed under Requirements? But we can maybe include under Requirements? However we should not create sections not in allowed list unless we have content. But we could incorporate into Requirements as prose. We have "A Little More About Ai2:" description about organization, mission, benefits, etc. That includes benefits details later. We have a Benefits section later: "Benefits: Team members and their families are covered by medical, dental, vision, and an employee assistance program. Team members are able to enroll in our health savings account plan, our healthcare reimbursement arrangement plan, and our health care and dependent care flexible spending account plans. Team members are able to enroll in our company's 401k plan. Team members will receive $125 per month to assist with commuting or internet expenses and will also receive $200 per month for fitness and wellbeing expenses. Team members will also receive up to ten sick days per year, up to seven personal days per year, up to 20 vacation days per year and twelve paid holidays throughout the calendar year. Team members will be able to receive annual bonuses." That's specific benefits. So we should create Benefits section with that content. We have Pay: "$159,650.00". So Pay section. We have schedule? Not explicitly given. There's mention of on-site requirements vary, but not schedule like full-time/part-time. So we should not create Schedule section because no specific schedule content. We have location: "Persons in these roles are expected to work from our offices in Seattle. On-site requirements vary based on position and team. If you have questions about on-site work arrangements for this role, please ask your recruiter." That could be considered under About the role or maybe a separate section like "Work Location". But not in allowed headings. Could incorporate into About the role as prose. We must not include boilerplate like EEO, E-Verify, etc. Remove those. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for section headings. Use

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

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "About the team" but we can merge into About the role. We need to avoid headings with filler text. Ensure each heading has substantive content. Let's extract content precisely. About the role: Could combine "Who You Are:" and "Who We Are:" and location info. But we must not repeat job title. So we can start with

    About the role

    then

    ...

    . We need to include all details from those sections. Let's craft About the role paragraph: "We seek a Young Investigator for a new three-year project to develop an AI-powered physics-informed hybrid climate model trained on historical data that is capable of multidecadal forecasts that are more accurate than the current state of the art. We're looking for someone with experience in AI and earth science who is excited to push the frontier in climate model development. Note: This position has a three year term. Ai2's Climate Modeling team is an international pioneer in using machine learning (ML) methodologies to improve on current physics-based climate models. Our fast, accurate autoregressive open-source emulator, ACE, stably reproduces the climate and weather extremes of an existing climate model or a reanalysis. We have coupled ACE to a ML ocean model, trained it to realistically account for changing CO2 concentrations, and downscaled (super-resolved) ACE outputs from their 100 km native scale to km-scale detail. Our tight-knit team of scientists and software engineers works closely with leading physics-based climate modeling centers to obtain unique training and testing data and get expert feedback on our progress. We collaborate with other leading research groups doing related AI work. Persons in these roles are expected to work from our offices in Seattle. On-site requirements vary based on position and team. If you have questions about on-site work arrangements for this role, please ask your recruiter." That seems to capture all. Now Responsibilities: from "Your Next Challenge:" and "You'll get to work on:" bullet list. We can combine into a
    • list. Responsibilities content: - Physically-based climate models discretize equations representing individual time-evolving processes like clouds, rain, wind, land and sea-ice, and ocean currents on a computational grid. Some processes (e.g. clouds) are less reliably encoded than others (e.g. winds). Hence such climate models have biases in representing present-day climate and produce an undesirably large range of projections of future climate change for a given human-caused change in CO2 or other climate forcings. Current AI-based climate models reduce present-day climate bias, but don't generalize well to future climate change. We are starting a 3-year project funded by google.org to develop an open source 'AI-first' climate model that can demonstrably project future climates more accurately than current physically-based climate models when trained on historical observations by judicious design of the AI to incorporate physical principles that reliably apply in any climate, seen or unseen. The model should be lightweight and easy for an ML-savvy climate scientist to train and deploy. Our starting point is the Google Research NeuralGCM model, a hybrid ML model that uses a conventional discretization of winds encoded in JAX and learns a column-local representation of all other atmospheric and land processes from historical data. Compared to other AI climate models, NeuralGCM uses ML in a conceptually simpler way and shows somewhat better future-climate generalization skill. It is an open-weight model but its training pipeline and documentation need to be adapted for a broader user community. You will join a small team to develop the desired NeuralGCM+ model and foster its uptake by the climate modeling community. This includes coupling it to an ML-based ocean model and designing approaches to demonstrably improve its skill in unseen climates. As a YI, you will lead the design and evaluation of NeuralGCM+ training and testing cases, using both historical data and customized physics-based climate model outputs, and collaborate with other team members on conceiving and implementing NeuralGCM+ model improvements suggested by these cases. You will also have the opportunity to set up and test your own novel applications of NeuralGCM+. Then the bullet list: - Select, design and evaluate NeuralGCM+ training and testing cases, using both historical data and customized physics-based climate model outputs. - Conceiving and implementing NeuralGCM+ model improvements that increase its generalizability to unseen climates and improve the simulated coupling between earth system components such as the atmosphere, ocean, land, and sea ice, in collaboration with other team members. - Presenting results at major relevant AI and climate modeling conferences and in peer-reviewed publications. - Open-source code development as part of a tightly connected team, including daily meetings, code review, design documents and interaction with external collaborators. - Mentoring interns as appropriate. We need to ensure we don't duplicate content. The paragraph before bullet list includes some of those points; but we can keep both as they are substantive. However we might be repeating. But instructions: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep both. We could combine them into a single
      list, but the paragraph before is prose. We'll keep as

      for the paragraph then

      for bullet list. Now Requirements/Qualifications/Skills. We have "What You'll Need:" (requirements) and "It's A Bonus If You:" (bonus skills). Also "Physical Demands and Work Environment:" could be part of Requirements. We need to decide headings: We have allowed headings: Requirements, Qualifications, Skills. Could map: - Requirements: mandatory requirements (What You'll Need:) - Qualifications: