Enterprise - Full Stack Developer - Java, Apache, Linux

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, referral, etc? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO paragraph, referral & inquiries, etc. Also remove "At Erias Ventures, we are dedicated to fostering a diverse and inclusive workplace..." that's EEO. Also remove "Referrals & Inquiries ..." and "Please Send Referrals..." etc. Also remove "To learn more about our company visit our webpage or LinkedIn." Also remove "Clearance" maybe part of Requirements? It's a requirement: clearance needed. Should be included under Requirements or Qualifications. We'll decide. We need sections: About the role (maybe from first paragraph describing company and role). Responsibilities (description of work). Requirements (education, experience, clearance). Qualifications maybe similar to Requirements? Could combine. But we need to follow instruction: use headings only when posting has real specific content. We can have About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly Qualifications separate if distinct. Let's parse. Original text: "Erias Ventures was founded to serve its customers with an entrepreneurial mindset. We value creative problem-solving, open communication, and empowering our employees to make decisions and put forth new ideas. Our staff includes technical experts working across multiple disciplines, bringing diverse perspectives to every project. We are seeking engineers who wish to grow their careers and want to become part of a technically strong and growth-oriented company focused on bringing innovative solutions to the difficult mission problems facing our customers." That's about company and role. Could be About the role. "Description We are seeking a Full Stack Developer to support sustainment efforts. Support will focus on development and sustainment of key reporting tools tools. Efforts will include creating enhancements based on high-priority mission needs, as well as maintenance/sustainment of the existing code base." That's responsibilities. "Clearance A current Top-Secret/SCI with polygraph security clearance is required. Candidates cannot be sponsored or nominated for a government security clearance under this position." That's a requirement. "Experience Bachelor’s degree in computer science or related discipline or four additional years’ software engineering experience. Master's degree can be substituted for two (2) years' experience." That's qualification/experience. "Required Skills Java 8+C/C++Scripting (python, bash, php)Apache TomcatElasticsearchOracleSpring BootRESTful web servicesSolrComfortable working in a Linux environmentUnderstanding, maintaining, and troubleshooting interfaces between multiple applications" That's required skills. "Desired Skills Amazon Web Services (AWS)PrimefacesQuarkusNode.jsLex/YaccBasic sysadmin skills (managing cron jobs, selinux, etc.)Agency reporting and dissemination toolsAgency classification policiesWorking in an agile environment using JIRA and Confluence" That's desired skills (could be under Skills as well). "Benefits Erias Ventures provides a complete package of wealth, health, and happiness benefits. The expected salary range for this position, depending on education and years of experience is $185,000 - $275,000." Then list of benefits. We need to separate Pay and Benefits sections if salary is given. Pay section: salary range. Benefits: list of wealth, health, happiness benefits. Schedule: not mentioned, so omit. We must not include placeholder like "commensurate with experience". Not present. We need to output HTML fragment only. Structure:

About the role

... (company description)

Responsibilities

• ... maybe multiple items? The description is a sentence; we could put as

  or

• . Since it's a list of duties, we can use
  • for each duty. There's only one duty sentence: "Support will focus on development and sustainment of key reporting tools. Efforts will include creating enhancements based on high-priority mission needs, as well as maintenance/sustainment of the existing code base." Could split into two li: development and sustainment of key reporting tools; creating enhancements based on high-priority mission needs; maintenance/sustainment of existing code base. But we must preserve all info, not invent. Splitting may be okay as it's still same info. Safer to put as

    maybe. The instruction: Use

    • for any list of duties/requirements/benefits. If we have a list, we should use ul. The responsibilities could be considered a list: we can break into bullet points based on the sentences. Let's do: - Support will focus on development and sustainment of key reporting tools. - Efforts will include creating enhancements based on high-priority mission needs. - Maintenance/sustainment of the existing code base. That's accurate.

      Requirements

      Maybe include clearance and experience? Could separate Requirements (clearance) and Qualifications (education/experience). But we can combine under Requirements. However we have also Required Skills and Desired Skills. Could have Skills section. Let's decide sections: - About the role - Responsibilities - Requirements (clearance, education/experience) - Skills (required and desired) - Benefits - Pay We must not repeat job title. Use

      for each. Now content: About the role paragraph: combine first paragraph plus maybe the sentence "We are seeking engineers who wish to grow their careers and want to become part of a technically strong and growth-oriented company focused on bringing innovative solutions to the difficult mission problems facing our customers." That's part of about. We'll put:

      Erias Ventures was founded to serve its customers with an entrepreneurial mindset. We value creative problem-solving, open communication, and empowering our employees to make decisions and put forth new ideas. Our staff includes technical experts working across multiple disciplines, bringing diverse perspectives to every project. We are seeking engineers who wish to grow their careers and want to become part of a technically strong and growth-oriented company focused on bringing innovative solutions to the difficult mission problems facing our customers.

      Responsibilities: as above. Requirements: include clearance and education/experience. We need to preserve all info: clearance statement, experience statement. We can format as

      • for each requirement. - A current Top-Secret/SCI with polygraph security clearance is required. Candidates cannot be sponsored or nominated for a government security clearance under this position. - Bachelor’s degree in computer science or related discipline or four additional years’ software engineering experience. Master's degree can be substituted for two (2) years' experience. That's fine. Skills: required and desired. Could separate Required Skills and Desired Skills as subheadings? But we only have h3 headings allowed; we could have a Skills section with two lists: Required Skills and Desired Skills as

        ? Not allowed. Could just combine into one list but we need to preserve distinction. Could have two

        sections: Required Skills and Desired Skills. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists Skills as a possible heading. It doesn't forbid having multiple skill headings. But we should only create sections when posting has real specific content. We have both required and desired skills, so we could have Required Skills and Desired Skills as separate h3 sections. That seems okay. Thus sections: Required Skills, Desired Skills. But we also have Benefits and Pay. Let's list sections: - About the role - Responsibilities - Requirements - Required Skills - Desired Skills - Benefits - Pay Now ensure we don't include Schedule. Now content for Required Skills: list each skill. Original: "Java 8+C/C++Scripting (python, bash, php)Apache TomcatElasticsearchOracleSpring BootRESTful web servicesSolrComfortable working in a Linux environmentUnderstanding, maintaining, and troubleshooting interfaces between multiple applications" We need to parse into items. Could split by commas? The text is messy. Let's extract: Java 8+ C/C++ Scripting (python, bash, php) Apache Tomcat Elasticsearch Oracle Spring Boot RESTful web services Solr Comfortable working in a Linux environment Understanding, maintaining, and troubleshooting interfaces between multiple applications We'll make each a

        . Desired Skills: "Amazon Web Services (AWS)PrimefacesQuarkusNode.jsLex/YaccBasic sysadmin skills (managing cron jobs, selinux, etc.)Agency reporting and dissemination toolsAgency classification policiesWorking in an agile environment using JIRA and Confluence" Parse: - Amazon Web Services (AWS) - Primefaces - Quarkus - Node.js - Lex/Yacc - Basic sysadmin skills (managing cron jobs, selinux, etc.) - Agency reporting and dissemination tools - Agency classification policies - Working in an agile environment using JIRA and Confluence Now Benefits: The paragraph: "Erias Ventures provides a complete package of wealth, health, and happiness benefits." Then list: Wealth Benefits: - Above Market Hourly Pay - 11% Roth or Traditional 401k with Immediate Vesting and Deposit - Spot Bonuses for Assisting with Business Development and Company Growth - Professional Development Bonuses for Certificates and Degrees Health Benefits: - Company subsidized Medical Coverage - 100% Company Paid Vision and Dental Coverage - 100% Company Paid Long Term Disability, Short Term Disability, and Group Life Insurance - Monthly Wellness Reimbursement Happiness Benefits: - Paid Time Off with Flexible Work Schedules and Birthday Off - Amazon Prime Membership and Monthly Internet Reimbursement - Technology and Productivity Allowance for Equipment and Supplies - Morale Building and Company Events to Celebrate our Successes and Build our Community - Onboarding and Annual Swag - Company Paid Professional Development and Training We need to preserve all. Use

        • for each benefit category? Could have subheadings but not allowed. Could just list all benefits as a flat list. But we need to preserve categorization? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we flatten, we still preserve all items, just lose category headings. That's okay as long as we don't lose info. However category headings are part of the posting; they are substantive? They are headings within benefits. Might be considered part of the content. Safer to preserve them as maybe or just include them as part of list items? Could include them as
        • with the category name then sublist? But we cannot use nested headings. We could use
        • Wealth Benefits: then a
          inside? That's nested list, still allowed? The instruction only says use
          • for any list of duties/requirements/benefits. It doesn't forbid nested lists. But to keep simple, we can just list all benefits as items, preserving the text exactly as they appear, maybe preceded by the category as part of the item. Eg: "
          • Wealth Benefits: Above Market Hourly Pay
          " but that changes wording. Better to keep category as separate
          • like "
          • Wealth Benefits
          " then subitems? That adds extra items not originally there (the category headings). Might be considered adding detail? It's actually present in the posting as headings; we could treat them as list items. That's preserving them. However the instruction: "Use
          • for any list of duties/requirements/benefits". If we treat category headings as list items, they'd