Java Developer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. No placeholder like "commensurate with experience". No Pay/Schedule/Benefits unless posting actually states them. The posting includes location, remote, role overview, responsibilities, required qualifications, additional qualifications, preferred qualifications, minimum physical job requirements, reporting structure, company description, benefits overview. No explicit pay or schedule details (though mentions flexible schedule, weekends, shifts outside core business hours, travel up to 5%). That's schedule info: "Ability to work a flexible schedule including weekends and shifts outside of core business hours as needed for technical support and/or project needs." That's schedule info. So we can include a Schedule section with that content. Benefits: they have a benefits overview. So we can include Benefits section summarizing benefits. Pay: not mentioned, so omit Pay section.
We must not repeat job title as heading. Use for each section heading.
We need to preserve all substantive info, not invent or summarize away detail. Must not omit details. Must include all content except boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove duplicated EEO statements. Also remove virtual recruiter instructions, privacy policy links, etc. Also remove "Everforth Apex Benefits Overview:" maybe keep benefits content but not the heading? We'll include Benefits section with the benefits details.
We need to include location and remote? Possibly in About the role section.
We need to include Job#? Probably minor metadata, can be folded into short
or drop. We can include a short paragraph with Job# and Location. Let's parse content: Job#: 3053189 Job Description: Java Developer Location: Eagan, Minnesota (Remote) Role Overview: This position supports the FirstIQ product within the Clinical Care Programs block. This role is responsible for designing technology solutions to ensure they meet all resiliency, stability, non-functional, functional, and operational readiness use cases. The software engineer will own the technology solutions within their area, including proactive monitoring and alerting, the technological roadmap, and communication of overall health and future sustainability. This is a business-critical and highly visible effort, requiring strong collaboration across product, business, and technology teams. Key Responsibilities: list bullet points. Required Qualifications: Education, Experience, Technical Skills, Other (must be eligible to work in US without visa). Additional Qualifications: list of abilities. Preferred Qualifications: list. Minimum Physical Job Requirements: list. Reporting Structure: This role reports to a Team Lead and a Manager in the Information Technology department. Company description: Everforth Apex is a world-class IT services company... (including awards, virtual recruiter, etc). We need to remove boilerplate like virtual recruiter details, EEO, etc. But we can keep a brief description of company? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description may be considered not boilerplate but maybe part of job posting. It's not explicitly prohibited. However, it includes some promotional text that may be okay to keep. But we should remove duplicated EEO statements and virtual recruiter instructions, privacy policy, etc. Also remove the "Everforth Apex Benefits Overview:" heading maybe but keep benefits list. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the benefits details as given. We must not include application instructions like "Click here for more details", "By applying for this job, you agree to receive calls..." etc. Those are application instructions; remove them. Also remove the "Everforth Apex Systems is an equal opportunity employer..." repeated. Also remove the "UnitedHealthcare creates and publishes the Transparency in Coverage Machine-Readable Files..." etc. Also remove the address and NYSE ticker maybe? That's not boilerplate but maybe considered metadata; could be kept? It's not explicitly prohibited. However, it's not part of job description; could be considered boilerplate? It's company info. Might be okay to keep but it's not essential. Safer to omit? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The address and ticker are not those categories. Might be okay to keep but could be considered not substantive for the job. However, we need to preserve ALL substantive information; the address is not substantive to the job. Might be considered extra. I'd drop it to keep concise. We need to output only HTML fragment, no /, no markdown. We'll structure:
Job#: 3053189 – Location: Eagan, Minnesota (Remote)
About the role
... role overview ...
Responsibilities
- ... ...
Requirements
maybe combine Education, Experience, Technical Skills, Other? Or we could have Qualifications section. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have Required Qualifications (Education, Experience, Technical Skills, Other). Additional Qualifications (soft skills). Preferred Qualifications (extra). Minimum Physical Job Requirements (maybe under Requirements? Could be separate but we don't have a heading for physical requirements; we could include under Requirements or maybe under Qualifications? The instruction says we can include sections only when posting has real specific content. We have content for Requirements (education, experience, technical skills, eligibility). We have content for Qualifications (additional qualifications). We have content for Skills (maybe technical skills already covered). But we could combine. Better to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. We'll put: - Requirements: Education, Experience, Technical Skills, Other (US work eligibility). - Qualifications: Additional Qualifications (list of abilities) + Preferred Qualifications (list) maybe combined. - Skills: maybe we already covered technical skills under Requirements; but we could still have Skills heading for any remaining skills like "Ability to transition abstract concepts..." but those are more qualifications. Could omit Skills if no distinct content. But we have technical skills already in Requirements; we could still have Skills heading for any other skills like "Experience with AWS, AWS-lambda, Java, Springboot, SQL, JSF or any UI experience, and Github Copilot". That's technical skills. So we could put that under Skills. Then Requirements could be Education and Experience and Other (US eligibility). Let's decide. We need to avoid duplication. Let's parse: Required Qualifications: Education: Bachelor's degree in Computer Science or related, or equivalent combination; High School Diploma or GED also required. Experience: 7-10 years experience with application development or package software implementation; previous experience working in Agile/Product Delivery model necessary. Technical Skills: Experience with AWS, AWS-lambda, Java, Springboot, SQL, JSF or any UI experience, and Github Copilot needed. Other: Must be eligible to work in US without need for work visa or residency sponsorship. Additional Qualifications: list of soft skills. Preferred Qualifications: list. Minimum Physical Job Requirements: list. Thus we can map: Requirements heading: Education, Experience, Other (US eligibility). (Technical skills maybe under Skills.) Skills heading: Technical Skills (AWS, etc.) Qualifications heading: Additional Qualifications + Preferred Qualifications (maybe combine). Schedule heading: flexible schedule info. Benefits heading: benefits overview. We must not include Pay. Now we need to ensure we preserve all substantive info: include all bullet points from responsibilities, additional qualifications, preferred qualifications, physical job requirements, reporting structure, company description? The company description may be considered substantive but not under any heading; we could put it under About the role maybe after role overview. But we already have role overview paragraph. The company description includes awards, virtual recruiter, etc. Some of that is boilerplate (virtual recruiter, EEO). We should remove those. Keep the description of Everforth Apex as a world-class IT services company that serves thousands of clients, values innovation, collaboration, continuous learning, offers quality career resources, training, certifications, development opportunities, comprehensive benefits package, commitment to excellence reflected in awards (ClearlyRateds Best of Staffing® in Talent Satisfaction in US and Great Place to Work® in UK and Mexico). That's substantive. We can keep that but remove the virtual recruiter details, EEO, etc. Also remove the "Everforth Apex uses a virtual recruiter as part of the application process. Click here for more details." That's application instruction. Remove. Also remove the "By applying for this job, you agree to receive calls..." etc. Also remove the privacy policy link. Also remove the benefits overview heading maybe but keep benefits list. Also remove the duplicated EEO statements. Also remove the address and NYSE ticker. Also remove the "Everforth Apex Systems is an equal opportunity employer..." repeated. Also remove the "UnitedHealthcare creates and publishes the Transparency in Coverage Machine-Readable Files..." etc. Now we need to output HTML. Let's craft:Job#: 3053189 – Location: Eagan, Minnesota (Remote)
About the role
This position supports the FirstIQ product within the Clinical Care Programs block. This role is responsible for designing technology solutions to ensure they meet all resiliency, stability, non-functional, functional, and operational readiness use cases. The software engineer will own the technology solutions within their area, including proactive monitoring and alerting, the technological roadmap, and communication of overall health and future sustainability. This is a business-critical and highly visible effort, requiring strong collaboration across product, business, and technology teams.
Everforth Apex is a world-class IT services company that serves thousands of clients across the globe. When you join Everforth Apex, you become part of a team that values innovation, collaboration, and continuous learning. We offer quality career resources, training, certifications, development opportunities, and a comprehensive benefits package. Our commitment to excellence is reflected in many awards, including ClearlyRateds Best of Staffing® in Talent Satisfaction in the United States and Great Place to Work® in the United Kingdom and Mexico.
Responsibilities
- Lead design to ensure technology solutions meet all resiliency, stability, and readiness use cases.
- Lead ongoing development, maintenance, and support of existing systems and platforms.
- Manage work direction, lead, influence, and provide feedback to other team members.
- Participate in staffing plans to identify subject matter experts and provide feedback for staff performance reviews.
- Own technology solutions, including proactive monitoring, alerting, and the technological roadmap.
- Drive innovation and continuous improvement.
- Define requirements, map workflows, and drive large-scale implementation efforts.
- Other duties as assigned.
Requirements
- Education: A Bachelor's degree in Computer Science or a related area of study, or an equivalent combination of education and/or relevant work experience is required. A High School Diploma or GED equivalent is also required.
- Experience: 7-10 years of experience with application development or package software implementation is required. Previous experience working in an Agile/Product Delivery model is also necessary.
- Other: Must be eligible to work in the United States without need for work visa or residency sponsorship.
Skills
- Experience with AWS, AWS-lambda, Java, Springboot, SQL, JSF or any UI experience, and Github Copilot is needed.
Qualifications
Additional Qualifications