We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, diversity, application instructions, etc. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Job Title: Web Application Developer (but not used as heading)
- Supervisor: Ocean Data Products (ODP) Program Director
- Starting Salary Range: $75,000-$79,399
- Overview: description of GMRI, ODP team role, projects.
- Web Developer I description: early career web developer, full-time regular position based on-site in Portland, ME with flexibility around hybrid work, reports to ODP Program Director. Aimed toward early career candidates with growing skills in back-end development, data acquisition and integration, or DevOps. Provide ongoing support and contribute to development of suite of web-based software and tools used by stakeholders to access data and information about marine environment. Work closely with ODP program director, ODP programmers, research scientists, stakeholders, designers to support and maintain these systems. Collaborate with internal partners at GMRI and external clients in ocean observing, marine science, fisheries communities, other stakeholders interested in marine data.
- Ideal candidate: demonstrated knowledge and capacity to program web applications using industry standard programming languages, open source preferred. Outstanding problem-solver with excellent coding skills, ability to understand and work within variety of software technologies, capacity to keep up to speed on industry trends and adapt to new technologies.
- Requirements: Required Qualifications list (bulleted). Let's extract each line:
- A bachelor’s degree in computer science, web development or related field, or 3 to 5 years of equivalent education and experience
- 3+ years direct experience developing consumer-facing web applications.
- Proficiency developing in web application frameworks and environments (preferred: Django, Node.js)
- Experience developing and supporting content management frameworks (e.g., Python, Django, Wagtail, CKAN)
- Proficiency with client and server-side programming languages (preferred: Python, JavaScript, Typescript, Node.js, React)
- Experience supporting front end website development, including proficient knowledge and experience with web markup, including HTML5 and CSS
- Experience with relational and non-relational databases (preferred: PostgreSQL, MySQL)
- Demonstrated knowledge of web-oriented data formats (XML, JSON)
- Proficiency developing and implementing REST-based web services and APIs
- Demonstrated knowledge of repository-based development, preferably GitHub
- Familiarity with object-oriented programming concepts and their applications
- Demonstrated ability translating functional requirements into technical specifications and infrastructure requirements
- Proficiency in managing application environments with cloud hosting providers
- Well-developed written and verbal communication skills
- Ability to thrive on a team that manages multiple projects with fixed deadlines
- Other Preferred Qualifications (list):
- Integration of data from sensors and large, unstructured time series and gridded data sets (satellite, buoys, models) and data formats (e.g. NetCDF, xarray, Zarr)
- Scientific data management systems (ERDDAP/THREDDS)
- Developing mobile/touch responsive or platform-specific applications
- Provide basic system administration for multiple servers and technologies
- GIS and mapping software (OpenLayers, ESRI, Google Maps, Leaflet, Mapbox, or similar)
- Advanced front-end visualization libraries and tools (HighCharts, D3, or similar)
- Cloud storage services (Amazon S3, Digital Ocean)
- Container application platforms (Docker, Kubernetes)
- Workflow orchestration tools (e.g., Dagster, Prefect)
- Authentication services
- Development in cloud compute environments (AWS or equivalent)
- An academic background or previous work experience with marine science, fisheries, climate, or environmental issues
- Desire to work for a mission-driven non-profit
- Diversity And Inclusion: boilerplate, remove.
- Salary And Benefits: "Gulf of Maine Research Institute offers a competitive salary and benefits package." This is vague; we need to include Benefits and Pay sections only if posting actually states them. It says competitive salary and benefits package but no specifics besides salary range earlier. We have Starting Salary Range: $75,000-$79,399. That is specific pay info. So we can include Pay section with that range. Benefits: only statement "competitive salary and benefits package" no specifics; we should not create Benefits section unless specific benefits listed. Since not specific, we should omit Benefits section. Schedule: mention full-time regular position based on-site in Portland, ME with flexibility around hybrid work. That's schedule info: full-time, on-site with hybrid flexibility. So we can include Schedule section.
- About the role: we can use Overview and description of role. Could be About the role section.
- Responsibilities: we have description of what Web Developer I will do: provide ongoing support, contribute to development, work closely with team, collaborate with internal/external, etc. That's responsibilities.
- Requirements: we have Required Qualifications list.
- Qualifications: maybe we separate Required vs Preferred? But we have only Qualifications heading allowed. Could combine required and preferred? But we should not create thin sections. We could have Requirements section for required qualifications, and Qualifications section for preferred qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications. We'll put required qualifications under Requirements, and preferred qualifications under Qualifications.
- Skills: maybe we can extract skills from requirements (proficiency in languages, frameworks, etc.) but that overlaps. Could create Skills section summarizing technical skills. However we must not create thin sections; we need substantive content. We could put skills under Requirements or Qualifications. But we have both headings allowed; we could put technical skills under Skills, and educational/experience under Requirements. However the posting already lists qualifications that include skills. Might be okay to split.
But we must not invent or summarize away detail. We need to preserve ALL substantive information. If we split, we must ensure we don't lose any detail. We could put all qualification details under Requirements and leave Qualifications empty (but we cannot emit empty heading). So we need to decide.
Better: Use Requirements for the required qualifications list. Use Qualifications for the preferred qualifications list. Use Skills maybe not needed; we could omit Skills section if no specific skills beyond those already captured. But we could put some skills like "proficiency in Python, JavaScript, Typescript, Node.js, React; experience with Django; HTML5/CSS; REST APIs; GitHub; OOP; cloud hosting; databases; etc." That is essentially same as required qualifications. Might be redundant.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements, Pay, Schedule. Omit Qualifications, Skills, Benefits. But we have preferred qualifications that are substantive; we could include them under Requirements as "Preferred Qualifications" sublist? But the heading Requirements is for required qualifications; we could still include preferred under same heading but label them. However that might mix required and preferred. But we can still include them under Requirements as a separate subsection. The instruction didn't forbid mixing; just said use headings for sections. It didn't say we cannot have subheadings. But we should avoid creating thin sections. So we could have Requirements section containing both required and preferred qualifications, maybe with subheadings
Required and
Preferred. That preserves all info.
Thus sections: About the role, Responsibilities, Requirements, Pay, Schedule.
Now we need to format:
-
About the role
then
with overview text (GMRI mission, ODP role, projects, Web Developer I description). Must not repeat job title.
-
Responsibilities
then
- items for responsibilities: provide ongoing support and contribute to development of suite of web-based software and tools; work closely with ODP program director, ODP programmers, research scientists, stakeholders, designers to support and maintain these systems; collaborate with internal partners at GMRI as well as external clients in ocean observing, marine science, fisheries communities, and other stakeholders interested in marine data. Possibly also "aimed toward candidates early in their career with growing skills..." but that's more about candidate. Responsibilities: we can list those.
-
Requirements
then maybe with intro then
- for required qualifications and another
for preferred? Could do two lists: one for Required Qualifications, one for Preferred Qualifications. But that might be thin? However each list is substantive. We'll do:
Required Qualifications:
Preferred Qualifications:
That preserves all.
- Pay
then Starting Salary Range: $75,000-$79,399.
-
Schedule
then Full-time regular position based on-site in Portland, ME with flexibility around hybrid work.
We must not include boilerplate like EEO, diversity, application instructions, etc.
Check for any other substantive info: Supervisor: Ocean Data Products (ODP) Program Director. Could be included in About the role or Responsibilities? Might be worth including in About the role as "Reports to the ODP Program Director." We'll include that.
Also mention "Web Developer I position is a full-time regular position based on-site in Portland, ME with flexibility around hybrid work and reports to the ODP Program Director." That's schedule and supervisor.
We already have schedule; we can mention supervisor in About the role.
Now ensure we preserve all substantive info: overview of GMRI, ODP role, projects list, etc. Let's capture:
Overview: "The Gulf of Maine Research Institute (GMRI) develops and delivers collaborative solutions to global ocean challenges. We are dedicated to the resilience of the Gulf of Maine ecosystem and the communities that depend on it. To learn more, visit gmri.org."
Then ODP description: "The primary role of the Ocean Data Products team at GMRI is to develop and support data management and cyberinfrastructure (DMAC) systems that provide access to real-time, historic, and forecast data in the northeast region through customized data products. ODP has served as the lead data management provider for NERACOOS (the Northeastern Regional Association for Coastal and Ocean Observing Systems) since the early 2000s. Additionally, ODP works with partners at GMRI and collaborators in the region developing products and data management infrastructure for fisheries, climate, and marine environmental data. Current projects include development of an infrastructure for meteorological and oceanographic data from offshore buoys and sensors, web based tools and dashboards for accessing water level data and model forecast visualizations, GMRI’s public-facing community science platform, and a data infrastructure for GMRI research data."
Then Web Developer I description: "The ODP team is looking an early career web developer to join the team. The Web Developer I position is a full-time regular position based on-site in Portland, ME with flexibility around hybrid work and reports to the ODP Program Director. The position is aimed toward candidates early in their career with growing skills and interest in one or more areas of specialization that will complement the skills of the current team, such as: back-end development, data acquisition and integration, or DevOps. The Web Developer I will provide ongoing support and contribute to the development of the suite of web-based software and tools used by stakeholders to access data and information about the marine environment. The Web Developer I will work closely with the ODP program director, ODP programmers, research scientists, stakeholders, and designers to support and maintain these systems. The person in this role will collaborate with internal partners at GMRI as well as external clients in the ocean observing