Meteorologist and Data Scientist Developer
Lynker · College Park, MD · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove application instructions (none present). Need to preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: description of role, tasks, context. The first paragraph: "Lynker is seeking a talented Meteorologist and Data Scientist Developer to support a long term contract at the Weather Prediction Center (WPC) and will have direct interaction with scientists within NOAA as well as partners outside of NOAA. This includes NCEP centers, NWS weather forecast offices, NOAA research facilities, academia, and the NWS Science and Operations Officer community. In this capacity the incumbent will work with these partners to develop and implement verification methods to gauge the effectiveness of new forecaster tools applied to operational and experimental forecasts. The work will also strive to build the capacity to enhance impact decision support services (IDSS), effectively building a Weather Ready Nation. The role will also focus on leveraging machine learning techniques to enhance forecasting capabilities. This includes leading projects that apply advanced AI algorithms to predictive modeling. In addition, the incumbent will work to provide enhancements that build upon current forecaster tools as well as work to develop new services and forecaster tools. Promising work will be transitioned to operations. The incumbent will provide training materials on the enhanced forecaster products and tools. The incumbent will specifically employ machine learning models to improve existing tools and pioneer new, data-driven services. Areas of particular need and interest to be addressed include developing forecaster and verification tools for hazardous weather. Additional areas of focus include the use of ensemble model output to aid forecaster generation of probabilistic products. A key focus will be integrating AI and machine learning workflows to optimize the processing of ensemble model output and other complex meteorological datasets. This also entails applying neural networks to enhance high-resolution numerical weather prediction models. The ideal Meteorologist and Data Scientist Developer will be able to identify pertinent datasets (satellite, land use, and meteorological) and develop forecaster tools which may be implemented on web pages or within the forecaster platforms. Assignments are typically received in terms of expected outcomes, and incumbents are expected to act independently to develop methodologies, and to provide sound analyses and recommendations. Assigned projects may include analysis, application development, or other areas specific to the assignment. The ideal candidate will also leverage AI-driven data pipelines to automate the ingestion and preprocessing of vast meteorological datasets."
That's a lot; we can treat as "About the role" prose.
- Responsibilities: list of duties after "Duties of the Meteorologist and Data Scientist Developer will include the following". Then bullet list:
Collaborate with meteorologists at NCEP, NWS field offices, academia, and outside partners to develop forecast tools for short to medium range time frames regarding hazardous weather.
Use scientific and technical meteorological expertise to develop tools for determination of hazard information.
As appropriate, contribute to formal scientific publications, and/or attending off-site conferences, symposia and hazardous-weather-related outreach events.
Collaborate to transition forecaster tools developed at WPC and elsewhere within NOAA into operations at WPC and other NOAA offices.
Develop web applications using modern industry languages and tools such as, GIS, Python, and PHP.
Develop training materials to transition new tools and techniques into operations.
Perform related duties as assigned.
Design and train machine learning models to identify precursors to hazardous weather events.
Implement AI-based anomaly detection systems to identify errors or gaps in real-time forecast data.
We need to put these in
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove application instructions (none present). Need to preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: description of role, tasks, context. The first paragraph: "Lynker is seeking a talented Meteorologist and Data Scientist Developer to support a long term contract at the Weather Prediction Center (WPC) and will have direct interaction with scientists within NOAA as well as partners outside of NOAA. This includes NCEP centers, NWS weather forecast offices, NOAA research facilities, academia, and the NWS Science and Operations Officer community. In this capacity the incumbent will work with these partners to develop and implement verification methods to gauge the effectiveness of new forecaster tools applied to operational and experimental forecasts. The work will also strive to build the capacity to enhance impact decision support services (IDSS), effectively building a Weather Ready Nation. The role will also focus on leveraging machine learning techniques to enhance forecasting capabilities. This includes leading projects that apply advanced AI algorithms to predictive modeling. In addition, the incumbent will work to provide enhancements that build upon current forecaster tools as well as work to develop new services and forecaster tools. Promising work will be transitioned to operations. The incumbent will provide training materials on the enhanced forecaster products and tools. The incumbent will specifically employ machine learning models to improve existing tools and pioneer new, data-driven services. Areas of particular need and interest to be addressed include developing forecaster and verification tools for hazardous weather. Additional areas of focus include the use of ensemble model output to aid forecaster generation of probabilistic products. A key focus will be integrating AI and machine learning workflows to optimize the processing of ensemble model output and other complex meteorological datasets. This also entails applying neural networks to enhance high-resolution numerical weather prediction models. The ideal Meteorologist and Data Scientist Developer will be able to identify pertinent datasets (satellite, land use, and meteorological) and develop forecaster tools which may be implemented on web pages or within the forecaster platforms. Assignments are typically received in terms of expected outcomes, and incumbents are expected to act independently to develop methodologies, and to provide sound analyses and recommendations. Assigned projects may include analysis, application development, or other areas specific to the assignment. The ideal candidate will also leverage AI-driven data pipelines to automate the ingestion and preprocessing of vast meteorological datasets."
That's a lot; we can treat as "About the role" prose.
- Responsibilities: list of duties after "Duties of the Meteorologist and Data Scientist Developer will include the following". Then bullet list:
Collaborate with meteorologists at NCEP, NWS field offices, academia, and outside partners to develop forecast tools for short to medium range time frames regarding hazardous weather.
Use scientific and technical meteorological expertise to develop tools for determination of hazard information.
As appropriate, contribute to formal scientific publications, and/or attending off-site conferences, symposia and hazardous-weather-related outreach events.
Collaborate to transition forecaster tools developed at WPC and elsewhere within NOAA into operations at WPC and other NOAA offices.
Develop web applications using modern industry languages and tools such as, GIS, Python, and PHP.
Develop training materials to transition new tools and techniques into operations.
Perform related duties as assigned.
Design and train machine learning models to identify precursors to hazardous weather events.
Implement AI-based anomaly detection systems to identify errors or gaps in real-time forecast data.
We need to put these in - .
- Requirements: after "The Meteorologist and Data Scientist Developer selected should have the following". Then list:
A degree (e.g. B.S. or B.A.) from an accredited institution in Atmospheric Science, Oceanography, or other Geophysical Sciences, Engineering, Computer Sciences, or Mathematics and have at least 2 years of experience in related areas.
Experience applying artificial intelligence (AI) and machine learning (ML) techniques to analyze and model complex environmental or meteorological datasets.
Experience with software development support in a team environment
Experience with Python and Unix shell scripting within a UNIX/Linux Environment.
Knowledge of deterministic and ensemble prediction system data sets and their application to hazardous weather diagnosis and prediction.
Knowledge of weather forecasting - short to medium range
Ability to organize, plan, and complete projects
Excellent written and oral communication skills for documentation and presentations
Ability to support team initiatives, demonstrate respect for team members, and seek team consensus
These are requirements.
- Qualifications: after "The Ideal Meteorologist and Data Scientist Developer will have the following". Then list:
Experience with development Frameworks for web based map applications ( e.g. ArcGIS, JavaScript, API)
Proficiency in data science frameworks and libraries such as TensorFlow, PyTorch, or Scikit-learn, and experience with deep learning applications in weather prediction.
These could be considered "Skills" or "Qualifications". The instruction says we can have sections like Qualifications, Skills. We need to decide. The posting lumps them as "The Ideal Meteorologist and Data Scientist Developer will have the following". That's more like "Preferred Qualifications" or "Skills". We'll treat as "Qualifications" maybe. But we already have Requirements section. Could also have "Skills" for the frameworks and libraries. Let's decide: Use "Qualifications" for the degree and experience? Actually typical: Requirements = mandatory; Qualifications = preferred. The posting has "selected should have the following" (mandatory) and "Ideal ... will have the following" (preferred). So we can have Requirements (mandatory) and Qualifications (preferred). Good.
- Benefits: after "Lynker's benefits include the following". Then list bullet items:
Comprehensive healthcare for the employee at no monthly cost
Healthcare benefit covers medical, prescription drug, dental, and vision
Personal Time Off (PTO) Policy plus paid holidays
Highly competitive compensation plan regularly calibrated against industry and location benchmarks
401(k) retirement plan with company-matching
Employee Stock Ownership Plan (ESOP) - we're all company owners!
Flexible spending accounts
Employee assistance program (EAP)
Short- and long-term disability insurance
Life and accident insurance
Tuition assistance/Training/Workforce improvement reimbursement per year
Spot bonuses for exceptional performance
Annual Employee Recognition Awards with bonuses
Employee Referral Program
Free centralized, self-directed Learning Management System to learn at your own pace
Personalized career growth plans for every employee
We need to include Benefits section only if posting actually states them. Yes.
- Pay: Not mentioned explicitly. No salary figure. So we should NOT include Pay section.
- Schedule: Not mentioned. So omit.
- About Lynker: there is a paragraph about Lynker after benefits? Actually after benefits there is "About Lynker Lynker is a growing, employee owned business..." That's company description. Could be a section "About the company" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should not include that as a heading. However we could incorporate that info into maybe "About the role"? But it's about the company, not role. 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? It says use those for section headings. Likely we should only use those headings. So we should omit the "About Lynker" paragraph entirely? But we must preserve ALL substantive information; do NOT invent or summarize away detail. However if we omit that paragraph, we lose substantive info about the company. But maybe we can incorporate it into "About the role" as part of context? The instruction says "Prefer a few substantive sections over many thin ones." It didn't say we cannot add other sections, but the examples given are those. It might be okay to add an "About the company" section if we want to preserve info, but the instruction says use those headings for section headings. It might be interpreted that we should use those headings when applicable; but we could also add other headings if needed? Safer to stick to allowed headings and incorporate company info into "About the role" or maybe "Benefits"? But benefits already separate. Could add a short paragraph about Lynker inside "About the role" after the role description. That would preserve info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include the Lynker description somewhere. We can add it as a paragraph within "About the role" section after the role description. That seems acceptable.
Thus final HTML:
About the role
... (role description + Lynker description)
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
- ...
Benefits
- ...
...
Make sure no extra headings like Pay or Schedule.
We need to ensure we don't include boilerplate like EEO, E-Verify, equal opportunity employer, etc. Remove those lines.
Also remove any duplicated lines.
Check the posting for any duplicated lines: Not seeing.
Now craft the HTML.
We need to be careful with punctuation and HTML escaping? Not needed.
Let's compile the role description paragraph.
We'll combine the initial description up to before "Duties of the Meteorologist and Data Scientist Developer will include the following". Also add Lynker description after that.
Role description text (copy):
"Lynker is seeking a talented Meteorologist and Data Scientist Developer to support a long term contract at the Weather Prediction Center (WPC) and will have direct interaction with scientists within NOAA as well as partners outside of NOAA. This includes NCEP centers, NWS weather forecast offices, NOAA research facilities, academia, and the NWS Science and Operations Officer community. In this capacity the incumbent will work with these partners to develop and implement verification methods to gauge the effectiveness of new forecaster tools applied to operational and experimental forecasts. The work will also strive to build the capacity to enhance impact decision support services (IDSS), effectively building a Weather Ready Nation. The role will also focus on leveraging machine learning techniques to enhance forecasting capabilities. This includes leading projects that apply advanced AI algorithms to predictive modeling. In addition, the incumbent will work to provide enhancements that build upon current forecaster tools as well as work to develop new services and forecaster tools. Promising work will be transitioned to operations. The incumbent will provide training materials on the enhanced forecaster products and tools. The incumbent will specifically employ machine learning models to improve existing tools and pioneer new, data-driven services. Areas of particular need and interest to be addressed include developing forecaster and verification tools for hazardous weather. Additional areas of focus include the use of ensemble model output to aid forecaster generation of probabilistic products. A key focus will be integrating AI and machine learning workflows to optimize the processing of ensemble model output and other complex meteorological datasets. This also entails applying neural networks to enhance high-resolution numerical weather prediction models. The ideal Meteorologist and Data Scientist Developer will be able to identify pertinent datasets (satellite, land use, and meteorological) and develop forecaster tools which may be implemented on web pages or within the forecaster platforms. Assignments are typically received in terms of expected outcomes, and incumbents are expected to act independently to develop methodologies, and to provide sound analyses and recommendations. Assigned projects may include analysis, application development, or other areas specific to the assignment. The ideal candidate will also leverage AI-driven data pipelines to automate the ingestion and preprocessing of vast meteorological datasets."
Now Lynker description:
"Lynker is a growing, employee owned business, specializing in professional, scientific and technical
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings? It says use those for section headings. Likely we should only use those headings. So we should omit the "About Lynker" paragraph entirely? But we must preserve ALL substantive information; do NOT invent or summarize away detail. However if we omit that paragraph, we lose substantive info about the company. But maybe we can incorporate it into "About the role" as part of context? The instruction says "Prefer a few substantive sections over many thin ones." It didn't say we cannot add other sections, but the examples given are those. It might be okay to add an "About the company" section if we want to preserve info, but the instruction says use those headings for section headings. It might be interpreted that we should use those headings when applicable; but we could also add other headings if needed? Safer to stick to allowed headings and incorporate company info into "About the role" or maybe "Benefits"? But benefits already separate. Could add a short paragraph about Lynker inside "About the role" after the role description. That would preserve info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include the Lynker description somewhere. We can add it as a paragraph within "About the role" section after the role description. That seems acceptable.
Thus final HTML:
About the role
... (role description + Lynker description)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ...
- ...
Benefits
- ... ...